This layer contains detailed outlines of Maryland counties. The Maryland land county boundaries were built using political county boundaries and the National Hydrology Data (NHD). Land boundaries are a key geographic featue in our mapping process.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Last Updated: UnknownFeature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PhysicalBoundaries/FeatureServer/0

Esri ArcGIS Online (AGOL) Hosted Feature Layer which provides access to the MDOT SHA County Boundaries data product.MDOT SHA County Boundaries data consists of polygon geometric features which represent the geographic area & extent (boundary) of each County throughout the State of Maryland. MDOT SHA County 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 the geographic area & extent of each County throughout the State of Maryland. MDOT SHA County Boundaries data is updated & published on an As-Needed basis as this data does not frequently or regularly change. For additional information, contact the MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Esri ArcGIS Online (AGOL) Feature Layer which provides access to the MDOT SHA County Flood Statistics MapsMDOT SHA County Flood Statistics Maps data consists of polygon geometric features which represent the geographic extent of each Maryland County with an available MDOT SHA County Flood Statistics Map. Users of this layer should consume the URL contained within each pop-up to access the MDOT SHA County Flood Statistics Map.MDOT SHA County Flood Statistics Maps data is owned & maintained by the MDOT SHA OPPE Innovative Planning & Performance Division (IPPD).For more information related to the maps, contact MDOT SHA OPPE Innovative Planning & Performance Division (IPPD):Email: IPPD@mdot.maryland.govFor more information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Maryland Department of Planning (MDP) maps annexations from municipalities. This dataset is created and maintained by the Maryland Department of Planning. These boundaries are not intended to serve as a legal description. Fields:Municipality Name: Name of Municipality located in Maryland.Jurisdiction Code – Four letter county code: ALLE (Allegany), ANNE (Anne Arundel), BACI (Baltimore City), BACO (Baltimore County), CALV (Calvert), CARO (Caroline), CARR (Carroll), CECI (Cecil), CHAR (Charles), DORC (Dorchester), FRED (Frederick), GARR (Garrett), HARF (Harford), HOWA (Howard), KENT (Kent), MONT (Montgomery), PRIN (Prince George’s) QUEE (Queen Anne’s), SOME (Somerset), STMA (St. Mary’s), TALB (Talbot), WASH (Washington), WICO (Wicomico), WORC (Worcester). Last updated: 9/5/2024This is an MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/FeatureServer/2

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. For additional information, contact MDOT SHA Geospatial Technologies 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://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.

The Traffic Volume Maps show the Annual Average Daily Traffic (AADT) numbers displayed at various locations on Maryland's roadways. Traffic counts are reported as the number of vehicles expected to pass a given location. This is an average day of the year for all traffic-counting stations in the state. Traffic volume data is collected from more than 8,700 Program Count stations and 91 Automatic Traffic Recorders (ATRs) located throughout Maryland.Program Count data is collected (both directions) at regular locations on either a three (3) year or six (6) year cycle depending on type of roadway. Growth factors are applied to counts which were not taken during the current year and the counts are factored based on the past yearly growth of an associated ATR. Counters are placed for 48 hours on a Monday or Tuesday and are picked up that Thursday or Friday, respectively. The ATR and toll count data is collected on a continuous basis. The toll station data is provided by Maryland Transportation Authority.Traffic Volume Maps are updated and published annually in March. Please see the Traffic Volume Map Introduction (PDF, ~148 kb) and ATR and Toll Locations (PDF, ~32 kb) for more information about the Traffic Volume Maps.The entire current Maryland Traffic Volume Map (~9.4 MB) is available as a PDF file.Traffic Volume Maps from previous years back to 1980 are available as PDF files.Please Note: The PDF file sizes for the Traffic Volume Maps vary. It may take a few seconds or a few minutes to display.MDOT SHA Website

This is the County Boundary layer for Anne Arundel County, Maryland.

Tabulates acres by land use category as of 2018 for each of Maryland’s 23 counties and Baltimore City. Derived from the Maryland Department of Planning’s 2018 Statewide Land Use Dataset (2024 Edition). Given methodology changes, this dataset is not comparable with MDP’s previous Land Use Land Cover products and should not be used to assess change over time.

