We are in the process of changing a number of projects from SS2 to ORD. Since there is not a 1 to 1 agreement between the XIN and the Feature Definition dgnlib, there are a lot of features, alignments etc that appear in ORD on the default level. Select by attributes and a Match command that will match Feature Definitions for a selection is MIA.
A suggestion other than picking one feature at a time and changing it and going to the next one will be appreciated.
Importing a DTM, Terrain only works great, but when the Feature option is turned on, everything slows down to a crawl and eventually hangs up on a feature. Other than to open the DTM in SS2 and delete the offending feature, is there a better way to import the information in a DTM? Should I create a 3D plot from the DTM and import each level individually using the either From Elements or Graphical Filter command?
I believe you can create the terrain from the DTM without features, and then use the Graphical Filter command to APPEND the feature elements to that terrain.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Mary: My terrain is very large, so it will be a could of days before I finish. I am trying your suggestion.
David E. Stewart
Calgary, Alberta
ORD 2022R1
Large terrains are never easy, no matter what method I've used for them. It's a lot of data...And I haven't found any way around that yet.
Mary: I found 3 ways that work for now.
1. Start a new drawing with a 3D Seed, attach a 3D model of the ground, (from SS2). Copy the parts of the drawing that you want to create the terrain, create a Selection set, (use Element Selection, select by level) Import Terrain From Elements for each Feature type. The features will not have any symbology. When you want to display the terrain, use the original 3D drawing.
2. Start a new drawing with a 3D seed. Create your terrain, from file, import the spots only, Import your features as in #1.
3. Start a new drawing with a 3D seed. Create your terrain using Survey. (for a surveyed site only)
If you are willing to use a SS2 3D model for the background, at this time, I see no need to change each and every feature symbology as a command to bulk change feature symbologies escapes me.
I prefer each feature having the proper symbology so that a background reference is not required, but for large SS2 DTMs that is a time consuming option.