A few Control Codes from InRoads Survey did not make the cut and there are some new codes that are different from the coding modes as well.
The ability to generate XML Reports while carried forward, has become less robust. We regularly use a PNEZD type of Report from InRoads Survey as input to Civil 3D. This report is a custom report I created, but it was not too much work. The D of PNEZD is usually the exact Code String from the Survey RAW file, but may also contain extra characters built from certain attributes.
This does not appear to be possible with Open Roads survey.
There is a attribute in the XML file that sometimes contains the data from the code string, but it has been reformatted and will take a lot of effort to recreate this report output. Also, the Attribute as exported are combined into a single "|" delimited text string which will also need some new coding to gather any of those values to combine with the code string, when appropriate.
The ability to generate XML Reports while carried forward, has become less robust. We regularly use a PNEZD type of Report from InRoads Survey as input to Civil 3D. This report is a custom report I created, but it was not too much work. The D of PNEZD is usually the exact Code String from the Survey RAW file, but may also contain extra characters built from certain attributes.
This does not appear to be possible with Open Roads survey.
There is a attribute in the XML file that sometimes contains the data from the code string, but it has been reformatted and will take a lot of effort to recreate this report output. Also, the Attribute as exported are combined into a single "|" delimited text string which will also need some new coding to gather any of those values to combine with the code string, when appropriate.