State Routes are depicted as lines with State Route identifiers and route measure attributes. All State Routes are included in this dataset. A directional indicator has been added to the RouteIdentifier to distinguish between the increasing and decreasing direction of mileposting. Please direct questions about this dataset to: TransportationGISDataSteward@wsdot.wa.gov.

A description of linear referencing and how MD SHA implements it.

The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.

Esri ArcGIS Online (AGOL) for Maryland Feature Layer for accessing the MDOT SHA OMOC Network data product.MDOT SHA One Maryland One Centerline (OMOC) Network is the official linear referencing system (LRS) and comprehensive route network for the State of Maryland. The OMOC Network is a current, sustainable, authoritative, and muti-use route centerline data product that is the result of collaborative partnerships between the MDOT State Highway Administration, the Maryland Transportation Authority (MDTA), the City of Baltimore, Maryland's 23 counties, and 159 incorporated municipalities across the State. The OMOC Network is also the basis for all roadway event data.The OMOC Network is owned & maintained by the MDOT SHA Office of Planning & Preliminary Engineering (OPPE), specifically under the MDOT SHA OPPE Data Services Division (DSD) State & Local Unit.MDOT SHA OMOC Network data is updated on a Daily basis throughout the year. This service and data product are dynamically tied to the enterprise production database that supports the One Maryland One Centerline (OMOC) program. For more information related to the data, contact MDOT SHA OPPE Data Services Division (DSD):Email: DSD@mdot.maryland.govFor more information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

PCC Lines are shown by major branch lines. This data is used as 1) a linear referencing system (LRS); 2) for locating features on the PCC system by milepost value. PCC lines were built using existing data sources including railroad line track charts, track right-of-way maps, and recently digitized linework based off aeiral photos. In LRS, the locations of both data and events are determined according to their distance along a railroad line from some known point (e.g., the beginning of the line or line segment, a mile marker, a junction with another rail line, or a railroad crossing).

Esri ArcGIS Online (AGOL) Hosted Feature Layer for accessing the MDOT SHA Roadway Routes data product.MDOT SHA Roadway Routes data consists of linear geometric features which represent the geographic extent of roadways throughout the State of Maryland. MDOT SHA Roadway Routes data includes geometry which is based on unique Route ID and is calibrated with Measured Values (M-Values) for linear referencing. MDOT SHA Roadway Routes data is owned & maintained by the MDOT SHA Office of Planning & Preliminary Engineering (OPPE). MDOT SHA Roadway Routes data is updated & published on an Annual basis for the prior year. This data is for year 2022.For more information related to the data, contact MDOT SHA OPPE Data Services Division (DSD):Email: DSD@mdot.maryland.govFor more information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Historic data for the Washington State Routes 24k linear referencing system in the increasing direction. State Routes are depicted as lines with State Route identifiers and route measure attributes. Routes in this feature class are for the increasing side of the highway mileposting. This data set is used: 1) for general-purpose base mapping; 2) as a Linear Referencing System (LRS); 3) for locating features on the State Route network by State Route Accumulated Route Mileage (dynamic segmentation). This dataset is a snapshot of the roadway system.

Historic data for the Washington State Routes 24k linear referencing system in the decreasing direction. State Routes are depicted as lines with State Route identifiers and route measure attributes. Routes in this feature class are for the increasing side of the highway mileposting. This data set is used: 1) for general-purpose base mapping; 2) as a Linear Referencing System (LRS); 3) for locating features on the State Route network by State Route Accumulated Route Mileage (dynamic segmentation). This dataset is a snapshot of the roadway system.

Historic data for the Washington State Routes 24k linear referencing system ramps. State Routes are depicted as lines with State Route identifiers and route measure attributes. Routes in this feature class are for the increasing side of the highway mileposting. This data set is used: 1) for general-purpose base mapping; 2) as a Linear Referencing System (LRS); 3) for locating features on the State Route network by State Route Accumulated Route Mileage (dynamic segmentation). This dataset is a snapshot of the roadway system.

Historic data for the Washington State Routes 24k linear referencing system turnbacks. State Routes are depicted as lines with State Route identifiers and route measure attributes. Routes in this feature class are for the increasing side of the highway mileposting. This data set is used: 1) for general-purpose base mapping; 2) as a Linear Referencing System (LRS); 3) for locating features on the State Route network by State Route Accumulated Route Mileage (dynamic segmentation). This dataset is a snapshot of the roadway system.

Historic data for the Washington State Routes 24k linear referencing system in the decreasing direction. State Routes are depicted as lines with State Route identifiers and route measure attributes. Routes in this feature class are for the increasing side of the highway mileposting. This data set is used: 1) for general-purpose base mapping; 2) as a Linear Referencing System (LRS); 3) for locating features on the State Route network by State Route Accumulated Route Mileage (dynamic segmentation). This dataset is a snapshot of the roadway system.

Historic data for the Washington State Routes 24k linear referencing system in the decreasing direction. State Routes are depicted as lines with State Route identifiers and route measure attributes. Routes in this feature class are for the increasing side of the highway mileposting. This data set is used: 1) for general-purpose base mapping; 2) as a Linear Referencing System (LRS); 3) for locating features on the State Route network by State Route Accumulated Route Mileage (dynamic segmentation). This dataset is a snapshot of the roadway system.

