Esri ArcGIS Online (AGOL) Hosted Feature Layer which provides access to the MDOT SHA District Boundaries data product.MDOT SHA District Boundaries data consists of polygon geometric features which represent the geographic area & extent (boundary) of each MDOT SHA District throughout the State of Maryland. Each MDOT SHA District includes multiple Maryland Counties. There are a total of seven MDOT SHA Districts (District 1 - District 7) throughout the State of Maryland. MDOT SHA District Boundaries data was generated using geometry from Maryland's political county boundaries. MDOT SHA District Boundaries data is used by various transportation business units throughout MDOT, as well as many other Federal, State & local government agencies. MDOT SHA District Boundaries data is key to understanding the geographic area & extent (boundary) of each MDOT SHA District throughout the State of Maryland. MDOT SHA District Boundaries data is updated and published on an As-Needed basis, as this data does not frequently change.For additional information, contact the MDOT SHA OIT Enterprise Information Services: Email: GIS@mdot.maryland.gov

MDOT SHA District Boundaries data consists of polygon features which represent the boundaries of each Maryland Department of Transportation State Highway Administration (MDOT SHA) District. Each MDOT SHA District includes multiple Maryland Counties. There are a total of seven MDOT SHA Districts (District 1 - District 7) throughout the State of Maryland. MDOT SHA District Boundaries data was generated using geometry from Maryland's political county boundaries. MDOT SHA District Boundaries data is maintained by the Maryland Department of Transportation State Highway Administration (MDOT SHA), under the Office of Planning and Preliminary Engineering (OPPE) Data Governance Division (DSD). MDOT SHA District Boundaries data is used by various modules throughout MDOT, as well as many other Federal, State and local government agencies. MDOT SHA District Boundaries data is key to understanding and identfying the geographic extent for each MDOT SHA District. MDOT SHA District Boundaries data is updated and published on an As-Needed basis, as this data does not frequently change. This data was last updated in December 2017. For questions, contact MDOT SHA Geospatial Technologies: (GIS@sha.state.md.us)

Esri ArcGIS Online (AGOL) Hosted Feature Layer which provides access to the MDOT SHA Maintenance Shop Boundaries data product.MDOT SHA Maintenance Shop Boundaries data consists of polygon geometric features which represent the geographic area of responsibility for each MDOT SHA Maintenance Shop Facility throughout the State of Maryland. MDOT SHA Maintenance Shop Facility Boundaries data is used by various transportation business units throughout the Maryland Department of Transportation (MDOT), as well as many other Federal, State & local government agencies. This data is key to understanding and visualizing the geographic area of maintenance responsibility for MDOT SHA Maintenance Shop Facilities throughout the State of Maryland. MDOT SHA Maintenance Shop Boundaries data is owned by the MDOT SHA Office of Maintenance (OOM). This data is updated & published on an As-Needed basis, as it does not frequently or regularly change. However, as of February 2024, this data product was updated as part of a data quality assurance / quality control process in preparation for the MDOT SHA Asset Management Office (AMO) and their future management of MDOT asset data.For additional information, contact the MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Polygon features that represent the political boundaries of Metropolitan Planning Organizations (MPO) that exist in Maryland and for which the Maryland Department of Transportation (MDOT) is a member. In several instances, these MPO boundaries extend beyond Maryland’s borders into neighboring states as well as the District of Columbia. MPO Boundaries’ data includes information on each boundary's name, geographic location, and the total size / extent of each area. MPO Boundaries data was intended to be used for planning purposes within governments at the National and State level. Maryland's MPO Boundaries data is a sub-set of the U.S. Department of Transportation (USDOT) Office of the Assistant Secretary for Research and Technology's Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). A metropolitan planning organization (MPO) is a federally-mandated and federally-funded transportation policy-making organization that is made up of representatives from local governments and governmental transportation authorities. Federal law requires the formation of an MPO for any urbanized area (UZA) with a population greater than 50,000. Federal funding for transportation projects and programs are channeled through this planning process. Congress created MPOs to ensure that existing and future expenditures of federal funds for transportation projects and programs are based on a continuing, cooperative, and comprehensive (“3‑C”) planning process. MPOs are charged with developing a 20-year long-range transportation plan (LRTP) and a short-term (usually 2-6 years) program called the transportation improvement program (TIP) for each of their respective regions. The seven MPOs of which Maryland jurisdictions and agencies are members are listed below. The Maryland member jurisdictions are listed under each MPO (note that some MPOs cover multi-State regions). The Maryland Department of Transportation is a member of each of the MPOs listed. Maryland's MPOs are as follows: National Capital Region Transportation Planning Board (TPB), Baltimore Regional Transportation Board (BRTB), Cumberland Area Metropolitan Planning Organization (CAMPO), Hagerstown/Eastern Panhandle Metropolitan Planning Organization (HEPMPO), Wilmington Area Planning Council (WILMAPCO), Salisbury/Wicomico Metropolitan Planning Organization (S/WMPO), and Calvert-St. Mary’s Metropolitan Planning Organization (C-SMMPO). Maryland's MPO Boundaries data is owned and maintained by the Transportation Secretary's Office (TSO) of the Maryland Department of Transportation (MDOT). Being a subset of the USDOT's NTAD, an annual update of Maryland's MPO Boundaries data is performed by TSO in close coordination with each MPO, the Maryland Department of Transportation State Highway Administration (MDOT SHA) and the Federal Highway Administration (FHWA). MPO Boundaries data is a strategic resource for the USDOT, FHWA, MDOT, as well as many other National, State, and local government agencies. Maryland's MPO Boundaries data is updated on an annual basis. For additional MPO information, contact MDOT's Office of Planning and Capital Programming (MDOTGIS@mdot.state.md.us) For additional data information, contact the MDOT SHA Geospatial Technologies Team (GIS@sha.state.md.us)

