Annual Population and Household Estimates, 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:
Annual Population and Household Estimates, Twin Cities Metropolitan Area
Abstract:
This dataset consists of a time series of annual, local population and household estimates, as well as Decennial Census counts, for the Twin Cities seven-county area. These estimates are the official population and household estimates for State government purposes, per Minnesota Statutes 473.24.
For details on the estimates methdology, please visit https://metrocouncil.org/populationestimates
Please be aware that input data sources and methods are revised each year, so estimates from different years should not be compared to derive estimates of annual change. Instead, compare estimates to the 2020 Census.
Purpose:
This dataset consists of a time series of annual, local population and household estimates, as well as Decennial Census counts, for the Twin Cities seven-county area. These estimates are the official population and household estimates for State government purposes, per Minnesota Statutes 473.24.
For details on the estimates methdology, please visit https://metrocouncil.org/populationestimates
Time Period of Content Date:
04/01/2023
Currentness Reference:
2023 estimates published July 2024.
Progress:
Complete
Maintenance and Update Frequency:
Annually
Spatial Extent of Data:
Twin Cities seven-county metropolitan area. This includes the counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington in Minnesota.
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, households, annual estimates, census
Theme Keyword Thesaurus:
None
Access Constraints:
None
Use Constraints:
Station Areas 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:
Matt Schroeder,
Senior Researcher
Metropolitan Council
390 Robert Street North
St. Paul,
MN
55101-1805
Phone: 651.602.1513
Email: [email protected]
Browse Graphic:
none available
Associated Data Sets:
Section 2: Data Quality
Attribute Accuracy:
Valid code tests have been conducted. No known attribute errors exist. See the estimates methodology, available via metrocouncilorg/populationestimates, for an explanation of the calculations.
Logical Consistency:
Completeness:
Entire seven county geographic area is covered.
Horizontal Positional Accuracy:
Lineage:
Historical data may be available for the following places:
Burns Township (became the city of Nowthen, July 2008)
Chaska Township (merged with the city of Chaska, January 2005)
Columbus Township (became the city of Columbus, September 2006)
Credit River Township (became the city of Credit River, June 2021)
Elko (merged with the city of New Market to become Elko New Market, January 2007)
Empire Township (became the city of Empire, February 2023)
Forest Lake Township (merged with the city of Forest Lake, March 2000)
Grant Township (became the city of Grant, January 1997)
Hassan Township (merged with the city of Rogers, January 1, 2012)
New Market (merged with the city of Elko to become Elko New Market, January 2007)
New Scandia Township (became the city of Scandia, January 2007)
Norwood (merged with the city of Young America to become Norwood Young America, January 1997)
Oak Grove Township (became the city of Oak Grove, December 1993)
Young America (merged with the city of Norwood to become Norwood Young America, January 1997)
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:
See the estimates methodology, available via metrocouncilorg/populationestimates, for an explanation of the calculations, which reflect the review and comment of cities and townships. New data are added every year. This is a record of official estimates, so older data are not edited as new information becomes available. As a result, estimates from two different years are not necessarily comparable.
Attributes for Chart Data (Note: Not all attributes are present in every chart):
GEOG_UNIT_ID: Geographic identifier for the area (Geographic Names Information System [GNIS] codes are available at https://geonames.usgs.gov/domestic/index.html, except for seven-county Twin Cities region, which has the code 'R11000')
CTU_NAME: Name of the geographic area (region; county; or city, township or unorganized territory, such as Benton Twp. or Blaine.)
YEAR: Year of the data.
DATASOURCE: Source of the data.
CENS = Census
METC = Metropolitan Council
FORECAST = Metropolitan Council forecast
POPULATION: Total count or estimate of individuals (includes people living in households and people living in group quarters).
HOUSEHOLDS: Total count or estimate of households. A household includes all the persons who together occupy a housing unit. By definition, the number of households is the same as the number of occupied housing units.
GROUP_QUARTERS_POP: Total count or estimate of individuals residing in group quarters. Group quarters are defined as a place where people live or stay, in a group living arrangement, that is owned or managed by an organization providing housing and/or services for the residents.
POPULATION_IN_HOUSEHOLDS: Total count or estimate of people living in households (as opposed to group quarters).
Attributes for Tabular Data (County or 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 DESC: Description of the data source, e.g. Census Bureau.
POP_RECORD_TYPE_DESC: Detail of data source, e.g. Decennial
Census SF1.
YEAR: Year of the data.
POPULATION: Total count of individuals.
GROUP_QUARTERS_POP: Total count of individuals residing
in group quarters. Group quarters are defined as a place where
people live or stay, in a group living arrangement, that is owned
or managed by an organization providing housing and/or services
for the residents.
HOUSEHOLDS: Count of households. A household includes
all the persons who together occupy a housing unit.
POPULATION_IN_HOUSEHOLDS: Number of people living in households.
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 Data (Station Area). See Use Constraints for Station Area analysis:
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 DESC: Description of the data source, e.g. Census Bureau.
POP_RECORD_TYPE_DESC: Detail of data source, e.g. Decennial
Census SF1.
YEAR: Year of the data.
POPULATION: Total count of individuals.
GROUP_QUARTERS_POP: Total count of individuals residing
in group quarters. Group quarters are defined as a place where
people live or stay, in a group living arrangement, that is owned
or managed by an organization providing housing and/or services
for the residents.
HOUSEHOLDS: Count of households. A household includes
all the persons who together occupy a housing unit.
POPULATION_IN_HOUSEHOLDS: Number of people living in households.
COMMUNITY DESIGNATION: A designation of each city and township based on the overall state of development and regional issues faced by that community.
Detailed Citation:
None
Table Detail:
Section 6: Distribution
Publisher:
Metropolitan Council
Publication Date:
periodically revised
Contact Person Information:
Matt Schroeder,
Senior Researcher
Metropolitan Council
390 Robert Street North
St. Paul,
MN
55101-1805
Phone: 651.602.1513
Email: [email protected]
Distributor's Data Set Identifier:
Annual Population and Household Estimates
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.
Section 7: Metadata Reference
Metadata Date:
07/12/2024
Contact Person Information:
Matt Schroeder,
Senior Researcher
Metropolitan Council
390 Robert Street North
St. Paul,
MN
55101-1805
Phone: 651.602.1513
Email: [email protected]
Metadata Standard Name:
Minnesota Geographic Metadata Guidelines
Metadata Standard Version:
1.2