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.
Bluffs within Scott County.
Geospatial data about Scott County, Minnesota Water Bodies. Export to CAD, GIS, PDF, CSV and access via API.
Geospatial data about Scott County, Minnesota Zoning. Export to CAD, GIS, PDF, CSV and access via API.
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.
Driveways within Scott County. This planimetric data was collected in 2003.
This dataset contains the address points within Scott County, in MetroGIS format. The attributes of the data allow for accurate geocoding.
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 Driveways. Export to CAD, GIS, PDF, CSV and access via API.
Geospatial data about Scott County, Minnesota Address Points. Export to CAD, GIS, PDF, CSV and access via API.
This dataset contains the agricultural ditches within Scott County.
Geospatial data about Scott County, Minnesota Parcels. Export to CAD, GIS, PDF, CSV and access via API.
Park & Ride Lots within Scott County. For more information, visit the SmarkLink Transit website.
Railroads within Scott County. This planimetric data was collected in 2003.
Points of Interest
Geospatial data about Scott County, Minnesota Buildings. Export to CAD, GIS, PDF, CSV and access via API.
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 44 suppliers that have opted-in to share their data openly as of the publication date of this dataset: Aitkin County, Anoka County, Benton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Cook County, Dakota County, Douglas County, Fillmore County, Grant County, Hennepin County, Houston County, Isanti County, Itasca County, Koochinching County, Lac qui Parle County, Lake 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, Ramsey County, Renville County, Rock County, Saint Louis County, Scott County, Sherburne County, Stearns, Stevens County, Waseca County, Washington County, Wright County, and Yellow Medicine 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. Transfer NG9-1-1 data from the DPS 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 = 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 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 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
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.