Metadata: 2003 Regional Parcel Dataset - Seven County Twin Cities Metropolitan Area

- View Sample -

2003 Regional Parcel Dataset - Seven County Twin Cities Metropolitan Area

This page last updated: 04/20/2004
Metadata created using Minnesota Geographic Metadata Guidelines

Metadata Summary

Originator	Counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington
Abstract	This dataset is a compilation of tax parcel polygon layers from the seven Twin Cities, Minnesota metropolitan area counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington. The seven counties were assembled into a common coordinate system. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. Not all attributes are populated for all counties. This is an annual version of the MetroGIS Regional Parcel Dataset that can be used with other annual versions to do change analysis and time series investigations. This dataset is intended to contain all updates to each county's parcel data through the end of 2003. It was originally published as the 'January 1, 2004' version of the dataset. See the Currentness Reference below and the Entity and Attribute information in Section 5 for more information about the dates for specific aspects of the dataset. This dataset contains one record for each real estate/tax parcel polygon. In many places a one-to-one relationship does not exist between these parcel polygons and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties. Some counties have also made available a parcel points dataset that includes the same attribute fields as the polygon dataset. The point are intended to provide information in situations where multiple tax parcels are represented by a single polygon. The primary example of this is the condominium. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. This is a MetroGIS Regionally Endorsed dataset. (See http://www.metrogis.org/data/about/index.shtml#whatis for more information.) Each of the seven Metro Area counties has entered into a multiparty agreement with the Metropolitan Council to assemble and distribute the parcel data for each county as a regional (seven county) parcel dataset.
Browse Graphic	View a sample of the data.
Time Period of Content Date	12/31/2003
Currentness Reference	This dataset reflects the status of each county's parcel polygon and attribute data as of the following dates: Anoka = 12/16/2003 for polygons and 12/16/2003 for attributes Carver = 01/21/2004 for polygons and 01/21/2004 for attributes Dakota = 12/31/2003 for polygons and 12/31/2003 for attributes Hennepin = 01/12/2004 for polygons and 01/05/2004 for attributes Ramsey = 01/05/2004 for polygons, attribute dates vary Scott = 01/08/2004 for polygons and 01/10/2004 for attributes Washington = 12/26/2003 for polygons and 12/26/2003 for attributes
Access Constraints	Access to this dataset is restricted by licensing requirements imposed by the counties that supplied the source data. Under these licensing requirements, the regional parcel dataset is available through MetroGIS at no cost to certain ''Governmental Units'' and ''Academic Institutions''. It is available to other organizations and individuals directly from each county. ''Governmental Units'' means all counties, cities, townships, soil and water conservation districts, watershed districts, watershed management organizations and school districts located within the Minnesota counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott, Washington, Sherburne, Chisago, Isanti, Wright, Goodhue, LeSueur, Sibley, Rice, and McLeod, and the Wisconsin counties of Pierce, St Croix and Polk; ; regional governmental agencies including the Metropolitan Airports Commission, the Metropolitan Sports Facilities Commission, the Metropolitan Council, the Metropolitan Parks and Open Space Commission, the Metropolitan Radio Board and the Metropolitan Mosquito Control Commission; the Minnesota State Legislature and agencies and departments of the State of Minnesota and the federal government which have jurisdiction within the counties listed herein. ''Academic Institutions'' means a college or university that belongs to the University of Minnesota system, Minnesota State Colleges and University System (MnSCU) or the Minnesota Private Colleges Council or any other institution of higher learning approved by the MetroGIS Board Note that for these governmental and academic institutions, one licensing procedure exist for Hennepin County and a different licensing procedure exists for the other 6 counties in the metro area. Individuals and organizations that do not qualify as governmental or academic institutions must acquire the dataset directly from each county. A license is required and a fee will be assessed.
Use Constraints	See license agreements.
Distributor Organization	Metropolitan Council, on behalf of MetroGIS
Ordering Instructions	LICENSING This is a licensed dataset. The licensing and data acquisition procedures differ depending upon the type of organization requesting the datasets. Qualifying governmental units and academic interests may obtain the dataset without fee directly from MetroGIS. More information about licensing for these organizations can be found at http://www.metrogis.org/data/datasets/parcels/public/index.shtml . All other organizations and individuals must obtain the dataset directly from each county. In most cases a fee is required. More information about licensing and acquisition procedures can be found at http://www.metrogis.org/data/datasets/parcels/private/index.shtml . DOWNLOADING Licensed governmental and academic users may download the parcel dataset using the userID, password and instructions provided with their license approval. The dataset is downloaded from a password protected FTP site. This data is not available on the DataFinder Cafe.
Online Linkage	none available

