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

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

This layer contains the boundaries and IDs of the Maryland tax maps produced by Maryland Department of Planning. Tax maps, also known as assessment maps, property maps or parcel maps, are a graphic representation of real property showing and defining individual property boundaries in relationship to contiguous real property.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/PlanningCadastre/MD_PropertyData/MapServer/2

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

This dataset includes Hospitals located in the Montgomery County vicinity. It was developed and is maintained by TEBS-GIS. This dataset satisfies County basemap accuracy requirements (1:2400) and is included in the Places of Interest Guide.This data is used both by Government and the public. The Places of Interest Guide can be used to find a Place of Interest within Montgomery County, Maryland by address, by title, by place name or city, or by category. Once you've located the place of interest, then you can generate travel directions, time estimates, maps and distances.

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 is the County Boundary layer for Anne Arundel County, Maryland.

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

This is a comprehensive point theme that incorporates parcel ownership and address information, parcel valuation information and basic information about the land and structure(s) associated with a given tax assessment account. Data for the Parcel point theme are obtained from the State Department of Assessments and Taxation with added data from Maryland Department of Planning. The date the point was most recently published in Planning's data products MdProperty View and FINDER Quantum is contained in the mdpvdate field. The date of the most recent Assessments data linkage to MdProperty View/FINDER Quantum points is contained in the sdatdate field. Accounts deleted between those two dates are no longer represented as points. For more information on the attribute definitions please see the MdProperty View User's Guide, available for download at https://planning.maryland.gov/Pages/OurProducts/DownloadFiles.aspx . Please Note: Due to the extensive size of the parcel points file, download is recommended from the REST endpoint (https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/MapServer/exts/MDiMapDataDownload/customLayers/0)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/PlanningCadastre/MD_PropertyData/MapServer/0**Please note, due to the size of this dataset, you may receive an error message when trying to download the dataset. You can download this dataset directly from MD iMAP Services at: https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/MapServer/exts/MDiMAPDataDownload/customLayers/0**

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.

