Scott County Parcels represent property tax boundaries and were created, and are maintained, by the Survey department. The tax boundaries are joined to the Assessor's CAMA data using the PID field providing field attributes for each property. For a list of field descriptions, click here.

This dataset contains the address points within Scott County, in MetroGIS format. The attributes of the data allow for accurate geocoding.

Points of Interest

This dataset contains the agricultural ditches within Scott County.

Bluffs within Scott County.

This dataset contains Orderly Annexation Areas within Scott County. The Orderly Annexation Area boundaries reflect areas mapped in annexation agreements between adjacent townships and cities.

Railways within Scott County. This planimetric dataset was collected using Scott County 2020 3-inch imagery. Vendor: Eastview Geospatial. Projection: NAD 1983 HARN Adj MN Scott (US Feet).

Geospatial data about Scott County, Minnesota Address Points. Export to CAD, GIS, PDF, CSV and access via API.

Park & Ride Lots within Scott County. For more information, visit the SmarkLink Transit website.

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 = 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 is a link to the MNTopo website, which allows users to view and download high resolution elevation contours within the state of Minnesota.

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 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 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 2009 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 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: gis@co.washington.mn.us

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 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

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 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 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

Hydric Soils in Scott County Minnesota.