Commercial, Industrial, and Public and Institutional Construction, Twin Cities Metropolitan Area

This page last updated: 08/29/2016
Metadata created using Minnesota Geographic Metadata Guidelines


Go to Section:
1. Overview
2. Data Quality
3. Data Organization
4. Coordinate System
5. Attributes
6. Distribution - Get Data
7. Metadata Reference

Section 1 Overview
Originator Metropolitan Council
Title Commercial, Industrial, and Public and Institutional Construction, Twin Cities Metropolitan Area
Abstract This dataset consists of summary data for commercial, industrial, and public and institutional projects, based on building permits issued during each calendar year by cities and townships within the Region. Data is collected via an annual survey of building officials, in conjunction with collection of data on residential building permits.
Purpose This dataset was created to summarize and analyze development trends of commercial, industrial, and public and institutional building in the seven-county Twin Cities Region.
Time Period of Content Date 08/29/2016
Currentness Reference This dataset reflects permit information collected annually from 2003 through 2015.
Progress In work
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 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 commercial, industrial, public, institutional, nonresidential building permits, building permits, permits
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 (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
1017 = Red Rock

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: joel.nyhus@metc.state.mn.us
Browse Graphic None available
Associated Data Sets None

Section 2 Data Quality
Attribute Accuracy Valid code tests have been conducted. No known attribute errors exist.
Logical Consistency
Completeness Entire seven county geographic area is covered.
Horizontal Positional Accuracy
Lineage The data were obtained through an annual survey sent to communities by the Metropolitan Council in conjunction with collection of residential building permits. Respondents are asked to provide project information for new buildings and additions to buildings if permit valuation is $100,000 or more. Data does not include permits for work such as plumbing, mechanical, reroofing, etc. or if the project is for remodeling only (not involving a new structure or adding square footage to an existing structure).

Data on square footage and value should not be used to attempt to determine value per square foot, as not all projects include data for both variables.

A small number of communities each year may not provide data. These are typically places with no nonresidential construction occurring.

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. No information on demolitions is included, so the data represent a gross construction volume, but not the net gain in property value or space. With subsequent annual updates, the data should be useful for assessing longer-range trends.

Multiple building permits may be issued for a given project, separate from the permit for the major structural work, for example, for foundation work, mechanical, electrical, and finishing work. Metropolitan Council has attempted to represent the permit valuation and square footage for all new projects and additions (if over $100,000) and to avoid duplicate reporting of these. However, there may be some inconsistency because of the complexity of some projects and differences among local permit record-keeping systems. Where it was possible to differentiate, permits that were for remodeling, mechanical, electrical, plumbing, and finishing work only have not been included.

Project 'value' reflects the estimated cost of construction reported on the building permit. Permit values exclude some costs including land and landscaping, and are typically lower than market values of completed properties.

City-to-city comparisons may not be entirely valid if there are differences in survey completeness or methods of permit valuation.

Other construction activity may have occurred on properties of state and federal jurisdictions that are not included in this report. The University of Minnesota, for example, is not covered in Metropolitan Council's survey since it does not have to apply for building permits from local jurisdictions.

Occasionally a project will be put on hold after the building permit has been issued. All permits reported by local officials for this survey are included in our data base and in this report, regardless of status. It would not be feasible to do continuous follow up of all projects through the construction process.

Council Research staff designated each listing as "Commercial," "Industrial," or "Public or Institutional", based on descriptive information provided by survey respondents. The Public or Institutional category includes government-owned structures and semi-public buildings such as hospitals, schools, churches and community centers, owned or occupied by nonprofit organizations (including religious). All schools were coded as Public or Institutional use, whether ownership is public or private.

The Minneapolis-St. Paul International Airport is not within the boundaries of a minor civil division. The Metropolitan Airports Commission provided data on airport construction.

For complete information for each construction project, and mapping capability, see the MetroGIS website at http://www.datafinder.org.

Historical data may or may not 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)
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)

Section 3 Spatial Data Organization (not used in this metadata)

Section 4 Coordinate System
Horizontal Coordinate Scheme
Horizontal Datum
Horizontal Units

