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

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: 08/23/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

This data contains the location and legend of mileposts markers (signs) on state owned highways.This GIS base layer can be used for planning purposes and as a reference layer on standard Oregon Department of Transportation (ODOT) city and county map formats. Full details: https://geohub-oregon-geo.hub.arcgis.com/datasets/oregon-geo::mileposts/about

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.

Right of way mileposts within the Kenai Peninsula Borough. Data sources include Alaska Department of Transportation and KPB staff.

Colorado Highway and Frontage road milepost locations. Mileposts are locations of milepost (mile marker) locations alongside CDOT highways, collected during GPS mapping efforts in the early 2000s. MIleposts differ from milepoints in that milepoints represent the location along CDOT highways where that highway's linear reference system indicates a whole number reference point (such as 57.000). Therefore, mileposts are not necessarily found at exactly at milepoints. Also includes collection date of point, route ID and some GPS locations.

The FRA Milepost is a spatial file that originates of multiple sources and contains point locations of mileposts along the FRA's rail network. The mileposts was developed from varies sources and should only be used as a reference file. The railroad lines and their mileposts are privately owned and are subjected of changed based on the rail owner. If used for identifying specific locations, please contact the railroad to verify the mileposts numbers and their locations.

The purpose of this data set is to provide a geographic representation of the location of each state mile marker sign in the Commonwealth, and is to be used in a number of other products and projects. The locations of state mile marker signs on interstates and primary routes are important sources for various traffic studies as well as information for travelers. This GIS layer displays the locations and corresponding information of state mile marker signs. The signs may have been placed close but not exactly at the mile point due to geographic restrictions.Attribute NameContentsFIDInternal Feature NumberShapeFeature GeometryHTRISDEFHTRIS Definition in the Roadway InventoryROADSIDELocations of Mile Marker Posts (Right, Left, or Median)LATITUDEGPS latitude for each Mile Marker point in decimal degreesLONGITUDEGPS longitude for each Mile Marker point in decimal degreesSIGNSTYLE0: Small & Non-MUTCD Compliant, 1: MUTCD Standard (D10-1, D10-2 or D10-3), 2: MUTCD Enhanced (D10-4 or D10-5)SIGNVALUENumeric Value from the Sign Text except NULL, -1, and -2 valuesSIGNTEXTFull Sign TextM_JURISDICMaintenance Jurisdiction Code

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

The GIS Web Mapping Application is design to have the look and feel as Google Earth. The primary functionality is to provide the user information about FRA's rail lines, rail crossings, freight stations, and mileposting.

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

Reference Post locations on the Nebraska Highways.

Mile Marker was derived from the Flat Sheet Sign feature layer. This dataset contains single points representing the flat sheet signs located on interstates, ramps, state routes, TDOT maintained state park roads, and locally owned NHS routes in Tennessee. This dataset can be queried by either location information, mounting type, sign orientation, sign type, visual condition, or MUTCD code. These records were derived from vehicle mounted LiDAR sensors and digitally captured photos. This information was collected by Mandli Communications, Inc. under the direction of the Asset Management Division and the Long Range Planning Division. Questions on this dataset should be directed to TDOT.Maint.AssetManagement@tn.gov.

This map shows various state routes where outdoor advertising control (OAC) is mandated by both state and federal law. By toggling layers and using pan functions the end-user can quickly identify which routes require OAC. The end-user can also learn where active billboard permits are located and identify permit-related metadata (e.g., sign owner, permit number, highway name, milepost marker, conforming/nonconforming status, and much more).

This service was derived from a multitude of Alaska Department of Transportation & Public Facilities (AKDOT&PF) data elements. Facilities layer contains Harbors, Public Airports, Ferry Terminals, and Maintenance Stations. Mileposts layer contains Milepost markers for the State of Alaska. Milepost data is scale dependent and is only visible at specific scales in the map. Milepost data was derived from our Photolog. Intersection layer contains Non-System Intersections and System Intersections. Intersection data is scale dependent and is only visible at specific scales in the map. Route Classification contains Functional Classification, The National Highway System (NHS), The Alaska Highway System (AHS), and the approved FHWA Urban Area boundaries that have a population greater than 5,000. The census area boundaries that are not included in this data set are as follows : Barrow, Bethel, Eielson AFB, Kenai, Kotzebue, and Nome. Bridge layer contains Bridge Points (mid-point of the bridge decking) and Bridge Lines (total length of bridge). Bridges lines are only available on routes that exist on our LRS network (road centerlines) while Bridge points exist for all bridges in this data set. Road Centerlines contains our Linear Reference System (LRS) routes for the State of Alaska. Jurisdictional Boundaries layer contains the Borough Boundaries, The AKDOT&PF Maintenance Station Boundaries, The AKDOT&PF Maintenance District Boundaries, The AKDOT&PF Region Boundaries, The Alaska State House District Boundaries, and The Alaska State Senate District Boundaries.

Wyoming Roads Data Provided by the Wyoming Department of Transportation (WYDOT). Contact WYDOT directly with questions regrading these data. Refer to README.text and DISCLAIMER.text for data use details. Datasets include county roads, highways, and mileposts.

The National Rail Network (NRWN) is a geometric and attributive description of the Canadian rail network. The NRWN product consists of the features classes: Track Segment, Railway Crossing, Railway Station, Marker Post, Junction and Railway Structure. Descriptive attributes include amongst others: Track Classification, Track Name, Track Operator, Track User, Track Owner, Subdivision Name, Junction Type, Crossing Type, Level of Crossing, Warning System, Transport Canada Identifier, Station Name, Station Type, Station User, Structure Type.

This map displays the boudaries of Capitol Reef Nation Park in 1956. The two 1956 boundaries being compared are the UDOT boundary line, and the Cares Highway line. The old boundaries are highlighted using other map layers such as SITLA land ownership, and milepost markers.