How to edit/create multiple imported alignments with civil geometry then export to ALG PRT SS4

I have been struggling with this all day.

I have to create many different alignments as I am designing a rail yard.

I have the existing rails as an ALG and have imported them using "Import Geometry." From there, I don't know how to edit and save them with civil geometry.

How do I select a particular alignment to edit?

If I create a new "alignment" (drawing elements) with the various tools under horizontal geometry in Microstation, I cannot figure out how to export them as a new horizontal alignment to be used in the InRoads explorer.

How do I tell it that the lines I drew should be an ALG file when I "Export to Native? 

When it's exported, where does it go? I cannot find a new file that is created.

Where do feature definitions come in to this? I have tried to change things to "Auto Save" per some things I've seen online, but how do I tell it to save to (for example) track 2 alignment instead of track 1? 

I have also seen "Auto Persist" come up a lot. Can't even locate that when I make a new feature definition.

Parents
  • It is a bit confusing about intended workflow and actual knowledge of the OpenRoad technology.
    Importing existing rails from ALG: how to edit ?

    1. It is not usual to edit the rails as alignment.
      It can be an issue because existing rails are made of a large number of elements (plan and profile). There is a limitation of number of elements in SS4 and variables to control the limit in the config file to create rules (CIVIL_RELAX_NUMBER_OF_ELEMENTS). And it is sometime not possible to rule the imported alignment, so the alignment can't be edited as Civil Geometry.
    2. When you import Geometry it does create the alignment in the DGN. The data is the DGN
    3. A civil Geometry created using various civil geometry tools can be exported to ALG with the export option beside the import option (export as native)
      Depending how you designed the alignment you may have to "Complex by element" to link all elements
      You must set a feature definition to the complex, with a name. If a profile exists (civil geometry), it must have a name to be exported as native.
    4. Export to native export to the active or named geometry project, Then the geometry project must be saved or saved as ALG.
      The geometry project is named if the civil geometry is initially coming from an ALG.
    5. Feature definitions are a key feature in OpenRoads technology, as styles are in legacy rail track.
      A civil geometry (or feature) must have a feature definition to have a name. A command allows you to set a feature definition to any object.
      Then you can change the name using quick properties or MicroStation properties panel.
    6. You can explore feature definitions using the explorer in the Civil Standard tab
      For linear feature definition you can set parameter Auto Annotate and Auto Export.
      I don't like much Auto Export. I prefer to manage it on demand. It is not recommended to loop between ALG edit and Civil Geometry edit.



Reply
  • It is a bit confusing about intended workflow and actual knowledge of the OpenRoad technology.
    Importing existing rails from ALG: how to edit ?

    1. It is not usual to edit the rails as alignment.
      It can be an issue because existing rails are made of a large number of elements (plan and profile). There is a limitation of number of elements in SS4 and variables to control the limit in the config file to create rules (CIVIL_RELAX_NUMBER_OF_ELEMENTS). And it is sometime not possible to rule the imported alignment, so the alignment can't be edited as Civil Geometry.
    2. When you import Geometry it does create the alignment in the DGN. The data is the DGN
    3. A civil Geometry created using various civil geometry tools can be exported to ALG with the export option beside the import option (export as native)
      Depending how you designed the alignment you may have to "Complex by element" to link all elements
      You must set a feature definition to the complex, with a name. If a profile exists (civil geometry), it must have a name to be exported as native.
    4. Export to native export to the active or named geometry project, Then the geometry project must be saved or saved as ALG.
      The geometry project is named if the civil geometry is initially coming from an ALG.
    5. Feature definitions are a key feature in OpenRoads technology, as styles are in legacy rail track.
      A civil geometry (or feature) must have a feature definition to have a name. A command allows you to set a feature definition to any object.
      Then you can change the name using quick properties or MicroStation properties panel.
    6. You can explore feature definitions using the explorer in the Civil Standard tab
      For linear feature definition you can set parameter Auto Annotate and Auto Export.
      I don't like much Auto Export. I prefer to manage it on demand. It is not recommended to loop between ALG edit and Civil Geometry edit.



Children
No Data