Just curious if there is a better way to manage this process. Problem is the IRD Converter makes the symbology default white for everything after the conversion.
There are several factors for this, including;
among other things, which begs the question, "What would be the best way to manage this migration process?" The objective is to at least make it appears as we were still in SS2 Roadway Designer, symbolgy wise, for reasons such as earthwork, printing, etc.
I've began working on a "remapper" VBA to take some of the old SS2 stuff and translate to what they should be in ORD. The idea was to build a table with SS2 (old) and ORD (new) objects which I wanted to remap. Starting with remapping template component and point styles, they will be remapped to the new feature definition.
Now the symbology comes in correct using the new remapped IRD after processing the import.
Just curious if I should spend any more time in developing this procedure or is there an IRD Editor I'm missing. Be nice to know if I'm even playing in the same ball park? :)
Hi Derricke, it's no biggie. My thinking is you will always need an IRD importer/converter, whether you are going from SS2 to SS3/SS4 or from SS2 to directly to ORD. Makes no sense to import the IRD from SS2 to SS3/SS4 then convert to file format to ORD again. If you are already working in SS3/SS4 then the discussion of anything related to an IRD is totally moot. We are just discussing the conversion of SS2 IRD to OpenRoads, whether it's SS3, SS4, or ORD CONNECT Edition. I am aware of Bentley's plan to upgrade SS3 and SS4 file format change to ORD, but this is not the purpose of the IRD importer, nor the intended usage of the IRD remapper.
As long as Bentley maintains the statement that, "Everything you can do in SS4, functionality wise, you will be able to do in OpenRoads Designer in the commercial release," then we should not have any issue migrating/converting/remapping our SS2 projects to OpenRoads. The "Import IRD" command is currently located under the Corridors tab in EAP2. If Bentley's plan is to get rid of it for the commercial release, then that will be a major showstopper for us for migrating our existing State SS2 projects to ORD. Please advise if this is the case.
I also understand our situation is sometime unique, but one can find some similarities in the need to remap the IRD. Say you are going from SS2 to SS3 and the name of the SS2 style changed to a new feature definition (such as in our case), or the new feature definitions are now organized into a new folder structure like the EAPs feature definition DGNLIBs (also such as in our case), you will need to remap these IRD objects to retrofit to the new system. Yes, your new feature definition DGNLIBs must be created first to work as intended. I just used what was delivered in EAP2 because I was too lazy and added a couple of feature definitions of my own when there were no corresponding FDs, e.g. Subgrade and Subgrade Daylight.
MS (SELECTseries 2) Ver. 08.11.07.443Geopak Ver. 08.11.07.619