Full Metadata

2003 Regional Parcel Dataset - Seven County Twin Cities Metropolitan Area

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	Counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington
Title	2003 Regional Parcel Dataset - Seven County Twin Cities Metropolitan Area
Abstract	This dataset is a compilation of tax parcel polygon layers from the seven Twin Cities, Minnesota metropolitan area counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington. The seven counties were assembled into a common coordinate system. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. Not all attributes are populated for all counties. This is an annual version of the MetroGIS Regional Parcel Dataset that can be used with other annual versions to do change analysis and time series investigations. This dataset is intended to contain all updates to each county's parcel data through the end of 2003. It was originally published as the 'January 1, 2004' version of the dataset. See the Currentness Reference below and the Entity and Attribute information in Section 5 for more information about the dates for specific aspects of the dataset. This dataset contains one record for each real estate/tax parcel polygon. In many places a one-to-one relationship does not exist between these parcel polygons and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties. Some counties have also made available a parcel points dataset that includes the same attribute fields as the polygon dataset. The point are intended to provide information in situations where multiple tax parcels are represented by a single polygon. The primary example of this is the condominium. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. This is a MetroGIS Regionally Endorsed dataset. (See http://www.metrogis.org/data/about/index.shtml#whatis for more information.) Each of the seven Metro Area counties has entered into a multiparty agreement with the Metropolitan Council to assemble and distribute the parcel data for each county as a regional (seven county) parcel dataset.
Purpose	To view, analyze and display parcel data anywhere in the seven county metro area. This is an annual version of the MetroGIS Regional Parcel Dataset that can be used with other annual versions to do change analysis and time series investigations.
Time Period of Content Date	12/31/2003
Currentness Reference	This dataset reflects the status of each county's parcel polygon and attribute data as of the following dates: Anoka = 12/16/2003 for polygons and 12/16/2003 for attributes Carver = 01/21/2004 for polygons and 01/21/2004 for attributes Dakota = 12/31/2003 for polygons and 12/31/2003 for attributes Hennepin = 01/12/2004 for polygons and 01/05/2004 for attributes Ramsey = 01/05/2004 for polygons, attribute dates vary Scott = 01/08/2004 for polygons and 01/10/2004 for attributes Washington = 12/26/2003 for polygons and 12/26/2003 for attributes
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 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	parcels, regional parcel data, cadastre, land ownership
Theme Keyword Thesaurus	None
Access Constraints	Access to this dataset is restricted by licensing requirements imposed by the counties that supplied the source data. Under these licensing requirements, the regional parcel dataset is available through MetroGIS at no cost to certain ''Governmental Units'' and ''Academic Institutions''. It is available to other organizations and individuals directly from each county. ''Governmental Units'' means all counties, cities, townships, soil and water conservation districts, watershed districts, watershed management organizations and school districts located within the Minnesota counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott, Washington, Sherburne, Chisago, Isanti, Wright, Goodhue, LeSueur, Sibley, Rice, and McLeod, and the Wisconsin counties of Pierce, St Croix and Polk; ; regional governmental agencies including the Metropolitan Airports Commission, the Metropolitan Sports Facilities Commission, the Metropolitan Council, the Metropolitan Parks and Open Space Commission, the Metropolitan Radio Board and the Metropolitan Mosquito Control Commission; the Minnesota State Legislature and agencies and departments of the State of Minnesota and the federal government which have jurisdiction within the counties listed herein. ''Academic Institutions'' means a college or university that belongs to the University of Minnesota system, Minnesota State Colleges and University System (MnSCU) or the Minnesota Private Colleges Council or any other institution of higher learning approved by the MetroGIS Board Note that for these governmental and academic institutions, one licensing procedure exist for Hennepin County and a different licensing procedure exists for the other 6 counties in the metro area. Individuals and organizations that do not qualify as governmental or academic institutions must acquire the dataset directly from each county. A license is required and a fee will be assessed.
Use Constraints	See license agreements.
Contact Person Information	SEE METADATA FOR INDIVIDUAL COUNTIES, , Phone: FAX: E-mail: none available
Browse Graphic	View a sample of the data.
Browse Graphic File Description	Sample map showing the MetroGIS Regional Parcel Data.
Associated Data Sets	Various parcel datasets available at the MetroGIS DataFinder website at http://www.datafinder.org/catalog.asp#Land%20Ownership