The Texas Department of Transportation (TxDOT) maintains a spatial dataset of roadway polylines for planning and asset inventory purposes, as well as for visualization and general mapping. This dataset covers the state of Texas and includes on-system routes (those that TxDOT maintains), such as interstate highways, U.S. highways, state highways, and farm and ranch roads, as well as off-system routes, such as county roads and local streets. Route segments in this version of TxDOT Roadways are broken by functional classification. For an unsegmented version of TxDOT Roadways, see TxDOT Roadways Unsegmented.

This data contains measures. Measures are stored as M-values within each vertex along the line, in the same way that some datasets store z-values for the elevation, except that measures store the distance from the origin, or DFO, along the line. M-enabled networks serve as frameworks for locating roadway assets along the network using linear referencing. This data set must be downloaded as a file geodatabase in order to keep M-Values intact. If downloaded as a shapefile or added to a map from a connection to ArcGIS online, measures will not be applied to the line.

Update Frequency: Monthly

Source: Geospatial Roadway Inventory Database (GRID)

Security Level: Public

This dataset represents county roads open to the public in Washington State as listed in the County Road Administration Board (CRAB) Road Log compiled as a GIS Linear Referencing System (LRS) using County Road Numbers and county milepost values. Route measure values are valid as of 12/31/2024. Please direct questions about this dataset to: TransportationGISDataSteward@wsdot.wa.gov.

DescriptionPoint geographic dataset representing the location along a CDOT highway where that highway's linear reference system indicates a whole number reference point.Please note, mile posts are not necessarily found at milepoints. Last Update2024Update FrequencyAs neededData OwnerDivision of Transportation DevelopmentData ContactGIS Support UnitCollection Method ProjectionNAD83 / UTM zone 13NCoverage AreaStatewideTemporal Disclaimer/LimitationsThere are no restrictions and legal prerequisites for using the data set. The State of Colorado assumes no liability relating to the completeness, correctness, or fitness for use of this data.

A control section is a unique identifier for individual segments of a roadway. Historically control sections were only assigned to on-system, or state-maintained, highways, and were created as a highway referencing system for planning and maintenance projects, etc. However, this dataset also includes off-system, or non-state-maintained, roadways. Control Section numbers are assigned for the life of the roadway and generally do not change or move, regardless of improvements to the roadway. Currently, control sections are located geographically along roadway using linear referencing. The data was created by the TxDOT Transportation Planning and Programming Division's Data Management Section.This data contains measures. Measures are stored as M-values within each vertex along the line, in the same way that some datasets store z-values for the elevation, except that measures store the distance from the origin, or DFO, of the line. M-enabled networks serve as a framework for locating roadway assets along the network using linear referencing. This data set must be downloaded as a file geodatabase in order to keep M-values intact. If downloaded as a shapefile or added to a map from a connection to ArcGIS online, measures will not applied to the line.Update Frequency: 1 MonthsSource: Geospatial Roadway Inventory Database (GRID)Security Level: PublicOwned by TxDOT: TrueRelated LinksData Dictionary PDF [Generated 2025/05/21]

The Highway Performance Monitoring System (HPMS) dataset is as of October 21, 2019 and is from the Federal Highway Administration (FHWA), and part of U.S. Department of Transportation (USDOT) / Bureau of Transportation Statistics' (BTS') National Transportation Atlas Database (NTAD). FHWA released this dataset as the latest version of HPMS which represents the highway system as of the 2018 calendar year. The Highway Performance Monitoring System (HPMS) provides data that reflects the extent, use, condition, and performance of the public roads in the United States. It consists of the All Road Network of Linear Referenced Data (ARNOLD) geometry and the Section Data which is the attribution. ARNOLD and Sections are linked though linear referencing and are part of the HPMS data program. This data is analytical for the purpose of supporting transportation program, funding and policy decisions at a national level. Operational applications such as navigation and routing may take advantage of HPMS with the understanding that it represents the average and not “real-time” of the system. The Highway Performance Monitoring System Field Manual contains a detailed description of each data element including coding instructions and attribute definitions. The Field Manual is available at: https://doi.org/10.21949/1519108

This is an extract from the State Highway Log that shows access control information along State Routes. State Route identifiers and locations based on State Route Mileposts and Accumulated Route Mileage are also included for geographic reference and for use with the Washington State Department of Transportation's 24k and 500k Linear Referencing Systems. Please direct questions about this dataset to: TransportationGISDataSteward@wsdot.wa.gov.

This is an extract from the State Highway Log that shows roadway width (feet) information along State Routes. State Route identifiers and locations based on State Route Mileposts and Accumulated Route Mileage are also included for geographic reference and for use with the Washington State Department of Transportation's 24k and 500k Linear Referencing Systems. Please direct questions about this dataset to: TransportationGISDataSteward@wsdot.wa.gov.

This is an extract from the State Highway Log that shows lanes designated for turn movements at intersection locations along State Routes. Details include: turn lane length, width, left/right indicator, and near/far indicator. State Route identifiers and locations based on State Route Mileposts and Accumulated Route Mileage are also included for geographic reference and for use with the Washington State Department of Transportation's 24k and 500k Linear Referencing Systems. Please direct questions about this dataset to: TransportationGISDataSteward@wsdot.wa.gov.