This GIS dataset contains growth tier maps adopted by local (county and municipal) jurisdictions under SB236. Data are generally collected from county and municipal jurisdictions by the Maryland Department of Planning (Planning) or digitized by Planning in coordination with local jurisdictions. For more information about SB236, see Planning’s Septics Law Implementation Website at https://planning.maryland.gov/Pages/OurWork/SB236Implementation.aspxThis document describes standard operating procedures for aggregating growth tier map GIS data. These procedures may not apply to historical data (i.e. records for which both the SRC_DATE and GIS_SRC fields are blank). For example, Planning may have realigned historical data from local jurisdictions to parcel polygon boundaries or used different procedures to represent municipal tiers when municipalities concurred with county tier maps.Planning generally requests updated GIS data once a jurisdiction notifies Planning that a growth tier map has been amended. Aggregated data may be outdated or incomplete if Planning has not yet received or processed GIS updates from jurisdictions. Planning generally does not alter geometries received from the local jurisdictions except to divide municipal tiers at the county boundary (see JURSCODE field description). This dataset may contain overlap where multiple jurisdictions designate tiers in the same area.Fields include:JURSCODE – MdProperty Viewjurisdiction code (four-letter county or Baltimore City code). For tiers designated by counties, this is the jurisdiction responsible for designating the growth tier. For tiers designated by municipalities, this is the jurisdiction in which the growth tier is physically located. Municipal tiers that cross counties are divided at the county boundary so this field can be populated. See the MUNI field for the municipality responsible for designating a municipal tier.County – Full name of the jurisdiction represented by the JURSCODE.MUNI – The name of the municipality responsible for designating the tier. This field will be blank (‘ ‘) if the tier has been designated by a county. The MUNI field is formatted consistently with municipality names in the Planning’s municipal boundary datasets. When municipalities adopt tier maps by concurring with county tiers instead of submitting tier data independently, the MUNI field remains blank within the entire county tier map dataset. Depending on internal needs, an independent municipal tier dataset may or may not be generated by Planning and included within the aggregated tiers.TIER – Growth tier identifier used by the source jurisdiction and standardized as Tier 1, Tier 1A, Tier 2, Tier 2A, Tier 3, and Tier 4. May include additional alphabetical annotations used by the jurisdictions such as Tier 2B. If the TIER_CODE field is 99, the TIER field retains the descriptor provided by the jurisdiction, which may be a blank or null value.TIER_CODE – Integer field containing the growth tier standardized by Planning: 1 (Tier I); 11 (Tier IA or any other annotated version of Tier I, such as IB, etc.); 2 (Tier II), 22 (Tier IIA or any other annotated version of Tier II, such as IIB, etc.); 3 (Tier III); 4 (Tier IV); 44 (Areas annotated as Tier IVA for municipal greenbelts or any other annotated version of Tier IV); 99 – Areas included in the jurisdiction’s growth tier GIS data that are not assigned a tier, such as rights-of-way or water.Adopt_Date – Date growth tier map was adopted or amended. When a local jurisdiction updates its growth tier map, Planning generally requests a comprehensive GIS update to replace all existing data for the jurisdiction.Acres – GIS acres calculated by Planning in NAD83 Meters (EPSG 26985)GIS_SRC (GIS Source) – The original source of the GIS spatial and attribute information Planning obtained, which concatenates the JURSCODE field (or MUNI field for municipal tier maps), followed by a space, followed by the name of the shapefile or feature class received from the jurisdiction. Field contains “MDP” if tiers were digitized by Planning, and is blank (‘ ‘) for historical data.SRC_DATE (GIS Source Date) – The date (YYYYMMDD) the GIS data were obtained by Planning from the local jurisdiction. If the month or day is unknown, the date is YYYY0000. If Planning digitized the growth tier map in coordination with a local jurisdiction, this should be the date Planning’s edits are verified by the jurisdiction. This field will be blank (‘ ’) if Planning’s edits have not been verified or if the dataset is historical and the source is unknown.NOTE – Text field containing additional notes about the dataLast Updated: 7/26/2023This is a Maryland Department of Planning hosted service. Find more information on https://imap.maryland.govMap Service Link: https://mdpgis.mdp.state.md.us/arcgis/rest/services/PlanningCadastre/Septic_Growth_Tiers/MapServer

Geographic Extent: SANDY_Restoration_DE_MD_QL2 Area of Interest covers approximately 3.096 square miles. Lot #5 contains the full project area Dataset Description: The SANDY_Restoration_DE_MD_QL2 project called for the Planning, Acquisition, processing and derivative products of LIDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LIDAR Specification, Version 1. The data was developed based on a horizontal projection/datum of State Plane Zone Maryland (1900), NAD83, feet and vertical datum of NAVD1988 (GEOID12A), feet. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.2 Files formatted to 3842 individual 1500m x 1500m tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 1500m x 1500m schema, and Breaklines in ESRI shapefile format. Ground Conditions: LiDAR was collected in Winter 2013 / Spring 2014, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications, Quantum Spatial established a total of 78 QA control points and 99 Land Cover control points that were used to calibrate the LIDAR to known ground locations established throughout the SANDY_Restoration_DE_MD_QL2 project area.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/Caroline/MD_caroline_aspect_m/ImageServer

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.

Address and Locations of all Public Schools in Montgomery County, MD.

Address and Locations of all Public Schools in Montgomery County, MD.

Address and Locations of all Public Schools in Montgomery County, MD.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

This dataset contains Career and Volunteer Fire Stations in Maryland that are operated at the County level. This dataset was created using information from the 2012 Maryland State Fireman's Association (MSFA) Volunteer Stations dataset, the Maryland Coordination and Analysis Center (MCAC) Career and Volunteer Fire Station dataset, and the Community Anchor Institutions (CAI) Public Safety dataset.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/PublicSafety/MD_Fire/FeatureServer/1

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 is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. The units of geography used for the 2010 Census maps displayed here are the Census tracts. 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. Census tract boundaries generally follow visible and identifiable features. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances - a census tract may consist of noncontiguous areas. The data collected on the short form survey are general demographic characteristics such as age - race - ethnicity - household relationship - housing vacancy and tenure (owner/renter).Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Demographics/MD_CensusData/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.