Section 2	Data Quality Information	Top of full metadata	Top of page
Attribute Accuracy	A standard set of attribute fields is included for each county. However, not all attributes are available for all counties. No attempt has been made by MetroGIS to assess the accuracy of the attribute data. Any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person listed in the individual county metadata. Links to that metadata can be found in the Horizontal Positional Accuracy element below.
Logical Consistency	No attempt was made to edgematch or rubbersheet the seven counties, thus overlaps and gaps will exist between counties. Not all tax parcels are represented by a unique polygon. For example, a county might have one polygon representing a condominium complex. Some counties have provided an additional parcel points shape file that will include points to represent such tax parcels (e.g. a point for each individual condominium).
Completeness	For parcel attributes, see Section 5 of this metadata. For parcel geography, see metadata for individual counties. Any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person listed in the individual county metadata. Links to that metadata can be found in the Horizontal Positional Accuracy element below.
Horizontal Positional Accuracy	ANOKA: No information provided. CARVER: The Horizontal Accuracy of the counties parcel dataset is, for the most part, UNDER 1' accuracy. This is possible because the County's Surveyor used COGO (Coordinate Geometry) which is a highly accurate way of plotting parcel lines. DAKOTA: 90% less than 2.0 feet HENNEPIN: Estimated to be +or- 2 to 4 feet at section corners. Positional accuracy decreases with distance from section corners. RAMSEY: Digitized information is generally +or- 7 feet; some areas have been found to be +or- 30 feet. Cogo (coordinate geometry) accuracy generally is +or- 1.0 foot. SCOTT: No information provided. WASHINGTON: Digitized features outside areas of high vertical relief (e.g. major river valleys) tested 23 feet horizontal accuracy at the 95 % confidence level using National Standard Spatial Data Accuracy (NSSDA). Digitized features within areas of high vertical relief tested 120 feet horizontal accuracy by other testing procedures. All other features are generated by coordinate geometry and based on a framework of accurately located PLSS corner positions used with public information of record. Computed positions of parcel boundaries are not based on individual field surveys. Although tests of randomly selected points may show high accuracy between field and parcel map content, variations between boundary monumentation and legal description of record can and do exist. Caution is necessary in use of land boundary data shown. Contact the Land Management/Land Survey Division for more information.
Lineage	Each county provided parcel polygons and attributes in shape file format with UTM coordinates, to the Metropolitan Council. The Metropolitan Council checked each shape file to insure it had all desired attribute fields, field names, types and lengths. No attempt was made to edgematch or rubber sheet the parcel geography between counties.
Source Scale Denominator

Section 3	Spatial Data Organization Information	Top of full metadata	Top of page
Native Data Set Environment	See metadata for individual counties.
Geographic Reference for Tabular Data	None
Spatial Object Type	Vector
Vendor Specific Object Types	polygon shapes
Tiling Scheme	One shape file for each of the seven counties.

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
UTM Zone Number	15

Section 5	Entity and Attribute Information	Top of full metadata	Top of page

Entity and Attribute Overview

A standard set of attribute fields is included for each county; however, not 
all attributes fields are populated by each county.  Some qualifying comments 
have been provided by counties and are included after the description of 
the attributes. 
  
  
COUNTY_ID:  Three digit FIPS and state standard county code. 
            003 = Anoka 
            019 = Carver 
            037 = Dakota 
            053 = Hennepin 
            123 = Ramsey 
            139 = Scott 
            163 = Washington 
  
  
PIN:        Unique regional parcel ID comprised of the county PIN with  
            the county code and dash appended to the front. 
  
   
OWN_NAME:   The full (first and last) name of the owner. The format  
            (e.g. last name first or last name last) and inclusion of  
            multiple owners is up to each county. 
  
            Anoka:      No data. 
            Dakota:     Owner name or Contract Purchaser name. Not all owner  
                        names will appear on joint or multiple ownership 
                        parcels. 
            Ramsey:     Uses PRIMARY. This is not guaranteed to be the owner. 
  
  
OWN_ADD_L1: Owner address line 1. 
OWN_ADD_L2: Owner address line 2. 
OWN_ADD_L3: Owner address line 3. 
            These three fields are for the mailing address of the owner.  
            Typically line 1 is street address and line 2 is city, state  
            & zip, but other variations exist. 
  
            Hennepin:   No data. 
            Ramsey:     Uses PRIMARY address.  This is not guaranteed  
                        to be the owner's address. 
  
  
TAX_NAME:   The full (first and last) name of the taxpayer. The format  
            (e.g. last name first or last name last) and inclusion of  
            multiple taxpayers is up to each county. 
  
            Anoka:      No data. 
            Dakota:     No data. 
            Ramsey:     Uses ALTERNATE name.  When available, this is 
                        often the person who pays taxes.  This field is  
                        usually blank. 
            Washington: Some data provided. 
  
  
