The feature layer contains mile marker signs found along all Interstate Highways and Appalachian Highway Corridors. Information included in this layer includes the Route Information, FAB Code, Sign Text, sign size, Coordinates, and Collection Date. Data is current as of January 1, 2021 and is updated as needed.Coordinate System : NAD_1983_UTM_Zone_17N

In general, the mile markers are measured from west to east and south to north. Such as I-10 starting in Escambia County, bordering Alabama, with mile marker 1 then increases eastward. And for I-95 from Miami-Dade County starting with mile marker 1 then increases northward. The data is refreshed weekly and changes are made by the District Offices who are responsible to collect and upkeep the data. This data may also be collected for call boxes that are located at integral milepoints instead of the usual mile marker signs. This data is required for all interstate, tolled or non-tolled expressway facilities, and US routes. This dataset is maintained by the Transportation Data & Analytics office (TDA). The source spatial data for this hosted feature layer was created on: 07/12/2025.For more details please review the FDOT RCI Handbook Download Data: Enter Guest as Username to download the source shapefile from here: https://ftp.fdot.gov/file/d/FTP/FDOT/co/planning/transtat/gis/shapefiles/milemarkers.zip

Part of the emergency response facilities layers, the mile markers contribute to emergency response. This is a point layer featuring the mile marker locations on the highways throughout the county. The data was last updated in 2014 and is not maintained by SCGIS. Mile markers on highways provide a more precise location during emergencies. Those seeking emergency assistance on a highway can report to dispatchers the closest mile marker and help get a faster response.

Overseas highway milemarkers along US 1 in Florida Keys from Key West to Florida mainland in Monroe County.

Point features which represent the locations of mile marker signs along public roadways in the State of Maryland. Roadway Mile Markers data is developed as part of the Highway Performance Monitoring System (HPMS) which maintains and reports transportation related information to the Federal Highway Administration (FHWA) on an annual basis. HPMS is maintained by the Maryland Department of Transportation State Highway Administration (MDOT SHA), under the Office of Planning and Preliminary Engineering (OPPE) Data Services Division (DSD). This data is used by various modules throughout MDOT, as well as many other State and local government agencies for purposes such as planning, land use, transportation, data & asset collection. Roadway Mile Markers data is published on an annual (yearly) basis for the prior year. For additional information, contact the MDOT SHA Geospatial Technologies Team:GIS@mdot.state.md.usFor additional information related to the Maryland Department of Transportation (MDOT):http://www.mdot.maryland.gov/ For additional information related to the Maryland Department of Transportation State Highway Administration (MDOT SHA):http://www.roads.maryland.gov/Home.aspx MDOT SHA Geospatial Data Legal Disclaimer:The Maryland Department of Transportation State Highway Administration (MDOT SHA) makes no warranty, expressed or implied, as to the use or appropriateness of geospatial data, and there are no warranties of merchantability or fitness for a particular purpose or use. The information contained in geospatial data is from publicly available sources, but no representation is made as to the accuracy or completeness of geospatial data. MDOT SHA shall not be subject to liability for human error, error due to software conversion, defect, or failure of machines, or any material used in the connection with the machines, including tapes, disks, CD-ROMs or DVD-ROMs and energy. MDOT SHA shall not be liable for any lost profits, consequential damages, or claims against MDOT SHA by third parties.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_RoadwayMileMarkers/FeatureServer/0

This dynamic map service provides a general linear referencing system used to locate highway characteristics and events. These milepoints are spaced at 1/10th of a mile intervals.

Reference posts (often called Mile Post or Mile Markers) are green numbered signs along the side of a highway roughly a mile apart for traveler reference.

Check other metadata records in this package for more information on Highway Reference Post Information.


Link to ESRI Feature Service:

Highway Reference Posts in Minnesota: Highway Reference Posts

The Mile Marker Inventory contains mile marker location information along Michigan's highways. Descriptive information for the mile markers include: latitude and longitude, route name, region, TSC, county, control section number, physical reference (PR) number, PR mile point, and mile number. The information was collected in 2011 using Framework V11. The data has not been updated and more current data may be available. Please see the MDOT Metadata Form for additional information. Update Cycle: The Mile Marker inventory was initially collected and completed in 2011 as part of the Lane Mile Inventory (LMI). There is currently no update plan in place to re-collect or update this inventory.Data Quality: Data was collected to +/- 25ft accuracy using a laptop equipped with ArcGIS Desktop and a tethered USB puck GPS unit.Coverage: This inventory is complete in its coverage of all State of Michigan trunkline roadways as of 2011.Symbology: The symbology for the Mile Markers is a simple point.Contact: Alonso Uzcategui, uzcateguia@michigan.gov

Reference markers not necessarily exact mile increments

Highway mile post marker locations provided by the TN Department of Transportation (TDOT)

