I have been playing around a bit with the Organization-Civil directory structure within OpenRoads Designer (10.05.00.30) and- much like was the case in developing MicroStation Connect edition standards over the last couple of months- the program is starting to have a certain "feel" to me (and congratulations to you Bentley folks for all but completely standardizing the folder structures across the differing new software offerings). The primary step which I am interested in currently is to convert our Company Standard XIN file to a "Features_Annotations_Levels_Elem Temp Imperial.dgnlib" format for use within OpenRoads and tackle those items which may best serve our needs. What is the Current Best Methods Practice for Converting a Power InRoads SS2 XIN to an OpenRoads Designer Element Template Library? Does this latest version of OpenRoads Designer have a converter for us, or will much of the conversion have to take a more "manual" import and export route?
Thanks!
Mark
There are new versions of what are called Migration Utilities delivered with ORD. The default delivery location of their folders are:
C:\ProgramData\Bentley\OpenRoads Designer CE\Configuration\Organization-Civil\Migration Utilities
There are some CFG variables that you need to assign yourself and then, you can even import and export Feature Definitions and Feature Symbologies to and from XML and/or XSLX, in conjunction with one components of the Migration Utilities. One of the other utilities is a XIN to Element Template conversion tool. Like the other, it can work with XML and/or XLSX files. There is a check box to indicate the units used in the XIN that prevents it from progressing until you indicate the units. That one has tripped me up before.
To implement the capabilities that an XIN provided - unique symbologies for various uses (plan, profile, line, point, arc, etc.) they added Feature Symbologies between most Feature Definitions and Element Templates. Also the XIN to Element Template utility also converts Element Template XML files to and from an Element Template Excel file, and in the newer versions of this utility, even the Terrain Element extended Element Template settings are supported.
The learning path link in jpin's reply covers all of this, but a quick summary is always helpful. I just wish they had a manual as well.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Gentlemen:
One of the things I have ran into today was to follow a (Bentley) prescribed method of exporting out styles via the style-manager in SS2. The issue with this method (unlike the videos I have watched) is that I get no menu when right-clicking> Export to XML in the style manager application. I assume that there is a configuration variable which needs to be set/ removed in order for me to be able to do the export? I have already converted all of my surface features to components in a backup XIN file. Sigh...