The layer will be removed from the iMap Data Catalog in the near future. To access the most recent Baltimore City neighborhood data please visit https://data.baltimorecity.gov/datasets/baltimore::neighborhood-1.

Qualified Census Tract geometries within Baltimore City Limits. Based on data from HUD published September 2024.Change Log2022-2-15:- Added FY2022 data- Metadata added- Columns renamed to a standard format- Agency names reformatted with Workday conventions2024-8-27:update the dataset and metadata to reflect the current data and descriptionData Dictionaryfield_namedescriptiondata_typerange_of_possible_valuesexample_valuessearchableCensus Tract 2010 The ID of the US census tract from 2010 Census results. Only Qualified Census tracts are includedTextIDs of QCT's in Baltimore city range from 24510030100 to 24510280500, but not by regular intervals since only tracts designated QCT are listed. The values are not integers, they are numerical IDs.24510070200NogeometryMulti-polygon shapes for each census tractThese are shape polygons, thus don't have a single value or expected rangeNo To leave feedback or ask a question about this dataset, please fill out the following form: Baltimore City Qualified Census Tracts feedback form.

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 1,000 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.This data set represents the Department of Natural Resources interpretation of the location and extent of the Critical Area; however, the digital maps are not recognized as the "official" maps. In accordance with Subsection 8-1807(a) of the Critical Area Act, the Critical Area consists of (1) All waters and lands under the Chesapeake Bay and its tributaries to the head of tide as indicated on the State wetland maps, and all State and private wetlands designated under Environment Article, Title 16, annotated Code of Maryland; (2) All land and water areas within 1,000 feet beyond the landward boundaries of State or private wetlands and the of tides designated under Environment Article, Article 16, Annotated Code of Maryland; and (3) Modification to these areas through inclusions or exclusions proposed by local jurisdictions and approved by Commission as specified in Natural Resources Article, Subsection 8-1807, annotated Code of Maryland. These maps are hard copy maps that cannot be exactly replicated in a digital format; therefore, some interpretation was necessary to create the digital line. Hard copy maps depicting the official Critical Area boundary line are available for review at the Chesapeake Bay Critical Area Commission, and at most local planning and zoning departments. 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 intended use is for general information and planning purposes. It is not intended to be used to determine the exact location of the Critical Area boundary on a specific parcel or to determine the acreage within the Critical Area on a specific site. 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-ROMs or DVD-ROMs 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.There were many parties involved in producing Maryland's Critical Area data and the key parties will be listed. Each county and city (listed below) produced a hard copy map and submitted the map to the Chesapeake Bay Critical Area Commission (CBCAC) for approval. Through Coastal Zone Management grants, CBCAC digit

Median household income is the middle value of the incomes earned in the prior year by households in an area. Income and earnings are inflation-adjusted for the last year of the 5-year period. The median value is used as opposed to the average so that both extremely high and extremely low prices do not distort the total amount of income earned by households in an area. Source: American Community SurveyYears Available: 2006-2010, 2007-2011, 2008-2012, 2009-2013, 2010-2014, 2011-2015, 2012-2016, 2013-2017, 2014-2018, 2015-2019, 2016-2020, 2017-2021, 2018-2022, 2019-2023Please note: We do not recommend comparing overlapping years of data due to the nature of this dataset. For more information, please visit: https://www.census.gov/programs-surveys/acs/guidance/comparing-acs-data.html

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

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.

Forest areas by commercial type for Baltimore County and City circa 1914. Forest types identified include merchantable hardwoods, culled hardwoods, hardwood saplings, scrub pine, scrub pine saplings, and mixed hardwoods and scrub pine. Statistical data on the amount of saw timber per acre by forest type is also presented. In addition to showing the forest stand data the map has very detailed transportation, urban area, hydrological, and topographic features. The map was scanned at a resolution of approximately 4.3 meters, it was then georeferenced using 22 control points from 1:100000 hydrologic and transportation data and rectified to UTM Zone 18N, NAD83. The cell size on the rectified map was set to 10m in order to reduce the size of the rectified map. Please exercise caution when using this dataset since significant positional inaccuracies do exist. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

