Residential Permits
Go to Section:- Overview
- Data Quality
- Data Organization
- Coordinate System
- Attributes
- Distribution - Get Data
- Metadata Reference
Section 1: Overview
Originator:Metropolitan Council
Title:
Residential Permits
Abstract:
This dataset consists of residential building permits issued in the 7-county Twin Cities Metropolitan Area from 2009 through 2024.
The data were obtained through an annual survey sent to communities by the Metropolitan Council and from the U.S. Census Bureau. The data on returned surveys were verified by Metropolitan Council staff through various means. Data from the Residential Construction Branch of the Manufacturing and Construction Division of the U.S. Census Bureau were used if a community did not return the survey. Data may be periodically updated to reflect corrections.
Purpose:
This dataset was created to track residential building permits issued in the 7-county Metropolitan Area.
Time Period of Content Date:
12/31/2024
Currentness Reference:
This dataset reflects permit information collected annually from 2009 through 2024.
Progress:
Complete
Maintenance and Update Frequency:
Annually
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
Theme Keywords:
Residential building permits, building permits, permits
Theme Keyword Thesaurus:
Access Constraints:
None. This dataset is public domain under the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). If the dataset is not available from the Online Linkage in Section 6, please contact the Distribution Contact Person.
Use Constraints:
This dataset is public domain under the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13).
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 (18) 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 = Blue Line
1001, 1004 = Northstar Commuter Rail
1005, 1006, 1011 = Red Line
1001, 1002, 1007, 1015 = Green Line
1013, 1014, 1015 = A Line
1008 = Green Line Extension
1009 = Blue Line Extension
1010 = Orange Line
1012 = Gold Line
1016, 1022 = C Line
1017 = Red Rock
1018, 1022 = D Line *Note: May wish to include 1001 & 1002 for partial overlap with downtown LRT
1019 = Rush Line
Note: avoid double counting common Corridor segments (i.e., 2001, 2002) when summarizing multiple corridors (i.e., Blue and Green Lines).
Contact Person Information:
Joel Nyhus,
Reseacher
Metropolitan Council
390 Robert Street North
St. Paul,
MN
55101-1805
Phone: 651.602.1634
Email: [email protected]
Browse Graphic:
None available
Associated Data Sets:
Commercial, Industrial, and Public and Institutional Construction, Twin Cities Metropolitan Area.
Section 2: Data Quality
Attribute Accuracy:
Logical Consistency:
Completeness:
Entire 7 county area is covered.
Horizontal Positional Accuracy:
Lineage:
The data were obtained through an annual survey sent to communities by the Metropolitan Council and from the U.S. Census Bureau.
The data on returned surveys were verified by Metropolitan Council staff through various means including: contact with community staff, comparison to data from the Residential Construction Branch of the Manufacturing and Construction Division of the U.S. Census Bureau, community websites, and comparison to data submitted by communities in the Metropolitan Council's annual Livable Communities Act (LCA) survey. Data from the Residential Construction Branch of the Manufacturing and Construction Division of the U.S. Census Bureau were used if a community did not return the survey.
Data may be periodically updated to reflect corrections.
A small number of communities each year may not provide data. These are typically places with no residential construction occurring.
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)
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)
The data on returned surveys were verified by Metropolitan Council staff through various means including: contact with community staff, community websites, and comparison to data in the Council's Service Availability Charge (SAC) reports where possible.
For this data, projects are counted at the time local units of government issue building permits.
Section 3: Spatial Data Organization (not used in this metadata)
Section 4: Coordinate System
Horizontal Coordinate Scheme:
Universal Transverse Mercator
UTM Zone Number:
15
Horizontal Datum:
NAD83
Horizontal Units:
meters
Vertical Datum:
Vertical Units:
Depth Datum:
Depth Units:
Section 5: Attributes
Overview:
SDE_ID: Unique identifier
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. As of 2006, these codes have been officially retired by the federal government. They arereplaced 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 (concatenation of CO_CODE and CTU_ID_CEN). This is the official U.S.Census Bureau format
CTU_NAME: Name of the city, township or unorganized territory
YEAR: The year the permit was issued
TENURE: Owner, rental, or co-op
HOUSING_TYPE: Housing type code:
SFD = single family detached units
DTQ = duplex, triplex and fourplex units
TH = townhouse units
MF5 = multifamily (5 or more units in a building)
ADU = accessory dwelling unit
HOUSING_TYPE_DESC:
Single-Family Detached
Duplex, Triplex and Quad
Townhomes (single-family attached
Multifamily (5 units or more)
Accessory Dwelling Unit
RES_PERMIT_TYPE:
SFD - Single Family Detached
New Unit (NU) Gain in SFD
Moved in (MI) Gain in SFD
Removed from stock (RM) Loss in SFD
Moved out (MO) Loss in SFD
Converted from commercial (FC) Gain in SFD
Converted to commercial (TC) Loss in SFD
Converted from duplex, triplex, quad (FD) Gain in SFD
Converted to duplex, triplex, quad (TD) Loss in SFD
Converted from multifamily (FM) Gain in SFD
Converted to multifamily (TM) Loss in SFD
Remodel (RE) (over $1 million)
TH - Townhouse
New unit (NU) Gain in TH
Converted to more units (MU) Gain in TH
Removed from stock (RM) Loss in TH
Converted to fewer units (TF) Loss in TH
Converted from commercial (FC) Gain in TH
Converted to commercial (TC) Loss in TH
Remodel (RE) (over $1 million)
DTQ - Duplex, Triplex, amd Quads
New unit (NU) Gain in DTQ
Moved in (MI) Gain in DTQ
Converted to more units (MU) Gain in DTQ
Removed from stock (RM) Loss in DTQ
Moved out (MO) Loss in DTQ
Converted to fewer units (TF) Loss in DTQ
Converted from commercial (FC) Gain in DTQ
Converted to commercial (TC) Loss in DTQ
Converted from single family (FS) Gain in DTQ
Converted to single family (TS) Loss in DTQ
Converted from multifamily (FM) Gain in DTQ
Converted to multifamily (TM) Loss in DTQ
Remodel (RE) (over $1 million)
MF5 - Multifamily (5 or more units in a building)
New unit (NU) Gain in MF5
Converted to more units (MU) Gain in MF5
Removed from stock (RM) Loss in MF5
Converted to fewer units (TF) Loss in MF5
Converted from commercial (FC) Gain in MF5
Converted to commercial (TC) Loss in MF5
Converted from single family (FS) Gain in MF5
Converted to single family (TS) Loss in MF5
Converted from duplex, triplex, quad (FD) Gain in MF5
Converted to duplex, triplex, quad (TD) Loss in MF5
Remodel (RE) (over $1 million)
ADDRESS: Location of the residential unit(s)
ZIP_CODE: Zip code of the residential unit(s)
NAME: The name of the building, developer, or owner of the building
NAME: Name of the building
BUILDINGS: Number of buildings associated with the residential unit
UNITS: Number of residential units
AGE_RESTRCTED: Residential units that are specifically aimed at persons age 55 and older
MEMORY_CARE: Long-term care units designed to meet the specific needs of a person with Alzheimer's disease, dementia or other types of memory problems
ASSISTED: Housing for the elderly or disabled that provides nursing care, housekeeping, and prepared meals as needed.
COM_OFF_RET: Examples include buildings with retail businesses and residential units as well as buildings with offices and residential units
ACREAGE: The amount of land associates with the residential unit
SQF: The square footage of the residential unit or complex
PIN: The unique parcel identifier (PID) or parcel identification number (PIN) that is use within the county
PUBLIC_FUNDS: Public funds associated with the unit(s)
PERMIT_VALUE: Permit value of construction
COMMUNITY_DESIGNATION: A designation of each city and township based on the overall state of development and regional issues faced by the community
NOTES: General notes
Detailed Citation:
RESEARCH_WEB_RESIDENTIAL_PERMIT_ADDR
GISCD.DBO.ResidentialPermitPoints
Table Detail:
Section 6: Distribution
Publisher:
Metropolitan Council
Publication Date:
05/06/2025
Contact Person Information:
Joel Nyhus,
Reseacher
Metropolitan Council
390 Robert Street North
St. Paul,
MN
55101-1805
Phone: 651.602.1634
Email: [email protected]
Distributor's Data Set Identifier:
ResidentialPermits
Distribution Liability:
NOTICE: The Geographic Information System (GIS) Data to which this notice is attached are made available pursuant to the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). THE GIS DATA ARE PROVIDED TO YOU AS IS AND WITHOUT ANY WARRANTY AS TO THEIR PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The GIS Data were developed by the Metropolitan Council for its own internal business purposes. The Metropolitan Council does not represent or warrant that the GIS Data or the data documentation are error-free, complete, current, or accurate. You are responsible for any consequences resulting from your use of the GIS Data or your reliance on the GIS Data. You should consult the data documentation for this particular GIS Data to determine the limitations of the GIS Data and the precision with which the GIS Data may depict distance, direction, location, or other geographic features. If you transmit or provide the GIS Data (or any portion of it) to another user, it is recommended that the GIS Data include a copy of this disclaimer and this metadata.
Ordering Instructions:
See Online Linkage Below
Section 7: Metadata Reference
Metadata Date:
05/06/2025
Contact Person Information:
Joel Nyhus,
Reseacher
Metropolitan Council
390 Robert Street North
St. Paul,
MN
55101-1805
Phone: 651.602.1634
Email: [email protected]
Metadata Standard Name:
Minnesota Geographic Metadata Guidelines
Metadata Standard Version:
1.2