Neighborhoods within Baltimore City limits. This dataset was sourced from Baltimore Neighborhood Indicators Alliance (BNIA). No additional

   metadata was provided with the dataset.


   This is part of a collection of 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.

Baltimore City boundary limits. This is the "official" city boundary used by many Baltimore agencies. It DOES NOT agree with the universal MSA boundaries dervied from GDT census data. 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.

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

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

Geospatial data about Baltimore Metro - Baltimore County Boundary. Export to CAD, GIS, PDF, CSV and access via API.

These boundaries were developed by the Department of Planning based on 2020 Census data. Be aware that other organizations may use different neighborhood boundaries in their analyses.Demographics included are: race, ethnicity, gender, vacancy rate, homeowner status, family structure, and age.DATA DICTIONARY:

Field Name

Description

Name

Name of neighborhood statistical area

Population

Total population (P3)

White

White alone population (P3)

Blk_AfAm

Black or African American alone population (P3)

AmInd_AkNa

American Indian/Native Alaskan alone population (P3)

Asian

Asian alone population (P3)

NatHaw_Pac

Native Hawaiian and other Pacific Islander alone population (P3)

Other_Race

Some other race alone population (P3)

TwoOrMore

Two or more races population (P3)

Hisp_Lat

Hispanic or Latino population (P4)

Male

Male population (P12)

Female

Female population (P12)

Total_Units

Total housing units (H1)

Occ_Occupied

Occupied housing units (H3)

Occ_Vacant

Vacant housing units (H3)

Tenure_Owner

Owner-occupied units (H4)

Tenure_Renter

Renter-occupied units (H4)

Vacant_ForRent

Vacant units for rent (H5)

Vacant_ForSale

Vacant units for sale (H5)

Vacant_Other_All

All other vacant units (H5)

HH_Total

Total households (P16)

HH_Family

Total family households (P16)

HH_Married

Married couple family households (P16)

HH_OtherFamily

Other family households (P16)

HH_Male_NoSpouse

Male householder, no spouse present family household (P16)

HH_Female_NoSpouse

Female householder, no spouse present family household (P16)

HH_NonFamily

Total nonfamily households (P16)

HH_NonFamilyAlone

Householder living alone nonfamily households (P16)

HH_NonFamilyNotAlone

Householder not living alone nonfamily households (P16)

HH18_With18

Households with one or more people under 18 (P21)

HH18_FamilyWith18

Family households with one or more people under 18 (P21)

HH18_NonFamilyWith18

Nonfamily households with one or more people under 18 (P21)

HH18_No18

Households with no people under 18 (P21)

HH18_FamilyNo18

Family households with no people under 18 (P21)

HH18_NonFamilyNo18

Nonfamily households with no people under 18 (P21)

Age_U5

Population under 5 years (P12)

Age_5_9

Population age 5-9 (P12)

Age_10_14

Population age 10-14 (P12)

Age_15_17

Population age 15-17 (P12)

Age_18_21

Population age 18-21 (P12)

Age_22_24

Population age 22-24 (P12)

Age_25_29

Population age 25-29 (P12)

Age_30_34

Population age 30-34 (P12)

Age_35_39

Population age 35-39 (P12)

Age_40_44

Population age 40-44 (P12)

Age_45_49

Population age 45-49 (P12)

Age_50_54

Population age 50-54 (P12)

Age_55_59

Population age 55-59 (P12)

Age_60_64

Population age 60-64 (P12)

Age_65_69

Population age 65-69 (P12)

Age_70_74

Population age 70-74 (P12)

Age_75_79

Population age 75-79 (P12)

Age_80_84

Population age 80-84 (P12)

Age_85up

Population age 85 and up (P12)

Med_Age

Median age (P13)

Med_Age_Male

Median male age (P13)

Med_Age_Female

Median female age (P13)

To leave feedback or ask a question about this dataset, please fill out the following form: Neighborhood Statistical Area (NSA) Boundaries feedback form.

Detailed street boundaries for Baltimore City. No metadata was provided with this dataset; the UVM Spatial Analysis Lab has attempted to evaluate this dataset and generate metadata. This dataset depicts the linear boundaries for street and paved areas in Baltimore City and has an extremely high degree of positional accuracy. For the best available transportation data use the Roads_GDT_MSA dataset. 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.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2010 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