In 1984, the General Assembly enacted the Chesapeake Bay Critical Area Act to regulate development, manage land use and conserve natural resources on land in those areas designated as Critical Area. For this document, the Critical Area is all land and water areas within 1,000 feet of the tidal waters' edge or from the landward edge of adjacent tidal wetlands and the lands under them. Georeferenced digital data files of the critical Area have been produced for Baltimore City and the 16 Maryland counties with land located within the Critical Area. The digital maps produced for each jurisdiction are polygons depicting the Critical Area and the land use classifications recognized by the Chesapeake Bay Critical Area Commission (CBCAC). Each jurisdiction is a separate file. The data were produced from hard copy parcel maps originally submitted by the counties as part of the requirements for developing their Critical Area Program. For the purpose of the Mdimap web service the Critical Area Data is displayed by two data layers, one general layer and one layer showing the available critical area data for local towns.This data set represents the Department of Natural Resources interpretation of the location and extent of the Critical Area; however, the digital maps are not recognized as the "official" maps. In accordance with Subsection 8-1807(a) of the Critical Area Act, the Critical Area consists of (1) All waters and lands under the Chesapeake Bay and its tributaries to the head of tide as indicated on the State wetland maps, and all State and private wetlands designated under Environment Article, Title 16, annotated Code of Maryland; (2) All land and water areas within 1,000 feet beyond the landward boundaries of State or private wetlands and the of tides designated under Environment Article, Article 16, Annotated Code of Maryland; and (3) Modification to these areas through inclusions or exclusions proposed by local jurisdictions and approved by Commission as specified in Natural Resources Article, Subsection 8-1807, annotated Code of Maryland. These maps are hard copy maps that cannot be exactly replicated in a digital format; therefore, some interpretation was necessary to create the digital line. Hard copy maps depicting the official Critical Area boundary line are available for review at the Chesapeake Bay Critical Area Commission, and at most local planning and zoning departments. The Department of Natural Resources makes no warranty, expressed or implied, as to the use or appropriateness of Spatial Data, and there are no warranties of merchantability or fitness for a particular purpose or use. The intended use is for general information and planning purposes. It is not intended to be used to determine the exact location of the Critical Area boundary on a specific parcel or to determine the acreage within the Critical Area on a specific site. The information contained in Spatial Data is from publicly available sources, but no representation is made as to the accuracy or completeness of Spatial Data. The Department of Natural Resources 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. The Department of Natural Resources shall not be liable for any lost profits, consequential damages, or claims against the Department of Natural Resources by third parties. The liability of the Department of Natural Resources for damage regardless of the form of the action shall not exceed any distribution fees that may have been paid in obtaining Spatial Data.There were many parties involved in producing Maryland's Critical Area data and the key parties will be listed. Each county and city (listed below) produced a hard copy map and submitted the map to the Chesapeake Bay Critical Area Commission (CBCAC) for approval. Through Coastal Zone Management grants, CBCAC digit

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state but may extend across county and county subdivision boundaries. An incorporated place is usually a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs are often defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2024, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census, but some CDPs were added or updated through the 2024 BAS as well.

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

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

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 (DGD). 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 identifying 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. For the latest information available from each MDOT SHA District, visit each MDOT SHA District Website:MDOT SHA District 1MDOT SHA District 2MDOT SHA District 3MDOT SHA District 4MDOT SHA District 5MDOT SHA District 6MDOT SHA District 7For additional information, contact the MDOT SHA Geospatial Technologies TeamEmail: 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_MDOTSHADistrictBoundaries/FeatureServer/0

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined because of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division or incorporated place boundaries in some states and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard Census Bureau geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous.

This dataset contains digitized land use/land cover (LULC) for the years 2011, 2015, and 2017. The dataset contains 1-meter resolution raster maps for each year covering the geographic area for six watersheds within and near the Clarksburg Special Protection Area located in Montgomery County, Maryland, USA. The area includes LULC within 500-foot buffered watersheds. Watershed boundaries for Cabin Branch (CB), Crystal Rock (CR), Soper Branch (SB), Tributary 104 (T104), and Tributary 109 (T109) were derived using USGS topographic maps (1:24,000-scale) while Ten Mile Creek (TMC) was derived using Montgomery County, Maryland LiDAR data (1-meter resolution). LULC classes include a water class (10), impervious surface class (20), barren class (30), forest class (40), grass class (70), and agriculture class (80).

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

This layer contains data concerning the location and characteristics of bedrock, mappable geologic units, within Frederick county. This geodatabase contains geologic data from Frederick County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Frederick County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

This layer contains data concerning the location and characteristics of unconsolidated Quaternary deposits within Frederick county. This geodatabase contains geologic data from Frederick County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Frederick County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

1 in.= 600 feet Tax Map index of Anne Arundel County

Map of Washington County, Maryland, showing distribution of geological formations.