| - Full Metadata - | - View Attributes - | - none available - | - Get Data - |
This page last updated: 04/11/2007
Metadata created using Minnesota Geographic Metadata Guidelines
| Originator | U.S. Bureau of the Census; Minnesota Legislative Coordinating Commission/GIS Office; Land Management Information Center (LMIC), Minnesota Planning |
| Abstract | This minor civil division (MCD) boundary file was derived from U.S. Census 1990 TIGER/Line files, contains 1990 Census population data for Minnesota's MCDs, and matches 1990 Census statistics. Minor civil divisions are political or administrative units such as cities and townships. Since some MCDs are made up of non-contiguous areas (and thus of multiple polygons), a convention was developed to ensure that the total population would not be counted for each polygon. Two versions of the file are included; one contains county boundaries, the other does not. |
| Browse Graphic | none available |
| Time Period of Content Date | 1990 |
| Currentness Reference | Year when data was collected for the 1990 Census TIGER/Line files. |
| Access Constraints | None |
| Use Constraints | In obtaining this data from LMIC, it is understood that individuals or organizations have the right to use it for any internal purpose. If data is modified, changes should be documented in a metadata record that should accompany all redistributed data. If data is transmitted or provided in any form to another user, the data must be accompanied by a copy of this disclaimer and all documentation provided with the original data set, including the full metadata record. |
| Distributor Organization | Minnesota Land Management Information Center (LMIC) |
| Ordering Instructions | This data set is distributed on the internet in two ways. Clicking the link under 'Online Linkage' allows you to preview the data and download part or all of the data set in shapefile format. Alternatively, you can download the entire dataset, in Arc Export format, from the LMIC FTP site. Interactive map download: When you access the interactive map download site from the 'Online Linkage', this data layer appears in the map box. The interactive map allows you to examine the linework of the data set and its attributes before you decide to download it. You can designate the area you wish to download by drawing a box on the screen with the 'zoom in' tool. Then use the 'download' tool to download the subset of the file to your own machine in ArcView shapefile format. The shapefile, associated data tables, metadata, and liability notice are all included in the download. Besides the data layer which you have selected, this map may contain related data sets as well as reference information. You may choose to examine and download any of the related data sets at the same time. See the help at the site for more detail. FTP download: To download the entire file, point your browser to: ftp://ftp.lmic.state.mn.us/pub/data/admin_poli/mcd90.exe Doing so will tell your browser to start downloading a self-extracting 'ZIP' file which will contain the following: - Arc Export files (.e00) of coverages for MN_MCD90 (version without county boundaries, 10 mb) and MN_MCDCN (version with county boundaries and attributes, 13 mb) - Shapefile formats for the above (.shp, .shx and .dbf files, 5.4 mb and 6 mb) - Metadata (.htm) file for the data set - NOTICE.RTF, an important notice about this data set that can be read by most word processing software, and an ascii text version of the same notice (NOTICE.TXT) After downloading this self-extracting 'zip' file (which will have an 'exe' extension), simply execute (run) the file. (For example, you can double click it from Windows Explorer or File Manager). Doing this will automatically extract the files described above. You can then delete file types that you do not need, if any. |
| 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 | U.S. Bureau of the Census; Minnesota Legislative Coordinating Commission/GIS Office; Land Management Information Center (LMIC), Minnesota Planning | |||
| Title | Minor Civil Divisions, Minnesota, 1990 | |||
| Abstract | This minor civil division (MCD) boundary file was derived from U.S. Census 1990 TIGER/Line files, contains 1990 Census population data for Minnesota's MCDs, and matches 1990 Census statistics. Minor civil divisions are political or administrative units such as cities and townships. Since some MCDs are made up of non-contiguous areas (and thus of multiple polygons), a convention was developed to ensure that the total population would not be counted for each polygon. Two versions of the file are included; one contains county boundaries, the other does not. | |||
| Purpose | 1990 MCD boundaries are used to match 1990 Census data. Versions are provided with and without county boundaries in order to allow different viewing and analysis options for MCDs that cross county boundaries. For example, the city of St. Cloud covers parts of three counties. To treat St. Cloud as one entity, use the MCD file without county boundaries; to treat St. Cloud as three separate areas, use the MCD file with county boundaries. | |||
| Time Period of Content Date | 1990 | |||
| Currentness Reference | Year when data was collected for the 1990 Census TIGER/Line files. | |||
| Progress | Complete | |||
| Maintenance and Update Frequency | None planned | |||
| Spatial Extent of Data | Minnesota | |||
| Bounding Coordinates | -97.5 -89 49.5 43 |
|||
| Place Keywords | Minnesota | |||
| Theme Keywords | boundaries, minor civil division, MCD, census, city, town, political township, unorganized territory, population | |||
| Theme Keyword Thesaurus | ISO 19115 Topic Category | |||
| Access Constraints | None | |||
| Use Constraints | In obtaining this data from LMIC, it is understood that individuals or organizations have the right to use it for any internal purpose. If data is modified, changes should be documented in a metadata record that should accompany all redistributed data. If data is transmitted or provided in any form to another user, the data must be accompanied by a copy of this disclaimer and all documentation provided with the original data set, including the full metadata record. | |||
| Contact Person Information | Sandi Kuitunen,
GIS Project Manager Minnesota Land Management Information Center (LMIC) 658 Cedar Street, 300 Centennial Building St. Paul, MN 55155 Phone: (651) 201-2486 FAX: (651) 296-3698 E-mail: clearing.house@state.mn.us | |||
| Browse Graphic | none available | |||
| Browse Graphic File Description | ||||
| Associated Data Sets | 1. Updated versions of the MCD file from the Secretary of State's office are available via the Legislative GIS Office website: http://www.commissions.leg.state.mn.us/gis/index.html 2. The U.S. Bureau of the Census will release revised MCD boundary files when the 2000 Census data is available. For updates, check: http://www.census.gov |
|||
| Section 2 | Data Quality Information | Top of full metadata | Top of page | |
| Attribute Accuracy | MCD codes and population attributes are as accurate as they are in the 1990 TIGER/Line files (see http://www.census.gov for more information on TIGER/Line files). MCD names were input from undocumented sources at the Legislative GIS Office and LMIC. The files have been used extensively at LMIC, and any discovered errors have been corrected. | |||
| Logical Consistency | Data have been topologically structured and verified. | |||
| Completeness | ||||
| Horizontal Positional Accuracy | Unknown | |||
| Lineage | The Legislative GIS Office (LGO) extracted the MCD boundaries from 1990 U.S. Census TIGER/Line files as part of the legislative redistricting process. LGO then provided the boundary file to LMIC. LMIC created the MN_MCDCN version by intersecting LGO's MCD boundary file with 1990 Census county boundaries. This process created many sliver polygons. Frequency counts were used to flag the polygons that should be retained, notably new ones added for MCDs that crossed county boundaries as well as any MCDs that were made of multiple non-contiguous polygons. |
|||
| Source Scale Denominator | 100000 | |||
| Section 3 | Spatial Data Organization Information | Top of full metadata | Top of page | |
| Native Data Set Environment | ARC/INFO | |||
| Geographic Reference for Tabular Data | ||||
| Spatial Object Type | Vector | |||
| Vendor Specific Object Types | polygon, arc, node | |||
| Tiling Scheme | State | |||
| Section 4 | Spatial Reference Information | Top of full metadata | Top of page | |
| Horizontal Coordinate Scheme | UTM | |||
| Ellipsoid | GRS80 | |||
| Horizontal Datum | NAD83 | |||
| Horizontal Units | Meters | |||
| Distance Resolution | Unknown | |||
| Altitude Datum | Not applicable | |||
| Depth Datum | Not applicable | |||
| UTM Zone Number | 15E | |||
| Coordinate Offsets or Adjustments | None | |||
| Section 5 | Entity and Attribute Information | Top of full metadata | Top of page | |
| Entity and Attribute Overview | Both MN_MCD90 and MN_MCDCN have the following items (item names are listed as they appear in the ARC/INFO coverage format; shapefile item names contain only the first 10 characters). Note: There are two population items: POP_PUBLAW90 is used for generating population counts; POP_MULTI_MCD is used for mapping. If the explanation of these items for multi-polygon MCDs is confusing, try looking at the city of St. Cloud. It is a good example since portions of the city are located in three counties and since it has four non-contiguous polygons in Stearns County. Locate the polygons by selecting for 'St. Cloud city' in the MCD90_NAME item. 1. MCD90_NAME: the descriptive name of the MCD in mixed case type. 2. MCD90_CODE: a 5-digit code assigned to each MCD in the TIGER/Line files. Within a county, MCD numbers are unique. However, since MCDs may cross county boundaries, the MCD number needs to be preceded by the county number to uniquely match Census Summary Tape data when using statewide data (see CTYMCD_FIPS item below in the MN_MCDCN file). 3. POP_PUBLAW90: The 1990 Census population total for each MCD. In the case of an MCD that includes two or more separate polygons, this item will equal the total population figure only in the polygon with the largest area. For the smaller polygons, POP_PUBLAW90 will equal 0 and MULTI_POLY = Y. This convention ensures that population figures will not be counted more than once. 4. MULTI_POLY_MCD: this item is blank if the MCD is a single polygon. If the MCD includes two or more separate polygons, this item is blank for the largest polygon and equals 'Y' for each of the smaller polygon(s). 5. POP_MULTI_MCD: this item is the same as POP_PUBLAW90 if the MCD is a single polygon. If the MCD includes two or more polygons, then the largest polygon will contain the total MCD population in both POP items; however, for the smaller polygons (MULTI_POLY_MCD = 'Y'), the population is in this item and POP_PUBLAW90 is zero. This item is useful for creating population maps since each polygon of an MCD is assigned the same population value. The MN_MCDCN file has several additional items since it contains county boundaries: 1. NAME_4CHAR_CTY: The first four letters of a county name, capitalized (Exception: Lake of the Woods is LOTW). 2. NAME_LOWER_CTY: The full county name, mixed case. 3. MLMIS_CTY: A 2-digit county code created by sequentially numbering an alphabetized list of Minnesota's 87 counties. 4. FIPS_CTY: The 3-digit federal information processing standards (FIPS) code assigned to each county. It is unique within Minnesota. 5. CTYMCD_FIPS: The FIPS county code followed by the MCD code. This combined code is unique within Minnesota. |
|||
| Entity and Attribute Detailed Citation | See http://www.census.gov for more information about TIGER/Line and MCD data and codes. | |||
| Section 6 | Distribution Information | Top of full metadata | Top of page | |
| Publisher | Minnesota Land Management Information Center (LMIC) | |||
| Publication Date | Unknown | |||
| Contact Person Information | Nancy Rader GIS Data Coordination Specialist Minnesota Land Management Information Center (LMIC) 658 Cedar Street, 300 Centennial Building St. Paul, MN 55155 Phone: 651-296-2499 FAX: 651-296-3698 E-mail: clearing.house@state.mn.us |
|||
| Distributor's Data Set Identifier | mcd90 | |||
| Distribution Liability | DISTRIBUTION LIABILITY STATEMENT For data or maps delivered online or by physical media by the Land Management Information Center at MN Planning Limitations: Although extensive effort has been made to produce error-free and complete data, all geographic information has limitations due to the scale, resolution, date and interpretation of the original source materials. Users should consult available data documentation (metadata) for this particular data to determine limitations and the precision to which the data depict distance, direction, location or other geographic characteristics. Data may be subject to change without prior notification. No warranty: Data is provided as is, without any warranty whatsoever, including but not limited to any warranty as to performance, merchantability or fitness for any particular purpose. Liability: The entire risk as to the results of the use of this data is assumed by the user. LMIC is not responsible for any interpretation or conclusions made by those who acquire or use it. LMIC shall not be liable for any direct, indirect, special, incidental, compensatory or consequential damages or third-party claims resulting from the use of this data, even if LMIC has been advised of the possibility of such potential loss or damage. In states that do not allow the exclusion or limitation of incidental or consequential damages, this data may not be used. Redistribution conditions: In obtaining this data from LMIC, it is understood that individuals or organizations have the right to use it for any internal purpose. If data is modified, changes should be documented in a metadata record that should accompany all redistributed data. If data is transmitted or provided in any form to another user, the data must be accompanied by a copy of this disclaimer and all documentation provided with the original data set, including the full metadata record. Data delivered on electronic media: If data has been requested from LMIC on magnetic media, CD or any other physical media, LMIC will deliver it in the computer-readable format agreed upon with the requestor. LMIC will reissue data if it is unreadable by correctly adjusted computer input devices or when the media is delivered in a damaged condition. Requests for reissue of this digital data product must be made within 30 days of the date shipped from LMIC. |
|||
| Transfer Format Name | ARC/INFO export (coverage) or shapefile | |||
| Transfer Format Version Number | ||||
| Transfer Size | 11 megabytes (zip file) | |||
| Ordering Instructions | This data set is distributed on the internet in two ways. Clicking the link under 'Online Linkage' allows you to preview the data and download part or all of the data set in shapefile format. Alternatively, you can download the entire dataset, in Arc Export format, from the LMIC FTP site. Interactive map download: When you access the interactive map download site from the 'Online Linkage', this data layer appears in the map box. The interactive map allows you to examine the linework of the data set and its attributes before you decide to download it. You can designate the area you wish to download by drawing a box on the screen with the 'zoom in' tool. Then use the 'download' tool to download the subset of the file to your own machine in ArcView shapefile format. The shapefile, associated data tables, metadata, and liability notice are all included in the download. Besides the data layer which you have selected, this map may contain related data sets as well as reference information. You may choose to examine and download any of the related data sets at the same time. See the help at the site for more detail. FTP download: To download the entire file, point your browser to: ftp://ftp.lmic.state.mn.us/pub/data/admin_poli/mcd90.exe Doing so will tell your browser to start downloading a self-extracting 'ZIP' file which will contain the following: - Arc Export files (.e00) of coverages for MN_MCD90 (version without county boundaries, 10 mb) and MN_MCDCN (version with county boundaries and attributes, 13 mb) - Shapefile formats for the above (.shp, .shx and .dbf files, 5.4 mb and 6 mb) - Metadata (.htm) file for the data set - NOTICE.RTF, an important notice about this data set that can be read by most word processing software, and an ascii text version of the same notice (NOTICE.TXT) After downloading this self-extracting 'zip' file (which will have an 'exe' extension), simply execute (run) the file. (For example, you can double click it from Windows Explorer or File Manager). Doing this will automatically extract the files described above. You can then delete file types that you do not need, if any. |
|||
| 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 | 04/11/2007 | |||
| Contact Person Information | Nancy Rader,
GIS Data Coordination Specialist Minnesota Land Management Information Center (LMIC) 658 Cedar Street, 300 Centennial Building St. Paul, MN 55155 Phone: 651-201-2499 FAX: 651-296-3698 E-mail: clearing.house@state.mn.us |
|||
| Metadata Standard Name | Minnesota Geographic Metadata Guidelines | |||
| Metadata Standard Version | 1.2 | |||
| Metadata Standard Online Linkage | http://www.lmic.state.mn.us/gc/stds/metadata.htm | |||
This page last updated: 04/11/2007