Description: This dataset was created by a joint collaborative project involving the technical and managerial GIS staff from the ten Metropolitan Counties of the Twin Cities in Minnesota (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne and Washington), the Metropolitan Emergency Services Board (MESB), MetroGIS and the Metropolitan Council. Core needs this dataset are intended to satisfy include:- Vehicular routing;- Address geocoding;- Next Generation 911 call routing and location validation;- Emergency services dispatching;- Linear referencing uses;- Cartographic representation of road features;For specific questions regarding centerline alignments or attributes, please contact the county belowAnoka: https://www.anokacounty.us/315/GISCarver: gis@co.carver.mn.usChisago: gisservices@chisagocountymn.govDakota: gis@co.dakota.mn.usHennepin: gis.info@hennepin.usIsanti: Nate.Kirkwold@co.isanti.mn.usRamsey: RCGISMetaData@co.ramsey.mn.usSherburne: gis@co.sherburne.mn.usScott: gis@co.scott.mn.usWashington: gis@co.washington.mn.usFull metadata: https://resources.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metrogis/trans_road_centerlines_gac/metadata/metadata.html
Description: The functional class roads layer contains major roads and highways in the Twin Cities seven county metropolitan area.In 2024, Metropolitan Council staff reviewed the functional class file to ensure parity with the roadscenterlines file from MetroGIS. In its review, staff identified missing segments that should be classified but were missing data. This review ensured parity of roadway segments between the functional class roads layer and the roadscenterlines to ensure completeness.The specific classifications assigned to the roadways resulted from efforts of the Land Transportation Committee, Transportation Technical Advisory Committee and the Transportation Advisory Board as specified in the transportation planning process, using federal rules and guidelines. The final product was approved with Metropolitan Council concurrence.The 'A' minor arterial network was adopted by the Transportation Advisory Board in 1993. As part of a review of functional classification in 2023-2024, 'A' minor arterial designation was modified to simplify the standard. Now, all 'A' Minor Arterials are coded in the following manner:212 ... Minor Reliever213 ... Minor Expander214 ... Minor Connector215 ... Minor Arterial.The 'Other Arterial' designation was retired and those roadway segments were assigned either 212 - Minior Reliever, 213 - Minor Expander, or 214 - Minor Collector.215 - Minor Arterial was added during a 2024 project to realign the file with the roadscenterlines and it applies only to Wright County roads. The reason this applies only to Wright County is because the MetroGIS roadscenterlines file does not contain Wright County.Attributes include functional classification code and road name.Please note that changes to the status of the planned functional class roads MAY impact the classification of this layer. Please confer with Metropolitan Council staff if you have questions.Full metadata: https://resources.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metc/trans_fnctnl_cls_rds/metadata/metadata.html
Description: The Regional Bicycle Transportation Network (RBTN) dataset was created by the Metropolitan Council for the 2040 Transportation Policy Plan (TPP). The RBTN is represented by two map layers including alignments and corridors. Alignments represent existing or proposed bicycle paths and bike corridors represent areas where bicycle path alignments are yet to be determined. Both corridor and alignment layers can be classified into tiers. Tier 1 Alignments/Corridors have higher priorities than Tier 2 Alignments/Corridors. This is the RBTN Alignment and Corridor file used in the 2023 Regional Solicitation Grant process and includes an alignment of the planned Gold Line Transitway bike facility.Full metadata: https://resources.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metc/trans_regional_bike_trans_netwrk/metadata/metadata.html
Description: Transportation Policy Plan (TPP) 2050 RBTN Corridors is a copy developed from the original RBTN Corridors dataset published for the 2040 TPP. This version will not be edited or updated further. To find up to date data, see http://gisdatacatalog/home/index/RBTNCorridors.The Regional Bicycle Transportation Network (RBTN) dataset was created by the Metropolitan Council for the 2040 Transportation Policy Plan (TPP). The RBTN is represented by two map layers including alignments and corridors. Alignments represent existing or proposed bicycle paths and bike corridors represent areas where bicycle path alignments are yet to be determined. Both corridor and alignment layers can be classified into tiers. Tier 1 Alignments/Corridors have higher priorities than Tier 2 Alignments/Corridors. This is the RBTN Alignment and Corridor file used in the 2023 Regional Solicitation Grant process and includes an alignment of the planned Gold Line Transitway bike facility.This data can be seen in the Bike Investment Plan Chapter, and appears in one figure titled "Regional Bicycle Transportation Network". Associated datasets include RBTN Alignments and RBTN Destinations.This data are for planning purposes and should be used at a regional level. Data subject to any amendments of the TPP.Full metadata: https://resources.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metc/trans_tpp2050/metadata/metadata.html
Description: Transportation Policy Plan (TPP) 2050 Active Railroads was developed as part of the 2050 TPP, published 2024.This data can be seen in the Freight Investment Chapter, and appears in one figure titled "Metropolitan Freight System". Associated dataset includes Freight Terminal Types.This dataset originally comes from the Rail Route Network dataset published by the Minnesota Department of Transportation (MnDOT), to represent all active rail routes - meaning not abandoned or tracks removed - in Minnesota. The data has been clipped to the extent for the Metropolitan Planning Organization (MPO) for use in the 2050 TPP. For more information on the original dataset, please see: https://mndot.maps.arcgis.com/home/item.html?id=a28a3f24ef0d43cf96772f86e6707639This data are for planning purposes and should be used at a regional level. Data subject to any amendments of the TPP.The data determinations were made on a subjective basis by managers at Metropolitan Transportation Services.Full metadata: https://resources.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metc/trans_tpp2050/metadata/metadata.html
Description: This file shows the most current Metropolitan Council Transportation Analysis Zone (TAZ) 2020-2040 forecasts for cities and townships within the 7-County Metropolitan Area. The TAZ system in this shapefile is the most recent, official TAZ system (with 3,030 zones).This shapefile title has been renamed; the previous name was Transportation Analysis Zones (TAZ) 2010 with Current ForecastsNote: Forecasts for the older TAZ system with 1,566 zones are available in the Transportation Analysis Zones (Legacy TAZ System w/1,566 Zones) with Current Forecasts shapefile.IMPORTANT NOTES:These TAZ forecasts will change multiple times over the next few years.The Metropolitan Council will ask cities and townships to allocate their TAZ forecasts as part of their 2018 Comprehensive Plan Update (go to http://www.metrocouncil.org/Handbook/Plan-Elements/Transportation.aspxfor more information about this process). Communities may also revise their current TAZ forecasts before the 2018 Comprehensive Plan Update. In the meantime, the Council provides these Current TAZ forecasts for transportation planning.If you are using TAZ forecasts for analysis and/or transportation planning, please download the latest version of this shapefile to ensure you are using the most up-to-date data.If you represent a community that wants to revise your TAZ forecasts, please contact your community's sector representative or Dennis Farmer (see contact information at the end of this document).Full metadata: https://resources.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metc/trans_anlys_zones_offical_curent/metadata/metadata.html
Description: Transportation Policy Plan (TPP) 2050 Transit Market Areas was developed as part of the 2050 TPP, published 2024. Data was edited April 2025 to correct data error and fill in water features.This data can be seen in the Transit Investment Chapter, and appears in one figure titled "Transit Market Areas". Associated dataset includes Freestanding Town Centers.Block groups are separated into the five Transit Market Areas (TMA) based on transit market index values. Market Area 1 indicates the highest potential for transit ridership, while Market Area 5 indicates lowest potential transit ridership. These typically also coordinate with higher density urban centers and corridors, and rural and smaller communities, respectively.The transit market index (TMI) is a prediction of transit passenger activity that can be expected based on population, employment, and the built environment. The Met Council, in coordination with regional partners, uses this index to create the transit market area map that communicates the places in the region where different levels of transit service may be appropriate. More information on how the Transit Market Index is calculated can be found in the Transit Design and Performance Guidelines Appendix of the TPP.This data are for planning purposes and should be used at a regional level. Data subject to any amendments of the TPP.The data determinations were made on a subjective basis by managers at Metropolitan Transportation Services and Metro Transit.Full metadata: https://resources.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metc/trans_tpp2050/metadata/metadata.html
Description: Transportation Policy Plan (TPP) 2050 Freestanding Town Centers was developed as part of the 2050 TPP, published 2024This data can be seen in the Transit Investment Chapter, appearing in a figure titled "Transit Market Areas". Associated dataset includes Transit Market Areas.This data are for planning purposes and should be used at a regional level. Data subject to any amendments of the TPP.The data determinations were made on a subjective basis by managers at Metropolitan Transportation Services and Metro Transit.Full metadata: https://resources.gisdata.mn.gov/pub/gdrs/data/pub/us_mn_state_metc/trans_tpp2050/metadata/metadata.html