This dataset shows the 36 facilities of the State Highway Administration (SHA), including maintenance offices, landscape depots, and district offices, as well as the SHA Headquarters in Baltimore City and Hanover Complex.

This is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. In 1993 - the Maryland Department of Planning and the Maryland State Highway Administration entered into a Data Base Usage Agreement with Bell Atlantic and Data Chromatics - Inc. to develop an enhanced street address map for Maryland. ZIP Code boundary area files were one of the products derived from this partnership. The resulting boundary area files were intended to improve the cartographic quality and accuracy of the ZIP code boundary area files derived from the U.S. Census Bureau's post 1990 Census TIGER\Line Files (based on the Census Bureau's ZIP code tabulation areas - ZCTAs). Subsequent iterative improvements to the ZIP Code boundary area files have been made using premise address information associated with mapped parcel records as provided in the Maryland Department of Planning's MdProperty View GIS tax map and parcel record DVD product. The resulting files are meant to serve as a good approximation"" of ZIP codes as polygons (which in reality they are not) but are not official ZIP Code maps and are not meant to be a substitute for any products offered by the U.S. Postal Service - the official source for ZIP code information. While there are no restrictions on their use we do recommend that they are best used with MdProperty View and that MDP makes no guarantee or warranty regarding the files. Last Updated: 2012Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/FeatureServer 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.

Roadway Functional Classification consists of linear features which specifically show the functional classification of public roadways in the State of Maryland. Roadway Functional Classification is defined as the role each roadway plays in moving vehicles throughout a network of highways. Roadway Functional Classification is primarily used for general planning purposes, and for Federal Highway Administration (FHWA) Highway Performance Monitoring System (HPMS) annual submission & coordination. The Maryland Department of Transportation State Highway Administration (MDOT SHA) currently reports this data only on the inventory direction (generally North or East) side of the roadway. Roadway Functional Classification data is not a complete representation of all roadway geometry.Maryland's roadway system is a vast network that connects places and people within and across county borders. Planners and engineers have developed elements of this network with particular travel objectives in mind. These objectives range from serving long-distance passenger and freight needs to serving neighborhood travel from residential developments to nearby shopping centers. The functional classification of roadways defines the role each element of the roadway network plays in serving these travel needs. ​ Over the years, functional classification has come to assume additional significance beyond its purpose as a framework for identifying the particular role of a roadway in moving vehicles through a network of highways. Functional classification carries with it expectations about roadway design, including its speed, capacity and relationship to existing and future land use development. Federal legislation continues to use functional classification in determining eligibility for funding under the Federal-aid program. Transportation agencies describe roadway system performance, benchmarks and targets by functional classification. As agencies continue to move towards a more performance-based management approach, functional classification will be an increasingly important consideration in setting expectations and measuring outcomes for preservation, mobility and safety.Roadway Functional Classification 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 business units throughout MDOT, as well as many other Federal, State and local government agencies. Roadway Functional Classification data is key to understanding the role each roadway plays in moving vehicles throughout Maryland's network of highways.Roadway Functional Classification data is updated and published on an annual basis for the prior year. This data is for the year 2017. View the most current Roadway Functional Classification data in the MDOT SHA Roadway Functional Classes Application For additional information, contact the MDOT SHA Geospatial TechnologiesEmail: GIS@mdot.state.md.usFor additional information related to the Maryland Department of Transportation (MDOT):https://www.mdot.maryland.gov/For additional information related to the Maryland Department of Transportation State Highway Administration (MDOT SHA):https://roads.maryland.gov/Home.aspxMDOT 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.Map Service Link:https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_HighwayPerformanceMonitoringSystem/MapServer/2

