Minor Civil Divisions, Minnesota, 2003

This page last updated: 04/11/2007
Metadata created using Minnesota Geographic Metadata Guidelines


Metadata Summary

Originator Minnesota Land Management Information Center (LMIC)
Abstract This medium-scale (generally 1:100,000) data set represents municipal boundaries in Minnesota, including changes filed with and approved by the Minnesota Department of Administration's Municipal Boundary Adjustments group through May 31, 2003. The over 3,000 municipalities (minor civil divisions or MCDs) in Minnesota include cities, townships and unorganized territories. Municipal Boundary Adjustments staff work with property owners, local governments, and state agencies to review and facilitate 375 to 400 municipal boundary adjustments annually. The majority of petitions for adjustment are from property owners and the remainder are from cities and townships.

The U.S. Bureau of the Census 2000 Municipal Boundary File (TIGER) for Minnesota served as the foundation for this work. The data was first adjusted by the Minnesota Legislative Coordinating Commission (LCC) GIS Office (see Lineage Section of this metadata record for more information on the original file) and subsequently by LMIC in 2002, at the request of the Office of the Secretary of State. Most recently, boundary changes filed with and approved by the Minnesota Boundary Adjustments group since February 2002 were incorporated in this file.
Browse Graphic none available
Time Period of Content Date 05/31/2003
Currentness Reference Municipal boundary adjustments filed with and approved by the Department of Administration's Minnesota Municipal Boundary Adjustments group between February 2002 and May 31, 2003.
Access Constraints None
Use Constraints This dataset is best suited for general reference only. It is not suitable for precise land measurements or ground surveys.

Redistribution Conditions: In obtaining these data from LMIC, it is understood that you and/or your organization have the right to use them for any internal purpose. If you modify them, you should document those changes in a metadata record that should accompany all redistributed data. If you transmit or provide these data in any form to another user, the data MUST be accompanied by a copy of LMIC's disclaimer NOTICE.TXT and all documentation provided with the original data set including the full metadata record.
Distributor Organization Land Management Information Center
Ordering Instructions This data set is distributed on the internet by clicking below after Online Linkage. Doing so will tell your browser to start downloading a self-extracting 'ZIP' file which will contain the following:

- Shapefile: mcd2003 (.shp, .shx, .dbf, .prj)
- ARC/INFO export (coverage) file: mcd2003.e00
- Documentation (.html, .xml, .lgr) 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.

Full Metadata

Minor Civil Divisions, Minnesota, 2003

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 Minnesota Land Management Information Center (LMIC)
Title Minor Civil Divisions, Minnesota, 2003
Abstract This medium-scale (generally 1:100,000) data set represents municipal boundaries in Minnesota, including changes filed with and approved by the Minnesota Department of Administration's Municipal Boundary Adjustments group through May 31, 2003. The over 3,000 municipalities (minor civil divisions or MCDs) in Minnesota include cities, townships and unorganized territories. Municipal Boundary Adjustments staff work with property owners, local governments, and state agencies to review and facilitate 375 to 400 municipal boundary adjustments annually. The majority of petitions for adjustment are from property owners and the remainder are from cities and townships.

The U.S. Bureau of the Census 2000 Municipal Boundary File (TIGER) for Minnesota served as the foundation for this work. The data was first adjusted by the Minnesota Legislative Coordinating Commission (LCC) GIS Office (see Lineage Section of this metadata record for more information on the original file) and subsequently by LMIC in 2002, at the request of the Office of the Secretary of State. Most recently, boundary changes filed with and approved by the Minnesota Boundary Adjustments group since February 2002 were incorporated in this file.
Purpose This data set was developed to record all municipal boundary changes filed with and approved by the Minnesota Department of Administration's Municipal Boundary Adjustments group through May 31, 2003. Up-to-date municipal boundaries help ensure the proper application of regional and local taxes and are needed to support the election process. This dataset is best suited for general reference only. It is not suitable for precise land measurements or ground surveys.
Time Period of Content Date 05/31/2003
Currentness Reference Municipal boundary adjustments filed with and approved by the Department of Administration's Minnesota Municipal Boundary Adjustments group between February 2002 and May 31, 2003.
Progress Complete
Maintenance and Update Frequency Irregular
Spatial Extent of Data State of Minnesota
Bounding Coordinates -97.269853
-89.389133
49.404387
43.435244
Place Keywords Minnesota
Theme Keywords boundaries, Municipal boundary, municipal boundaries, MCD boundary, MCD boundaries, minor civil division boundary, minor civil division boundaries, city and township boundaries, jurisdictional boundary, jurisdictional boundaries, city boundary, township boundary, political township, unorganized territory, city, township
Theme Keyword Thesaurus ISO 19115 Topic Category
Access Constraints None
Use Constraints This dataset is best suited for general reference only. It is not suitable for precise land measurements or ground surveys.

