XSL Report format change in ORD

RE: XSL Report format change in ORD

Derek Schmidt — Mon, 06 Mar 2023 20:27:38 GMT

Thanks, Mark. I expected so, but I just began converting some reports and I didn't notice any issues but I wanted to check.

RE: XSL Report format change in ORD

Mark Shamoun — Mon, 06 Mar 2023 20:20:50 GMT

Hi Derek, if I recall correctly, this was fixed a while ago.

RE: XSL Report format change in ORD

Derek Schmidt — Mon, 06 Mar 2023 20:16:38 GMT

Thanks, Kevin. Do you know if this has been fixed, 5.5 years later?

RE: XSL Report format change in ORD

John Mark Palacios — Wed, 03 Jul 2019 22:58:49 GMT

Kevin, do you have an update on documentation? Since you have removed the format.xsl file, documentation is even more crucial as we have no way of knowing what functions are available in the cif namespace. We used to be able to open format.xsl and review all the javascript functions that were present, but now we have no way of knowing what functions are available. Am in the process of updating FDOT's XSL reports to work in ORD.

RE: XSL Report format change in ORD

Kevin McDonald — Wed, 21 Jun 2017 19:11:06 GMT

Thanks for the notice about the doubling of the Position() values. I've filed a defect (717703) to get this fixed.

RE: XSL Report format change in ORD

Mark Shamoun — Wed, 21 Jun 2017 04:23:18 GMT

After updating my previous SS4 reports, this is what I have found:

xml namespace "cif" needs to be manually defined (to replace previous "inr" namespace), eg. xmlns:cif="cif"
All "inr" namespace references must be repaced with "cif", eg. cif:stationFormat (vs inr:stationFormat)
xslShowHelp parameter is now required (for Report Help), eg. <xsl:param name="xslShowHelp" select="cif:xslShowHelp"/>
All Format parameters now have self-constained unit and precision variables (definition using custom variables no longer available),
- eg. "cif:directionFormat(number(@tangentialDirectionEnd))" (vs "inr:directionFormat(number(@tangentialDirectionEnd), $xslDirectionFormat, $xslDirectionPrecision, $xslDirectionModeFormat1, $xslAngularMethod1)"
- This now locks definition of units and precision to the Civil Report format options (can be hardcoded using format-number function)
"EastingFormat", "NorthingFormat" and "ElevationFormat" parameters have been replaced with a new "OrdinateFormat" paramete
Previous current node Position() = 1 (first node in node list) now needs to be defined as Position() = 2
Previous last node position - Position() = last() now needs to be defined as Position() = last() - 1
Related to the changes above, there seems to be a doubling up of node counts, ie. Previous nodes = 7 now has nodes = 14

Attached is an example of a SS4 report and its updated ORD version - Please note: these have hardcoded precision set in the report (except bearing)

communities.bentley.com/.../HorizontalAlignment_2D00_Type1.zip

RE: XSL Report format change in ORD

Kevin McDonald — Thu, 20 Apr 2017 15:01:44 GMT

Hi Mark, This change occurred because all of the JavaScript code had to be re-written to work with the newer versions of the Microsoft XML code. The schemas should all be pretty much the same in the XML, but the JavaScript used to format will have to be modified as you've shown above. I was told that more documentation will follow, but at this time we don't have a full list with the changes. I am planning to start a WIKI over in the OpenRoads Designer pages to list the differences as we find them.

communities.bentley.com/.../33435.openroads-designer-connect-edition-wiki-articles-and-videos