I am looking to report horizontal and (optionally) vertical offset differences between two strings at points / intervals defined by a reference string (base alignment).
In MX there is a very useful function ‘160’ which does that and provides output in a practical tabular format.
In ORD I only managed to use Station Base report which provides offsets from a base alignment (first selected string) to subsequently selected strings, in separate rows. Currently there doesn’t seem to be a report that would calculate and list the offsets between two non-base strings i.e. the subsequently selected strings. So, the offsets need to be calculated in Excel.
Such report can be very useful in reporting pavement widening as differences between proposed and existing edge of pavement or other strings comparison.
Perhaps someone has an xsl that can provide formatting for Station Base report that achieves the above?
Here you go ;) Note that due to the Station-Base Report bugs in 10.12, i was unable to test properly, but should do what you need (let me know if not).
OpenRoads Designer 2023 | Microstation 2023.1 | ProjectWise 2023
Many thanks for coming back so quickly!
I have tested the xsl in 10.11 and the output shows most of the information but the comparative values seem only at two locations and also we would expect only one row per chainage in this table?
Benefits of learning HTML / XSL are obvious :)
OpenRoads Designer 2022 R1
I have replaced the xsl in the previous post. and it should work well now There are still some bugs in 10.11s Base Station reporting to do with Base Stations, but hopefully fixed in the new enhanced 2023 Station Offset Reporting.
Having at least one person in your team who can at least edit XSLT code is critical to being able to get the most out of ORD reporting. The thing that makes it easier is that there are plenty of reports that can be reverse engineered and a lot of learning content online.
Answer Verified By: Mariusz Heczko
I tested all of the reports in 10.12, and could swear that they are all good. Can you verify, or are there still some issues in this particular area like there were in 10.11?
Unless there is an issue with my preferences being corrupt, i am only having issues with the Station Base Report (Station Offset is fine). I'm seeing issues with it reporting lengths outside the range of the offset elements (when using intervals - since 10.11) and offset element names missing in 10.12. Looking at the raw XML data it is an issue in the reporting itself and not the XSLs.
Thanks so much for the reply, Mark. I will look into this XML (and indeed the XSL to confirm) this weekend.
Now, it works exactly as requested:
Thank you so much Mark, much appreciated.
And yes, learning XSLT is inevitable for ORD reports customisation and key in improving workflow efficiency.
I can attest to developing a skill set in XSLT will prove valuable for ORD. I found that while there are some books devoted exclusively to XSLT, often books on XML will contain sections on XSLT. And if you can find those books on clearance, it is less painful on the purse. I have a library of $30+ books often purchased for $5 or less.
i started learning this when the Report Browser became part of InRoads. And I learned a lot by studying the delivered reports.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration