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.

This web map presents a vector basemap of OpenStreetMap (OSM) data hosted by Esri. Esri created this vector tile basemap from the Daylight map distribution of OSM data, which is supported by Facebook and supplemented with additional data from Microsoft. This version of the map is rendered using OSM cartography. The OSM Daylight map will be updated every month with the latest version of OSM Daylight data.OpenStreetMap is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap site:www.OpenStreetMap.org. Esri is a supporter of the OSM project and is excited to make this enhanced vector basemap available to the ArcGIS user and developer communities.

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

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

Sum of city tax by zip code, based on real property taxes

Current Real Property Tax in Baltimore. For more detailed information, visit SDAT at http://sdat.resiusa.org/RealProperty/Pages/default.aspx

Tags

   soil survey, soils, Soil Survey Geographic, SSURGO




   Summary


   SSURGO depicts information about the kinds and distribution of

   soils on the landscape. The soil map and data used in the SSURGO

   product were prepared by soil scientists as part of the National

   Cooperative Soil Survey.


   Description


   This data set is a digital soil survey and generally is the most

   detailed level of soil geographic data developed by the National

   Cooperative Soil Survey. The information was prepared by digitizing

   maps, by compiling information onto a planimetric correct base

   and digitizing, or by revising digitized maps using remotely

   sensed and other information.


   This data set consists of georeferenced digital map data and

   computerized attribute data. The map data are in a 3.75 minute

   quadrangle format and include a detailed, field verified inventory

   of soils and nonsoil areas that normally occur in a repeatable

   pattern on the landscape and that can be cartographically shown at

   the scale mapped. A special soil features layer (point and line

   features) is optional. This layer displays the location of features

   too small to delineate at the mapping scale, but they are large

   enough and contrasting enough to significantly influence use and

   management. The soil map units are linked to attributes in the

   National Soil Information System relational database, which gives

   the proportionate extent of the component soils and their properties.


   Credits

   There are no credits for this item.


   Use limitations


   The U.S. Department of Agriculture, Natural Resources Conservation

   Service, should be acknowledged as the data source in products

   derived from these data.


   This data set is not designed for use as a primary regulatory tool

   in permitting or citing decisions, but may be used as a reference

   source. This is public information and may be interpreted by

   organizations, agencies, units of government, or others based on

   needs; however, they are responsible for the appropriate

   application. Federal, State, or local regulatory bodies are not to

   reassign to the Natural Resources Conservation Service any

   authority for the decisions that they make. The Natural Resources

   Conservation Service will not perform any evaluations of these maps

   for purposes related solely to State or local regulatory programs.


   Photographic or digital enlargement of these maps to scales greater

   than at which they were originally mapped can cause misinterpretation

   of the data. If enlarged, maps do not show the small areas of

   contrasting soils that could have been shown at a larger scale. The

   depicted soil boundaries, interpretations, and analysis derived from

   them do not eliminate the need for onsite sampling, testing, and

   detailed study of specific sites for intensive uses. Thus, these data

   and their interpretations are intended for planning purposes only.

   Digital data files are periodically updated. Files are dated, and

   users are responsible for obtaining the latest version of the data.


   Extent



   West -76.713689  East -76.526117 

   North 39.374398  South 39.194856 




   Scale Range

   There is no scale range for this item.

This feature class represents the petitioned sewer master plan areas that have been introduced in previous years through cycle amendments within Baltimore County. Unlike the SHisMasterPlan feature class, this feature class does not distinguish between different cycle amendment petitions and only reflects the most current sewer master plan designation.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.

Road centerlines for Baltimore County, Maryland. Includes road names and road ranges.

Feature class contains all contour lines for Baltimore County. Contours are captured in 2 foot intervals. Contours were created from LiDAR captured to meet or exceed the FEMA QL 2 specification. LiDAR was captured in April of 2014.

Baltimore County's Urban Rural Demarcation Line (URDL) has divided the county into "urban" and "rural" areas since established by the Planning Board in 1967. Developed primarily as a growth management tool, it has influenced zoning, land-use, and infrustructure decisions, and was the baseline for the Baltimore County part of Maryland's Priority Funding Area. However, this boundary (digitized at a scale of 1:24,000 where 1" represents 2,000') was became obsolete as the county's GIS data increased in resolution (to 1:2,400 where 1" represents 200'). Until recently, determining a property's status as either urban or rural was of a highly interpretative nature. A new URDL was developed to more accurately match the 1:2,400 data (parcel, street centerline, zoning, etc). This version was reviewed and modified in a series of meetings with several interested county agencies. The new URDL removes much of the old one's ambiguity while keeping its original intent. The new URDL was reviewed, modified, and subsequently approved by the Planning Board on June 19, 2003. Minor revisions were effected 9/2/04, 10/21/04, 9/4/07, 5/21/09, 10/1/09 and 11/15/12. The URDL_poly feature class is one part of the URDL feature dataset.

The percent of properties that are classified as being vacant and abandoned that are owned by Baltimore City. Baltimore City has come to own these properties through a variety of ways including (but not limited to) eminent domain, unpaid tax or water bills, and direct purchase. Source: Baltimore City Department of Housing and Community Development Years Available: 2011, 2012, 2013, 2017, 2018, 2019, 2020, 2021, 2022, 2023

The number of residential properties that received the Historic Tax Credit per 1,000 residential properties within an area. The credit is granted on the increased assessment directly resulting from qualified improvements. The duration of the credit is for 10 years, and is applicable to properties located in designated areas of significant historical value. Source: Baltimore City Department of Finance Years Available: 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2023

The number of residential properties that received the homeowners tax credit per 1,000 residential properties within an area. The homeowner's tax credit sets a limit on the amount of property taxes any homeowner must pay based upon his or her income. Source: Baltimore City Department of Finance Years Available: 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2021, 2023

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.

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

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 Maryland Coordinate System, U.S. Survey Foot. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

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

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

The number of residential properties that received the homestead tax credit per 1,000 residential properties within an area. The Homestead Credit limits the increase in taxable assessments each year to a fixed percentage. Every county and municipality in Maryland is required to limit taxable assessment increases to 10% or less each year, with the Baltimore City rate capped at 4%. Source: Baltimore City Department of Finance Years Available: 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2023