Hi, I am trying to report proposed and existing elevations along alignment at specified interval including level delta similar to annotation on profile.
I have tried the Station Offset Report on alignment with active existing terrain active. ProfileExistingProposedElevation.XSL looks like the best report for this task but the existing elevations and the cut fill depths are missing.
Is there anything I am missing? Is there any other way to compile such report e.g. modifying a stylesheet or perhaps using different reporting tool?
I have also tried Terrain > Analysis > Points > Analyze Elevation (in 3D model) but I can't specify the chainage interval and it doesn't report the chainage.
This works fine for us. The key is to use an offset greater than 0 like 0.0001 if the offset element is at a zero offset to the Alignment. This is a bug that we have noticed for a while, but not sure if it's been reported.
OpenRoads Designer 2021 R1 (10.10) | Microstation CE Update 16.2 | ProjectWise CE 3.4
Hi Mark, thanks for the tip.
We have tried the greater then zero offset but it didn't make difference when using the Station Offset Report. However, what worked is your setting on Station Base Report with StationBaseOffset-ANZ.xsl. This format doesn't give the level delta but this can be added in Excel.
We have also noticed StationBaseXfall-to-SuperEI_CSV-[x]HS.xsl format in the ANZ section. Do you use these to create superelevation based on existing crossfalls when projecting template points to existing terrain? Perhaps this could also be used to annotate super on profile in such cases?
That's right - this is something we put together for that exact reason. It is a workaround for a function we really need - the ability to annotate crossfall between 2 linear elements on Profile Drawings,, just like we did in older software like MX.
The reports were added to "correct" some issues with the delivered reports and things added like skipping reporting of gaps in linear elements so we dont see incorrect results.
I recommend you learn some XSL as the reports can be easily edited to give you what you want in the first instance with a minor change, instead of having to post-process them in Excel.
That's great, thanks Mark.
Have you been given an Enhancement Request ID for this badly needed functionality?
Also, correct me if I am wrong, but I understand the superelevation data in CSV format to work require empty rows between each row of data. Do you use some macro to format the output from the StationBaseXfall-to-SuperEI_CSV-[x]HS.xsl to insert these empty rows?
We will definitely explore the XML / XSL as this opens new capabilities. It would be still great if the standard delivered XSL reports were updated from old InRoads to work in ORD.
It looks like a small change occurred in the report structure and must be changed in the XSL.
Where @existingGroundElevation is found it should be replaced with centerLinePoint/@existingElevation
So the path is not anymore centerLinePoint/point but centerLinePoint and the value has changed from @existingGroundElevation to @existingElevation
Report with a zero offset does work well once correction done in the XSLs.
Here are the XSLs (from Default/Reports/StationOffset folder) where I fixed the issue:
Excellent, jpln. I found the issue with the "ProfileExistingProposedElevation.xsl" a few months ago, but did not follow up to other xsl's where such could have taken place. A nice bit of work here!
The nice notepad++ capability search/replace in all opened files.
Yeah, I think that I must have busy with some other things at the time, LOL. notepad++ is a great editor, and I am always surprised when folks are unaware of it!
Don't forget to install the XML Tools plug in. Pretty Print reformats XML files to make them more human friendly. And it you register CFG (PCF, UCF, too) files as BASH files, they syntax coloring makes them easier to read as well.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
A solid point, Chuck!