ESRI ArcMap 10.1

Linear Referencing Tools

Author

George Wong

Date, Revisions

Created on 17 December, 2015

Software

ESRI ArcMap 10.1+

Description

This is a quick reminder of how to use linear referencing and displaying road centrelines for infrastructure asset mapping in ArcMaps.



Summary

This is a quick reminder of how to use linear referencing and displaying road centrelines for infrastructure asset mapping in ArcMaps. This would be useful for any kind of asset mapping that makes use of linear referencing.

Organisations that collect information on highways, city streets, railroads, rivers, pipelines, water and sewer networks often use linear referencing systems to store data.

When data is linearly referenced, many datasets can be linked to any portion of an existing linear feature. For example a bus stop (point feature) or a stretch of footpath (polyline feature) could be linked to a segment of road that is linearly referenced.

ESRI has extensive web resources for ArcGIS on linear referencing.

If you have existing feature classes that are already ready to use, then you can display the chainage by enabling [Hatches] under that layer's properties.

It can take a stupid amount of time to load the labels if you make the hatches too frequent. In the above example I've set the hatch interval to every 10 metres. Adjust this based on scale and required precision.

It may be beneficial to include an arrow on the end of the line to indiciate the direction of the line. You can also figure this out based on the way the chainage is counting. This then gives you a 'left' and 'right' side of the road.

Most assets will have these fields: Asset ID, Street Name, Road ID, Block ID, RoadID_BlockID.

You can derive distance and direction from the feature classs.

On the asset tables, you're likely to find start and end points in metres (chainage), the starting and ending street names, the street it is on, the Block ID, the side of the street, and the Asset ID. The Asset ID is the most important so make sure it is entered into the geodatabase correctly.

back to
WORK