Population, Households and Employment Forecasts to 2040, Twin Cities Metropolitan Area
Go to Section:- Overview
- Data Quality
- Data Organization
- Coordinate System
- Attributes
- Distribution - Get Data
- Metadata Reference
Section 1: Overview
Originator:Metropolitan Council
Title:
Population, Households and Employment Forecasts to 2040, Twin Cities Metropolitan Area
Abstract:
Forecasts of population, households and employment for each city, township or unincorporated area (CTU) in the seven-county metropolitan area. Current forecasts were updated by Metropolitan Council on July 8, 2015. Interim revisions are possible, typically in response to changes in local comprehensive plans.
Purpose:
The Council's forecasts align shared expectations of when, where and how much growth, enabling coordinated regional and local planning, per Minn. Statutes 473.146, 473.856 and 473.859.
Time Period of Content Date:
2040
Currentness Reference:
Census 2010 and forecast years 2020, 2030, 2040. The forecast set is periodically updated with interim revisions.
Progress:
Complete
Maintenance and Update Frequency:
As needed
Spatial Extent of Data:
Twin Cities 7 county metropolitan area. This includes the counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington.
Bounding Coordinates:
-94.012
-92.732
45.415
44.471
Place Keywords:
Twin Cities, Anoka County, Carver County, Dakota County, Hennepin County, Ramsey County, Scott County, Washington County
Theme Keywords:
Population, demographics, forecasts, projections
Theme Keyword Thesaurus:
None
Access Constraints:
None
Use Constraints:
Station Area are defined as half-mile, non-overlapping transit-influenced areas based on existing and planned transitway station locations as defined by MetroTransit. In general, transitway stations are defined as a centrally located, single station point representing multidirectional transit stops or platforms. Additional consolidations of transitway stations were made to "coexisting" multimodal stations (i.e., Blue Line's 46th Street Station (Hiawatha Ave) A-Line's 46th Street Station) before defining Station Area. Both the consolidation of stations and definition of station areas are supported by the Federal Transportation Administration (FTA) Reporting Instructions for the Section 5309 Capital Investment Grant Program.
The source and allocation methodology of data included in the Station Area Statistics can be found in the data layer metadata record.
Because some station areas can represent more than one transitway corridor, the statistics for all Station Areas are provided with the download of any data layer requested at the All Station Area geography. Each Station Area is associated with a transitway Corridor segment (Corridor_ID). A Corridor segment can include one (1) to eighteen (30) stations. Use the following matrix to associate and/or summarize Corridor segments to a specific corridor(s):
Corridor_ID = Corridor
1001, 1002, 1003, 1005, 1014, 1025, 1027, 1036, 1039 = Blue Line
1001, 1004 = Northstar Commuter Rail
1005, 1006 = Red Line
1001, 1002, 1007, 1015, 1025, 1027, 1031, 1039 = Green Line
1008, 1026, 1032 = Green Line Extension
1009, 1024, 1026 = Blue Line Extension
1010, 1027, 1034 = Orange Line
1012, 1029, 1033 = Gold Line
1019, 1029, 1031 = Purpled Line
1013, 1014, 1015, 1037 = A Line
1028, 1032, 1033, 1035, 1036, 1037, 1038 = B Line
1016, 1022, 1024, 1026, 1027 = C Line
1018, 1022, 1026, 1027, 1035 = D Line
1030, 1038, 1039, 1040 = E Line
1023, 1025, 1029, 1033 = Riverview
Note: avoid double counting common Corridor segments (i.e., 2001, 2002) when summarizing multiple corridors (i.e., Blue and Green Lines).
Contact Person Information:
Todd Graham,
Principal Forecaster
Metropolitan Council
390 Robert Street North
Saint Paul,
MN
55101-1805
Phone: 651-602-1322
Fax: 651-602-1674
Email: [email protected]
Browse Graphic:
none available
Associated Data Sets:
None
Section 2: Data Quality
Attribute Accuracy:
No known attribute errors exist.
Logical Consistency:
Completeness:
Entire seven county area is covered.
Horizontal Positional Accuracy:
Lineage:
Section 3: Spatial Data Organization (not used in this metadata)
Section 4: Coordinate System
Horizontal Coordinate Scheme:
Horizontal Datum:
Horizontal Units:
Vertical Datum:
not applicable
Vertical Units:
NA
Depth Datum:
NA
Depth Units:
NA
Section 5: Attributes
Overview:
Attributes for Chart Data (Note: Not all attributes are present in every chart):
Population and Households -
GEOG_UNIT_ID: The Geographic Names Information System (GNIS) official federal unique identifier of the city, township or unorganized territory.
CTU_NAME: Name of the city, township or unorganized territory.
YEAR: The projection year.
DATASOURCE: Source of the data
CENS = U.S. Census Bureau
METC = Metropolitan Council
FORECAST = Metropolitan Council forecast
POPULATION: Number of persons, including both persons in households and in group quarters.
HOUSEHOLDS: Number of households.
GROUP_QUARTERS_POP: Number of persons in group quarters.
POPULATION_IN_HOUSEHOLDS: Number of persons living in households.
Employment -
GEOGRAPHY: Name of the city, township or unorganized territory.
FORECAST YEAR: The projection year.
EMPLOYMENT: Numer of wage and salary jobs
Attributes for Tabular Download (County and Community):
CO_CODE: 3 digit FIPS and state standard county ID code
003 = Anoka County
019 = Carver County
037 = Dakota County
053 = Hennepin County
123 = Ramsey County
139 = Scott County
163 = Washington County
CTU_CODE: 5 digit FIPS55 'Place' code for CTU. They are replaced
by the GNIS codes below. The Census Bureau will continue to create
FIPS55 Place codes for new cities and townships through the 2010
Census. After that, no new FIPS55 codes will be created. Note that
for townships that wholly incorporate into cities, the same FIPS55
code for the former township will usually be used for the new city.
Conversely, GNIS creates a new ID for the new city.
CTU_ID: The Geographic Names Information System (GNIS)
official federal unique identifier for each city, township or unorganized
territory.
COCTU_ID: 11 digit identifier for the combination of county
and CTU (concatination of CO_CODE and CTU_ID_CEN).
CTU_NAME: Name of the city, township or unorganized territory,
e.g. Benton Twp., Blaine.
DATASOURCE: Source of the data
CENS = U.S. Census Bureau
METC = Metropolitan Council
FORECAST = Metropolitan Council forecast
YEAR: The projection year.
EMPLOYMENT: Number of wage and salary jobs
POPULATION: Number of persons, including both persons in households and in group quarters.
HOUSEHOLDS: Number of households.
MAX_APPROVAL_DATE: Date of the most recent Metropolitan Council action that revised the city or town's forecast. All cities and towns were updated on July 8, 2015. Additional forecast revisions may have occurred since then.
COMMUNITY DESIGNATION: A designation of each city and township based on the overall state of development and regional issues faced by that community.
Attributes for Tabular Download (Station Areas):
See Use Constraints for Station Area Analaysis.
CORRIDOR_SEGMENT_ID: 4 digit indicator of the Corridor Segment.
CORRIDOR_SEGMENT: Description of the Corridor Segment. Corridor
Segments make up full corridors. A Corridor Segment can be part of
multiple corridors
STATION_AREA_ID: Station Area Identifier (COUNTY_CODE + CTU_ID +
Unique Station ID).
STATION_AREA: Description of the Station Area
CTU_ID: The Geographic Names Information System (GNIS)official federal
unique identifier for the city, township or unorganized territory
where the station is located.
COMMUNITY: Description of the community where the Station is located.
COUNTY_CODE: 3 digit FIPS and state standard county ID code where the Station is located
COUNTY: Name of the county where the station is located
DATASOURCE: Source of the data
CENS = U.S. Census Bureau
METC = Metropolitan Council
FORECAST = Metropolitan Council forecast
YEAR: The projection year.
EMPLOYMENT: Numer of wage and salary jobs
POPULATION: Number of persons, including both persons in households and in group quarters.
HOUSEHOLDS: Number of households.
COMMUNITY DESIGNATION: A designation of each city and township based on the overall state of development and regional issues faced by that community.
Because a Station area can exist in multiple communities, MAX_APPROVAL_DATE is not provided at the Station Area. If you are interested in knowing the approval date of the current forecast for a station area, please review the community(ies) it resides within.
Detailed Citation:
None
Table Detail:
Section 6: Distribution
Publisher:
Metropolitan Council
Publication Date:
periodically revised
Contact Person Information:
Todd Graham,
Principal Forecaster
Metropolitan Council
390 Robert Street North
Saint Paul,
MN
55101-1805
Phone: 651-602-1322
Fax: 651-602-1674
Email: [email protected]
Distributor's Data Set Identifier:
Population, Households and Employment Forecasts to 2040
Distribution Liability:
NOTICE: The data to which this notice is attached are made available pursuant to the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). THE DATA ARE PROVIDED TO YOU AS IS AND WITHOUT ANY WARRANTY AS TO THEIR PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The Metropolitan Council developed some of the data for its own internal business purposes and is redistributing data developed by other data providers (e.g., the U.S. Census Bureau and the Minnesota Department of Employment and Economic Development). The Metropolitan Council does not represent or warrant that the data or the data documentation are error-free, complete, current, or accurate. You are responsible for any consequences resulting from your use of the data or your reliance on the data. You should consult the data documentation for these particular data to determine the limitations of the data. If you transmit or provide the data (or any portion of it) to another user, it is recommended that the data include a copy of this disclaimer and this metadata.
Ordering Instructions:
This entire dataset is available on the internet by clicking below after 'Online Linkage'. Doing so will tell your browser to download a 'ZIP' file which will contain the following:
- csv file
- metadata for the dataset (.htm)
- NOTICE.RTF, an important notice about this dataset that can be read by any word processing software.
This dataset can also be viewed and downloaded using the Download Tabular Data tool at http://stats.metc.state.mn.us/data_download/DD_start.aspx
The Download tool allows users to choose subsets of the dataset, such as a city or county. Online Linkage:
None available
Section 7: Metadata Reference
Metadata Date:
04/10/2023
Contact Person Information:
Todd Graham,
Principal Forecaster
Metropolitan Council
390 Robert Street North
Saint Paul,
MN
55101-1805
Phone: 651-602-1322
Fax: 651-602-1674
Email: [email protected]
Metadata Standard Name:
Minnesota Geographic Metadata Guidelines
Metadata Standard Version:
1.2