This dataset is the Maryland ZIP codes based on the most current MD PropertyView data. In 1993, the Maryland Department of Planning and the Maryland State Highway Administration entered into a Data Base Usage Agreement with Bell Atlantic and Data Chromatics, Inc. to develop an enhanced street address map for Maryland. Zip Code boundary area files were one of the products derived from this partnership. The resulting boundary area files were intended to improve the cartographic quality and accuracy of the zip code boundary area files derived from the U.S. Census Bureau's post 1990 Census TIGER\Line Files (based on the Census Bureau's zip code tabulation areas, ZCTAs). Subsequent iterative improvements to the Zip Code boundary area files have been made using premise address information associated with mapped parcel records as provided in the Maryland Department of Planning's MdProperty View GIS product. The resulting files are meant to serve as a "good approximation" of zip codes as polygons (which in reality they are not) but are not official Zip Code maps and are not meant to be a substitute for any products offered by the U.S. Postal Service, the official source for zip code information. While there are no restrictions on their use we do recommend that they are best used with MdProperty View and that MDP makes no guarantee or warranty regarding the files. For information on the date of the data to each jurisdiction's corresponding MdProperty View edition, see the production schedule located here: https://res1planningd-o-tmarylandd-o-tgov.vcapture.xyz/Documents/OurProducts/PropertyMapProducts/Sched.pdf.

Polygon features that represent the political boundaries of Metropolitan Planning Organizations (MPO) that exist in Maryland and for which the Maryland Department of Transportation (MDOT) is a member. In several instances, these MPO boundaries extend beyond Maryland’s borders into neighboring states as well as the District of Columbia. MPO Boundaries’ data includes information on each boundary's name, geographic location, and the total size / extent of each area. MPO Boundaries data was intended to be used for planning purposes within governments at the National and State level. Maryland's MPO Boundaries data is a sub-set of the U.S. Department of Transportation (USDOT) Office of the Assistant Secretary for Research and Technology's Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). A metropolitan planning organization (MPO) is a federally-mandated and federally-funded transportation policy-making organization that is made up of representatives from local governments and governmental transportation authorities. Federal law requires the formation of an MPO for any urbanized area (UZA) with a population greater than 50,000. Federal funding for transportation projects and programs are channeled through this planning process. Congress created MPOs to ensure that existing and future expenditures of federal funds for transportation projects and programs are based on a continuing, cooperative, and comprehensive (“3‑C”) planning process. MPOs are charged with developing a 20-year long-range transportation plan (LRTP) and a short-term (usually 2-6 years) program called the transportation improvement program (TIP) for each of their respective regions. The seven MPOs of which Maryland jurisdictions and agencies are members are listed below. The Maryland member jurisdictions are listed under each MPO (note that some MPOs cover multi-State regions). The Maryland Department of Transportation is a member of each of the MPOs listed. Each of the listed member jurisdictions has a different level of involvement with its MPO.Maryland's MPOs are as follows: National Capital Region Transportation Planning Board (TPB)https://www.mwcog.org/tpb/- Charles County, Maryland- Frederick County, Maryland- Montgomery County, Maryland- Prince George's County, Maryland- City of Bowie, Maryland- City of College Park, Maryland- City of Frederick, Maryland- City of Gaithersburg, Maryland- City of Greenbelt, Maryland- City of Laurel, Maryland- City of Rockville, Maryland- City of Takoma Park, Maryland- Maryland Department of Transportation (MDOT)Baltimore Regional Transportation Board (BRTB)https://baltometro.org/- Anne Arundel County, Maryland- Baltimore County, Maryland- Carroll County, Maryland- Harford County, Maryland- Howard County, Maryland- Queen Anne's County, Maryland- City of Annapolis, Maryland- City of Baltimore, Maryland- Maryland Department of Transportation (MDOT)Cumberland Area Metropolitan Planning Organization (CAMPO)https://alleganygov.org/473/Metropolitan-Planning-Organization- Allegany County, Maryland- City of Cumberland, Maryland- City of Frostburg, Maryland- Maryland Department of Transportation (MDOT)Hagerstown / Eastern Panhandle Metropolitan Planning Organization (HEPMPO)https://www.hepmpo.net/- Washington County, Maryland- City of Hagerstown, Maryland- Maryland Department of Transportation (MDOT)Wilmington Area Planning Council (WILMAPCO)https://www.wilmapco.org/- Cecil County, Maryland- Maryland Department of Transportation (MDOT)Salisbury / Wicomico Metropolitan Planning Organization (S / WMPO)https://www.swmpo.org/- Wicomico County, Maryland- City of Fruitland, Maryland- City of Salisbury, Maryland- Town of Delmar, Maryland- Maryland Department of Transportation (MDOT)Calvert-St. Mary’s Metropolitan Planning Organization (C - SMMPO)https://www.calvert-stmarysmpo.com/- Calvert County, Maryland- St. Mary's County, Maryland- Maryland Department of Transportation (MDOT)Maryland's MPO Boundaries data is owned and maintained by the Transportation Secretary's Office (TSO) of the Maryland Department of Transportation (MDOT). Being a subset of the USDOT's NTAD, an annual update of Maryland's MPO Boundaries data is performed by TSO in close coordination with each MPO, the Maryland Department of Transportation State Highway Administration (MDOT SHA) and the Federal Highway Administration (FHWA). MPO Boundaries data is a strategic resource for the USDOT, FHWA, MDOT, as well as many other Federal, State, and local government agencies. Maryland's MPO Boundaries data is updated on an annual basis. For additional MPO information, contact MDOT's Office of Planning and Capital Programming:MDOTGIS@mdot.state.md.usFor additional data information, contact the MDOT SHA Geospatial Technologies Team:GIS@sha.state.md.usFor additional information related to the Maryland Department of Transportation (MDOT):https://www.mdot.maryland.gov/For additional information related to the Maryland Department of Transportation State Highway Administration (MDOT SHA):https://www.roads.maryland.gov/This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/BusinessEconomy/MD_IncentiveZones/FeatureServer/13

