I'm using Openroads 2020 R3, I need to export and import my superelevation from one file to the other. I need to do this because it's a fairly long model with many transitions all build manualy and my alignement changed a little bit and I need to have many option with profiles ans sections.
I know I can do a superelevation report to CSV and then import it back. It's just NOT working, even if I create a superelevation section and empty superelevations lanes in the new file the software does not recognise the imported data. I have try with the default metric and with my workspace, not working. I have try a clean installation, erase all folders related to openroads then re-install, not working.
I want to know if it's working, can anybody try this, thanks.
Hello, Yes, it works. I am able to import csv (I had to change a decimal separator to semicolon only) in 2020 R3. Btw another way how to use any old prepared superelevation (lanes, sections etc...) is to save it to separate dgn and then use it as reference file.
what decimal separator did you had to change?
When I export by Superelevation report with xsl "SuperelevationToCSV.xsl" and Save as txt, there are coma as separator in saved file. I need to change it to semicolon and then I can import it back.Reported textL_koruna,0.000,0.03298700,RS,U,L,0.000L_koruna,15.890,0.06000000,RS,FS,L,0.000L_koruna,87.110,0.06000000,RS,FS,L,0.000I change it to L_koruna;0.000;0.03298700;RS;U;L;0.000L_koruna;15.890;0.06000000;RS;FS;L;0.000L_koruna;87.110;0.06000000;RS;FS;L;0.000and then is it ok for import.
Answer Verified By: JeremieDL
THANK YOU SO MUCH!! thanks Josef you just save me a lot lot works! I'm not 100% sure but I think it is related to Windows Regional setting for list separator.
Yes, I think so. That is neverending story. Therefore I have created two xsl files for reporting for our customers - with coma and semicolon as decimal separator.