Redistribution Conditions: In obtaining these data from LMIC, it is understood that you and/or your organization have the right to use them for any internal purpose. If you modify them, you should document those changes in a metadata record that should accompany all redistributed data. If you transmit or provide these data in any form to another user, the data MUST be accompanied by a copy of LMIC's disclaimer NOTICE.TXT and all documentation provided with the original data set including the full metadata record.
Contact Person Information Norman Anderson, GIS Project Manager
Land Management Information Center
658 Cedar Street, Suite 300
St. Paul, MN 55155
Phone: 651-201-2483
FAX: 651-296-3698
E-mail: norm.anderson@state.mn.us
Browse Graphic none available
Browse Graphic File Description
Associated Data Sets Municipal boundary (MCD) files for previous years can be obtained from the following websites:

1. Mn/DOT BaseMap 2001 - Muni - http://www.dot.state.mn.us/tda/basemap/metadata/Muni.htm
2. 2000 Minor Civil Divisions - http://www.lmic.state.mn.us/chouse/metadata/mcd.html (this file contains many Census 2000 population attributes)
3. MCD 1998/1995 - ftp://ftp.commissions.leg.state.mn.us/pub/gis/shape/
4. Minor Civil Divisions, Minnesota, 1990 - http://www.lmic.state.mn.us/chouse/metadata/mcd90.html (this file contains 1990 Census population totals).

 
Section 2 Data Quality Information Top of full metadata Top of page
Attribute Accuracy MCD codes were verified against an existing TIGER 2000 MCD list.

Known problems:
1. Miscoding one 2714156896 St. Cloud City polygon (the county code field 27009 should have been 27141): this has been corrected so users with an older file should download the updated version.

2. Georgetown and Morristown: There are two Georgetown Township and two Morristown Township polygons. It appears that the smaller of each set should have been coded as a City rather than as a Township. See two maps showing the problem at:

- Georgetown: ftp://ftp.lmic.state.mn.us/pub/data/admin_poli/georgetown.pdf

- Morristown: ftp://ftp.lmic.state.mn.us/pub/data/admin_poli/morristown.pdf

This is a problem with the original Census data but since there is no official change, it has not been changed in this file. Users can likely fix the problem by changing polygon 2702723498 from Georgetown Township to Georgetown City, and by changing polygon 2713144314 from Georgetown Township to Georgetown City.
Logical Consistency Data have been topologically structured and verified.
Completeness All municipal boundary changes that were filed with and approved by the Minnesota Department of Administration's Municipal Boundary Adjustments group through May 31, 2003 have been captured in this data set.
Horizontal Positional Accuracy Municipal boundary changes that were filed with and approved by the Municipal Boundary Adjustments group and incorporated in this dataset were made primarily through a 'heads-up' digitizing process. This process relied on other GIS datasets for reference purposes. Existing municipal boundaries were used as the primary reference base whenever possible. Because the positional accuracy of these datasets varied significantly and because heads-up digitizing was used, this dataset is best suited for general reference only. It is not suitable for precise land measurements or ground surveys.

Data used for ground reference included the following:

1. U.S. Bureau of the Census TIGER 2000 Line data - including roads, railroads, rivers, and lakes. Full metadata for these layers is available at:

http://www.census.gov/geo/www/tiger/rd_2ktiger/tlrdmeta.txt

The following is an excerpt regarding the positional accuracy from this metadata record:

'The information present in these files is provided for the purposes of statistical analysis and census operations only. Coordinates in the TIGER/Line files have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest. The positional accuracy varies with the source materials used, but generally the information is no better than the established National Map Accuracy standards for 1:100,000-scale maps from the U.S. Geological Survey (USGS); thus it is NOT suitable for high-precision measurement applications such as engineering problems, property transfers, or other uses that might require highly accurate measurements of the earth's surface.'

