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 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

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 map shows the borders of the City of Mount Rainier, Maryland. Data are provided from imap.maryland.gov

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 data set represents the Department of Natural Resources interpretation of the location, land cover/land use type and geographic extent of the critical land areas for towns near the Chesapeake Bay. A Critical Area includes all land within 1,000 feet of tidal waters and wetlands in Maryland, as well as the waters of Maryland's Chesapeake Bay and coastal bay area. This data file Critical Areas Towns only contains Critical Areas in 14 Maryland Towns: Charlestown, Chesapeake City, Crisfield, Leonardtown, North Beach, Northeast, Perryville, Port Deposit, Princess Anne, Rock Hall, Salisbury, Secretary, Snow Hill and Vienna.-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/Environment/MD_CriticalAreas/FeatureServer/0

This dataset includes municipal police facilities within Maryland.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_Police/FeatureServer/2

Feature class depicting road-separated bicycle routes throughout the State of Maryland. In many instances these routes can be used by pedestrians, but not by any motorized vehicle. “Road Separated” indicates that these segments are physically separated from roads in which motorized vehicles travel. That is, these are not bike lanes, sharrows, or signed bike routes per se – these segments are separated from the main road by a physical barrier (E.g., grass, natural earth, trees, etc.) and in many instances do not follow a motorized vehicle route network at all (E.g., a wholly separated trail). This information in this feature class will be used in conjunction with the One Maryland One Centerline (OMOC) initiative to provide a Level of Traffic Stress (LTS) map for the State of Maryland. The recommended LTS score for each road-separated bicycle route is listed in the pop-up menu.Bikeways included in the map are of varying surface material but are typically paved or hard-packed surface. Sidewalks, typically 6-feet-wide, hard surface pathways primarily for pedestrian use, are not included in this map. The preferred width of bikeways included is at least 10-feet wide, although bikeways may be narrower if anticipated traffic volumes are minimal. For instance, while most pathways within Columbia are 8 to 10 feet wide, some pathways are narrower when connecting to cul-du-sacs. These narrower pathways are included in the map as the anticipated traffic volume are low enough to minimize user conflict. This feature class was compiled by the Maryland Department of Transportation (Secretary’s Office) using a variety of sources including (but not limited to) state data sources from various agencies including the Maryland Department of Transportation (MDOT), Maryland Department of Planning (MDP), and Maryland Department of Natural Resources (DNR). Data has also been augmented by counties and municipalities throughout the State of Maryland as well as several agencies, organizations, and conservancies. Certain named trails are included within this dataset and their sources have varied from state, local, and non-profits as well as through the digitizing of various aerial/satellite imagery, digital elevation models (DEM), right-of-ways, former railways, and corridors by MDOT staff. None of the alignments included in this dataset are restricted to private use.The searchable data includes attribute information containing the route’s name (if applicable), calculated segment length (using the Maryland State Plane 1983 Projection), and Level of Traffic Stress (LTS) score. The data mostly contains alignment segments with a LTS of 0, the lowest score. This score indicates that the bikeway can be comfortably used by cyclists of all levels and experience and has minimal automobile traffic interaction. There are several segments with LTS scores of 1 or 2 within this feature class as well, but these are mostly connector paths/trails between larger segments. LTS scores of 1 or 2 indicate very little automobile traffic and/or slower speeds required for the automobile traffic.This feature class will be updated as needed but is scheduled to be comprehensively reviewed on an annual basis. ATTRIBUTES:Route Name (if Applicable): The name of the route is provided if the route is namedCounties within Route: The counties in Maryland through which the route passes are listedRoute's Length: The route distance is calculated and listed in miles. Note that this is the length of the entire named route - and not just the segment selected. Distance calculated using the NAD 1983 StatePlane Maryland FIPS 1900 (US Feet) Projection.LTS Score: Level of Traffic Stress. For this map (road-separated routes) the scores range from 0 (road-separated) to 2 (generally low traffic). The areas that are not 0 in this map/data represent portions of the road-separated routes that cross streets or have portions that are briefly on-road as connections.

