The watershed data set contains areas of land that contribute runoff and groundwater into a specific stream system. This data set shows the Baltimore County portion of the State-defined Maryland "8-digit" watersheds*. There are 14 major watersheds in Baltimore County. The data was interpreted from Baltimore County's 1953 topographic maps and was delineated at 1:2400 scale.

*These features are not identical to the State-defined Maryland "8-digit" watersheds. The features were refined using 1953 topographic data and a larger delineation scale.

This dataset consists of a digital geospatial representation of all identified Tier II segments in the State of Maryland. Based on data collected between 1995-2019, this dataset currently contains information for 263 designated Tier II stream segments. Main segment breakpoints were determined using the 100,000:1 National Hydrography Dataset (NHD). The final designated Tier II segments are the merged sub segments that make up the 24,000:1 NHD meeting the 100,000:1 breakpoints. Tier II stream segments generally terminate at confluences, impoundment outfalls, and tidal boundaries.Creator: Maryland Department of the Environment, Water Science Administration (MDE WSA) Assessment Data: Maryland Department of Natural Resources, Monitoring and Non-tidal Assessment Division, Maryland Biological Stream Survey Program (DNR MBSS), MDE WSA, Baltimore County Department of Environmental Protection and Sustainability, Frederick County Department of Sustainability and Environmental Resources, Wetland Studies and Solutions, McCormick Taylor Inc., and various non-government certified entities. Other Geospatial Data: USGSMap Service Link: https://mdewin64.mde.state.md.us/arcgis/rest/services/MDE_Water_Quality/MD_TierIIHighQualityWaters_2022/MapServer/1

This dataset consists of a digital geospatial representation of all identified Tier II segments in the State of Maryland. Based on data collected between 1995-2015, this dataset currently contains information for 253 designated Tier II stream segments. Main segment breakpoints were determined using the 100,000:1 National Hydrography Dataset (NHD). The final designated Tier II segments are the merged sub segments that make up the 24,000:1 NHD meeting the 100,000:1 breakpoints. Tier II stream segments generally terminate at confluences, impoundment outfalls, and tidal boundaries. Last Update: 9/11/2016 Contact: Angel D. Valdez, Antidegradation Implementation Lead Maryland Department of the Environment, 1800 Washington Blvd, Baltimore, MD 21230 Phone: 410-537-3606 E-Mail: angel.valdez@maryland.gov.Map Service Layer Link:https://mdewin64.mde.state.md.us/arcgis/rest/services/MDE_Water_Quality/MD_TierIIHighQualityWaters_2016/MapServer/1

In any given 1-square meter point in this EnviroAtlas dataset, the value shown gives the percentage of impervious surface within 1 square kilometer centered over the given point. Water is shown as '-99999' in this dataset to distinguish it from land areas with low impervious. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

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 EnviroAtlas dataset describes the percentage of a 15-m riparian buffer that is vegetated. In this community, vegetated land is defined as Trees & Forest, Grass & Herbaceous, Woody Wetlands, and Emergent Wetlands. There is a potential for decreased water quality in areas where the riparian buffer is less vegetated. The displayed line represents the center of the analyzed riparian buffer. The water bodies analyzed include hydrologically connected streams, rivers, connectors, reservoirs, lakes/ponds, ice masses, washes, locks, and rapids within the EnviroAtlas community area. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

This EnviroAtlas dataset describes the percentage of a 51-m riparian buffer that is vegetated. In this community, vegetated land is defined as Trees & Forest, Grass & Herbaceous, Woody Wetlands, and Emergent Wetlands. There is a potential for decreased water quality in areas where the riparian buffer is less vegetated. The displayed line represents the center of the analyzed riparian buffer. The water bodies analyzed include hydrologically connected streams, rivers, connectors, reservoirs, lakes/ponds, ice masses, washes, locks, and rapids within the EnviroAtlas community area. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

