This data set shows the centerlines of all public and some private roads within the state of Minnesota. Segments of pavement may have only one route or muitple routes traveling over them. One route will always be idenflied as primary and all attributes of these roadways signed to it. Other routes sharing the same pavement will be consisted co-incident or secendary and will not be a signed roadway attributes.

State highways are divided into segments called control sections for record keeping, maintenance, construction, and other administrative purposes. The four-digit control section number is composed of the two-number county code and an identifying two-digit number within that county. Control sections are revised due to jurisdictional transfers (typically from state to county) when new highway segments or entirely new state highways are built.

Routes State AID represent road centerlines for all state aid routes within the state of Minnesota.

Check other metadata records in this package for more information on routes centerlines.


Links to ESRI Feature Services:

Coincident Routes in Minnesota: Coincident Routes

MnDOT Control Sections: MnDOT Control Sections

MnDOT Roadway Routes in Minnesota: MnDOT Roadway Routes

Primary Routes in Minnesota: Primary Routes

State Aid Routes in Minnesota: State Aid Routes

Trunk Highways in Minnesota: Trunk Highways

This set of GeoTIFF and EPPL7 files represents the Minnesota Department of Transportation's County Highway Map Series in georeferenced image formats. These images of the standard Mn/DOT County Highway Map product can be used in GIS systems and overlayed with other GIS information. The origin of this data is Mn/DOT's Microstation CAD system, where all linework, feature type coding, and symbolization is stored and updated. To produce these data sets, Mn/DOT exported the data from Microstation into postscript files. LMIC then imported the data into GIS systems for georeferencing and further processing. The GeoTIFF data are distributed in both County Highway Map map sheet and full county extents; EPPL7 data sets are distributed only as full county files. Map collars have been removed. This data set represents the Mn/DOT County Highway Map as of January 1, 2002.

DCGIS is an interactive map that provides increased functionality for advanced users as well as access to about 150 layers of GIS data, including parcel information, contour lines, aerial photography, county park amenities, park trails, bikeways, county road construction, roundabouts, floodplains and more. It allows you to create a map at any scale you wish.
The Interactive GIS Map is intended for use on any device - mobile or desktop - with high speed access.

Functional Road Classification map showing road classifications within Scott County.

This map of Minnesota cities, townships, and counties was published by MnGeo in January 2019. The primary data set for the map is the "Cities, Townships, and Unorganized Territories" (MnCTU) data maintained by the Minnesota Department of Transportation. Other reference data on the map include County Seats and Other Cities, County Boundaries, Interstate, US Trunk, and State Trunk Highways, Major Rivers, Lakes, County and State Boundaries. The download is a PDF file with embedded layers that can be printed at E-scale (36" x 48").

Description based on: 1932 sheet.; Each sheet lists the Commissioner of highways and the Chief Engineer.; On verso: Distance tables for various cities in Minnesota. on sheet 56 x 43 centimeters or smaller Scale approximately 1:1,530,000 Minnesota Transportation Maps

This map shows a 5-mile buffer around strategic highways in Minnesota.

The regional bikeways dataset was created by the Minnesota Dept of Transportation (MNDOT) in 2003. It has been maintained and updated by the Land Management Information Center (LMIC) through contract with the Metropolitan Council.

Dataset includes bicycle routes within nine Twin Cities metropolitan counties: Anoka, Carver, Chisago, Dakota, Hennepin, Ramsey, Scott, Washington, and Wright. The bikeways are from a number of sources including the Metro Bicycle Network map book (2001), supplemented by information from maps published by city, state, county and regional government agencies, and city and county planning maps. The map shows on-road and off-road bikeways, proposed and existing bikeways, and includes bike lanes, bike-able road shoulders, and trails.

The majority of the bikeways follow road centerlines of the MNDOT BaseMap 2002-Roads. A description of the bikeways attributes and sources of data are included in Section 5 of this document - Entity and Attribute Overview.

Detailed highway map of Scott County. This is the front of the map showing the locations of highways, townships, lakes, rivers, etc...

