# Project Alignment Centerline Chainage to an Offset Alignment

Hello,

Just wondering if there's an easy way to project the chainage from a centerline alignment to an offset alignment.  A contractor has asked for this as it helps them with construction staking.  I understand that mathematically the chainage of an offset alignment will change due to arc radii being different and this will have a compound effect as you go further along the alignment, hence the reason why just applying the chainage regularly to the offset alignment won't work.

Is there a way to develop/report/export this quickly/easily in ORD?

Thanks,

Jay

Parents
• Would the Station Offset Report get that.  It seems to be what you are looking for.  The station and off set from one alignment relative to an offset alignment.  The report below show the Station and off set of my "Offset Agligment" at the 25 FT station interval along my "Mainline" alignment.  You can switch it up and do several variations of this with the reports.

## Station Offset Report

Report Created:  Tuesday, March 21, 2023
Time:  12:03:28 PM

Project:  Description: Default OffSet Alignment C:\Projects\Dummy\5-ProfileMainLine.dgn 3/21/2023 12:02:37 Note:  All units in this report are in feet unless specified otherwise.

- - - - - - - - Baseline Alignment - - - - - - -
(OffSet Alignment)
- - - - - - - - Offset Alignment - - - - - - - -
(Mainline)
Station Type Distance to
Offset Point
Radial Direction   Station Type Distance to
Offset Point
500+00.000 POB 250.0000000 S0.000°E   100+00.000 POB 0.0000000 S26.565°E
500+22.361 POT 238.8196601 S0.000°E   100+25.000 POT 0.0000000 S26.565°E
500+44.721 POT 227.6393202 S0.000°E   100+50.000 POT 0.0000000 S26.565°E
500+67.082 POT 216.4589803 S0.000°E   100+75.000 POT 0.0000000 S26.565°E
500+89.443 POT 205.2786405 S0.000°E   101+00.000 POT 0.0000000 S26.565°E
501+11.803 POT 194.0983006 S0.000°E   101+25.000 POT 0.0000000 S26.565°E
501+34.463 POT 183.5507941 S0.000°E   101+50.000 POC 0.0000000 S22.651°E
501+57.909 POT 174.8945855 S0.000°E   101+75.000 POC 0.0000000 S17.877°E
501+81.994 POT 168.2199769 S0.000°E   102+00.000 POC 0.0000000 S13.102°E
502+06.551 POT 163.5732932 S0.000°E   102+25.000 POC 0.0000000 S8.328°E
502+31.409 POT 160.9867842 S0.000°E   102+50.000 POC 0.0000000 S3.553°E
502+56.397 POT 160.4784014 S0.000°E   102+75.000 POC 0.0000000 S1.222°W
502+81.340 POT 162.0516732 S0.000°E   103+00.000 POC 0.0000000 S5.996°W
503+06.066 POT 165.6956805 S0.000°E   103+25.000 POC 0.0000000 S10.771°W
503+30.402 POT 171.3851322 S0.000°E   103+50.000 POC 0.0000000 S15.546°W
503+54.181 POT 179.0805412 S0.000°E   103+75.000 POC 0.0000000 S20.320°W
503+77.236 POT 188.7284980 S0.000°E   104+00.000 POC 0.0000000 S25.095°W
503+99.640 POT 199.8201482 S0.000°E   104+25.000 POT 0.0000000 S26.565°W
504+22.001 POT 211.0004881 S0.000°E   104+50.000 POT 0.0000000 S26.565°W
504+44.362 POT 222.1808280 S0.000°E   104+75.000 POT 0.0000000 S26.565°W
504+66.722 POT 233.3611678 S0.000°E   105+00.000 POT 0.0000000 S26.565°W
504+89.083 POT 244.5415077 S0.000°E   105+25.000 POT 0.0000000 S26.565°W

Mike Longstreet
Vermont Agency of Transportation
Civil Engineering Technical Support

• Hi Mike, yeah, this looks like the closest available solution.  If there's a way that multiple offset alignments could be added (I tried adding multiple offset alignments (ex. a left offset alignment and a right offset alignment) though only one offset alignment seems to show up in the report) and also if the xy coordinates of the alignments at the stations listed could be displayed that would be optimal.

• I am able to select more than one offset geometry and it reports on both.  There are several types of reports depending on what you need.  I used the Station Offset, there is a Station Base report type, then within the report's browser there are StationOffset and StationBase Coordinate reports depending on what you need.  It is possible to create custom report combining these but typically cutting and pasting to a spread sheet works well.

Mike Longstreet
Vermont Agency of Transportation
Civil Engineering Technical Support

• Thanks, Mike -I will explore these options.

• The reports use XML data and reformat it to an HTML document. Often, the XML document contains more information than the report uses. When that is the case, it is possible to modify the XSL file to add columns or rows to report on the supplied, but unused data. And sometimes, there are other reports that do use the data which at the very least can be used as a guide to your modifications.

While it is not rocket science, it is a learning experience. Here are some starting tips:

• Always work on a copy of an existing report. Best if it is close to your desired results.
• Get Notepad++ with its XML Tools plugin.
• As you modify your report - make one change and test. XML error messages are often not much help and often tell you what it found that it was not expecting, but the error is caused by something nowhere near the reported error.
• Look for any guidance on XSL and XSLT. But be ready for a lot of information that is not applicable to Open Roads Reports.
• Books on XML usually have a chapter on XSL, but on occasion you will find a book on XSL only.
• Look in clearance areas of anyone who sells books. Often you can get a \$40 book for less than \$10.

Charles (Chuck) Rheault

• MicroStation user since IGDS, InRoads user since TDP.
• AutoCAD, Land Desktop and Civil 3D, off and on since 1996
• The reports use XML data and reformat it to an HTML document. Often, the XML document contains more information than the report uses. When that is the case, it is possible to modify the XSL file to add columns or rows to report on the supplied, but unused data. And sometimes, there are other reports that do use the data which at the very least can be used as a guide to your modifications.

While it is not rocket science, it is a learning experience. Here are some starting tips:

• Always work on a copy of an existing report. Best if it is close to your desired results.
• Get Notepad++ with its XML Tools plugin.
• As you modify your report - make one change and test. XML error messages are often not much help and often tell you what it found that it was not expecting, but the error is caused by something nowhere near the reported error.
• Look for any guidance on XSL and XSLT. But be ready for a lot of information that is not applicable to Open Roads Reports.
• Books on XML usually have a chapter on XSL, but on occasion you will find a book on XSL only.
• Look in clearance areas of anyone who sells books. Often you can get a \$40 book for less than \$10.

Charles (Chuck) Rheault