This is a MD iMAP hosted service. Find more information on http://imap.maryland.gov. ' above published service description.A representation of the boundaries of Baltimore City neighborhoods. The data can be obtained from the Baltimore City Open Data Portal at https://data.baltimorecity.gov/Neighborhoods/Neighborhoods-Shape/ysi8-7icr. Map Service Link: http://geodata.md.gov/appdata/rest/services/ TrainingProgram/MD_BaltimoreCityNeighborhoods/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.

Line feature showing the political boundary of Baltimore City. Last Updated 2008

Detailed street boundaries for Baltimore City. No metadata was provided with this dataset; the UVM Spatial Analysis Lab has attempted to evaluate this dataset and generate metadata. This dataset depicts the linear boundaries for street and paved areas in Baltimore City and has an extremely high degree of positional accuracy. For the best available transportation data use the Roads_GDT_MSA dataset. 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.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

Parcels_2003_BACI File Geodatabase Feature Class Thumbnail Not Available Tags BES Summary There is no summary for this item. Description Parcel Data for Baltimore City obatined from BNIA will all extraneous fields removed. Editing in progress The following edits were performed: 1) Resolved edge matching issues with Baltimore County parcels that border it and fall within the Gwynns Falls Watershed. 2) BLOCKLOT errors were noted and if necessary corrected. The BLOCKLOT ID is used to link the parcel data to the MD Property View A&T database. It should be pointed out that in some instances a single BLOCKLOT ID in the Property View A&T database may correspond to more than one parcel. There are only 14 instances were a single BLOCKLOT ID corresponds to 4 or more parcels, these are typically railroads, utility, or government properties. In other cases a single BLOCKLOT ID may correspond to two separate parcels that are essentially one property bisected by a road. There are other instances where there appears no logical explanation for a single BLOCKLOT ID corresponding to multiple parcels. Credits UVM Spatial Analysis Lab Use limitations There are no access and use limitations for this item. Extent West -76.713328 East -76.525885 North 39.374474 South 39.195051 Scale Range There is no scale range for this item.

Parcels_2004_BACI File Geodatabase Feature Class Thumbnail Not Available Tags Social Order, Land, Social System, Hierarchy, Territory, Parcels, BES, Property Summary Land ownership analysis. Description Property Parcel boundaries for Baltimore City, 2004 edition. Can be linked to the MD Property View Assessors and Taxation (A&T) Databse using the BLOCKLOT field. Accuracy issues have been observed in this layer, particularly in areas where there appears to have been recent construction. In those areas parcel boundaries may not correspond to actual ground conditions. In addition 12 parcels have no BLOCKLOT identifier, another 97 have BLOCKLOT codes identifying them as 'ROW', 'ERROR', or 'ERROR/ROW', leaving 109 parcels that cannot be joined to the A&T Database. Excluding these, there are 242 duplicate BLOCKLOT codes shared by 672 parcels. The number of duplicates for a single parcel ranges from 2 to 72. Credits UVM Spatial Analysis Lab Use limitations BES use only. Extent West -76.713449 East -76.525885 North 39.374474 South 39.195049 Scale Range There is no scale range for this item.

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

Ward boundaries for Baltimore, Maryland; circa 1876. Refer to the Sarah Hinman's enclosed thesis for more information. 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.

Line feature showing the political boundary of Baltimore City. Last Updated 2008

Parcel Data for Baltimore City obatined from BNIA will all extraneous fields removed. Editing in progress The following edits were performed: 1) Resolved edge matching issues with Baltimore County parcels that border it and fall within the Gwynns Falls Watershed. 2) BLOCKLOT errors were noted and if necessary corrected. The BLOCKLOT ID is used to link the parcel data to the MD Property View A and T database. It should be pointed out that in some instances a single BLOCKLOT ID in the Property View A and T database may correspond to more than one parcel. There are only 14 instances were a single BLOCKLOT ID corresponds to 4 or more parcels, these are typically railroads, utility, or government properties. In other cases a single BLOCKLOT ID may correspond to two separate parcels that are essentially one property bisected by a road. There are other instances where there appears no logical explanation for a single BLOCKLOT ID corresponding to multiple parcels. 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 dataset represents the ward precinct voting boundaries for the city of Baltimore. This dataset was updated in 2022 to reflect the new Legislative and Congressional districts To leave feedback or ask a question about this dataset, please fill out the following form: Ward-Precincts feedback form.

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