Hi - hope someone can help, please. Now the XML export feature is fixed with chainage showing against the cant (thanks!!), I wanted to try out the WinALC export as we need to do this for producing geometry files for our tampers.
I exported my design from MX in LandXML format, as usual, and imported into ORD 2022 R1 U11. That's all okay. I've gone through the usual steps to re-add the cant and export the to WinALC (not Smart ALC, as I don't use this). This is where I'm having some trouble.
My steps:
- I imported the LandXML file into ORD using the Import Geometry tool
- Used the Speed Table function
- Used the Create Cant on my centreline... and so far so good!
- Time to use Export Geometry from the centreline alignment... and it seems to work using the Plasser and Theurer option! But when checking the export, I noticed a big problem.
I can see the chainage is correct for my horizontal and vertical parts of the design when checking reports in ORD, and the same for the cant, but on the *.geo export, it all simply starts at 0m chainage and the end point is the extent of the job (in this case 1590m in length). It should be showing 269330m to 270920m. Cant is actually okay, and all the elements lengths and transitions are okay... it's just problematic starting at 0m rather than the proper start point.
Is this a similar issue to the old XML export problem, with a disconnect between the chainage of a design and the export?
Any help would be fantastic, please. Thanks.
Tip 1: Make sure that your alignment has a Feature Definion from the Alignment group. (So an Annotation Group is assigned.)
Tip 2: Make sure the Annotation scale in your current DGN is large enough to show visible texts.
As I can see no stationing is output in WinALC and SmartALC (H+V+Cant).I don't have specification for these formats to check, but I would be surprised we don't need the stationing.
So looks like a bug. I would suggest to raise a service request if not already done.