This dataset was created by a joint collaborative project involving the technical and managerial GIS staff from the ten Metropolitan Counties of the Twin Cities in Minnesota (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne and Washington), the Metropolitan Emergency Services Board (MESB), MetroGIS and the Metropolitan Council. Core needs this dataset are intended to satisfy include:

- Vehicular routing;
- Address geocoding;
- Next Generation 911 call routing and location validation;
- Emergency services dispatching;
- Linear referencing uses;
- Cartographic representation of road features;

For specific questions regarding centerline alignments or attributes, please contact the county below
Anoka: https://www.anokacounty.us/315/GIS
Carver: gis@co.carver.mn.us
Chisago: gisservices@chisagocountymn.gov
Dakota: gis@co.dakota.mn.us
Hennepin: gis.info@hennepin.us
Isanti: Nate.Kirkwold@co.isanti.mn.us
Ramsey: RCGISMetaData@co.ramsey.mn.us
Sherburne: gis@co.sherburne.mn.us
Scott: gis@co.scott.mn.us
Washington: gis@co.washington.mn.us

This is a tiled image layer of 2 foot contours in Anoka County. The contour data was created by the State of MN and was derived from LiDAR data collected by the state in 2011.

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees.

This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate systems from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties. Summary attribute information is in the Attributes Overview. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes document.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points 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.

This is a MetroGIS Regionally Endorsed dataset.

Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

Anoka = http://www.anokacounty.us/315/GIS
Caver = http://www.co.carver.mn.us/GIS
Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
Hennepin = http://www.hennepin.us/gisopendata
Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
Scott = http://opendata.gis.co.scott.mn.us/
Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

This data set contains polygons representing the state protected water basins in Anoka County. This data set was created by the MN DNR and represents the water and wetland basins that are protected by state regulations.

This dataset is a compilation of address point data from metro area address authorities, which are predominantly cities. The dataset is intended to contain a point location and the official address (as defined by the address authority) for all occupiable units and any other official addresses within the jurisdictional boundary of each address authority. A number of other attributes are available in the dataset, but may not be populated by some address authorities.

Metro area counties are playing a coordinative role to work with cities to create, maintain and aggregate address points. Currently this dataset contains points for all Seven Metropolitan Counties as well as participating bordering counties.

Some jurisdictions in this dataset contain parcel points and not complete address points. See Completeness in Section 2 of this metadata for more information.

The data used in this aggregated dataset are compliant with the Address Point Data Standard for Minnesota. http://www.mngeo.state.mn.us/committee/standards/address/address_standard.html

For specific questions regarding centerline alignments or attributes, please contact the county below Anoka: https://www.anokacounty.us/315/GIS Carver: gis@co.carver.mn.us Chisago: gis@co.chisago.mn.us Dakota: gis@co.dakota.mn.us Hennepin: gis.info@hennepin.us Isanti: amber.dalbec@co.isanti.mn.us Ramsey: RCGISMetaData@co.ramsey.mn.us Scott: gis@co.scott.mn.us Sherburne: gis@co.sherburne.mn.us Washington: gis@co.washington.mn.usMinnesota Geospatial Commons ItemInternal GIS Data Catalog Item

This dataset was created by a joint collaborative project involving the technical and managerial GIS staff from the ten Metropolitan Counties (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne and Washington), the Metropolitan Emergency Services Board, MetroGIS and the Metropolitan Council. Core needs this dataset are intended to satisfy include:- Vehicular routing;- Address geocoding;- Next Generation 911 call routing and location validation;- Emergency services dispatching;- Linear referencing uses;- Cartographic representation of road features;For specific questions regarding centerline alignments or attributes, please contact the county belowAnoka: https://www.anokacounty.us/315/GISCarver: gis@co.carver.mn.usChisago: gis@co.chisago.mn.usDakota: gis@co.dakota.mn.usHennepin: gis.info@hennepin.usIsanti: Nate.Kirkwold@co.isanti.mn.usRamsey: RCGISMetaData@co.ramsey.mn.usSherburne: gis@co.sherburne.mn.usScott: gis@co.scott.mn.usWashington: surveyor@co.washington.mn.us

