This is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. Polygon layer contains generalized outlines of Maryland counties.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PhysicalBoundaries/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.

This is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. The Maryland county boundaries were built using the USGS Topo Quads - county boundaries from the county governments - monument points - and historic records from the Maryland Archive. County boundaries are a key geographic asset in our mapping process and roadway data collection.Feature 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.

State of Maryland municipality boundary dataset.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:MUN_NAME (Municipality Name): Name of Municipality located in Maryland.RESOLUTION_NUMBER (Resolution Number): Local Municipality Annexation Resolution Number.ANNEXATION_DATE (Annexation Date) (DD/MM/YYYY): The Annexation Date field shows when there's been a change in the boundary. This date is known as the “Effective Date” from the municipality. The date 1/1/1997 is used as a default date of when annexation changes were first indicated in the GIS layer and not necessarily of when it was actually annexed. If there's a date of 1/1/1997, it can be assumed that the annexation occurred on this date or before. For example, for Baltimore City, the city boundary was determined hundreds of years ago. Other than that default date, the date will show when the property was annexed. ACRES (GIS Acres): GIS calculated acres.JURSCODE (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).This is a MD iMAP hosted service. Find more information on https://imap.maryland.govhttps://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/FeatureServer/5

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) Database (MTDB). The MTDB 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 as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) 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 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. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

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

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) Database (MTDB). The MTDB 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 primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

The 2015 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The records in this file allow users to map the parts of Urban Areas that overlap a particular county. After each decennial census, the Census Bureau delineates urban areas that represent densely developed territory, encompassing residential, commercial, and other nonresidential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the "urban footprint." There are two types of urban areas: urbanized areas (UAs) that contain 50,000 or more people and urban clusters (UCs) that contain at least 2,500 people, but fewer than 50,000 people (except in the U.S. Virgin Islands and Guam which each contain urban clusters with populations greater than 50,000). Each urban area is identified by a 5-character numeric census code that may contain leading zeroes. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2010.

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

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) Database (MTDB). The MTDB 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 primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentationMunicipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

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.

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 layer is a component of Parks and Recreation.

Prince George's County Parks and Recreation

© M-NCPPC

Precinct (voting district) polygon boundaries for 2022 collected by the Maryland Department of Planning (Planning) from counties (including Baltimore City) or digitized by Planning in coordination with counties, with precinct numbers reformatted as necessary for statewide consistency (see VTD field specifications below). All data are reprojected to WGS 1984 Web Mercator (auxiliary sphere) consistent with MD iMap standards, but precincts are otherwise delineated as received from counties. Planning may complete minor future adjustments to ensure precincts are edge matched with Census block boundaries.Fields include: JURSCODE (Jurisdiction Code) – MdProperty View jurisdiction code (four-letter county or Baltimore City code) COUNTY (County) – The US Census Bureau’s five-digit geographic identifier for each county in Maryland (including Baltimore City), which is includes the Maryland state code (24) followed by a three-digit county code. COUNTYNAME (County Name) – County name in text format VTD (Voting District Identifier) – Voting district identifier comprised of a five-digit county code (see “COUNTY” field) followed by a six-digit precinct identifier. The six-digit precinct identifier contains a two-digit election district number followed by a dash followed by a three-digit precinct number. This field is NULL for precinct names that could not be formatted according to these specifications. LABEL (Precinct Label) – Includes either the final six digits of the VTD field (precinct identifier) or the precinct name as provided by the county if a six-digit precinct identifier could not be derived from the source data. May be blank or NULL. Precinct labels are not unique across counties. NAME (Full Precinct Name) - Full precinct name, including the County Name and Precinct Label AGG_SRC (Aggregator Source) - Includes the aggregator organization credited with data aggregation, feature class name, and vintage date DATE_AGGREGATED (Date Aggregated) – Date the data were aggregated (YYMMDD) GIS_SRC (GIS Source) – The original source of the GIS spatial and attribute information the aggregator obtained, typically formatted as a shapefile or feature class name SRC_DATE (GIS Source Date) - The date (YYYYMMDD) the GIS data were obtained by the data aggregator. If the month or day is unknown, the date is YYYY0000This dataset includes historical precinct data from 2022. For the latest precinct information, please contact the Local Board of Elections: https://elections.maryland.gov/about/county_boards.html.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/Boundaries/MD_ElectionBoundaries/FeatureServer/2

2014 early voting locations in Montgomery County as selected October 21, 2013, subject to approval by the Maryland State Board of Elections. For more information, see www.777vote.org.

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

The units of geography used for the 2010 Census maps displayed here are the Census tracts. 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. 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).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/Demographics/MD_CensusData/FeatureServer/0

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

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) Database (MTDB). The MTDB 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 primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities.The boundaries for counties and equivalent entities are as of January 1, 2020, as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

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.

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 Universal Transverse Mercator Zone 18 North. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000. Coastal study data as defined in FEMA Gudelines and Specifications, Appendix D: Guidance for Coastal Flooding Analyses and Mapping, submitted as a result of a coastal study. Appendix D notes that a variety of analytical methodologies may be used to establish Base (1-percent-annual-chance) Flood Elevations (BFEs) and floodplains throughout coastal areas of the United States. Appendix D itemizes references for the methodologies currently in use by FEMA for specific coastal flood hazards, provides general guidance for documentation of a coastal flood hazard analysis, specifies flood hazard analysis procedures for the Great Lakes coasts, and outlines intermediate data submissions for coastal flood hazard analyses with new storm surge modeling and revised stillwater flood level (SWFL). (Source: FEMA Guidelines and Specs, Appendix D Guidance for Coastal Flooding Analyses and Mapping, Section D.1)