2. Public Land Survey System: Quarter-quarter sections (TRSQ), Minnesota

The TRSQ digital data set represents the Township, Range, Section, Quarter section, and Quarter-quarter section divisions of the state. Township, range and section boundaries were digitized at LMIC from the USGS 30' x 60' map series (1:100,000-scale). Quarter section and quarter-quarter section subdivisions were calculated using the section lines.

Full metadata for this layer is available at:

http://lucy.lmic.state.mn.us/metadata/trsq.html

The following is an excerpt regarding positional accuracy from this metadata record:

'Township and range lines were tested on two files, Anoka and Battle Lake, by the USGS National Mapping Division's Mid-Continent Mapping Center. The Center submitted the following evaluation to LMIC on September 1, 1993 in a letter from Mapping Center Chief Merle E. Southern: 'The positional accuracy of the Minnesota LMIC PLSS data evaluated met most of our recently adopted acceptance/rejection criteria. Tests of three thirty-minute segments all showed standard errors for x and y to be 5-mils [0.005 inch] or less. Tracking test on two segments were generally acceptable -- one line was encountered that was 12-mils off. No deviations of more than 11-mils are allowed. Shaping of line work was acceptable.''

3. Minnesota Department of Transportation General Highway Map (Image).

This data was an image of Mn/DOT's general county highway maps. They provided ground reference but were not used for locational editing. Documentation for this data set is in progress.

4. Minnesota Department of Transportation Municipal Boundaries Data Set (Mn/DOT BaseMap 2001 - Muni)

Muni, which represents municipal boundaries within the state, is a layer from the State of Minnesota's BaseMap 2001 and was digitized from USGS 7.5-minute quadrangles.

Full metadata record for this layer is available at:

http://rocky.dot.state.mn.us/BaseMap/metadata/Muni.htm

The following is an excerpt regarding positional Accuracy from this metadata record:

'Locational accuracy for features derived from USGS 7.5-minute quadrangles cannot be assumed to exceed National Map Accuracy Standards for 1:24,000 scale maps (+/- 40 feet or 12 meters) '
Vertical Positional Accuracy Not Applicable
Lineage This data set was created based on a municipal boundary (minor civil division - MCD) layer (LCC 2000) originally developed by the U.S. Bureau of the Census and adjusted by the Minnesota Legislative Coordinating Commission (LCC) GIS Office ( http://www.gis.leg.mn/index.html ) for 2000 redistricting in Minnesota. It was subsequently updated by LMIC in 2002.

After the data was received from the Census Bureau, LCC-GIS staff added to and standardized the attribute items and then created Maptitude Caliper files. These were later converted to ESRI shapefiles. The 2000 TIGER Line file contained municipal boundaries current as of January 1, 2000. There are 11 cities that do not appear in TIGER. They are cities that historically have depended on their surrounding township for election administration and for that reason, have not been separately tracked by the Census Bureau. The GIS Office has assigned each of these cities an unofficial FIPS (federal information processing standard) code and added it to Minnesota's redistricting geography, called LCC 2000. The cities are: Beardsley, Johnson, and Ortonville in Big Stone County; Calumet, Grand Rapids, La Prairie, Marble, Nashwauk, and Taconite in Itasca County; and Aurora and Kinney in St. Louis County. Some counties include unorganized territories that have served as election precincts but were not reported to the Census Bureau in time to be included in TIGER. The GIS Office has added them to the LCC 2000 file. They are: Peatland in Kittson County and America/Beltrami Island, Clear River/Oaks, and Jadis in Roseau County. Lake Superior has historically been included as an appendage to one of the towns in St. Louis, Lake, and Cook counties. The GIS Office has made it a separate unorganized territory in each of these counties.

Over the course of the past two years this data set has been edited to include municipal boundaries adjustments based on legal descriptions and maps delivered to the Department of Administration's Municipal Boundary Adjustments group. The quality of this information varied. In some cases the language describing the boundary adjustment was vague, or the map(s) illustrating the boundary adjustment was poorly drawn or not drawn to scale. Some maps were prepared at an engineering scale while others were photocopies with hand-drawn boundary changes made using a fat magic marker! LMIC staff made every effort to discern as nearly as possible the correct alteration. However, the accuracy of edits will vary. For more information on the boundary adjustments process see: http://www.mba.state.mn.us/process.html

The core municipal boundary file was edited using a 'heads-up' digitizing process and various base datasets were used for ground reference. Ground reference data is described in further detail in the Horizontal Positional Accuracy section of this metadata record and varied in positional accuracy. Often a road, railroad, lake edge or other physical feature was used to determine the new boundary location. Existing municipal boundaries were used as the primary reference base whenever possible. A small number of edits were completed using georeferenced locations on the ground and 'heads-up' digitizing in ArcMap.

Given the positional accuracy of the base data, the editing methods and the boundary source information, this GIS dataset is best suited for general reference only. It is not suitable for precise land measurements or ground surveys.
Source Scale Denominator
 
Section 3 Spatial Data Organization Information Top of full metadata Top of page
Native Data Set Environment ArcGIS 8.2
Geographic Reference for Tabular Data None
Spatial Object Type Vector
Vendor Specific Object Types Polygon
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
Altitude Datum Not applicable
Altitude Units Not applicable
Depth Datum Not applicable
Depth Units Not applicable
UTM Zone Number 15E
 
Section 5 Entity and Attribute Information Top of full metadata Top of page
Entity and Attribute Overview AREA: Total area of polygon
PERIMETER: Length of total perimeter of polygon
BNDADJ03# or Mcd2003_: Internal polygon code
BNDADJ03-ID or Mcd2003_id: Internal polygon code
COUNTY: Unique county identifier composed of FIPS State Code (27) plus FIPS County Code, 2000
MCD: Unique MCD identifier composed of FIPS State Code (27) plus FIPS County Code plus FIPS Minor Civil Division Code, 2000
NAME: MCD Name and Type (e.g., 'Angle Unorganized')
MCD_NAME: MCD Name (e.g., 'Angle')
TYPE: MCD Type (City, Township, and Unorganized)
Entity and Attribute Detailed Citation For links to more information about the state and county FIPS codes, see: http://www.gis.state.mn.us/standards.htm
 
Section 6 Distribution Information Top of full metadata Top of page
Publisher Minnesota Land Management Information Center (LMIC)
Publication Date 11/17/2004
Contact Person Information Nancy Rader
GIS Data Coordination Specialist
Land Management Information Center
658 Cedar Street, Room 300
St. Paul, MN 55155
Phone: 651-201-2489
FAX: 651-296-3698
E-mail: clearing.house@state.mn.us
Distributor's Data Set Identifier mcd2003
Distribution Liability DISTRIBUTION LIABILITY STATEMENT
For data delivered on-line or by physical media by
The Land Management Information Center

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. You should consult available data documentation (metadata) for these particular data to determine their limitations and the precision to which they depict distance, direction, location or other geographic characteristics. These data may be subject to periodic change without prior notification.

No Warranty: These data are provided as is, without any warranty whatsoever, including but not limited to any warranty as to their performance, merchantability, or fitness for any particular purpose.

Liability: The entire risk as to the results of the use of these data is assumed by the user. LMIC is not responsible for any interpretation or conclusions based on these data 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 these 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, you may not use these data.

Redistribution Conditions: In obtaining these data from LMIC, it is understood that you and/or your organization have the right to use them for any internal purpose. If you modify them, you should document those changes in a metadata record that should accompany all redistributed data. If you transmit or provide these data 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 these data have been requested from LMIC on magnetic media, CD-ROM or any other physical media, LMIC will deliver this product in the computer-readable format agreed upon with the requestor. LMIC will re-issue these data if they are determined unreadable by correctly adjusted computer input devices, or when the medium is delivered in a damaged condition. Requests for re-issue of this digital data product must be made within 30 days of the date shipped from LMIC.
Transfer Format Name Shapefile, Arc/Info export (coverage)
Transfer Format Version Number N/A
Transfer Size 8 mb
Ordering Instructions This data set is distributed on the internet by clicking below after Online Linkage. Doing so will tell your browser to start downloading a self-extracting 'ZIP' file which will contain the following:

- Shapefile: mcd2003 (.shp, .shx, .dbf, .prj)
- ARC/INFO export (coverage) file: mcd2003.e00
- Documentation (.html, .xml, .lgr) 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
Land Management Information Center
658 Cedar Street, Suite 300
St. Paul, MN 55155
Phone: 651-2-01-2489
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.gis.state.mn.us/stds/metadata.htm


This page last updated: 04/11/2007