This dataset is a compilation of tax parcel polygon and point 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. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points 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, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points 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.

Polygon and point counts for each county are as follows (based on the January 2012 dataset unless otherwise noted):

polygons / points
Anoka - 129385 / 129385
Carver - 38699 / 38699
Dakota - 136792 / 150666
Hennepin - 424702 / 424702
Ramsey - 148978 / 166846
Scott - 55227 / 55227
Washington - 106841 / 106841

This is a MetroGIS Regionally Endorsed dataset.

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.

A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2011 document.

Additional information may be available in the individual metadata for each county at the links listed below. Also, 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.

Anoka = http://www.anokacounty.us/315/GIS

Caver = http://www.co.carver.mn.us/GIS

Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx

Hennepin: http://www.hennepin.us/gisopendata

Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 59 counties that have opted-in as of the publication date of this dataset: Aitkin County, Anoka County, Becker County, Benton County, Big Stone County, Carlton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Clearwater County, Cook County, Crow Wing County, Dakota County, Douglas County, Fillmore County, Grant County, Hennepin County, Houston County, Isanti County, Itasca County, Jackson County, Koochiching County, Lac qui Parle County, Lake County, Lake of the Woods County, Lyon County, Marshall County, McLeod County, Mille Lacs County, Morrison County, Mower County, Murray County, Norman County, Olmsted County, Otter Tail County, Pennington County, Pipestone County, Polk County, Pope County, Ramsey County, Red Lake County, Renville County, Rice County, Scott County, Sherburne County, St. Louis County, Stearns County, Steele County, Stevens County, Traverse County, Wabasha County, Waseca County, Washington County, Wilkin County, Winona County, Wright County, and Yellow Medicine County.

If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.

County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.

This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.

There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.

The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.

DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees. This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate system from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties. NOTICE: The standard set of attributes changed to the MN Parcel Data Transfer Standard on 1/1/2019. https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html See section 5 of the metadata for an attribute summary. Detailed information about the attributes can be found in the Metro Regional Parcel Attributes document. The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated. The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area. In many places a one-to-one relationship does not exist between these parcel polygons or points 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. This is a MetroGIS Regionally Endorsed dataset. Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county. Anoka = http://www.anokacounty.us/315/GIS Caver = http://www.co.carver.mn.us/GIS Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx Hennepin = http://www.hennepin.us/gisopendata Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data Scott = http://opendata.gis.co.scott.mn.us/ Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

This dataset is a compilation of tax parcel polygon and point 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. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points 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, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points 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.

Polygon and point counts for each county are as follows (based on the July 2010 dataset unless otherwise noted):

polygons / points
Anoka - 129271 / 129271
Carver - 38205 / 38205
Dakota - 136067 / 150436
Hennepin - 424182 / 424182
Ramsey - 149101 / 168152
Scott - 55213 / 55213
Washington - 98933 / 104100 (October 2009)


This is a MetroGIS Regionally Endorsed dataset.

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.

A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2010 document.

Additional information may be available in the individual metadata for each county at the links listed below. Also, 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.

Anoka = http://www.anokacounty.us/315/GIS

Caver = http://www.co.carver.mn.us/GIS

Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx

Hennepin: http://www.hennepin.us/gisopendata

Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

This dataset is a compilation of address point data from metro area address authorities, which are predominantly cities. The dataset is intended to contain a point location and the official address (as defined by the address authority) for all occupiable units and any other official addresses within the jurisdictional boundary of each address authority. A number of other attributes are available in the dataset, but may not be populated by some address authorities.

Metro area counties are playing a coordinative role to work with cities to create, maintain and aggregate address points. Currently this dataset contains points for all Seven Metropolitan Counties as well as participating bordering counties.

