The RP_2016 feature class combined with the Swr_2016 feature class represents the sewer deficient areas and areas of concern in the County as represented on the 2016 Sewer Basic Services Map. The 2016 Sewer Basic Services Map was enacted under bill number 18-16 and is part of the Baltimore County Zoning Regulations, 1955 as amended by the bill adopted May 2, 2016. Effective May 16, 2016.

The Int_2016 feature class combined with the TZ_2016 feature class represents the intersections with a level of service rating of D, E or F and the associated commutershed as represented on the 2016 Transportation Basic Services Map. The 2016 Transportation Basic Services Map was enacted under bill number 18-16 and is part of the Baltimore County Zoning Regulations, 1955 as amended by the bill adopted May 2, 2016. Effective May 16, 2016.

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.

The Wtr_2016 feature class represents water deficient areas as represented on the 2016 Water Basic Services Map.The 2016 Water Basic Services Map was enacted under bill number 18-16 and is part of the Baltimore County Zoning Regulations, 1955 as amended by the bill adopted May 2, 2016. Effective May 16, 2016.There were no deficient areas identified in 2016.

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.

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 digitized the county data. Maryland DNR's Chesapeake and Coastal Watershed Service finalized the data and is handling data distribution. Anne Arundel County, Office of Planning and Code Enforcement., Baltimore City, Department of Planning., Baltimore County, Department of Environmental Protection and Resource Management., Caroline County, Economic Development Commission., Calvert County, Department of Planning and Zoning (digital data not included)., Cecil County, Office of Planning and Zoning., Charles County, Department of Planning and Zoning., Dorchester County, Planning and Zoning Office., Harford County, Department of Planning and Zoning., Kent County, County Planning Commission., Prince George's County, Department of Environmental Resources., Queen Anne's County, Office of Planning and Zoning., St. Mary's County, Department of Planning and Zoning., Somerset County, Department of Technical and Community Services., Talbot County, Office of Planning and Zoning., Wicomico County, Office of Planning and Zoning., and Worcester County, Office of Planning, Permits and Inspections.

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

Zoning is a system of land use regulation that controls the physical development of land. It is a legal mechanism by which local government is able to regulate an owner’s right to use privately owned land for the sake of protecting the public health, safety, and/or general welfare. Land is mapped into different zones with the primary purpose of promoting compatible land uses and to separate incompatible uses.

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

This layer shows population, household, and employment forecasts at the TAZ level. Anne Arundel County data includes the City of Annapolis. Forecasts endorsed by the Baltimore Regional Transportation Board on July 28, 2020.The mission of the Cooperative Forecasting Group (CFG) is to develop a set of population, household, and employment control totals and small area forecasts to be used for transportation planning. The data set is utilized at BMC as an input to the travel demand model and for air quality conformity testing, and is available to federal, state, and local government agencies, as well as the general public. The local planning agencies that comprise the CFG are responsible for the development of the estimates and forecasts for their own jurisdictions. While methodologies vary between jurisdictions, the forecasts are generally based on local comprehensive plans, adopted zoning maps and regulations, and an inventory of residential holding capacity. The allocation of employment to the small area and its distribution across industry sectors is based largely upon an inventory of employers across the region.

New forecast rounds are developed on an as needed basis, but are generally triggered by the update of major planning documents by the local jurisdictions, significant unforeseen demographic shifts, and the availability of small area data. The members of the CFG have the opportunity to make annual updates to the cooperative forecasts to account for unexpected changes when a complete new “round” of forecasts is not warranted. For more information, see https://www.baltometro.org.

Date: July 28, 2020 Update: Varies, see above. New forecasts are added as separate Open Data items. Attributes:

Field

Description

TAZ10

2010 BMC traffic analysis zones

COUNTYFP10

County FIPS code

RPD10

2010 BMC regional planning districts

POP15

2015 Population

POP20

2020 Population

POP25

2025 Population

POP30

2030 Population

POP35

2035 Population

POP40

2040 Population

POP45

2045 Population

HH15

2015 Household count

HH20

2020 Household count

HH25

2025 Household count

HH30

2030 Household count

HH35

2035 Household count

HH40

2040 Household count

HH45

2045 Household count

EMP15

2015 Number of jobs

EMP20

2020 Number of jobs

EMP25

2025 Number of jobs

EMP30

2030 Number of jobs

EMP35

2035 Number of jobs

EMP40

2040 Number of jobs

EMP45

2045 Number of jobs

This feature class represents the petitioned water master plan areas that have been introduced in previous years through cycle amendments within Baltimore County. Unlike the WHisMasterPlan feature class, this feature class does not distinguish between different cycle amendment petitions and only reflects the most current water master plan designation.The water master plan geodatabase includes a feature data set (WaterMasterPlan) containing three feature classes: WCurMasterPlan, WaterCombined and WHisMasterPlan. The feature classes participate in a topology (tWaterMasterPlan). The WCurMasterPlan feature class represents the petitions for the current cycle. The WaterCombined represents the current master plan designation within the county. The WHisMasterPlan contains all of the petitions areas from all cycles. The geodatabase includes relationship classes that associate related table containing information on assessments, councilmanic districts, election districts, lineage (feature level metadata), plan map, recommendations and zoning designations.

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

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

The mission of the Cooperative Forecasting Group (CFG) is to develop a set of population, household, and employment control totals and small area forecasts to be used for transportation planning. The data set is utilized at BMC as an input to the travel demand model and for air quality conformity testing, and is available to federal, state, and local government agencies, as well as the general public. The local planning agencies that comprise the CFG are responsible for the development of the estimates and forecasts for their own jurisdictions. While methodologies vary between jurisdictions, the forecasts are generally based on local comprehensive plans, adopted zoning maps and regulations, and an inventory of residential holding capacity. The allocation of employment to the small area and its distribution across industry sectors is based largely upon an inventory of employers across the region.New forecast rounds are developed on an as needed basis, but are generally triggered by the update of major planning documents by the local jurisdictions, significant unforeseen demographic shifts, and the availability of small area data. The members of the CFG have the opportunity to make annual updates to the cooperative forecasts to account for unexpected changes when a complete new “round” of forecasts is not warranted. For more information, see https://www.baltometro.org.Date: July 15, 2022Update: Varies, see above. New forecasts will be added as separate Open Data items.

Attributes:

Field

Description

STATEFP20

State FIPS code

COUNTYFP20

County FIPS code

NAME

2020 TAZ name

TAZ20

2020 BMC Traffic Analysis Zone number

JUR

Jurisdiction code

JURNAME

Jurisdiction name

ACRES

Acres

RPD20

2020 BMC Regional Planning District number

RPDNAME

2020 RPD name

Round

CFG round number

Pop20

2020 Population

Pop25

2025 Population

Pop30

2030 Population

Pop35

2035 Population

Pop40

2040 Population

Pop45

2045 Population

Pop50

2050 Population

HHs20

2020 Number of households

HHs25

2025 Number of households

HHs30

2030 Number of households

HHs35

2035 Number of households

HHs40

2040 Number of households

HHs45

2045 Number of households

HHs50

2050 Number of households

Emp20

2020 Number of jobs

Emp25

2025 Number of jobs

Emp30

2030 Number of jobs

Emp35

2035 Number of jobs

Emp40

2040 Number of jobs

Emp45

2045 Number of jobs

Emp50

2050 Number of jobs