TAX_ADD_L1: Taxpayer address line 1. 
TAX_ADD_L2: Taxpayer address line 2. 
TAX_ADD_L3: Taxpayer address line 3. 
            Mailing address of the taxpayer. Typically line 1 is street  
            address and line 2 is city, state & zip, but other variations 
            exist. 
  
            Dakota:     No data. 
            Ramsey:     Uses ALTERNATE address.  The fields are  
                        usually blank. 
            Washington: No data. 
  
  
HOMESTEAD:  Homesteaded (Y/N). 
  
            Anoka:      Used EXPT_CODE1 = HST.  Some additional homesteads  
                        may exist.  Does not distinguish between agricultural  
                        and residential homesteads. 
            Dakota:     Payable 2004 Homestead Status. Y includes fractional  
                        and disabled homesteads. 
            Hennepin:   2003 Assessment for Taxes Payable in 2004. 
            Ramsey:     Uses numeric codes.  There are issues with converting 
                        partial and disabled homesteads to a direct Y/N. 
  
  
BLDG_NUM:   The building or house number of the parcel. 
            Note that in some cases in Dakota and Hennepin Counties, leading  
            and following blank spaces exist in this field which may cause  
            problems when performing a search (e.g. search for '12345' may not  
            find ' 12345'). 
  
            Dakota:     Field is unverified. 
  
  
STREET:     The street name (with street type and direction). This is the  
            actual location of the parcel, which may not be the mailing  
            address. 
  
            Dakota:     Field is unverified. 
  
  
CITY:       Name of city or township in which the parcel resides (not the  
            mailing address city or township). 
 
 
            Note that for Carver, Ramsey, Scott and Washington Counties, this  
            field is not populated according to the definition above 
  
  
ZIP:        Zip code in which the parcel resides 
  
            Dakota:     Field is unverified. 
  
  
EMV_LAND:   Land estimated market value. 
EMV_BLDG:   Building estimated market value. 
EMV_TOTAL:  Total estimated market value.  This may include more than 
            the land and building values. 
  
            Anoka:      2003 estimated values for taxes payable in 2004. 
            Carver:     2003 estimated values for taxes payable in 2004. 
            Dakota:     2003 estimated values for taxes payable in 2004. 
            Hennepin:   2003 estimated values for taxes payable in 2004. 
                        EMV_TOTAL includes sum of Land, Building & Machinery 
                        Estimated Market Values. 
            Ramsey:     2002 estimated values for taxes payable in 2003. 
            Scott:      2003 estimated values for taxes payable in 2004. 
            Washington: 2003 estimated values for taxes payable in 2004. 
  
  
TAX_CAPAC:  Tax capacity of the parcel. 
  
            Anoka:      For taxes payable in 2003. 
            Carver:     For taxes payable in 2003. 
            Dakota:     Total tax capacity, year payable 2003. 
            Hennepin:   For taxes payable in 2003. 
            Ramsey:     No data. 
            Scott:      No data. 
            Washington: For taxes payable in 2003 
  
  
TOTAL_TAX:  Total tax of the parcel. 
  
            Anoka:      For taxes payable in 2003. 
            Carver:     For taxes payable in 2003. 
            Dakota:     Total real estate tax, including special assessments,  
                        due and payable in 2003. 
            Hennepin:   For Taxes Payable in 2003 (includes special 
                        assessments). 
            Ramsey:     For taxes payable in 2003. 
            Scott:      No data. 
            Washington: No data. 
  
  
TAX_EXEMPT: Tax exempt (Y/N). 
  
            Anoka:      Used EXPT_CODE1 = EXM. 
            Hennepin:   2002 Assessment for Taxes Payable in 2003. 
            Ramsey:     Uses CAMA numeric codes for land use codes.  Numeric 
                        codes in the six hundred range were assumed to be 
                        exempt and converted to Y. All others were coded N. 
            Scott:      No data. 
  
  
YEAR_BUILT: The year the primary structure was initially built. 
 
            Hennepin:   This field is populated by individual city assessors 
                        and cannot be guaranteed by Hennepin County. 
            Ramsey:     Dwelling data and Commercial data were combined. 
            Washington: No values newer than 1999.  No values for Woodbury. 
  
  
SCHOOL_DST: Unique school district number. 
  
  
WSHD_DIST:  Watershed district name. 
  
            Hennepin:   Data for approximately  63% of properties.  Properties 
                        that do not have a watershed name are located in a 
                        watershed district that does not levy a watershed 
                        district tax rate. 
            Ramsey:     The last character of the district code was used with a 
                        lookup table to produce a descriptive watershed 
                        district. 
            Scott:      No data. 
  
  