Some jurisdictions in this dataset contain parcel points and not complete address points. See Completeness in Section 2 of this metadata for more information.

The data used in this aggregated dataset are compliant with the Address Point Data Standard for Minnesota.
http://www.mngeo.state.mn.us/committee/standards/address/address_standard.html


For specific questions regarding centerline alignments or attributes, please contact the county below
Anoka: https://www.anokacounty.us/315/GIS
Carver: gis@co.carver.mn.us
Chisago: gisservices@chisagocountymn.gov
Dakota: gis@co.dakota.mn.us
Hennepin: gis.info@hennepin.us
Isanti: Nate.Kirkwold@co.isanti.mn.us
Ramsey: RCGISMetaData@co.ramsey.mn.us
Scott: gis@co.scott.mn.us
Sherburne: gis@co.sherburne.mn.us
Washington: gis@co.washington.mn.us

This dataset is a compilation of tax parcel polygon and point 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. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties will polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points 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. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points 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.

Polygon and point counts for each county are as follows (based on the January, 2007 dataset):

Anoka = 129,392 polygons, 129,392 points
Carver = 37,021 polygons, 37,021 points
Dakota = 135,586 polygons, 148,952 points
Hennepin = 358,064 polygons, 419,736 points
Ramsey = 148,967 polygons, 166,280 points
Scott = 54,741 polygons, 54,741 points
Washington = 97,922 polygons, 102,309 points

This is a MetroGIS Regionally Endorsed dataset.

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.

A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2006 document.

Additional information may be available in the individual metadata for each county at the links listed below. Also, 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.

Anoka = http://www.anokacounty.us/315/GIS

Caver = http://www.co.carver.mn.us/GIS

Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx

Hennepin: http://www.hennepin.us/gisopendata

Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

A County Geologic Atlas (CGA) project is a study of a county's geology, and its mineral and ground-water resources. The information collected during the project is used to develop maps, data-base files, and reports. This same information is also produced as digital files. The map information is formatted as geographic information system (GIS) files with associated data bases. The maps and reports are also reproduced as portable document files (PDFs) that can be opened on virtually any computer using the free Acrobat Reader from Adobe.com. All of the digital files for the CGA's can be downloaded from the University of Minnesota Digital Conservancy. The majority of the files can also be viewed and queried through the use of this Story Map.Atlas information is commonly used in planning and environmental protection programs, as an educational resource, and by industries involved in water and mineral resources. It represents a comprehensive, detailed compilation of geologic data and interpretations within a county. The distribution and character of geologic materials determine how and where water enters the earth, and where it is stored in aquifers that can supply our needs. Geologic maps are a key element in delineating those flow paths and in relating land use to water quality. The atlas also provides a framework and terminology to support more detailed, site-specific studies. The records of water wells drilled in the area are an important source of data for constructing the maps and for understanding the distribution and use of ground water in the county. A data base of the information from those wells is one of the atlas products, and it can be queried with the GIS files to yield valuable insights for managing the ground-water resource.The atlas is also useful to non-professionals who simply wish to learn more about the geology of the county. It is a one-stop, comprehensive collection of information in a variety of forms and styles that should be useful to anyone with an interest in earth science or the county.The geologic data and maps are produced and distributed by the Minnesota Geological Survey (MGS) as Part A of an Atlas. The Minnesota Department of Natural Resources follows with an investigation of the quantity, quality, and pollution sensitivity of ground water. Their products are distributed as Part B of the atlas, at a later date. If necessary, a report with additional information that was not possible to include on the limited space of the printed maps is produced by MGS as Part C of, or included as a supplement to, an atlas. The Atlas CD or DVD, which is available online at the Digital Conservancy, includes all the atlas products developed by the Minnesota Geological Survey.

This dataset is a compilation of tax parcel polygon and point 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. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points 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, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points 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.

Polygon and point counts for each county are as follows (Updated annually, current as of 1/08/2016):