This dataset is the Maryland ZIP codes based on the most current MD PropertyView data. In 1993, the Maryland Department of Planning and the Maryland State Highway Administration entered into a Data Base Usage Agreement with Bell Atlantic and Data Chromatics, Inc. to develop an enhanced street address map for Maryland. Zip Code boundary area files were one of the products derived from this partnership. The resulting boundary area files were intended to improve the cartographic quality and accuracy of the zip code boundary area files derived from the U.S. Census Bureau's post 1990 Census TIGER\Line Files (based on the Census Bureau's zip code tabulation areas, ZCTAs). Subsequent iterative improvements to the Zip Code boundary area files have been made using premise address information associated with mapped parcel records as provided in the Maryland Department of Planning's MdProperty View GIS product. The resulting files are meant to serve as a "good approximation" of zip codes as polygons (which in reality they are not) but are not official Zip Code maps and are not meant to be a substitute for any products offered by the U.S. Postal Service, the official source for zip code information. While there are no restrictions on their use we do recommend that they are best used with MdProperty View and that MDP makes no guarantee or warranty regarding the files. For information on the date of the data to each jurisdiction's corresponding MdProperty View edition, see the production schedule located here: https://planning.maryland.gov/Documents/OurProducts/PropertyMapProducts/Sched.pdf.

Esri ArcGIS Online (AGOL) Hosted Tile Layer which provides access to the MDOT SHA Context Zones data product.MDOT SHA Context Zones data consists of polygon geometric features which represent the geographic boundary of areas with related land use context throughout the State of Maryland. Context Zones are defined as Urban Core (Zone A), Urban Center (Zone B), Suburban Activity Center / Traditional Town Center (Zone C), Suburban (Zone D), & Rural (Zone E). MDOT SHA Context Zones data is owned & maintained by the MDOT SHA Office of Planning & Preliminary Engineering (OPPE) and the MDOT SHA Office of Highway Development (OHD) . This data is updated every decade (ten years) with the release of new Census information. This data was created in November 2018. For more information on Context Zones, view the MDOT SHA Context GuideFor questions related to Context Zones, contact the MDOT SHA Context Guide LiaisonsFor additional information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Esri ArcGIS Online (AGOL) Hosted, View Feature Layer for accessing the MDOT SHA Facilities data product.MDOT SHA Facilities data consists of point geometric features which represent the geographic locations of MDOT SHA Facilities throughout the State of Maryland. Facility types included are Headquarters, Complexes, District Offices, Maintenance Shops & Landscape Depots.MDOT SHA Facilities data is maintained by the MDOT SHA OIT Enterprise Information Services. MDOT SHA Facilities data is updated on an Irregular / As-Needed basis. This data was last updated in October 2020.For more information, contact MDOT SHA OIT Enterprise Information Services: Email: GIS@mdot.maryland.gov