This forest patch layer was created using a 2017/18 high-resolution urban tree canopy map of Baltimore City derived from LiDAR and NAIP imagery (CBPO 2022). To identify forest area, tree canopy over impervious surfaces was first subtracted from the canopy layer, including buildings and roads identified from planimetric data available from Baltimore City (https://data.baltimorecity.gov/). Morphological spatial pattern analysis (MSPA; Vogt et al. 2007) was then used to distinguish forest patches from remaining tree canopy using an edge parameter of 15 m based on observed changes in vegetation composition and structure (Baker, unpublished data). MSPA applies the edge parameter to distinguish interiors (i.e. ‘cores’) from surrounding edges, as well as five other morphometric primitives (i.e. branches, bridges, loops, and islets) that reflect how canopy is or is not connected to cores. Patches always include core areas and their surrounding edges, as well as any perforations. Patches are separated into two size classes: Forested Natural Areas are patches with greater core area and thickness than Groves. Patches are classified by land ownership categories using local parcel data available from Baltimore City (https://data.baltimorecity.gov/). Ownership categories include: Federal, State, Municipal, Commercial/Industrial, Institutional, and Private Residential owners. Parcels with unknown ownership were assigned Municipal ownership.

Exisiting and proposed park lands in Baltimore City and part of Baltimore County, 1904. The map was scanned at a resolution of approximately 2.55 meters, it was then georeferenced using 15 control points from 1:100000 hydrologic and transportation data and rectified to UTM Zone 18N, NAD83. Please exercise caution when using this dataset since significant positional inaccuracies do exist. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

This Sector boundary data shows the coverage areas that divide each District into smaller geographic areas for BPD’s internal administrative purposes. They also serve to group together the sub-Sector administrative boundaries called Posts, which help determine the correct assignment of BPD units to calls for service. For each current District there exist two Sectors (e.g., Sector 1, Sector 2). There are a total of 18 Sectors across the City.DATA DICTIONARY:Field NameDescriptionDistrictCodeThe code number value of each Police District, as designated by the Police Department.DistrictNameOfficial names for each Police District.DistrictAbbrThe abbreviation values for each Police District.SectorNumThe code number value of each Police Sector in each District, as designated by the Police Department.SectorNameOfficial names for each Police Sector in each District.SectorLabelOfficial names for each Police Sector in each District; also used as labeling values for cartographic purposes.Shape_LengthESRI geodatabase length field (in feet).Shape_AreaESRI geodatabase area field (in square feet). To leave feedback or ask a question about this dataset, please fill out the following form: Police Sectors feedback form.

This dataset represents the location and characteristics of major (Group A) crime against persons such as homicide, shooting, robbery, aggravated assault etc. within the City of Baltimore. Data is updated weekly. This dataset contains crime data starting 1/1/2022 through present.Note: The way the Baltimore Police Department collects and reports data on crimes has changed, effective Jan. 1, 2025. The FBI has mandated that all law enforcement agencies across the country make the transition to the National Incident-Based Reporting System (NIBRS) to improve the overall quality, accuracy and timeliness of crime data collected.For more information, visit: https://www.baltimorepolice.org/nibrs If you have any questions or need to report an issue for this dataset, please use this feedback form to submit your response, and the Open Baltimore support team will contact you.DATA DICTIONARY:

    Field Name
    Description

  CCNumberUnique identifier for the record.
  CrimeDateTimeDate and time when the crime occurred.
  DescriptionType of crime incident reported.
  CrimeCodeCode assigned to categorize the crime type.
  WeaponIndicates if a weapon was involved in the crime incident.
  ShootingIndicates if a shooting of a firearm was involved in the crime incident.
  PostPolice post (sub-unit of geography under districts) under the current mapping scheme.
  GenderSex or gender of the victim.
  AgeAge of the victim.
  RaceRace of the victim.
  EthnicityEthnicity of the victim.
  Old_DistrictPolice district under the previous mapping scheme.
  New_DistrictPolice district under the current mapping scheme.
  Inside_OutsideIndicates whether the crime occurred indoors or outdoors.
  NeighborhoodNeighborhood where the incident occurred.
  LocationAddress or general location where the incident occurred.
  LongitudeLongitude of the incident's geographic location.
  LatitudeLatitude of the incident's geographic location.
  GeoLocationConcatenation of the Latitude and Longitude fields.
  PremiseTypeType of premise where the incident occurred (residence, business, vacant building).
  Total_IncidentsTotal number of incidents occurring for the reported crime.

Listing of area dialysis centers developed by the Baltimore City Department of Health

The total number of businesses (both for-profit and non-profit) that report having less than 50 persons employed within an area at a single time in a year. Source: InfoUSA Years Available: 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023

Information on parking citations issued within the City of Baltimore. Data represents 2 rolling years of citations and any older citations with outstanding balances

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 dataset shows the 36 facilities of the State Highway Administration (SHA), including maintenance offices, landscape depots, and district offices, as well as the SHA Headquarters in Baltimore City and Hanover Complex.

The percent of persons, out of all persons living in an area, 65 years and above. Source: U.S. Bureau of the Census, American Community SurveyYears Available: 2010, 2011-2015, 2012-2016, 2013-2017, 2014-2018, 2015-2019, 2017-2021, 2018-2022, 2019-2023Please note: We do not recommend comparing overlapping years of data due to the nature of this dataset. For more information, please visit: https://www.census.gov/programs-surveys/acs/guidance/comparing-acs-data.html

This GIS dataset contains growth tier maps adopted by local (county and municipal) jurisdictions under SB236. Data are generally collected from county and municipal jurisdictions by the Maryland Department of Planning (Planning) or digitized by Planning in coordination with local jurisdictions. For more information about SB236, see Planning’s Septics Law Implementation Website at https://planning.maryland.gov/Pages/OurWork/SB236Implementation.aspxThis document describes standard operating procedures for aggregating growth tier map GIS data. These procedures may not apply to historical data (i.e. records for which both the SRC_DATE and GIS_SRC fields are blank). For example, Planning may have realigned historical data from local jurisdictions to parcel polygon boundaries or used different procedures to represent municipal tiers when municipalities concurred with county tier maps.Planning generally requests updated GIS data once a jurisdiction notifies Planning that a growth tier map has been amended. Aggregated data may be outdated or incomplete if Planning has not yet received or processed GIS updates from jurisdictions. Planning generally does not alter geometries received from the local jurisdictions except to divide municipal tiers at the county boundary (see JURSCODE field description). This dataset may contain overlap where multiple jurisdictions designate tiers in the same area.Fields include:JURSCODE – MdProperty Viewjurisdiction code (four-letter county or Baltimore City code). For tiers designated by counties, this is the jurisdiction responsible for designating the growth tier. For tiers designated by municipalities, this is the jurisdiction in which the growth tier is physically located. Municipal tiers that cross counties are divided at the county boundary so this field can be populated. See the MUNI field for the municipality responsible for designating a municipal tier.County – Full name of the jurisdiction represented by the JURSCODE.MUNI – The name of the municipality responsible for designating the tier. This field will be blank (‘ ‘) if the tier has been designated by a county. The MUNI field is formatted consistently with municipality names in the Planning’s municipal boundary datasets. When municipalities adopt tier maps by concurring with county tiers instead of submitting tier data independently, the MUNI field remains blank within the entire county tier map dataset. Depending on internal needs, an independent municipal tier dataset may or may not be generated by Planning and included within the aggregated tiers.TIER – Growth tier identifier used by the source jurisdiction and standardized as Tier 1, Tier 1A, Tier 2, Tier 2A, Tier 3, and Tier 4. May include additional alphabetical annotations used by the jurisdictions such as Tier 2B. If the TIER_CODE field is 99, the TIER field retains the descriptor provided by the jurisdiction, which may be a blank or null value.TIER_CODE – Integer field containing the growth tier standardized by Planning: 1 (Tier I); 11 (Tier IA or any other annotated version of Tier I, such as IB, etc.); 2 (Tier II), 22 (Tier IIA or any other annotated version of Tier II, such as IIB, etc.); 3 (Tier III); 4 (Tier IV); 44 (Areas annotated as Tier IVA for municipal greenbelts or any other annotated version of Tier IV); 99 – Areas included in the jurisdiction’s growth tier GIS data that are not assigned a tier, such as rights-of-way or water.Adopt_Date – Date growth tier map was adopted or amended. When a local jurisdiction updates its growth tier map, Planning generally requests a comprehensive GIS update to replace all existing data for the jurisdiction.Acres – GIS acres calculated by Planning in NAD83 Meters (EPSG 26985)GIS_SRC (GIS Source) – The original source of the GIS spatial and attribute information Planning obtained, which concatenates the JURSCODE field (or MUNI field for municipal tier maps), followed by a space, followed by the name of the shapefile or feature class received from the jurisdiction. Field contains “MDP” if tiers were digitized by Planning, and is blank (‘ ‘) for historical data.SRC_DATE (GIS Source Date) – The date (YYYYMMDD) the GIS data were obtained by Planning from the local jurisdiction. If the month or day is unknown, the date is YYYY0000. If Planning digitized the growth tier map in coordination with a local jurisdiction, this should be the date Planning’s edits are verified by the jurisdiction. This field will be blank (‘ ’) if Planning’s edits have not been verified or if the dataset is historical and the source is unknown.NOTE – Text field containing additional notes about the dataLast Updated: 7/26/2023This is a Maryland Department of Planning hosted service. Find more information on https://imap.maryland.govMap Service Link: https://mdpgis.mdp.state.md.us/arcgis/rest/services/PlanningCadastre/Septic_Growth_Tiers/MapServer

The percent of persons between the ages of 16 and 64 that are in the labor force (and are looking for work) but are not currently working. Source: American Community Survey Years Available: 2006-2010, 2007-2011, 2008-2012, 2009-2013, 2010-2014, 2011-2015, 2012-2016, 2013-2017, 2014-2018, 2015-2019, 2016-2020, 2017-2021, 2018-2022, 2019-2023Please note: We do not recommend comparing overlapping years of data due to the nature of this dataset. For more information, please visit: https://www.census.gov/programs-surveys/acs/guidance/comparing-acs-data.html

This EnviroAtlas dataset describes the breakdown of the land cover classes with each Census Block Group. In this community, forest is defined as Trees & Forest and Woody Wetlands. Green space is defined as Trees & Forest, Grass & Herbaceous, Agriculture, Woody Wetlands, and Emergent Wetlands. Agriculture is defined as Agriculture alone. Wetlands are defined as Woody Wetlands and Emergent Wetlands. This dataset also includes the area per capita for each block group for some land cover types. 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).