polygons / points
Anoka - 131121 / 131121
Carver - 40510 / 40509
Dakota - 140770 / 154109
Hennepin - 429241 / 429241
Ramsey - 154512 / 166225
Scott - 56219 / 56219
Washington - 106045 / 106045

This is a MetroGIS Regionally Endorsed dataset.

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.

A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2015 document.

Additional information may be available in the individual metadata for each county at the links listed below. Also, 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.

Anoka = http://www.anokacounty.us/315/GIS

Caver = http://www.co.carver.mn.us/GIS

Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx

Hennepin: http://www.hennepin.us/gisopendata

Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

NCompass Technologies, under contract with Metropolitan Council, created a 2010 Census Bureau block polygon dataset for the Twin Cities Metropolitan Area (Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington Counties). This dataset is coincident with and developed using the NCT Street Centerline and Landmarks databases where 2010 block boundaries fall on those features. For those block boundaries that are defined by features not included in NCT databases, NCT used other digital resources to generate these boundaries, such as orthophotography or additional features from city and county GIS databases. NCT used it's best judgement to digitize block boundaries when the block boundaries followed nonvisible features or street extensions. Polygon centroid points were also generated by the Metropolitan Council for blocks, block groups and tracts (Census2010RealignBlockGroupPoints, Census2010RealignBlockPoints, Census2010RealignTractPoints).

This dataset records modifications made to the MN address point data, capturing both attribute and geometry changes. Each modification, whether it involves an attribute or geometry change, is represented by a separate row/feature in the feature class. In cases where multiple attribute changes occur, each change is documented with its own entry.

- Address points
- Address geocoding;
- Next Generation 911 call routing and location validation;
- Emergency services dispatching;

For specific questions regarding centerline alignments or attributes, please contact the county below
Anoka: https://www.anokacounty.us/315/GIS
Carver: gis@co.carver.mn.us
Chisago: gis@co.chisago.mn.us
Dakota: gis@co.dakota.mn.us
Hennepin: gis.info@hennepin.us
Isanti: Nate.Kirkwold@co.isanti.mn.us
Ramsey: RCGISMetaData@co.ramsey.mn.us
Sherburne: gis@co.sherburne.mn.us
Scott: gis@co.scott.mn.us
Washington: surveyor@co.washington.mn.us

This dataset is a compilation of address point data from Minnesota suppliers that have opted-in for their address point data to be included in this dataset.

It includes the following 42 suppliers (51 counties) that have opted-in to share their data openly as of the publication date of this dataset: Metropolitan Emergency Services Board (10 county), Aitkin County, Becker County, Benton County, Big Stone County, Carlton County, Cass County, Chippewa County, Clay County, Cook County, Crow Wing County, Douglas County, Fillmore County, Grant County, Houston County, Itasca County, Jackson County, Koochiching County, Lac qui Parle County, Lake County, Lake of the Woods County, Le Sueur County, Lyon County, Marshall County, McLeod County, Morrison County, Mower County, Murray County , Otter Tail County, Pipestone County, Polk County, Pope County, Renville County, Rock County, Saint Louis County, Stearns County, Stevens County, Wabasha County, Waseca County, Winona County, Wright County, Yellow Medicine County

Metropolitan Emergency Services Board counties: Anoka County, Carver County, Chisago County, Dakota County, Hennepin County, Isanti County, Ramsey County, Scott County, Sherburne County, Washington County

The two sources of address point data are the Minnesota Next Generation 9-1-1 (NG9-1-1) Program, in collaboration with local data suppliers, and the MetroGIS Metro Address Points Dataset which is on the Minnesota Geospatial Commons:

The Minnesota NG9-1-1 Program enterprise database provides the data outside of the Metro Region which is provide by the suppliers. The data have been aggregated into a single dataset which implements the MN NG9-1-1 GIS Data Model (https://ng911gis-minnesota.hub.arcgis.com/documents/79beb1f9bde84e84a0fa9b74950f7589/about ).

Only data which have meet the requirements for supporting NG9-1-1 are in the statewide aggregate GIS data. MnGeo extracts the available data, applies domain translations, and transforms it to UTM Zone 15 to comply with the GAC Address Point attribute schema: https://www.mngeo.state.mn.us/committee/address/address_standard.html.

The MetroGIS Metro Address Points Dataset was created by a joint collaborative project involving the technical and managerial GIS staff from the ten Metropolitan Counties (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne, and Washington), the Metropolitan Emergency Services Board, MetroGIS and the Metropolitan Council. The data are pulled in from the Minnesota Geospatial Commons: https://gisdata.mn.gov/dataset/us-mn-state-metrogis-loc-address-points

‘Supplier’ is a term used throughout this document. A supplier will typically be a county, but it could also be a public safety answering point (PSAP), region, or tribal nation. The supplier is the agency which provides the individual datasets for the aggregated dataset. The loc_addresses_open_metadata feature layer will contain the geometry/shape of the supplier boundaries, supplier name, supplier type, and feature count.

Aggregation Process:
1. Download address location data from the NG9-1-1 Enterprise database.
2. Download the latest data from the Geospatial Commons for MetroGIS.
3. Extract, Translate, and Load (ETL) the data to the GAC Address Point Standard schema.
4. Combine NG9-1-1 data with MetroGIS data.
5. Filter the data for the Opt-In suppliers

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees.

This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate system from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

NOTICE: The standard set of attributes changed to the MN Parcel Data Transfer Standard on 1/1/2019.
https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

See section 5 of the metadata for an attribute summary.

Detailed information about the attributes can be found in the Metro Regional Parcel Attributes document.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points 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.

This is a MetroGIS Regionally Endorsed dataset.

Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

Anoka = http://www.anokacounty.us/315/GIS
Caver = http://www.co.carver.mn.us/GIS
Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
Hennepin = http://www.hennepin.us/gisopendata
Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
Scott = http://opendata.gis.co.scott.mn.us/
Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees. This also includes a combined layer of all points of the 7 counties.

This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate system from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

NOTICE: The standard set of attributes changed to the MN Parcel Data Transfer Standard on 1/1/2019.
https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

See section 5 of the metadata for an attribute summary.

Detailed information about the attributes can be found in the Metro Regional Parcel Attributes document.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points 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.

This is a MetroGIS Regionally Endorsed dataset.

Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

Anoka = http://www.anokacounty.us/315/GIS
Caver = http://www.co.carver.mn.us/GIS
Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
Hennepin = https://gis-hennepin.hub.arcgis.com/pages/open-data
Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
Scott = http://opendata.gis.co.scott.mn.us/
Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

This dataset logs the modifications of the MN road centerline data, adopting the GAC standard. It tracks both attribute and geometry changes. Each attribute and geometry change has one row/feature in the feature class. For example, if multiple attributes changes, each change would have its own entry/row/feature segment to represent that modification.

Road Centerline abstract:
This dataset was created by a joint collaborative project involving the technical and managerial GIS staff from the ten Metropolitan Counties (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne and Washington), the Metropolitan Emergency Services Board, MetroGIS and the Metropolitan Council. Core needs this dataset are intended to satisfy include:

- Vehicular routing;
- Address geocoding;
- Next Generation 911 call routing and location validation;
- Emergency services dispatching;
- Linear referencing uses;
- Cartographic representation of road features;

For specific questions regarding centerline alignments or attributes, please contact the county below
Anoka: https://www.anokacounty.us/315/GIS
Carver: gis@co.carver.mn.us
Chisago: gis@co.chisago.mn.us
Dakota: gis@co.dakota.mn.us
Hennepin: gis.info@hennepin.us
Isanti: Nate.Kirkwold@co.isanti.mn.us
Ramsey: RCGISMetaData@co.ramsey.mn.us
Sherburne: gis@co.sherburne.mn.us
Scott: gis@co.scott.mn.us
Washington: surveyor@co.washington.mn.us