Esri ArcGIS Online (AGOL) Map Image Layer for accessing the Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones data product.Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones consists of polygon geometric features which represent the geographic areas throughout the State of Maryland that are impacted by CRAB inundation (0 to 1ft, 1 to 2ft, and 2ft or more).The Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones data product was created using a GIS spatial analysis model, unique for each county in the State of Maryland. Coastal counties follow an analysis methodology that incorporates FEMA Stillwater wave action as it is understood from the FEMA identified VE zones. A Water Surface Elevation (WSE) and Still Water Elevation (SWEL) rasters are used as the baseline to identify existing water depths within each county. For all flood zones that are not classified as VE the WSE three feet was added to reflect a three-foot rise in the base flood elevations. For those WSEs falling within a FEMA floodplain identified V Zone, six feet was added (three feet for the increase in flood elevations for the CS-CRAB, and 3 feet to compensate for the minimum of 3 foot wave action typically mapped by FEMA) / wave heights greater than 3 feet were reduced to the 3 foot minimum for consistency across the shoreline. The newly calculated WSE plus three datasets were then converted to points and merged. Next, an Inverse Distance Weighted (IDW) Interpolation was used to compute the proportional weighted values between the WSE point locations based on proximity. The DEM for each county is then subtracted from the new IDW raster in order to show precise water locations as they relate to the land elevation, producing a freeboard depth grid representing the depth of flood waters above the existing ground elevation given a 3 foot increase in water level. A course resolution QAQC was applied to remove “islands” of data associated with DEM inaccuracies and other elevation anomalies. The analysis was run at a1 ft x 1 ft raster resolution. The DEM accuracy for each county varies based what is currently available. Here the breakdown of DEM accuracy for each county used in this project: Anne Arundel County DEM year is 2017 and horizontal resolution is 1ft. Baltimore County DEM year is 2015 and horizontal resolution is 2.5ft. Baltimore City DEM year is 2015 and horizontal resolution is 0.7m. Calvert County DEM year is 2017 and horizontal resolution is 1ft. Caroline County DEM year is 2013 and horizontal resolution is 3.125ft. Cecil county DEM year is 2013 and horizontal resolution is 0.6m. Charles County DEM year is 2014 and horizontal resolution is 0.9m. Dorchester County DEM year is 2013 and horizontal resolution is 0.9m. Harford County DEM is 2013 and horizontal accuracy is 1.5m. Kent County DEM year is 2015 and horizontal resolution is 0.7m. Prince George’s County DEM year is 2014 and horizontal resolution is 0.7m. Queen Anne’s County DEM year is 2013 and horizontal resolution is 0.6m. Somerset County DEM year is 2012 and horizontal accuracy is 1m. St Mary’s County DEM year is 2014 and Horizontal accuracy is 0.9m. Talbot County DEM year is 2015 and Horizontal accuracy is 0.7m. Wicomico County DEM year is 2012 and horizontal accuracy is 1m. Worchester County DEM year is 2011 and horizontal accuracy is 1m.The Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones data product was created by the Maryland Environmental Service (MES) in partnership with the Maryland Department of Environment (MDE) and the Coast Smart Council, under the guidance of the Maryland Department of Natural Resource (DNR).For additional information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

As included in this EnviroAtlas dataset, the community level domestic water use is calculated per capita in gallons of water per day (GPD), distributed dasymetrically, and summarized by census block group. Domestic water use, as defined in this case, is intended to represent residential indoor and outdoor water use (e.g., cooking, hygiene, landscaping, pools, etc.) for primary residences (i.e., excluding second homes and tourism rentals). Water use in this EnviroAtlas-defined study area is estimated at 70-80 GPD across four counties. It was calculated as a weighted average of USGS Water Use estimates for public-supplied and self-supplied use according to population. The dasymetric data is a geospatial distribution of population across the landscape. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

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 1000 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 MD iMap 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 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/MapServer/1

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 EnviroAtlas dataset shows the Baltimore, MD EnviroAtlas community boundary. It represents the outside edge of all the block groups included in the EnviroAtlas Community. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

This EnviroAtlas dataset describes the block group population and the percentage of the block group population that has potential views of water bodies. A potential view of water is defined as having a body of water that is greater than 300m2 within 50m of a residential location. The window views are considered "potential" because the procedure does not account for presence or directionality of windows in one's home. The residential locations are defined using the EnviroAtlas Dasymetric (2011/October 2015) map. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

This layer quantifies the yearly economic value of surface water protection provided by forests and wetlands across Maryland. About half of the water supply in Maryland is sourced from reservoirs. Natural lands are exceptionally important in maintaining water quality in reservoirs, reducing the cost to treat the water to water supply standards. This analysis is focused on the five major reservoirs in Maryland, Loch Raven, Liberty, Pretty Boy, Tridelphia, and Rocky Gorge are the major water sources for residents of the densely populated Baltimore-Washington corridor. The forests and wetlands within the watersheds of these reservoirs are of unique economic value, as help to provide clean water, reducing the cost of treatment, and avoiding the cost of expensive water treatment plant upgrades to maintain quality standards. Economic values are based on a number of factors, including the average cost savings of water treatment from having trees in the watershed, the municipal price of water, and the cost avoided of having to upgrade a treatment plant to advanced treatment. The average price was found to be $1.52 per m3 of water. Almost all of this service is concentrated in four counties- Baltimore, Carrol, Howard, and Montgomery, totaling $245 of the $246 million of value yearly.

This data layer was created as part of the Maryland Department of Natural Resources "Accounting for Maryland's Ecosystem Services" program.This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Map Service Link: https://mdgeodata.md.gov/imap/rest/services/Environment/MD_EcosystemServices/MapServer/22Download the Ecosystem Services layers at: https://www.dropbox.com/s/e6ovfcc01dxvnmo/EcosystemServices.gdb.zip?dl=0

The 5 - 10 Foot Sea Level Rise Inundation dataset is a derivative of high-resolution topographic data (LiDAR) that the State of Maryland in cooperation with local and federal agencies has acquired to identify areas vulnerable to inundation and flooding. The dataset represents inundation areas of Maryland coastal counties within the five to ten foot range of a ten foot sea level rise. Data is not available for Harford County, Prince George's County, and Baltimore City. 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 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-ROM's or DVD-ROM's 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.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/Weather/MD_SeaLevelRiseVulnerability/MapServer/2

Looking for information on a construction project near you? Project Portal offers a comprehensive view of all current, funded, and planned projects occurring across the State of Maryland. You can quickly and easily access specific project information, including a general overview, interactive map, news, schedule, pictures and video, supporting documents, and upcoming public meetings. It’s easy to search by location for a specific project, or by county for a list of all projects in your jurisdiction.(MDOT SHA Project Portal Individual Project Page Web Map)MDOT SHA WebsiteContact Us

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