Reference Posts are signs located in physical locations. They stay in roughly the same place over time and do not change when other sections of the road are realigned. This layer also contains current ALRS linear measures (LM) for the sign feature.This is a Roads and Highways Event Layer - RP StationingFor more information on the difference between reference post locations along the roadway and the ALRS mileage, please refer to the Linear Measure vs Sign Location informational page

Last Update: 08/29/2024The statewide roads dataset is a multi-purpose statewide roads dataset for cartography and range based-address location. This dataset is also used as the base geometry for deriving the GIS-representation of UDOT's highway linear referencing system (LRS). A network analysis dataset for route-finding can also be derived from this dataset. This dataset utilizes a data model based on Next-Generation 911 standards and the Federal Highway Administration's All Roads Network Of Linear-referenced Data (ARNOLD) reporting requirements for state DOTs. UGRC adopted this data model on September 13th, 2017.The statewide roads dataset is maintained by UGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. UGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. UGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is UGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/We are currently working with US Forest Service to improve the Forest Service roads in this dataset, however, for the most up-to-date and complete set of USFS roads, please visit their data portal where you can download the "National Forest System Roads" dataset.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/transportation/roads-system/

This dataset approximates the locations of the Highway Reference Features along the UDOT Routes. Reference features include: gates, maintenance stations, ports of entry, rest areas, roundabouts, structures such as culverts, sub stations, view areas, etc. It was created by deriving a location from a polylineM route feature class (ALRS) Data source is the Linear Referencing System (ALRS). The service is data intensive and may render slowly. For more information please see the Data Assessment Form. For questions on this data please contact Kelli Bacon at kbacon@utah.gov. To download this data please visit UDOT's Open Data Site.

Vector polygon map data of mile markers from the State of Utah containing 5758 features.

Mile marker GIS data consists of points along a linear feature, such as roads or railways. They serve as reference points to measure distances along these features. Mile markers are often labeled with numbers indicating their distance from a starting point, such as a highway's origin or a railway station.

These markers are invaluable for navigation, route planning, emergency response, and data collection. For example, they help drivers and emergency services identify their location precisely on a road. In transportation planning, mile markers aid in analyzing traffic patterns, determining optimal routes, and estimating travel times. Additionally, they facilitate maintenance activities by providing clear reference points for inspecting and repairing infrastructure.

This data is available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

This dataset approximates the locations of the Highway Reference Features along the UDOT Routes. Reference features include: gates, maintenance stations, ports of entry, rest areas, roundabouts, structures such as culverts, sub stations, view areas, etc. It was created by deriving a location from a polylineM route feature class (ALRS) Data source is the Linear Referencing System (ALRS). The service is data intensive and may render slowly.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

Last Update: 08/29/2024The statewide roads dataset is a multi-purpose statewide roads dataset for cartography and range based-address location. This dataset is also used as the base geometry for deriving the GIS-representation of UDOT's highway linear referencing system (LRS). A network analysis dataset for route-finding can also be derived from this dataset. This dataset utilizes a data model based on Next-Generation 911 standards and the Federal Highway Administration's All Roads Network Of Linear-referenced Data (ARNOLD) reporting requirements for state DOTs. UGRC adopted this data model on September 13th, 2017.The statewide roads dataset is maintained by UGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. UGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. UGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is UGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/We are currently working with US Forest Service to improve the Forest Service roads in this dataset, however, for the most up-to-date and complete set of USFS roads, please visit their data portal where you can download the "National Forest System Roads" dataset.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/transportation/roads-system/

