The District's Department of Transportation (DDOT) maintains centerline roadway data for all roads and alleys open to traffic. In recent years, the District has improved its centerline data offerings to support a broad array of analyses and information sharing.

Esri ArcGIS Online (AGOL) Hosted Feature Layer for accessing the MDOT SHA Roadway Centerline data product.MDOT SHA Roadway Centerline data consists of linear geometric features which represent the street centerline for roadways throughout the State of Maryland. The centerline represents the geographic location on the roadway between both shoulders (physical center), which often but not always coincides with the center painted line dividing bi-directional travel lanes. Roadway Centerline data plays an important role in transportation management and planning, while also being the basis for all other roadway-related data products.MDOT SHA Roadway Centerline data is the end product of a statewide data sharing process between the Federal Highway Administration (FHWA), Maryland Department of Transportation (MDOT), Maryland Department of Transportation State Highway Administration (MDOT SHA), county governments and local municipal governments. Using a common centerline allows for better exchange of information related to the roadway system and provides opportunities for more efficient collection of information about roadway assets. Some centerlines were created in-house using imagery, GPS data, and MDOT SHA's Highway Performance Monitoring System (HPMS) database and others were received from county governments and updated in house using imagery, GPS data and MDOT SHA's HPMS database. The Centerline data includes annual HPMS updates / improvements submitted to the Federal Highway Administration (FHWA).MDOT SHA Roadway Centerline data is needed for emergency response and management, routing buses and other vehicles, planning for land use and transportation needs, continuity of roadway data and display at county boundaries leading to the same "look and feel" across jurisdictions, tracking assets on and along the roadway network, producing maps at various scales, and numerous other applications. There are opportunities to make these processes more efficient, and this program addresses a shared foundation to solve some of these issues. This data is also used by various business units throughout MDOT, as well as many other Federal, State and local government agencies.MDOT SHA Roadway Centerline data is updated & published on an annual basis for the prior year. This data is for the year 2023.For more information about each attribute field, please review the MDOT SHA Roadway Centerline - Data DictionaryFor more information related to the data, contact MDOT SHA OPPE Data Services Division (DSD):Email: DSD@mdot.maryland.govFor more information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

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 below
Anoka: https://www.anokacounty.us/315/GIS
Carver: gis@co.carver.mn.us
Chisago: gisservices@chisagocountymn.gov
Dakota: gis@co.dakota.mn.us
Hennepin: gis.info@hennepin.us
Isanti: Nate.Kirkwold@co.isanti.mn.us
Ramsey: RCGISMetaData@co.ramsey.mn.us
Sherburne: gis@co.sherburne.mn.us
Scott: gis@co.scott.mn.us
Washington: gis@co.washington.mn.us

Roadway centerlines for all of Fairfax County, Fairfax City, City of Falls Church, City of Alexandria, and Arlington County. It also contains centerlines for a 1-3 mile buffer into Loudoun County and Prince William County.