The 2019 cartographic boundary KMLs 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 generalized boundaries for counties and equivalent entities are as of January 1, 2010.

The municipalities of Maryland operate numerous welcome centers and rest areas at major tourist locations within the State.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_WelcomeAndVisitorCenters/FeatureServer/2

This dataset contains Career and Volunteer Fire Stations in Maryland that are operated at the Municipal 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/2

UPDATED LAYER 11/2024:Feature class depicting road-separated bicycle routes throughout the State of Maryland. In many instances these routes can be used by pedestrians, but not by any motorized vehicle. “Road Separated” indicates that these segments are physically separated from roads in which motorized vehicles travel. That is, these are not bike lanes, sharrows, or signed bike routes per se – these segments are separated from the main road by a physical barrier (E.g., grass, natural earth, trees, etc.) and in many instances do not follow a motorized vehicle route network at all (E.g., a wholly separated trail).This information in this feature class will be used in conjunction with the One Maryland One Centerline (OMOC) initiative to provide a Level of Traffic Stress (LTS) map for the State of Maryland. The recommended LTS score for each road-separated bicycle route is listed in the pop-up menu.Bikeways included in the map are of varying surface material but are typically paved or hard-packed surface. Sidewalks, typically 6-feet-wide, hard surface pathways primarily for pedestrian use, are not included in this map. The preferred width of bikeways included is at least 10-feet wide, although bikeways may be narrower if anticipated traffic volumes are minimal. For instance, while most pathways within Columbia are 8 to 10 feet wide, some pathways are narrower when connecting to cul-du-sacs. These narrower pathways are included in the map as the anticipated traffic volume are low enough to minimize user conflict. This feature class was compiled by the Maryland Department of Transportation (Secretary’s Office) using a variety of sources including (but not limited to) state data sources from various agencies including the Maryland Department of Transportation (MDOT), Maryland Department of Planning (MDP), and Maryland Department of Natural Resources (DNR). Data has also been augmented by counties and municipalities throughout the State of Maryland as well as several agencies, organizations, and conservancies. Certain named trails are included within this dataset and their sources have varied from state, local, and non-profits as well as through the digitizing of various aerial/satellite imagery, digital elevation models (DEM), right-of-ways, former railways, and corridors by MDOT staff. None of the alignments included in this dataset are restricted to private use.The searchable data includes attribute information containing the route’s name (if applicable), calculated segment length (using the Maryland State Plane 1983 Projection), and Level of Traffic Stress (LTS) score. The data mostly contains alignment segments with a LTS of 0, the lowest score. This score indicates that the bikeway can be comfortably used by cyclists of all levels and experience and has minimal automobile traffic interaction. There are several segments with LTS scores of 1 or 2 within this feature class as well, but these are mostly connector paths/trails between larger segments. LTS scores of 1 or 2 indicate very little automobile traffic and/or slower speeds required for the automobile traffic.This feature class will be updated as needed but is scheduled to be comprehensively reviewed on an annual basis. (Public) ATTRIBUTES:Route Name (if Applicable): The name of the route is provided if the route is namedRoute's Length: The route distance is calculated and listed in miles. Note that this is the length of the entire named route - and not just the segment selected. Distance calculated using the NAD 1983 StatePlane Maryland FIPS 1900 (US Feet) Projection.LTS Score: Level of Traffic Stress. For this map (road-separated routes) the scores range from 0 (road-separated) to 2 (generally low traffic). The areas that are not 0 in this map/data represent portions of the road-separated routes that cross streets or have portions that are briefly on-road as connections. --For Network Analysis Work this feature layer should be used in conjunction with the "Road Separated Connectors" feature layer also hosted by MDOT. --This layer is continually updated and monitored by Maryland DOT, but updates are not always reported to us. If you have an update you do not see, please send to mdotgis@mdot.maryland.gov