Postmiles is used to display postmile locations on a digital map display, or to query for the purposes of finding a specific location reference by county, route, and postmile. Postmiles are coded with the district, county, route, postmile prefix (if any), postmile, and postmile suffix (if any). The source of data is the Caltrans TSN (Transportation System Network) database. Two additional fields - PMInterval and AlignCode - should be understood by the user for effective use of this data set (refer to the Entity and Attribute Information section of this metadata). PMInterval indicates the interval on which the postmile falls: 0.001, 0.01, 0.1, 1, 5, or 10. This field is handy for drawing a subset of postmiles at desired intervals, for example this Definition Query will tell ArcMap to draw postmiles only at 1 mile intervals: "PMInterval" >= 1 Though the vast majority of postmiles fall on a 0.1 (tenth mile) or larger intervals, postmiles are included that fall on a smaller interval. Examples are the beginning or end of a route or county, or at an equation point. These postmiles can be identified through use of the "HwySegment" field that contains codes of "Begin County", "Begin Segment", "Mid Segment", "End Segment", and "End County". Begins and ends of routes are coded "Begin County" and "End County". A Definition Query that would tell ArcMap to draw postmiles only at 1 mile intervals or the begin of county would be: "PMInterval" >= 1 OR "HwySegment" = 'Begin County'AlignCode indicates if the postmile is on a Right alignment, Left alignment, Right Side of an independent alignment, or Left Side of an independent alignment. Where TSN considers most state highways to have just a centerline, the underlying linework that the postmiles are based upon has a line for each direction. On undivided highways the right and left lines are identical. On divided highways the right and left are separated, but TSN treats the segment as a single centerline. In the last case where highways are not only divided but also have different lengths (where the right and left carriageway diverge around physical obstacles or are separated onto different one-way streets) the underlying linework has dual carriageways, and TSN treats the segment as an "independent alignment". In some cases (especially for small-scale mapping), it may be appropriate to display Postmiles for just one alignment (e.g. Right alignment), and only for the other side where TSN indicates independent right and left alignments. In other cases (e.g. large-scale mapping), it may be appropriate to display Postmiles for both alignments, regardless of how TSN treats the segment. This is an example of a Definition Query that would tell ArcMap to display postmiles at one mile intervals only on the right alignment where TSN indicates just a centerline, and on both right and left alignments where TSN indicates independent alignments: "PMInterval" >= 1 AND "AlignCode" <> 'Left' Similarly, only at 1 mile intervals or beginning of county, and not Left: ("PMInterval" >= 1 OR "HwySegment" = 'Begin County') AND "AlignCode" <> 'Left'The Odometer field represent the actual distance in miles from the start of the highway to the postmile. This is in contrast to the postmile value, which no longer represents this value as each highway is realigned (and made longer or shorter) over time.

Mile markers for select Boulder County roads and CDOT roads. The Boulder County roads were initially selected based on historic precedent, referencing printed maps in the Public Works (formerly Transportation) Department. Markers for more roads may be added after further review. Historic roads included some within municipalities, and mile markers were retained for those roads, regardless of annexations.Mile marker points along County roads were measured using GIS. Each road length was calculated using GIS, depending on accuracy from the Colorado StatePlane coordinate system and then accounting for slope from a 2.5 foot DEM. Markers, every quarter mile, were located along routes using a linear referencing method.Markers on CDOT roads were selected from a feature service owned by them. The selected roads were based on the Road_Map_Roads feature class.Note: Road Maintenance mile posts will be move based on markers in this dataset.

Depicts green mile marker signs that provide approximate mileage along NMDOT owned and maintained routes. Due to construction, vandalism, etc., the locations of milepost signs might be adjusted by NMDOT.Please select Milepost Interval Layers for Downloading Data

This is a vector point file showing mile markers at Great Smoky Mountains National Park (GRSM). Data were collected with GPS and/or aerial photography. Mile markers depict administrative distances on major roads and rivers within the park boundary. Mile markers shown on roads were derived from the Federal Highways Administration Road Inventory Program. To show the location of mile markers at Great Smoky Mountains National Park. The intended use of all data in the park's GIS library is to support diverse park activities including planning, management, maintenance, research, and interpretation. Mile markers are used for reporting purposes for facilities maintenance, as well as depicting locations of unnamed features (e.g. parking lots). Mile markers may not coincide with GPS or odometer information. Mile markers are intended for administrative use only, and should not be used for linear calibration purposes.The corresponding Integration of Resource Management Applications (IRMA) NPS Data Store reference is Great Smoky Mountains National Park Mile Markers.

Mileage Reference Markers (MRMs) for the South Dakota state trunk highway system and state frontage roads. The MRM system is maintained by the South Dakota Department of Transportation, Office of Inventory Management and Research, and contains information related to the mileage along state highways. MRM numbers are not mileages along the highway. This service is updated monthly.

This data contains the location and legend of mileposts markers (signs) on state owned highways.

This feature class contain mile marker points for US Highways located within Chatham County, NC. It also contains mile marker points for Jordan Lake. These point features are utilized within emergency response mapping operations and the data is maintained by the Chatham County E-911 Addressing Specialist.Chatham GIS SOP: "MAPSERV-12"

Highway and Railroad mile posts in Grand County, CO - published 9/28/2023

Table of TxDOT Linear Referencing Methods (LRM) contained in the Geospatial Roadway Inventory Database (GRID). All on-system highways are represented along with their TxDOT Districts, TxDOT Counties, Control Section and Milepoints, Reference Markers and Displacements and Distance From Origins. Mileage Reference Marker Equivalency (MPRME) is useful for translating highway centerline location between the LRMs. Used by the Design Construct Information System (DCIS), TxDOTCONNECT, the Crash Records Information System (CRIS), Pavement Analyst (PA), and the Maintenance Management System (MMS).

Locations of milepost markers along the State Highway System. Mileposts are used to assist with identifying specific locations along a roadway, such as directing maintenance crews to portions of a roadway in need or repair. Note, while ADOT makes every attempt to place mileposts at accurate mile locations, landscapes and other factors may require the markers to be placed slightly off from their true locations. It is recommended that mileposts not be used in projects that require high location accuracy. In those cases, engineering stations may be a more suitable alternative.

Reported Extent: Required for the State Highway System (i.e. all ADOT-owned roads). Optionally recorded for all other roadways.

Key Terms:
ADOT, MPD, 2023 HPMS, 2023, HPMS