DownloadA daily extract of the NPDES Conveyance dataset is available for download as a zipped file geodatabase.BackgroundAs a government agency that owns and maintains separate storm sewer systems, the Maryland State Highway Administration (SHA) is mandated to file a National Pollutant Discharge Elimination System (NPDES) permit with the Maryland Department of the Environment (MDE). The permit requires the inventory, inspection, and maintenance of SHA stormwater infrastructure. SHA is responsible for maintaining storm drain infrastructure on more than 5,000 miles of roadway statewide. SHA has developed a program consisting of SHA personnel, data managers, and subject matter experts to support the permit requirements and maintain these roadways. The tasks involved in the SHA NPDES data collection program are often completed by engineering consultants for SHA.The data are organized into a series of drainage systems with stormwater management facilities that are interconnected, allowing for flow-tracing function through distinct systems. A drainage system is defined as a series of storm drain structures or point features (i.e., manholes, inlets, endwalls) that connect hydraulically through conveyance features such as pipes and / or ditches. Closed and open storm drain structures are connected by pipe and ditch conveyance to create the drainage system. Stormwater management facilities (SWMF), also known as stormwater best management practices (BMP) are inventoried with the storm drain system. A system can include both open and closed storm drain features.ConveyanceConveyance features to be identified and inventoried include actual, physical features (pipes and ditches) and database connectivity features (hydraulic connectors). Conveyance is represented as line features in the database. Although they do not physically exist, hydraulic connectors should be inventoried to facilitate connection of drainage systems through stormwater BMPs; this is the only case where a hydraulic connector is created. Not every pipe or ditch conveyance is inventoried, but generally all conveyances between structures are inventoried. Conveyance features will have an upstream and downstream structure. When contract plans are not available showing proper conveyance for a storm drain system, conveyance can be determined by looking at the pipe(s) direction inside of structures. Field crews are not required to open manhole lids, and conveyance can be assumed at the field crew’s discretion when plans are not available.Pipes, Cross Culverts, & Driveway CulvertsPipes connect structures together in a system to maintain conveyance. Pipes consist of closed storm drain pipes, cross culverts, and driveway culverts. Rules for collecting cross culvert and driveway culvert pipes are described below. The following are rules that should be followed when collecting pipes within the storm drain network:All pipes between closed storm drain structures are inventoried.Pipes less than five feet in height are inventoried within SHA ROW.Pipes that are greater than five feet in height are not inventoried if they do not connect to closed storm drain structures. Pipes that are greater than five feet in height and do connect to closed storm drain structures are inventoried with the storm drain network.Closed storm drain systems that outfall through a pipe or culvert that is greater than five feet in height are inventoried. Pipe size, shape, invert, and material are recorded for all pipes. Because field crews are not required to open grates or manhole lids, this attribute information is most often gathered from contract plans. Pipe sizes and material should be verified in the field by observation through inlet grates and at end structures (headwalls, end sections, outfalls, projection pipes). Field crews should become familiar with different pipe sizes and materials prior to conducting field inventory.Cross Culverts are pipes, boxes, or arches that convey water from one side of the ROW to the other side, usually under the roadway. Cross culverts are inventoried as pipes. Depending on the situation and culvert size, not all cross culverts will be inventoried. The following are rules that should be followed when collecting cross culverts:The culvert height is determined from contract plans when available. Otherwise care should be taken to measure and estimate the actual culvert height in the field. This may require estimating the depth of sedimentation at the culvert ends to determine the feet of buried culvert.Culverts that are less than five feet in height are inventoried.Culverts that are greater than five feet in height are not inventoried.A culvert that is greater than five feet in height that has a closed storm drain tying in is not inventoried. Instead, the most downstream structure in the closed storm drain system is inventoried as a pipe connection at the location the storm drain system connects to the culvert.Driveway Culverts and entrance culverts are pipes, possibly with an end structure, that conveys water under driveways, utility access roads, or stormwater BMP access roads. Not all driveway culverts will be inventoried within SHA ROW. The following are rules that should be followed when collection driveway culverts:Private driveway culverts and culverts at farm or other access points that do not require access permits should not be inventoried. Culverts under entrance drives that provide two-way or greater traffic such as multi-family residential, commercial, public, or industrial properties are inventoried. Culverts under SHA-owned stormwater maintenance access or other utility access roads should also be inventoried.If the private driveway or access drive culvert has a closed storm drain structure such as an inlet or riser on the upstream or downstream end of the pipe, then the culvert should be inventoried.If a driveway culvert is excluded from the inventory, other adjoining closed drain structures completing the system should be connected using a ditch. The ditch in this case should be drawn through the culverts as if the culvert does not exist.DitchesDitches and open conveyance are channels or flow paths that connect open structures (headwalls, end sections, endwalls, projection pipes, inlets with open backs) in a system to maintain the conveyance. Attributes collected for ditches include material (vegetative, concrete, riprap, etc.), bottom width, and side slope. Not all ditches or open channels within SHA ROW are to be inventoried in the geodatabase. Ditches to be inventoried are the following:Ditches or open conveyance between open structures.Ditches or open conveyance greater than two feet in bottom width.Ditches or open conveyance that flow into stormwater BMPs regardless of bottom width.Hydraulic ConnectorsHydraulic Connectors connect the outfalls into stormwater BMPs to the control structure of the stormwater BMP to maintain conveyance through the system. Hydraulic connectors are used to represent connectivity through a stormwater BMP from inflows to control structures. Inflow points and control structures for stormwater BMPs should be connected with a hydraulic connector, including infiltration trenches. If hydraulic connectors do not exist in the previous inventory, the current development should create them. The hydraulic connector line features are stored in the CONVEYANCE feature class and no additional attribute information is collected. The connector is use so that connectivity between structures is maintained through stormwater BMPs and network tracing can occur.SimplificationsThe simplification process flattens database tables that normalize attribute information, resulting in a dataset with all attributes but also many null fields when the attribute type is not relevant to the SWMFAC type. The simplified data are a snapshot in time of the production NPDES data, updated every night.PublishingThis service was last published by Elliott Plack on 9/6/2019 based on a materialized view created by John Shiu. The service was republished on 11/26/2016 due to a security requirement on the source dataset.

