| - Full Metadata - | - View Attributes - | - View Sample - | - Get Data - |
This page last updated: 07/23/2008
Metadata created using Minnesota Geographic Metadata Guidelines
| Originator | Metropolitan Council |
| Abstract | This is a lookup table within Oracle containing various data related to cities, townships, unorganized territories (CTUs) and any divisions created by county boundaries splitting them. These are termed Minor Civil Division (MCDs) by the Census Bureau. The table encompases the Twin Cities 7-county metropolitan area. It is intended to be a Council wide master lookup table for these entites. It contains official federal and state unique identifiers for CTUs and MCDs as well as identifiers created and used by other organizations. The table also contains historical MCDs dating back to the 1990s and a few other non-MCD records that are of importance to Met. Council use of this table. NOTES: - Effective April 2008, a change was made in GNIS to match the FIPS place codes to the 'civil' feature for each city instead of the 'populated place' feature. Both cities and townships are now 'civil' features within GNIS. This means that the official GNIS unique ID for every city in Minnesota has changed. See full notice on change here: http://www.datafinder.org/notices/gnis_update.asp - Effective January of 2007, two new cities were created in the metro area. They are Elko New Market and Scandia. The CTU_ID and CTU_CODE values for Scandia are preliminary, pending approval by the USGS. The same attributes for Elko New Market contain temporary values (9999999 and 99999 respectively) until official codes are created. - As of January 1, 2006, the five digit FIPS 55-3 Place codes that were used as unique identifiers in this dataset (CTU_CODE and COCTU_CODE fields) were officially retired by the Federal governement. They are replaced by a set of integer codes from the Geographic Names Information System (GNIS_CODE field). Both codes will be kept in this database, but the GNIS_CODE is considered the official unique identifier from this point forward. The GNIS codes are also slated to become official ANSI codes for these geographic features. While GNIS treats these codes as 6 to 8 digit integer data types, the Census Bureau formats them as 8 digit text fields, right justified with leading zeros included. - The Census Bureau will continue to create FIPS 55 Place codes for new cities and townships through the 2010 Census. After that, no new FIPS 55 codes will be created. Note that for townships that wholly incorporate into cities, the same FIPS 55 code will be used for the new city. (GNIS creates a new ID for the new city.) - Cities and townships have also been referred to as ''MCDs'' (a Census term), however this term technically refers to the part of each city or township within a single county. Thus, a few cities in the metro area that are split by county boundaries are actually comprised of two different MCDs. This was part of the impetus for a proposed MN state data standard that uses the ''CTU'' terminology for clarity. - A variety of civil divisions of the land exist within the United States. In Minnesota, only three types exist - cities, townships and unorganized territories. All three of these exist within the Twin Cities seven county area. The only unorganized territory is Fort Snelling (a large portion of which is occupied by the MSP International Airport). - Some cities are split between two counties. Only those parts of cities within the 7-county area are included. - Prior to the 2000 census, the FIPS Place code for the City of Greenwood in Hennepin County was changed from 25928 to 25918. This dataset reflects that change. |
| Browse Graphic | View a sample of the data. |
| Time Period of Content Date | 07/23/2008 |
| Currentness Reference | The table is up to date as of the time period of content date shown above. Acreages are derived from the MetroGIS cities and township dataset dated 04/01/2007. http://www.datafinder.org/metadata/county_ctu.htm |
| Access Constraints | None |
| Use Constraints | By acceptance of this data, the user agrees to include a copy of this metadata record, including the liability disclaimer, whenever the user transmits or provides the GIS Data (or any portion of it) to another user. We recommend that other interested parties download this dataset from the Data Finder web site (www.datafinder.org) to ensure that the most current data is obtained. |
| Distributor Organization | Metropolitan Council |
| Ordering Instructions | This dataset is distributed 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: - dBase IV file - Excel file - metadata for the dataset (.htm) - NOTICE.RTF, an important notice about this dataset that can be read by any word processing software. |
| Online Linkage | Click here to download data. (See Ordering Instructions above for details.) By clicking here, you agree to the notice in "Distribution Liability" in Section 6 of this metadata. |
Go to Section:
1. Identification Information
2. Data Quality Information
3. Spatial Data Organization Information
4. Spatial Reference Information
5. Entity and Attribute Information
6. Distribution Information
7. Metadata Reference Information
| Section 1 | Identification Information |   | Top of page | |
| Originator | Metropolitan Council | |||
| Title | County CTU Lookup Table | |||
| Abstract | This is a lookup table within Oracle containing various data related to cities, townships, unorganized territories (CTUs) and any divisions created by county boundaries splitting them. These are termed Minor Civil Division (MCDs) by the Census Bureau. The table encompases the Twin Cities 7-county metropolitan area. It is intended to be a Council wide master lookup table for these entites. It contains official federal and state unique identifiers for CTUs and MCDs as well as identifiers created and used by other organizations. The table also contains historical MCDs dating back to the 1990s and a few other non-MCD records that are of importance to Met. Council use of this table. NOTES: - Effective April 2008, a change was made in GNIS to match the FIPS place codes to the 'civil' feature for each city instead of the 'populated place' feature. Both cities and townships are now 'civil' features within GNIS. This means that the official GNIS unique ID for every city in Minnesota has changed. See full notice on change here: http://www.datafinder.org/notices/gnis_update.asp - Effective January of 2007, two new cities were created in the metro area. They are Elko New Market and Scandia. The CTU_ID and CTU_CODE values for Scandia are preliminary, pending approval by the USGS. The same attributes for Elko New Market contain temporary values (9999999 and 99999 respectively) until official codes are created. - As of January 1, 2006, the five digit FIPS 55-3 Place codes that were used as unique identifiers in this dataset (CTU_CODE and COCTU_CODE fields) were officially retired by the Federal governement. They are replaced by a set of integer codes from the Geographic Names Information System (GNIS_CODE field). Both codes will be kept in this database, but the GNIS_CODE is considered the official unique identifier from this point forward. The GNIS codes are also slated to become official ANSI codes for these geographic features. While GNIS treats these codes as 6 to 8 digit integer data types, the Census Bureau formats them as 8 digit text fields, right justified with leading zeros included. - The Census Bureau will continue to create FIPS 55 Place codes for new cities and townships through the 2010 Census. After that, no new FIPS 55 codes will be created. Note that for townships that wholly incorporate into cities, the same FIPS 55 code will be used for the new city. (GNIS creates a new ID for the new city.) - Cities and townships have also been referred to as ''MCDs'' (a Census term), however this term technically refers to the part of each city or township within a single county. Thus, a few cities in the metro area that are split by county boundaries are actually comprised of two different MCDs. This was part of the impetus for a proposed MN state data standard that uses the ''CTU'' terminology for clarity. - A variety of civil divisions of the land exist within the United States. In Minnesota, only three types exist - cities, townships and unorganized territories. All three of these exist within the Twin Cities seven county area. The only unorganized territory is Fort Snelling (a large portion of which is occupied by the MSP International Airport). - Some cities are split between two counties. Only those parts of cities within the 7-county area are included. - Prior to the 2000 census, the FIPS Place code for the City of Greenwood in Hennepin County was changed from 25928 to 25918. This dataset reflects that change. |
|||
| Purpose | This dataset was developed to be used internally at the Metropolitan Council as a lookup and cross reference table for a variety of information related to cities, townships and unorganized territories. | |||
| Time Period of Content Date | 07/23/2008 | |||
| Currentness Reference | The table is up to date as of the time period of content date shown above. Acreages are derived from the MetroGIS cities and township dataset dated 04/01/2007. http://www.datafinder.org/metadata/county_ctu.htm |
|||
| 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 in Minnesota. | |||
| Bounding Coordinates | -94.0 -92.7 45.4 44.4 |
|||
| Place Keywords | Twin Cities, Anoka County, Carver County, Dakota County, Hennepin County, Ramsey County, Scott County, Washington County | |||
| Theme Keywords | counties, cities, townships, GNIS, FIPS place code, FIPS55, CTU, CTUs, MCD, minor civil divisions, municipal codes | |||
| Theme Keyword Thesaurus | None | |||
| Access Constraints | None | |||
| Use Constraints | By acceptance of this data, the user agrees to include a copy of this metadata record, including the liability disclaimer, whenever the user transmits or provides the GIS Data (or any portion of it) to another user. We recommend that other interested parties download this dataset from the Data Finder web site (www.datafinder.org) to ensure that the most current data is obtained. |
|||
| Contact Person Information | Jessica Deegan,
Senior GIS Tech Metropolitan Council 390 Robert Street North St. Paul, Minnesota 55101-1805 Phone: 651-602-1718 FAX: 651-602-1674 E-mail: jessica.deegan@metc.state.mn.us | |||
| Browse Graphic | View a sample of the data. | |||
| Browse Graphic File Description | ||||
| Associated Data Sets | County and CTU boundary datasets http://www.datafinder.org/metadata/county_ctu.htm County & CTU boundary dataset for 2000 http://www.datafinder.org/metadata/county_ctu_2000.htm County & MCD boundary dataset for 1990 http://www.datafinder.org/metadata/comcd_1990.htm State wide county and city boundary layers developed by the Minnesota Department of Transportation |
|||
| Section 2 | Data Quality Information | Top of full metadata | Top of page | |
| 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 | SOURCES USED: GNIS identifiers are taken from the U.S. Board of Geographic Names GNIS database at http://geonames.usgs.gov/domestic/index.html . FIPS 'Place' codes (CTU_CODE) are taken from the Federal Information Processing Standard (FIPS) Publication 55-3 database dated September, 2001. Updated FIPS codes are obtained from the GNIS database or the Census Bureau. Other codes are taken from various sources. Population figures are from the Metropolitan Council Research Unit. |
|||
| Source Scale Denominator | ||||
| Section 3 | Spatial Data Organization Information | Top of full metadata | Top of page | |
| Native Data Set Environment | Oracle | |||
| Geographic Reference for Tabular Data | CTU ID, County code, CTU code, county name, CTU name, COCTU ID, COCTU code | |||
| Spatial Object Type | ||||
| Vendor Specific Object Types | ||||
| Tiling Scheme | ||||
| Section 4 | Spatial Reference Information | Top of full metadata | Top of page | |
| Horizontal Coordinate Scheme | ||||
| Ellipsoid | ||||
| Horizontal Datum | ||||
| Horizontal Units | ||||
| Distance Resolution | ||||
| Section 5 | Entity and Attribute Information | Top of full metadata | Top of page | |
| Entity and Attribute Overview | Attributes for County CTU Lookup Table: |
| Entity and Attribute Detailed Citation | None | |||
| Section 6 | Distribution Information | Top of full metadata | Top of page | |
| Publisher | Metropolitan Council | |||
| Publication Date | Periodically revised | |||
| Contact Person Information | Mark Kotz GIS Database Administrator Metropolitan Council 390 Robert Street North St. Paul, Minnesota 55101-1805 Phone: 651-602-1644 FAX: 651-602-1674 E-mail: mark.kotz@metc.state.mn.us |
|||
| Distributor's Data Set Identifier | County CTU Lookup Table | |||
| 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, the GIS Data must include a copy of this disclaimer. | |||
| Transfer Format Name | ||||
| Transfer Format Version Number | ||||
| Transfer Size | ||||
| Ordering Instructions | This dataset is distributed 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: - dBase IV file - Excel file - metadata for the dataset (.htm) - NOTICE.RTF, an important notice about this dataset that can be read by any word processing software. |
|||
| Online Linkage | Click here to download data. (See Ordering Instructions above for details.) By clicking here, you agree to the notice in "Distribution Liability" above. | |||
| Section 7 | Metadata Reference Information | Top of full metadata | Top of page | |
| Metadata Date | 07/23/2008 | |||
| Contact Person Information | Jessica Deegan,
Senior GIS Tech Metropolitan Council 390 Robert Street North St. Paul, Minnesota 55101-1805 Phone: 651-602-1718 FAX: 651-602-1674 E-mail: jessica.deegan@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: 07/23/2008