Maryland Roadway Centerline data consists of linear geometric features which represent the street centerline for all public roadways in the State of Maryland. The centerline represents the geographic location on the roadway between both shoulders (physical center), which often but not always coincides with the center painted line dividing bi-directional travel lanes. Roadway Centerlines data plays an important role in transportation management and planning, while also being the basis for all other roadway related data products.Maryland Roadway Centerline data is the end product of a statewide data sharing process between the Federal Highway Administration (FHWA), Maryland Department of Transportation (MDOT), Maryland Department of Transportation State Highway Administration (MDOT SHA), county governments and local municipal governments. Using a common centerline allows for better exchange of information related to the roadway system and provides opportunities for more efficient collection of information about roadway assets. Some centerlines were created in-house using imagery, GPS data, and MDOT SHA's Highway Performance Monitoring System (HPMS) database and others were received from county governments and updated in house using imagery, GPS data and MDOT SHA's HPMS database. The Centerline data includes annual HPMS updates / improvements submitted to the Federal Highway Administration (FHWA). Maryland Roadway Centerline data is needed for emergency response and management, routing buses and other vehicles, planning for land use and transportation needs, continuity of roadway data and display at county boundaries leading to the same "look and feel" across jurisdictions, tracking assets on and along the roadway network, producing maps at various scales, and numerous other applications. There are opportunities to make these processes more efficient, and this program addresses a shared foundation to solve some of these issues. This data is also used by various business units throughout MDOT, as well as many other Federal, State and local government agencies. Maryland Roadway Centerline data is updated and published on an annual basis for the prior year. This data is for the year 2017. Last Updated: November 2018 (11/28/2018) For questions, contact the MDOT SHA Geospatial Technologies Team:Email: (GIS@mdot.state.md.us)For additional information related to the Maryland Department of Transportation (MDOT):Website: (https://www.mdot.maryland.gov/)For additional information related to the Maryland Department of Transportation State Highway Administration (MDOT SHA):Website: (https://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 Layer Link:https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_RoadCenterlines/MapServer/1

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

Download In State Plane Projection Here. ** The Street Centerline feature class now follows the NG911/State of Illinois data specifications including a StreetNameAlias table. The download hyperlink above also contains a full network topology for use with the Esri Network Analyst extension ** These street centerlines were developed for a myriad of uses including E-911, as a cartographic base, and for use in spatial analysis. This coverage should include all public and selected private roads within Lake County, Illinois. Roads are initially entered using recorded documents and then later adjusted using current aerial photography. This dataset should satisfy National Map Accuracy Standards for a 1:1200 product. These centerlines have been provided to the United States Census Bureau and were used to conflate the TIGER road features for Lake County. The Census Bureau evaluated these centerlines and, based on field survey of 109 intersections, determined that there is a 95% confidence level that the coordinate positions in the centerline dataset fall within 1.9 meters of their true ground position. The fields PRE_DIR, ST_NAME, ST_TYPE and SUF_DIR are formatted according to United States Postal Service standards. Update Frequency: This dataset is updated on a weekly basis.

New Mexico Road Centerline Point data are an aggregated resource for road centerlines across the state. These data are contributed by local governments for NM911 Program purposes.

Roads centerlines in Eaton County, Michigan, USA. This data is updated weekly to reflect new development. Features in this dataset are not typically survey-grade.

(Link to Metadata)(User Guide)(Symbology layer files: aotclass_only.lyr aotclass_surfacetyp.lyr)The Vermont Road Centerline data layer (TransRoad_RDS) contains all town and state highways, as well as many private roads. The centerlines were originally developed under contract by Greenhorne and O'Mara under the guidance of VCGI (1992). VCGI was the original steward of the road centerline data between 1992 and 2004. The Vermont Agency of Transportation (VTrans) is now considered the steward of this data layer. Updates have been performed over the years by VCGI, RPCs, and VTrans. The VT Agency of Transportation has taken over the update and maintenance of the road centerline data layer and has revised the layer to match "Official" highway mileage. NOTE: TransRoad_RDS meets the requirements articulated in the VGIS Road Centerline Data Standard (https://vcgi.vermont.gov/resources/standards).This layer is the most reliable source for official VTrans road class (AOTCLASS) information. However, this layer may not include every private road, and the road name information is not may not match perfectly with the EmergencyE911_RDS data layer. The EmergencyE911_RDS road centerline layer maintained by VT's E911 Board as the most up-to-date roadname information. It was originally based on TransRoad_RDS, and is therefore very similar. However, it includes all private roads and generally more reliable road name and address range information. There was a significant change in the schema in the June 2013 release as part of the effort between VTrans and E911 to merge their two datasets. The data layer includes the field structure agreed to by both entities, but most of the fields that are E911's have not been populated in this release.Stewards: Information Technology, Data Owner: Mapping Unit

This is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. The centerline is a data sharing process between the State Highway Administration (SHA) and local governments. Using a common centerline allows better exchange of information about the roadway system and provides opportunities for more efficient collection of information about that roadway asset. Some centerlines were created in-house using imagery - GPS data - and SHA's HPMS database and others were received from county governments and updated in house using imagery - GPS data and SHA's HPMS. The centerline data includes annual HPMS updates/improvements.This layer has been modified from its original form. Please see lineage section for details. Last Updated: Feature Service Layer Link: https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_RoadCenterlines/MapServer ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

OR-Trans is a GIS road centerline dataset compiled from numerous sources of data throughout the state. Each dataset is from the road authority responsible for (or assigned data maintenance for) the road data each dataset contains. Data from each dataset is compiled into a statewide dataset that has the best available data from each road authority for their jurisdiction (or assigned data maintenance responsibility). Data is stored in a SQL database and exported in numerous formats.

Road segments representing centerlines of all roadways or carriageways in a local government. Typically, this information is compiled from orthoimagery or other aerial photography sources. This representation of the road centerlines supports address geocoding and mapping. It also serves as a source for public works and other agencies that are responsible for the active management of the road network.

GIS representation of the UDOT Route System (main routes, ramps and collectors). Routes are represented as PolylineM features where the m coordinate is in miles. PolylineMs have been calibrated at end points and also some intermediate points as described in the UDOT linear referencing system (LRS) route descriptions for state route junctions, interstate bridge deck (begin and end) and other miscellaneous features.Updated: May 5, 2014

This data layer is an Esri file geodatabase polyline feature class that contains street centerlines maintained by county agencies in Indiana. It was released by the Indiana Geographic Information Office (IGIO) on December 1, 2022. The IGIO compiled the data as part of the Indiana Data Harvest program between the Indiana Geographic Information Council (IGIC) and all Indiana counties to provide the most accurate framework data for the citizens of Indiana. These layers include address points, street centerlines, land parcels, and governmental boundaries.

This dataset contains street centerlines for vehicular and foot traffic in Allegheny County. Street Centerlines are classified as Primary Road, Secondary Road, Unpaved Road, Limited Access Road, Connecting Road, Jeep Trail, Walkway, Stairway, Alleyway and Unknown. A Primary Road is a street paved with either concrete or asphalt that has two (2) or more lanes in each direction. A Secondary Road is a residential type hard surface road, or any hard surface road with only one (1) lane in each direction. An Unpaved Road is any road covered with packed dirt or gravel. A Limited Access Road is one that can only be accessed from a Connecting Road such as an Interstate Highway. A Connecting Road is a ramp connecting a Limited Access Road to a surface street. A Walkway is a paved or unpaved foot track that connects two (2) roads together. Walkways within College Campuses will also be shown. Recreational pedestrian trails and walkways through parks and wooded areas are not considered transportation and will not be digitized during this update. Walkways will not have an Edge of Pavement feature. A Stairway is a paved or wooden structure that connects two (2) roads together. Recreational pedestrian trails and walkways through parks and wooded areas are not considered transportation and will not be digitized during this update. An Alleyway is a road, usually narrower than a Secondary Road that runs between, but parallel to, two (2) Secondary Roads. Generally, Outbuildings will be adjacent to Alleyways. A Jeep Trail is a vehicular trail used for recreation. A Jeep Trail will not have an associated edge of pavement feature. A road coded as Unknown is a road, which in the judgment of the photogrammetrist, does not fall into any of the categories listed. Centerlines will be visually placed between the edges of pavement. One (1) centerline will be placed between each edge of pavement. Roads with medial strips, such as Limited Access Roads, will have two (2) centerlines for those portions of the road where the medial strip is present. For roads that terminate with a cul-de-sac, the centerline shall continue through the center of the cul-de-sac and stop at the edge of pavement. All attribute data will remain for all Street Centerlines that are not updated. For Street Centerlines that are new, the only attribute field that will be populated is the FeatureCode and UPDATE_YEAR. If a Street Centerline is graphically modified, the existing attribute data will remain and the UPDATE_YEAR will be set to 2004. The attribute values for 2004 Street Centerlines should be considered suspicious until verified. The ArcInfo Street Centerline coverage that is being updated has 800 segments of Paper Streets, 66 segments of Vacated Streets and 78 segments of Steps. Street Centerlines that are coded as Paper Streets in the OWNER field will remain unchanged in the updated dataset unless the area has been developed. In the event the area has been developed, the Street Centerlines will be modified to reflect the true condition of the visible roads. Street Centerlines that are coded as Vacated in the OWNER field will also remain unchanged in the updated dataset. In the event the area coinciding with the Vacated Streets has been developed, the Vacated Street Centerlines will be removed in order to reflect the true condition of the area. Street Centerlines that are coded as Steps in the OWNER field will be updated to reflect the current condition of the area. The Street Centerlines dataset consists of an external table that links to the supplied coverages and the Geodatabase created for this project using the "-ID" (UserID) field. In order to maintain the link to the external table and not loose valuable data the decision was made to keep all database information currently in the Street Centerline dataset. When a Street Centerline is modified during the update process, the field "UPDATE_YEAR" is set to 2004. All other database attributes will remain unchanged from the original values. All Street Centerline database data with an "UPDATE_YEAR" of 2004 should be verified before used. In some occasions the Street Centerline was divided into two (2) sections to allow for a new road intersection. Both sections of the resulting Street Centerline will have the same database attributes including Address Range. All new Street Centerlines will have zero (0) for "SystemID" and "UserID". This dataset was previously harvested from Allegheny County’s GIS data portal. The new authoritative source for this data is now the PASDA page (https://www.pasda.psu.edu/uci/DataSummary.aspx?dataset=1224), which includes links to historical versions of the shapefile representations of this data.

description: Road Centerline GIS Data exported from the CIty's GIS. See summary description (txt) file for information about intended use, projection, currency, attributes, etc. This map data layer represents the centerline of roadways for the City of Bloomington, Indiana. It includes source data from the City of Bloomington and Monroe County to create a countywide network. It includes public roads, named private roads, major multi-use trails, and proposed roadways to be constructed. Centerlines outside the City's mapped area may not be positioned accurately.; abstract: Road Centerline GIS Data exported from the CIty's GIS. See summary description (txt) file for information about intended use, projection, currency, attributes, etc. This map data layer represents the centerline of roadways for the City of Bloomington, Indiana. It includes source data from the City of Bloomington and Monroe County to create a countywide network. It includes public roads, named private roads, major multi-use trails, and proposed roadways to be constructed. Centerlines outside the City's mapped area may not be positioned accurately.

This layer contains a geospatial representation of the center of the paved surface of a travel roadway for all public and some private streets in Prince George's County, Maryland. Attributes for the centerline contain street information, routing functionality, and class type. The line work was created from the 1993 1FT aerial imagery and the attributes were entered by CENTECH Inc. This layer is maintained by Prince George's County Office of Information Technology and is primarily used to support the emergency response 911 system as well as other functions for the County agencies. The Spatial Data, and the information therein, is provided "as is" without warranty of any kind, either expressed, implied, or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall Prince George’s County be liable for direct, indirect, incidental, consequential or special damages of any kind. Prince George’s County does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data, nor is there responsibility assumed to maintain the Data in any manner or form. Any data derived from the Data must acknowledge Prince George’s County in the metadata.

This dataset comprises road centerlines for all roads in San Diego County. Road centerline information is collected from recorded documents (subdivision and parcel maps) and information provided by local jurisidictions (Cities in San Diego County, County of San Diego). Road names and address ranges are as designated by the official address coordinator for each jurisidcition. Jurisdictional information is created from spatial overlays with other data layers (e.g. Jurisdiction, Census Tract).The layer contains both public and private roads. Not all roads are shown on official, recorded documents. Centerlines may be included for dedicated public roads even if they have not been constructed. Public road names are the official names as maintained by the addressing authority for the jurisdiction in which the road is located. Official road names may not match the common or local name used to identify the road (e.g. State Route 94 is the official name of certain road segments commonly referred to as Campo Road).Private roads are either named or unnamed. Named private roads are as shown on official recorded documents or as directed by the addressing authority for the jurisdiction in which the road is located. Unnamed private roads are included where requested by the local jurisidiction or by SanGIS JPA members (primarily emergency response dispatch agencies). Roads are comprised of road segments that are individually identified by a unique, and persistent, ID (ROADSEGID). Roads segments are terminated where they intersect with each other, at jurisdictional boundaries (i.e. city limits), certain census tract and law beat boundaries, at locations where road names change, and at other locations as required by SanGIS JPA members. Each road segment terminates at an intersection point that can be found in the ROADS_INTERSECTION layer.Road centerlines do not necessarily follow the centerline of dedicated rights-of-way (ROW). Centerlines are adjusted as needed to fit the actual, constructed roadway. However, many road centerline segments are created intially based on record documents prior to construction and may not have been updated to meet as-built locations. Please notify SanGIS if the actual location differs from that shown. See the SanGIS website for contact information and reporting problems (http://www.sangis.org/contact/problem.html).Note, the road speeds in this layer are based on road segment class and were published as part of an agreement between San Diego Fire-Rescue, the San Diego County Sheriff's Department, and SanGIS. The average speed is based on heavy fire vehicles and may not represent the posted speed limit.

This map data layer represents the centerline of roadways for the City of Bloomington, Indiana. It includes source data from the City of Bloomington and Monroe County to create a countywide network. It includes public roads, named private roads, major multi-use trails, and proposed roadways to be constructed. Attributes for centerlines outside the City of Bloomington are updated from information supplied by Monroe County Planning, Monroe County Public Works, and Ellettsville Planning.