This dataset represents Baltimore City Council Districts. Below is a description of the fields/attributes contained in the layer.

DATA DICTIONARY:

Field Name

Description

AREA_NAME

Baltimore City Council district number.

CNTCT_NME

Baltimore City Council district representative.

CNTCT_PHN

Baltimore City Council district representative contact phone number.

CNTCT_EML

Baltimore City Council district representative contact email address.

CNTCT_ADDR

Baltimore City Council address.

CNTCT_CITY

Baltimore City Council city (Baltimore).

CNTCT_ZIP

Baltimore City Council zip code.

totalPop

Total population according to the 2020 Census.

White

White alone population according to the 2020 Census.

BlackAfAm

Black or African American alone population according to the 2020 Census.

HispanicLat

Hispanic alone population according to the 2020 Census.

Asian

Asian alone population according to the 2020 Census.

AIAN

American Indian and Alaska Native alone population according to the 2020 Census.

NHPI

Native Hawaiian and Pacific Islander alone population according to the 2020 Census.

Other

Other demographic categories population according to the 2020 Census.

TwoOrMore

Two or more category population according to the 2020 Census.

URLHyperlink to the City Council member webpage.To leave feedback or ask a question about this dataset, please fill out the following form: Baltimore City Council District 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.

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

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.

The MetroDistrict feature class contains the current land area included in the metropolitan district in Baltimore County. The metropolitan district is a land planning area determines the status of whether or not a property is eligible for public water and sewer services.The metropolitan district geodatabase includes the MetroDistrict, MetroDistrictLine, MetroDistrictPoly, MetroDistrictMargin feature classes and BCMDLineage table.

The BPD District boundaries show the coverage areas of Baltimore City that BPD is responsible for by District and are used for correct assignment of Districts for response to calls for service in public safety and other applications.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.Dist_AltAlternate names for each Police District.Dist_NameOfficial names for each Police District.DistrictThe code number value of each Police District, as designated by the Police Department.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 Districts 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).

This feature class contains the adminstrative boundaries of the Commission for Historical and Architectural Preservation designated historical districts. To leave feedback or ask a question about this dataset, please fill out the following form: CHAP Historic Districts feedback form.

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.

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

This layer represents the seven Councilmanic districts for the Baltimore County Council, as adopted by Bill 22-22 – Revision of Councilmanic Districts, and described in Exhibit A (Map) and Exhibit B (Population and Demographic summary). Bill 22-22 was passed by the County Council at an Emergency Legislative Session on March 24, 2022 following acceptance of the Map by a Federal Court Judge on that date as part of the Redistricting litigation. Bill 22-22 supersedes the previously-passed Redistricting legislation (Bill 103-21). The Council will keep the public informed if there are any subsequent changes to this Redistricting Map.

The percent chance that two people picked at random within an area will be of a different race/ethnicity. This number does not reflect which race/ethnicity is predominant within an area. The higher the value, the more racially and ethnically diverse an area. Source: U.S. Bureau of the Census, American Community Survey Years 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

Urban area boundaries for 1801, part of the Baltimore-Washington Spatial Dynamics and Human Impacts dataset. The Baltimore-Washington Spatial Dynamics and Human Impacts dataset is an integrated and flexible temporal urban land characteristics database for the Baltimore-Washington metropolitan area. The compilation of this data is a collaborative effort led by the U.S. Geological Survey and the University of Maryland Baltimore County. The database provides visual and historical perspective of the urban growth experienced in the area between 1792 and 1992. Data on built-up areas exists as separate geographic layers for the dates: 1792, 1801, 1822, 1850, 1878, 1900, 1925, 1938, 1953, 1966, 1972, 1982, and 1992. Temporal urban mapping reconstructs past landscapes by incorporating historic maps, census statistics, and commerce records to generate a progressive geo-referenced picture of the past changes in a region. Contemporary mapping focuses on the use of remotely sensed data, existing digital land use data, digital census information, and a variety of earth science infrastructure data, such as Digital Line Graphs, Digital Elevation Models, and key ancillary demographic information. Different procedures were used for different time periods, more fully described for each file in the Process Step Section 2.5.2. The resulting database of temporal urban land use/land cover and demographic changes provides an ideal source of test data and information for both urban geographers and global change research scientists. While this dataset was developed by the University of Maryland Baltimore County final quality control and metadata generation was performed by the University of Vermont's Spatial Analysis Lab. Two significant problems were noted regarding this dataset. The first anomoly is that the 1801, 1822, and 1878 layers have a much smaller extent, and contain data only for Baltimore City. The second discrepancy is that there are also some very obvious positional errors causing misalignments between layers of different dates (i.e. urban areas become non-urban in a very short time period, an unlikely occurance). 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 County Boundary represents the land boundary for Baltimore County, Maryland.

Middle School district boundaries for Baltimore County.

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

This is the 2020 vintage of the 2020 TIGER/Line county boundary. It includes Anne Arundel County, Baltimore County, Baltimore City, Carroll County, Harford County, Howard County, and Queen Anne's County. Note this boundary is a new vintage of the TIGER file but is otherwise identical the the Census 2010 county boundary.Date: 1/21/2021 Update: Update: Irregular. While Census boundaries are updated every 10 years, the Census Bureau makes annual corrections to the geographies as needed. These updates are usually minor and BMC reviews them every few years.Source: Census TIGER/Line. More information on Census geography can be found at https://www.census.gov/geo/maps-data/data/tiger-line.html.

County boundaries for the BES Metropolitan Study Area (MSA) derived from year 2000 GDT census data. This is the universal MSA boundary for all BES research. The MSA consists of the following 5 counties: Baltimore City, Baltimore County, Anne Arrundel, Carroll, Harford, and Howard.

   This is part of a collection of Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase itself is available online at beslter.org or lternet.edu. It is considerably large. Upon request, it can be shipped to you on media, such as a flash 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 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.