This dataset represents real property information within a parcel of land in the City of Baltimore. The data dictionary for this dataset can be accessed by visiting the following link.: Data Dictionary For Real Property Information | Open Baltimore (baltimorecity.gov). Data is updated on a weekly basis. To leave feedback or ask a question about this dataset, please fill out the following form: Real Property Information feedback form.

Outlines the boundaries of the Baltimore County Historic Districts. The agreement by the owners of 75 percent of the property within a proposed district’s boundary is required to form a local historic district. Any exterior modification or addition to a structure in a district, or any excavation building, or demolition permit, is subject to approval by the Landmarks Preservation Commission.

Subdivision boundaries for Baltimore County.

The cadastral data set is a representation of property boundaries as defined by legal records. The cadastral features captured in the database include parcels, lots, rights-of-ways and subdivision boundaries. Each parcel contains an Account Identifier.

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

This layer is a high-resolution tree canopy change-detection layer for Baltimore City, MD. It contains three tree-canopy classes for the period 2007-2015: (1) No Change; (2) Gain; and (3) Loss. It was created by extracting tree canopy from existing high-resolution land-cover maps for 2007 and 2015 and then comparing the mapped trees directly. Tree canopy that existed during both time periods was assigned to the No Change category while trees removed by development, storms, or disease were assigned to the Loss class. Trees planted during the interval were assigned to the Gain category, as were the edges of existing trees that expanded noticeably. Direct comparison was possible because both the 2007 and 2015 maps were created using object-based image analysis (OBIA) and included similar source datasets (LiDAR-derived surface models, multispectral imagery, and thematic GIS inputs). OBIA systems work by grouping pixels into meaningful objects based on their spectral and spatial properties, while taking into account boundaries imposed by existing vector datasets. Within the OBIA environment a rule-based expert system was designed to effectively mimic the process of manual image analysis by incorporating the elements of image interpretation (color/tone, texture, pattern, location, size, and shape) into the classification process. A series of morphological procedures were employed to insure that the end product is both accurate and cartographically pleasing. No accuracy assessment was conducted, but the dataset will be subjected to manual review and correction. 2006 LiDAR and 2014 LiDAR data was also used to assist in tree canopy change.

This is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. 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 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.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Environment/MD_CriticalAreas/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.

Easements in Baltimore County, Maryland are created as the right to use another persons land for a stated purpose. It may involve a general or specific portion of a property. These property boundaries include Ingress and Egress Easement,Stormwater Management Easement, Stormwater Management Reservation and Utility easement.

The total number of residential properties located within an area as identified by Maryland Property View. It is important to note that that this indicator is a count of properties (single family homes, condominiums, and duplexes) and that a property can be comprised of multiple housing units. Source: MdProperty View Years Available: 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020

This feature class represents the petitioned water master plan areas that have been introduced in previous years through cycle amendments within Baltimore County. All information was gathered from petition and approval documentation, with the property boundaries given on source maps used to compile geographic features from existing digital cadastral data. These features contain spatial data representing the boundaries of petitioned and effective master plans areas, as well as information about the effective date, cycle amendment numbers, associated properties, zoning designations, councilmanic and election districts, feature lineage, location within the BCMD and Urban Rural Demarcation Line (URDL), and links to digital source documentation.The water master plan geodatabase includes a feature data set (WaterMasterPlan) containing three feature classes: WCurMasterPlan, WaterCombined and WHisMasterPlan. The feature classes participate in a topology (tWaterMasterPlan). The WCurMasterPlan feature class represents the petitions for the current cycle. The WaterCombined represents the current master plan designation within the county. The WHisMasterPlan contains all of the petitions areas from all cycles. The geodatabase includes relationship classes that associate related table containing information on assessments, councilmanic districts, election districts, lineage (feature level metadata), plan map, recommendations and zoning designations.

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 feature class represents the petitioned sewer master plan areas that have been introduced in previous years through cycle amendments within Baltimore County. All information was gathered from petition and approval documentation, with the property boundaries given on source maps used to compile geographic features from existing digital cadastral data. These features contain spatial data representing the boundaries of petitioned and effective master plans areas, as well as information about the effective date, cycle amendment numbers, associated properties, zoning designations, councilmanic and election districts, feature lineage, location within the BCMD and Urban Rural Demarcation Line (URDL), and links to digital source documentation.The sewer master plan geodatabase includes a feature data set (sewerMasterPlan) containing three feature classes: SCurMasterPlan, sewerCombined and SHisMasterPlan. The feature classes participate in a topology (tsewerMasterPlan). The SCurMasterPlan feature class represents the petitions for the current cycle. The sewerCombined represents the current master plan designation within the county. The SHisMasterPlan contains all of the petitions areas from all cycles. The geodatabase includes relationship classes that associate related table containing information on assessments, councilmanic districts, election districts, lineage (feature level metadata), plan map, recommendations and zoning designations.

In this feature class, the number of structures within a park parcel is given by four fields described below:Count_of_Buildings_In_Parcel: This field counts the total number of structures contained in a particular park parcel.Count_of_Buildings_Outside_FZ: This field counts the number of structures contained in a particular park parcel that do not fall within the 100-year or 500-year flood zones.Count_of_Buildings_in_500yr_FZ: This field counts the number of structures contained in a particular park parcel that also intersect flood zone X per the 2022 preliminary Digital Flood Insurance Rate Map.Count_of_Buildings_in_100yr_FZ: This field counts the number of structures contained in a particular park parcel that also intersect the FEMA special flood hazard area per the 2022 preliminary Digital Flood Insurance Rate Map.The building structures counted in this feature class include Residential, Commercial, Institutional, Garages, Other structures, Buildings under Construction, Water Towers, Storage Tanks, and Silos, as provided by Baltimore County.

The Comprehensive Zoning Map Process (CZMP) takes place every four years where any citizen may request a zoning change on any property in the County. The request for change is mapped as an issue. The County Council enacting legislation for each issue whether to retain the existing zoning or to enact a different zone(s) or district(s).

The Comprehensive Zoning Map Process (CZMP) takes place every four years where any citizen may request a zoning change on any property in the County. The request for change is mapped as an issue. The County Council enacting legislation for each issue whether to retain the existing zoning or to enact a different zone(s) or district(s).

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