description: The TRSQ digital data set represents the Township, Range, Section, Quarter section, and Quarter-quarter section divisions of the state. Beginning in the late 1840s, the federal government began surveying Minnesota as part of the Public Land Survey System (PLSS). The resulting network of land survey lines divided the state into townships, ranges, sections, quarter sections, quarter-quarter sections and government lots, and laid the groundwork for contemporary land ownership patterns. The quarter-quarter section remains an important subdivision for rural Minnesota since these lines are used to define local boundaries, roads, and service areas. All survey lines were extended across water bodies despite the fact that U.S. Geological Survey (USGS) base maps depict them only on land. This addition allows all sections and townships to be represented as closed areas ensuring that township and range location can be determined for any point in the state. It also means that the data is not affected if lake levels change over time. The township, range and section boundaries were digitized at MnGeo (formerly the Land Management Information Center - LMIC) from the USGS 30' x 60' map series (1:100,000-scale). Quarter section and quarter-quarter section subdivisions were calculated using the section lines. They were not digitized from original plat book survey lines or from the meandered lines that surveyors laid out around water bodies. The existence of government lots within a quarter-quarter section is recorded in the data set; however, the government lot boundaries were not digitized. If a quarter-quarter section contains more than one government lot, the number of lots is recorded -- see Lineage, Section 2, for more detail. Note: For most uses, TRSQ has been superseded by the Minnesota Department of Natural Resources (DNR) 1:24,000-scale 'Control Point Generated PLS' data set which is free online. See https://gisdata.mn.gov/dataset/plan-mndnr-public-land-survey for more information. Also, many county surveyors offices have more accurate PLS (Public Land Survey) data sets. For county webpages and contact information, see http://www.mngeo.state.mn.us/cty_contacts.html .; abstract: The TRSQ digital data set represents the Township, Range, Section, Quarter section, and Quarter-quarter section divisions of the state. Beginning in the late 1840s, the federal government began surveying Minnesota as part of the Public Land Survey System (PLSS). The resulting network of land survey lines divided the state into townships, ranges, sections, quarter sections, quarter-quarter sections and government lots, and laid the groundwork for contemporary land ownership patterns. The quarter-quarter section remains an important subdivision for rural Minnesota since these lines are used to define local boundaries, roads, and service areas. All survey lines were extended across water bodies despite the fact that U.S. Geological Survey (USGS) base maps depict them only on land. This addition allows all sections and townships to be represented as closed areas ensuring that township and range location can be determined for any point in the state. It also means that the data is not affected if lake levels change over time. The township, range and section boundaries were digitized at MnGeo (formerly the Land Management Information Center - LMIC) from the USGS 30' x 60' map series (1:100,000-scale). Quarter section and quarter-quarter section subdivisions were calculated using the section lines. They were not digitized from original plat book survey lines or from the meandered lines that surveyors laid out around water bodies. The existence of government lots within a quarter-quarter section is recorded in the data set; however, the government lot boundaries were not digitized. If a quarter-quarter section contains more than one government lot, the number of lots is recorded -- see Lineage, Section 2, for more detail. Note: For most uses, TRSQ has been superseded by the Minnesota Department of Natural Resources (DNR) 1:24,000-scale 'Control Point Generated PLS' data set which is free online. See https://gisdata.mn.gov/dataset/plan-mndnr-public-land-survey for more information. Also, many county surveyors offices have more accurate PLS (Public Land Survey) data sets. For county webpages and contact information, see http://www.mngeo.state.mn.us/cty_contacts.html .

Current 511 Events for Minnesota. This data is updated every 10 minutes. This layer is provided as a courtesy from Iowa DOT for use by Iowa DOT web mapping applications. Iowa DOT does not take responsibility for its accuracy or completeness. Please visit Minnesota 511 for up-to-date conditions.

The vector data is updated utilizing positions calculated from plats using coordinate geometry programs. Plated, Public road centerlines are captured within this database. Private roads may not be shown.

The centerlines usually represent the center of the physical roadway pavement. The center of physical roadway pavement may or may not represent the center of the road right of way. Road right of ways may taper or change width.

This file has been further modified using several sources including survey field data and digitizing off aerial photos. Attributes have been included to allow geo-coding and the support of Washington County Sheriff's Office Communication Center. Regional Data is available through the MN Geocommons. https://gisdata.mn.gov/dataset/us-mn-state-metrogis-trans-road-centerlines-gac

Roads within Carlton County, MN. Data updated on an as needed basis.

Roads administered by the Commissioner of Natural Resources to provide access to lands administered by the Division of Forestry. These roads are generally open to the public for recreational use. Some of the segments in this shapefile are components of County administered forest road systems which cross State land. State Forest Roads are classified as either system roads or minimum maintenance roads. System roads are generally well maintained and capable of supporting low-clearance highway licensed vehicles. Minimum maintenance roads are not capable of sustaining routine traffic by highway licensed vehicles. They are posted with signs which state "Road may be impassable. Travel at your own risk".

This map layer represents roadways under the jurisdiction of Cook County, MN.

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

Images that come from the Snow Plow Dash Camera of Minnesota DOT Plows. This service only provides a portion of all the photos taken while Minnesota DOT vehicles are working around the state.Data provided by the Minnesota DOT. Minnesota DOT Disclaimer

AADT represents current (most recent) Annual Average Daily Traffic on sampled road systems. This information is displayed using the Traffic Count Locations Active feature class as of the annual HPMS freeze in January. Historical AADT is found in another table. Please note that updates to this dataset are on an annual basis, therefore the data may not match ground conditions or may not be available for new roadways. Resource Contact: Christy Prentice, Traffic Forecasting & Analysis (TFA), http://www.dot.state.mn.us/tda/contacts.html#TFA

Check other metadata records in this package for more information on Annual Average Daily Traffic Locations Information.


Link to ESRI Feature Service:

Annual Average Daily Traffic Locations in Minnesota: Annual Average Daily Traffic Locations

The Geodetic Database contains information on permanent geodetic control marks located in Minnesota or just outside its boundaries. Permanent geodetic control marks are established for the purpose of providing precise horizontal and vertical control positions for the registration of surveying and mapping activities in the local area. Information about the location of an object based on its geodetic location locates that object in a worldwide geographic information system. The marks have unique identification and year established stamped on the monument disk, usually an 89 mm (3.5 inch) diameter brass or aluminum disk. Monuments consist of material (concrete or metal) that is meant to stay in place for 50 to 100 years or more, and have little or no movement due to frost action or activity near the monument. The marks have been established by all levels of government in Minnesota, and they are referenced to the National Geodetic Reference System (NAD 1927, NAD 1983, NGVD 1929, and NAVD 1988). The Federal Government supports monumentation at the state level by providing technical expertise, adjustments of the data, and maintenance of the National Geodetic Reference System through its State Advisor Program.

Measurements were taken from roadway construction plan typical sections and confirmed using the measuring tool in ArcGIS. A single line segment was drawn down the county road centerline to represent areas where shoulders are 3 feet or wider. There are two fields within the attribute information which represent the left and right shoulder widths (in feet). The left and right shoulder widths were determined by working from west to east and from south to north. Any areas where the shoulder was less than 3 feet on both side of the road were not included within this mapping file.