NUM_UNITS:  Number of residential units. 
  
            Anoka:      Some data provided. 
            Carver:     No data. 
            Dakota:     Data provided. 
            Hennepin:   No data. 
            Ramsey:     Data provided. 
            Scott:      No data. 
            Washington: No data. 
  
  
STRUC_TYPE: Information pertaining to the type of structure on the parcel. 
  
            Carver:     No data. 
            Dakota:     Describes the main use for which this building was  
                        designed, such as single family residence, duplex,  
                        tri-plex, restaurant, etc. 
            Hennepin:   No data. 
            Ramsey:     Uses CAMA codes.  Dwelling and commercial tables  
                        were aggregated and a lookup table was developed to  
                        produce structure descriptions. 
 
 
SALE_DATE:  Date of last sale.  In general this includes all 'arm's length'  
            transactions and would not, for example, include a sale to a family  
            member for $1.  This may vary by county. 
               
            Carver:     Includes all sales. 
            Dakota:     Month and year of last QUALIFIED SALE (day not part of 
                        attributes available). Day of the month is fictitious  
                        (set to the 1st of the month to conform to date field 
                        FORMAT). 
            Ramsey:     The CAMA valid sales were used.  Data exist for 39% of 
                        parcels. 
            Washington: No values newer than 8/14/2000 and no data for  
                        Woodbury. 
 
  
SALE_VALUE: Value of last sale. 
  
            Anoka:      Field is partially populated. 
            Ramsey:     The CAMA valid sales were used.  Data exist for 39%  
                        of parcels. 
 
 
PARC_CODE:  Parcel Polygon to Parcel Point and PIN Relationship Code. This  
            field is used to provide information about the relationship between  
            parcel polygons, parcel points and unique tax parcel identifiers  
            (PINs). At this time, most counties do not populate this field.  
            Values are:  
 
            0 = Information not available or not provided 
            1 = Valid Parcel with a single tax PIN 
            2 = In polygon dataset: Parcel polygon representing multiple tax 
                PINs In point dataset: One of multiple parcel points that  
                together are represented by a single polygon 
 
            The values below are likely only to be found in the polygon  
            dataset.  The polygons for which they are assigned are unlikely to  
            have a tax PIN or other parcel attributes. The parcel points  
            datasets, where available, are unlikely to include these feature  
            types. 
 
            10 = Condominium Common Area 
            11 = Right-of-way 
            12 = Easement 
            13 = Ownership Unknown  
            14 = Gap between parcel boundary descriptions 
            15 = Water Body 
            16 = Ditch 
            17 = Walkway 
            98 = Other non-parcel feature 
            99 = Unspecified non-parcel feature 
 
            Anoka:    No data.  
            Hennepin: No data.  
            Scott:    No data.

Entity and Attribute Detailed Citation

Section 6	Distribution Information	Top of full metadata	Top of page
Publisher	The Metropolitan Council and the Counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington
Publication Date	Periodically revised
Contact Person Information	Jessica Deegan Metropolitan Council, on behalf of MetroGIS 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
Distributor's Data Set Identifier	metrogis_regional_parcels_2003
Distribution Liability	See license agreement.
Transfer Format Name	Shapefile
Transfer Format Version Number	ArcGIS: 8x
Transfer Size	Sizes of shape files in MB: Anoka = 91, Carver = 31, Dakota = 156, Hennepin = 258, Ramsey polygons = 142, Ramsey points = 98, Scott = 58, Washington = 88.
Ordering Instructions	LICENSING This is a licensed dataset. The licensing and data acquisition procedures differ depending upon the type of organization requesting the datasets. Qualifying governmental units and academic interests may obtain the dataset without fee directly from MetroGIS. More information about licensing for these organizations can be found at http://www.metrogis.org/data/datasets/parcels/public/index.shtml . All other organizations and individuals must obtain the dataset directly from each county. In most cases a fee is required. More information about licensing and acquisition procedures can be found at http://www.metrogis.org/data/datasets/parcels/private/index.shtml . DOWNLOADING Licensed governmental and academic users may download the parcel dataset using the userID, password and instructions provided with their license approval. The dataset is downloaded from a password protected FTP site. This data is not available on the DataFinder Cafe.
Online Linkage	none available

Section 7	Metadata Reference Information	Top of full metadata	Top of page
Metadata Date	04/20/2004
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
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/20/2004