Esri ArcGIS Online (AGOL) Hosted, View Feature Layer which provides access to the MDOT SHA Roadway Posted Speed Limit Signs data product.MDOT SHA Roadway Posted Speed Limit Signs data consists of point geometric features which represent the geographic locations of posted speed limit signs along MDOT SHA-maintained roadways throughout the State of Maryland. This layer is a hosted, view layer showing only Posted Speed Limit signage from the comprehensive MDOT SHA Roadway Sign Inventory. Roadway signs that share a sign support structure will be represented as stacked geometry.MDOT SHA Roadway Sign Inventory data is owned by the MDOT SHA Office of Traffic & Safety (OOTS). This data is currently updated on an annual basis. This is the latest version of the data, which was last updated in November 2019 (11/04/2019).MDOT SHA Roadway Sign Inventory data is published on ArcGIS Online for Maryland as a publicly available Hosted Feature Layer with Non-Restricted Access. Download / Export of the data is available in a variety of formats.For additional information, contact MDOT SHA OIT Enterprise Information Services:GIS@mdot.maryland.gov

Maryland Bicycle Level of Traffic Stress (LTS) An overview of the methodology and attribute data is provided below. For a detailed full report of the methodology, please view the PDF published by the Maryland Department of Transportation here. The Maryland Department of Transportation is transitioning from using the Bicycle Level of Comfort (BLOC) to using the Level of Traffic Stress (LTS) for measuring the “bikeability” of the roadway network. This transition is in coordination with the implementation of MDOT SHA’s Context Driven Design Guidelines and other national and departmental initiatives. LTS is preferred over BLOC as LTS requires fewer variables to calculate including:Presence and type of bicycle facilitySpeed limitNumber of Through Lanes/Traffic VolumeTraditionally, the Level of Traffic Stress (LTS) (scale “1” to “4”) is a measure for assessing the quality of the roadway network for its comfort with various bicycle users. The lower the LTS score, the more inviting the bicycle facility is for more audiences.LTS Methodology (Overview) MDOT’s LTS methodology is based on the metrics established by the Mineta Transportation Institute (MTI) Report 11-19 “Low-Stress Bicycling and Network Connectivity (May 2012) - additional criteria refined by Dr. Peter G. Furth (June 2017) below and Montgomery County's Revised Level of Traffic Stress. Shared-use Path Data Development and Complimentary Road Separated Bike Routes DatasetA complimentary dataset – Road Separated Bike Routes, was completed prior to this roadway dataset. It has been provided to the public via (https://maryland.maps.arcgis.com/home/item.html?id=1e12f2996e76447aba89099f41b14359). This first dataset is an inventory of all shared-use paths open to public, two-way bicycle access which contribute to the bicycle transportation network. Shared-use paths and sidepaths were assigned an LTS score of “0” to indicate minimal interaction with motor vehicle traffic. Many paved loop trails entirely within parks, which had no connection to the adjacent roadway network, were not included but may be included in future iterations. Sidepaths, where a shared-use path runs parallel to an adjacent roadway, are included in this complimentary Road Separated Bike Routes Dataset. Sidepaths do not have as an inviting biking environment as shared-use paths with an independent alignment due to the proximity of motor vehicle traffic in addition to greater likelihood of intersections with more roadways and driveways. Future iterations of the LTS will assign an LTS score of “1” to sidepaths. On-street Bicycle Facility Data Development This second dataset includes all on-road bicycle facilities which have a designated roadway space for bicycle travel including bike lanes and protected bike lanes. Marked shared lanes in which bicycle and motor vehicle traffic share travel lanes were not included. Shared lanes, whether sharrows, bike boulevards or signed routes were inventoried but treated as mixed traffic for LTS analysis. The bicycle facilities included in the analysis include:

Standard Bike Lanes – A roadway lane designated for bicycle travel at least 5-feet-wide. Bike lanes may be located against the curb or between a parking lane and a motor vehicle travel lane. Buffered bike lanes without vertical separation from motor vehicle traffic are included in this category. Following AASHTO and MDOT SHA design standards, bike lanes are assumed to be at least 5-feet-wide even through some existing bike lanes are less than 5-feet-wide.
Protected Bike Lanes – lanes located within the street but are separated from motor vehicle travel lanes by a vertical buffer, whether by a row of parked cars, flex posts or concrete planters. Shoulders – Roadway shoulders are commonly used by bicycle traffic. As such, roadways with shoulders open to bicycle traffic were identified and rated for LTS in relation to adjacent traffic speeds and volumes as well as the shoulder width. Shoulders less than 5-feet-wide, the standard bike lane width, were excluded from analysis and these roadway segments were treated as mixed traffic.

The Office of Highway Development at MDOT SHA provided the on-street bicycle facility inventory data for state roadways. The shared-use path inventory and on-street bicycle facility inventory was compiled from local jurisdiction’s open-source download or shared form the GIS/IT departments. Before integrating into OMOC, these datasets were verified by conducting desktop surveys and site visits, and by consulting with local officials and residents.
Data UsesThe 2022 LTS data produced through this process can be used in a variety of planning exercises. The consistent metrics applied across the state will help inform bicycle mobility and accessibility decisions at state and local levels. Primarily, the LTS analysis illustrates how bikeable Maryland roads are where the greatest barriers lie. While most roads in the state are an LTS 1, the main roadways which link residential areas with community services are typically LTS 4. In the coming months, MDOT will use the LTS in variety of way including:

Conducting a bicycle network analysis to develop accessibility measures and potential performance metrics. Cross-referencing with state crash location data; Performing gap analysis to help inform project prioritization.

Data Limitations A principle of data governance MDOT strives to provide the best possible data products. While the initial LTS analysis of Maryland’s bicycle network has many uses, it should be used with a clear understanding of the current limitations the data presents.

Assumptions - As noted earlier in this document, some of the metrics used to determine LTS score were estimated. Speed limits for many local roadways were not included in the original data and were assigned based on the functional classification of the roadway. Speed limits are also based on the posted speed limit, not the prevailing operating vehicle speeds which can vary greatly. Such discrepancies between actual and assumed conditions could introduce margins of error in some cases. As data quality improves with future iterations, the LTS scoring accuracy will also improve. Generalizations - MDOT’s LTS methodology follows industry standards but needs to account for varying roadway conditions and data reliability from various sources. The LTS methodology aims to accurately capture Maryland’s bicycle conditions and infrastructure but must consider data maintenance requirements. To limit data maintenance generalizations were made in the methodology so that a score could be assigned. Specifically, factors such as intersections, intersection approaches and bike lane blockages are not included in this initial analysis. LTS scores may be adjusted in the future based on MDOT review, updated industry standards, and additional LTS metrics being included in OMOC such as parking and buffer widths.
Timestamped - As the LTS score is derived from a dynamic linear referencing system (LRS), any LTS analysis performed reflects the data available in OMOC. Each analysis must be considered ‘timestamped’ and becoming less reliable with age. As variables within OMOC change, whether through documented roadway construction, bikeway improvements or a speed limit reduction, LTS scores will also change. Fortunately, as this data is updated in the linear referencing system, the data becomes more reliable and LTS scores become more accurate. --------------------------------------------------------------------------------------------------------------------------------------------------------------------Level of Traffic Stress (LTS) Attribute Metadata OBJECTID | GIS Object IDState ID (ID) | Unique identification number provided by Maryland State Highway Administration (MDOT SHA)Route ID (ROUTEID) | Unique identification number for the roadway segment/record as determined by Maryland State Highway Administration (MDOT SHA) From Measure (FROMMEASURE) | The mileage along the roadway record that the specific roadway conditions change and maintain the same conditions until To MeasureTo Measure (TOMEASURE) | The mileage along the roadway record that the specific roadway conditions change and maintain the same conditions since From MeasureRoadway Functional Class (FUNCTIONAL_CLASS) | The functional classification of the roadway as determined by the Federal Highway Administration in coordination with the Maryland Department of Transportation State Highway Administration (MDOT SHA). All roadway records have a functional classification value. The following values represent the functional classification:

