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 data contains mile posts that were created from UDOT's LRS. The mile post data is scale dependent and is only visible at specific scales. Mile Posts in this map only appear along state routes. This information is updated monthly. Click on MP for link to Streetview. 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.

This data contains mile posts that were created from UDOT's LRS. The mile post data is scale dependent and is only visible at specific scales. Mile Posts in this map only appear along state routes. This information is updated monthly. Click on MP for link to Streetview. 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.

Statewide Traffic Volume Historic and Forecast Historic traffic volume observations, future traffic volume forecasts, and adjustment factors -- are summarized using Utah's roadway planning summary segments -- for the Wasatch Front Regional Council metropolitan planning organization travel model area. This dataset can be viewed in an interactive map at: https://wfrc.org/traffic-volume-map/. This dataset provides segment level traffic volume data (historic estimates and future forecasts) within the state of Utah. Wasatch Front Regional Council (WFRC) metropolitan planning organization's travel model boundaries (including Salt Lake, Davis, western Weber, and southern Box Elder counties' urbanized areas). Future forecasts have been developed with the support of the Wasatch Front Travel Demand Model (v8.3.1) in conjunction with the adopted 2019 Regional Transportation Plan (RTP). This dataset was first released May 5th, 2020 (check the RELEASE field/column attribute for most recent update date). MAG travel model boundaries include the urbanized areas of Utah County. Cache travel model boundaries include Cache County. Dixie travel model boundaries include Washington County. Also contained within this dataset are adjustment factors, developed as part of a statewide effort led by UDOT, that can be used to scale the Average Annual Daily Traffic (AADT) volumes estimates and forecasts to provide more time-period specific volumes for a time period subsets (e.g. weekdays, weekends, specific months, seasons, maximum month, etc). Contact and additional information is available from https://wfrc.org/models-and-forecasting or through email contact to analytics@wfrc.org.UPDATE 12/31/2021: Highland Drive revised forecasts for SEGIDs 2082_009.0, 2082_009.6, 2082_011.5, 0152_002.5, 0152_002.8. Field names and descriptions are as follows: RELEASE (version of dataset) SEGID (Segment ID, combination of Route_ID and BMP) ROUTE_ID (Route Identification, <1000 for Interstate/State Routes, >1,000 for Federal Aid Routes) BMP (Begin Milepost, or milepost of beginning of segment) EMP (End Milepost, or milepost of ending of segment) FULLNAME (name of segment) CO_FIPS (County Federal Information Processing Standard, unique code for each county) CO_NAME (Name of county) X (Centroid of Segment, UTM Zone 12N) Y (Y Centroid of Segment, UTM Zone 12N) DISTANCE (length of segment in miles) F2050...F2024 (forecast AADT volumes for model years per 2019 RTP) CH17TO50...CH17TO19 (change in AADT volumes between model years) FNOTES (forecast notes, typically when drop or large increase in volumes) MOREINFO (url to more general information on models and forecasts) WFRC_FLG (flag value used internally by WFRC) AADT2017...AADT1981 (AADT estimates for a given year from UDOT) SUTRK2017 (Single-Unit, Box Type Truck percentage for 2017) CUTRK2017 (Combo-Unit, Semi Type Truck percentage for 2017) DOWFACFC (Day-of-Week Factor Functional Class) DOWFACAT (Day-of-Week Factor Area Type) FAC_MON...FAC_SUN (Day-of-Week factors for given days) FAC_WDAVG (Average Weekday Factor Monday-Thursday, multiply AADT by factor to get AWDT, divide AWDT by factor to get AADT) FAC_WEAVG (Average Weekend Factor Friday-Sunday) FAC_WEMAX (Max Weekend Factor Friday-Sunday) SSNGRP (Seasonal Factor Group) SSNVOLCLS (Seasonal Factor Volume Class) SSNATGROUP (Seasonal Factor Area Type Group) FAC_JAN...FAC_DEC (Month Factors, multiply AADT or AWDT get month ADT or AWDT) FAC_WIN (Winter Factor, December-February) FAC_SPR (Spring Factor, March-May) FAC_SUM (Summer Factor, June-August) FAC_FAL (Fall Factor, September-November) FAC_MAXMO (Month in which Maximum Month Factor is found) FAC_MAX (Maximum Month Factor)