The statewide roads dataset is maintained by AGRC in partnership with local government, the Utah 911 Committee, and UDOT.Questions can be directed to AGRC.Usage:Transportation.Roads utilizes the Statewide Roads Data Model Standard, formally known as the Utah Transportation Data Model. The UGIC Road Centerline Sub-committee has been in the process of revising the content and structure of the Utah Transportation Data Model. The final draft of what is now being referred to as the â Statewide Roads Data Model Standardâ is pending approval by the UGIC Standards Committee.View the data model attribute descriptions and definitions: https://docs.google.com/document/d/1ojjqCa1Z6IG6Wj0oAbZatoYsmbKzO9XwdD88-kqm-zQ/edit?usp=sharingView the data model schema diagram: https://docs.google.com/open?id=0Bz18jufMWioiU25icDNoQWlJa2MThe Statewide Roads Data Model Standard is divided into two â tierâ levels:Tier Level 1 fields pertain to address location, cartography, and routing. Stewards are encouraged to maintain data that will map to the Tier Level 1 fields. The field named DOT_* are an exception, as UDOT will maintain these themselves.Examples of the CARTOCODE (formally CFCC) field descriptions:1 â Interstates2 â US Highway, Separated4 â Major State Highway, Separated7 â Ramps, Collectors9 â Major Local Roads, PavedTier Level 2 fields pertain to local agency maintenance and inventory and are utilized and shared if the local steward chooses to do so.Changes to the data model include a more logical approach to the ordering of fields and their names, in addition to the removal of multiple redundant fields. Proposals by the UGIC Standards Committee are meant as suggested â best practicesâ and are primarily designed for data transfer and sharing. It is not the intent that all stewards will change their current data management process to match this standard, but rather that stewards will evealuate their current practices to see how well their data â mapsâ to this schema for data sharing purposes. Questions can be directed to AGRC.The native spatial reference for this dataset is UTM Zone 12N, NAD83 (0.01 meter coordinate precision).

GIS representation of the UDOT Route System (main routes, ramps and collectors). Routes are represented as PolylineM features where the m coordinate is in miles. PolylineMs have been calibrated at end points and also some intermediate points as described in the UDOT linear referencing system (LRS) route descriptions for state route junctions, interstate bridge deck (begin and end) and other miscellaneous features.Updated: May 5, 2014

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Primary roads are generally divided, limited-access highways within the interstate highway system or under State management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. The MAF/TIGER Feature Classification Code (MTFCC) is S1100 for primary roads. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, and/or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not bedivided, and usually have at-grade intersections with many other roads and driveways. They usually have both a local name and a route number. The MAF/TIGER Feature Classification Code (MTFCC) is S1200 for secondary roads.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Primary roads are generally divided, limited-access highways within the interstate highway system or under State management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. The MAF/TIGER Feature Classification Code (MTFCC) is S1100 for primary roads. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, and/or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not bedivided, and usually have at-grade intersections with many other roads and driveways. They usually have both a local name and a route number. The MAF/TIGER Feature Classification Code (MTFCC) is S1200 for secondary roads.

This dataset was derived from the most current GCDB version of Utah county boundaries (1/22/2015).

Graph and download economic data for Coefficient for Industrial Carbon Dioxide Emissions, Asphalt and Road Oil for Utah (EMISSCO2CARICBUTA) from 1980 to 2018 about road, coefficient, asphalt, carbon dioxide emissions, UT, oil, industry, and USA.

Reference Posts are signs located in physical locations. They stay in roughly the same place over time and do not change when other sections of the road are realigned. This layer also contains current ALRS linear measures (LM) for the sign feature. This is a Roads and Highways Event Layer - RP StationingSupports the RP Stationing App (still in development).Source data Mandli CollectionFor more information on the difference between reference post locations along the roadway and the ALRS mileage, please refer to the Linear Measure vs Sign Location informational page.

Roads and Highways HPMS Pavement Events reference layers

Last Update: 03/04/2025The statewide roads dataset is a multi-purpose statewide roads dataset for cartography and range based-address location. This dataset is also used as the base geometry for deriving the GIS-representation of UDOT's highway linear referencing system (LRS). A network analysis dataset for route-finding can also be derived from this dataset. This dataset utilizes a data model based on Next-Generation 911 standards and the Federal Highway Administration's All Roads Network Of Linear-referenced Data (ARNOLD) reporting requirements for state DOTs. UGRC adopted this data model on September 13th, 2017.The statewide roads dataset is maintained by UGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. UGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. UGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is UGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/We are currently working with US Forest Service to improve the Forest Service roads in this dataset, however, for the most up-to-date and complete set of USFS roads, please visit their data portal where you can download the "National Forest System Roads" dataset.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/transportation/roads-system/

This dataset contains the boundaries for utah counties, cities, regional government, zipcodes, tribal lands, national forests, national parks, national monuments, state parks, legislative and congressional districts and buffered polygons for placenames, junctions, and other features shown on the UDOT Highway Map.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.

The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.