Section 5 Attributes
Overview Attributes for Chart Data (Note: Not all attributes are present in every chart. The public and institutional projects totals exclude airport projects. While airport projects create employment, their impact on land use tends to be inconsequential because they are limited to
fixed airport boundaries. Including airport projects in public and institutional project figures artificially inflates the share of developed areas, which host the region's airports, in the region's public and institutional totals.)

DESCRIPTION: Designation of project into one of 18 building type categories.

GEOGRAPHY: Name of the city, township or unorganized territory, e.g. Benton Twp., Blaine.

TOTAL_PERMIT_VALUE: Permit value of building or ddition.

TOTAL SQUARE FOOTAGE: Square footage of building or addition.

YEAR: The year the permit was issued.


Attributes for Tabular Data (County and Community):
Note: The public and institutional projects totals exclude airport projects. While airport projects create employment, their impact on land use tends to be inconsequential because they are limited to fixed airport boundaries. Including airport projects in public and institutional project figures artificially inflates the share of developed areas, which host the region's airports, in the region's public and institutional totals.

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 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 (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, e.g. Benton Twp., Blaine.

YEAR: The year the permit was issued.

NONRES_GROUP: Designation of non-residential projects into 3 general categories (i.e., Commercial, Industrial, or Public and Institutional)

NONRES_SUBGROUP: Designation of non-residential projects into one of 12 categories

NONRES_TYPE_DESC: Designation of non-residential projects into one of 24 building type categories.

BLDG_NAME: The name of the building, developer or owner of the building.

BLDG_DESC: A description of the building's use.

PERMIT_TYPE: N = New
A = Addition

PERMIT_VALUE: Permit value of building or addition.

SQF: Square footage of new building or addition.

ADDRESS: Location of the project.

ZIP_CODE: A system of 5-digit codes that identifies the individual Post Office or metropolitan area delivery station associated with an address.

ZIP_PLUS_4: A 4-digit extension of the 5-digit ZIP code (preceded by a hyphen) that, in conjunction with the Zip code, identifies a specific range of the USPS delivery addresses.

PIN: Parcel Identification Number.

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 Areas):
See Use Constraints for Station Area Analysis.
Note: The public and institutional projects totals exclude airport projects. While airport projects create employment, their impact on land use tends to be inconsequential because they are limited to fixed airport boundaries. Including airport projects in public and institutional project figures artificially inflates the share of developed areas, which host the region's airports, in the region's public and institutional totals.

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

YEAR: The year of the data.

YEAR: The year the permit was issued.

NONRES_GROUP: Designation of non-residential projects into 3 general categories (i.e., Commercial, Industrial, or Public and Institutional)

NONRES_SUBGROUP: Designation of non-residential projects into one of 12 categories

NONRES_TYPE_DESC: Designation of non-residential projects into one of 24 building type categories.

BLDG_NAME: The name of the building, developer or owner of the building.

BLDG_DESC: A description of the building's use.

PERMIT_TYPE: N = New
A = Addition

PERMIT_VALUE: Permit value of building or addition.

SQF: Square footage of new building or addition.

ADDRESS: Location of the project.

ZIP_CODE: A system of 5-digit codes that identifies the individual Post Office or metropolitan area delivery station associated with an address.

ZIP_PLUS_4: A 4-digit extension of the 5-digit ZIP code (preceded by a hyphen) that, in conjunction with the Zip code, identifies a specific range of the USPS delivery addresses.

PIN: Parcel Identification Number.

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 Joel Nyhus, Reseacher
Metropolitan Council
390 Robert Street North
St. Paul, MN  55101-1805
Phone: 651.602.1634
Email: joel.nyhus@metc.state.mn.us
Distributor's Data Set Identifier nonresidential_building_permits
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.
Online LinkageDownload Page

Section 7 Metadata Reference
Metadata Date 08/29/2016
Contact Person Information Joel Nyhus, Reseacher
Metropolitan Council
390 Robert Street North
St. Paul, MN  55101-1805
Phone: 651.602.1634
Email: joel.nyhus@metc.state.mn.us
Metadata Standard Name Minnesota Geographic Metadata Guidelines
Metadata Standard Version 1.2
Metadata Standard Online Linkage http://www.gis.state.mn.us/stds/metadata.htm


This page last updated: 08/29/2016
Go back to top