1 - Local 2 - Minor collector 3 - Major collector 4 - Minor arterial 5 - Principal Arterial (other) 6 - Principal Arterial (other Freeways and Expressways) 7 - Interstate

Annual Average Daily Traffic (AADT) | The Annual Average Daily Traffic (AADT) represents the average number of motor vehicles that pass along a roadway segment during a 24-hour period. The value is derived from MDOT SHA’s Traffic Monitoring System (TMS), the state’s clearinghouse for all traffic volume records. Roadway Speed Limit (SPEED_LIMIT) | The posted speed limit for a roadway segment as assigned by the MDOT SHA for state roadways and the local jurisdiction’s transportation management agency. Values for SPEED_LIMIT are measured in miles per hour (mph) in 5 mph increments from 5 mph through 70 mph. Roadway Access Control (ACCESS_CONTROL) | The access control indicates the types of entry points along the roadway segment, ranging from full to no access control. Interstates and other state roadways with no at-grade crossings are full access control, whereas a neighborhood street open to all modes of traffic represents a roadway with no access control. The values in

Esri ArcGIS Online (AGOL) Hosted Feature Layer which provides access to the MDOT SHA Roadway Functional Classification data product. MDOT SHA Roadway Functional Classification data consists of linear geometric features which showcase the functional classification of roadways throughout the State of Maryland. Roadway Functional Classification is defined as the role each roadway plays in moving vehicles throughout a network of highways. MDOT SHA Roadway Functional Classification data is primarily used for general planning purposes, and for Federal Highway Administration (FHWA) Highway Performance Monitoring System (HPMS) annual submission & coordination. The Maryland Department of Transportation State Highway Administration (MDOT SHA) currently reports this data only on the inventory direction (generally North or East) side of the roadway. MDOT SHA Roadway Functional Classification data is not a complete representation of all roadway geometry.The State of Maryland's roadway system is a vast network that connects places and people within and across county borders. Planners and engineers have developed elements of this network with particular travel objectives in mind. These objectives range from serving long-distance passenger and freight needs to serving neighborhood travel from residential developments to nearby shopping centers. The functional classification of roadways defines the role each element of the roadway network plays in serving these travel needs. ​ Over the years, functional classification has come to assume additional significance beyond its purpose as a framework for identifying the particular role of a roadway in moving vehicles through a network of highways. Functional classification carries with it expectations about roadway design, including its speed, capacity and relationship to existing and future land use development. Federal legislation continues to use functional classification in determining eligibility for funding under the Federal-aid program. Transportation agencies describe roadway system performance, benchmarks and targets by functional classification. As agencies continue to move towards a more performance-based management approach, functional classification will be an increasingly important consideration in setting expectations and measuring outcomes for preservation, mobility and safety.MDOT SHA Roadway Functional Classification 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 & Preliminary Engineering (OPPE) Data Services Division (DSD). This data is used by various business units throughout MDOT, as well as many other Federal, State and local government agencies. Roadway Functional Classification data is key to understanding the role each roadway plays in moving vehicles throughout the State of Maryland's network of highways.MDOT SHA Roadway Functional Classification data is owned & maintained by the MDOT SHA Office of Planning & Preliminary Engineering (OPPE). This data product is updated & published on an annual basis for the prior year. This data product is for the year 2024.For more information related to the data, contact MDOT SHA OPPE Data Services Division (DSD):Email: DSD@mdot.maryland.gov For more information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Esri ArcGIS Online (AGOL) Feature Layer for accessing the MDOT SHA OED EPD Delineated Assets data products.MDOT SHA OED EPD Delineated Assets consists of polygon geometric features with related tabular information which represent the geographic area & location of delineated Wetland Assets, Stream Assets, Study Areas, and Buffer Zones along roadways throughout the State of Maryland. MDOT SHA OED EPD Delineated Assets are owned & maintained by the MDOT SHA Office of Environmental Design (OED), specifically under the MDOT SHA OED Environmental Programs Division (EPD)For more information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

This data was developed in response to citizens’ road maintenance requests from across the state as to whom to contact as the official maintenance authority - be it MDOT State Highway Administration, MDOT Transportation Authority, a county, or a municipality.MDOT SHA Website

National Highway System (NHS) subset of Maryland’s 2018 National Bridge Inventory submission reporting conditions for 2017, with national transportation performance measure infrastructure conditions. This data will assist MPOs in analyzing the baseline conditions of the NHS in each planning area and inform 2-year and 4-year performance targets.Last Updated: September 2018For additional information, contact the MDOT SHA Geospatial Technologies Team:Email: GIS@mdot.maryland.govFor additional data, visit the MDOT GIS Open Data Portal:Website: https://data.imap.maryland.gov/pages/mdot/