I am trying to take horizontal alignments w/ their respective profiles that were originally created in V8i and import them into a new DGN via an XML file. I go into PowerGEOPAK V8i, select the geometry, go to Horizontal Reports, and save as an XML. I can open this XML and it appears sound. The horizontal and vertical definitions are there. Of note, it is indicating XML version 1.0 in these files (not sure if this has anything to do with it or not). When I go into OpenRoads Designer (CE 2021 R2), I go to Geometry, Import/Export and select my .XML file. On the Import Geometry dialog box that comes up, the top portion shows a checkbox with "LandXML...", but there is nothing below that like there normally would be, eventually showing the alignment names to be imported. I can check the box and resize the dialog, but nothing shows up. If I check the box and still hit Import, there is nothing brought into the DGN file.
The horizontal alignments are very simple (two alignments, each just a tangent line). The names shouldn't be an issue ("PRA" for horiz and "PRA_PG" for vertical).
Any ideas why this is not importing?
Thanks in advance all!
These don't look to be "proper" LandXML files eg. they contain "HorizontalAlignment" elements and not the standard "Alignment", etc. Although they are XMLs, I dont believe they are formatted as LandXMLs?
OpenRoads Designer 2022 R1 (10.11) | Microstation CE Update 17.2 | ProjectWise CE 3.4
I don't know enough about XML to determine proper or not, but this is the output from the Bentley Civil Report "Alignments to LandXML" report when saving as File Type XML. Since you mentioned this, I tried the same report, but saved as File Type TXT, and it indicates "Alignment" instead of "HorizontalAlignment".
Not sure if it's the issue or not, but just one difference I noticed when saving the file.
Yep, the XML you exported previously was the raw report data. The text file should be the actual report output. Once you rename to XML it should work fine.
Answer Verified By: Ken Harrison
Looks like this did the trick.
I'm curious, when would you want to use the other XML version of the output?
The other XML is how Reporting works in InRoads and Open Roads. An XML file is create and then a stylesheet is applied to it to reformat the data. It is a very powerful methodology that open up a lot of custom report capabilities beyond what LandXML data offers. In Civil 3D, a lot of extra code is required to calculate similar data. This is usually done with java or vb code within the stylesheet. It is way mor complicated to customize that Bentleys approach.
I believe a lot of this originated as part of the Implementation of Roadway Designer into all three V8i products, which is why a GEPAK user would end up with an XML file branded as InRoads
I do believe there is a more native way to export LANDXML from GEOPAK however.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration