9 datasets found
  1. a

    Parcels

    • gis-anokacounty.opendata.arcgis.com
    • gisbackup-anokacounty.opendata.arcgis.com
    • +1more
    Updated Mar 7, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    JohnSlusarczyk (2017). Parcels [Dataset]. https://gis-anokacounty.opendata.arcgis.com/datasets/f17da178a02c4867916c6c685a5b037c
    Explore at:
    Dataset updated
    Mar 7, 2017
    Dataset authored and provided by
    JohnSlusarczyk
    Area covered
    Description

    This data set contains polygons representing the parcel boundaries in Anoka County. The parcel lines are initially drawn by the Anoka County Surveyor's Office using coordinate geometry. The parcel lines are then converted to polygons and added to the GIS parcel basemap where there are given attributes. Parcels are split and merged based on PIN number. Right-of-way (ROW) polygons are removed from the data set so the road right-of-ways are open spaces.

  2. M

    Parcels, Compiled from Opt-In Open Data Counties, Minnesota

    • gisdata.mn.gov
    fgdb, gpkg, html +2
    Updated Nov 7, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Geospatial Information Office (2025). Parcels, Compiled from Opt-In Open Data Counties, Minnesota [Dataset]. https://gisdata.mn.gov/dataset/plan-parcels-open
    Explore at:
    html, gpkg, fgdb, webapp, jpegAvailable download formats
    Dataset updated
    Nov 7, 2025
    Dataset provided by
    Geospatial Information Office
    Area covered
    Minnesota
    Description

    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.

  3. w

    MetroGIS Regional Parcel Dataset (Year End 2011)

    • data.wu.ac.at
    • gisdata.mn.gov
    fgdb, gpkg, html +2
    Updated Feb 21, 2016
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MetroGIS (2016). MetroGIS Regional Parcel Dataset (Year End 2011) [Dataset]. https://data.wu.ac.at/odso/gisdata_mn_gov/MGEyMzc3NzQtZmFkMy00ZDVjLTg1ODEtZmFjOGQyMmY5YzFh
    Explore at:
    gpkg, html, fgdb, shp, jpegAvailable download formats
    Dataset updated
    Feb 21, 2016
    Dataset provided by
    MetroGIS
    Area covered
    914bd5d04066b7a591536611c3295aa930b7a54f
    Description

    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

  4. M

    MetroGIS Regional Parcel Dataset (Year End 2015)

    • gisdata.mn.gov
    ags_mapserver, fgdb +4
    Updated Mar 22, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MetroGIS (2024). MetroGIS Regional Parcel Dataset (Year End 2015) [Dataset]. https://gisdata.mn.gov/dataset/us-mn-state-metrogis-plan-regonal-parcels-2015
    Explore at:
    jpeg, fgdb, gpkg, html, shp, ags_mapserverAvailable download formats
    Dataset updated
    Mar 22, 2024
    Dataset provided by
    MetroGIS
    Description

    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

  5. M

    MetroGIS Regional Parcel Dataset (Year End 2010)

    • gisdata.mn.gov
    • data.wu.ac.at
    ags_mapserver, fgdb +4
    Updated Mar 29, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MetroGIS (2024). MetroGIS Regional Parcel Dataset (Year End 2010) [Dataset]. https://gisdata.mn.gov/dataset/us-mn-state-metrogis-plan-regonal-parcels-2010
    Explore at:
    html, shp, gpkg, fgdb, jpeg, ags_mapserverAvailable download formats
    Dataset updated
    Mar 29, 2024
    Dataset provided by
    MetroGIS
    Description

    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

  6. w

    MetroGIS Regional Parcel Dataset - (Year End 2016)

    • data.wu.ac.at
    • gisdata.mn.gov
    fgdb, gpkg, html +2
    Updated Feb 10, 2017
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MetroGIS (2017). MetroGIS Regional Parcel Dataset - (Year End 2016) [Dataset]. https://data.wu.ac.at/schema/gisdata_mn_gov/ZDUyYTYyZTgtYTJmMC00N2Y2LTliYmMtNjlhOTlhMDA0ODU1
    Explore at:
    gpkg, fgdb, jpeg, html, shpAvailable download formats
    Dataset updated
    Feb 10, 2017
    Dataset provided by
    MetroGIS
    Area covered
    56f8c880dafa11d0abb73f4a29432f6fd67ed681
    Description

    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.

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

    polygons / points
    Anoka - 131708 / 131708
    Carver - 41204 / 41203
    Dakota - 142121 / 154945
    Hennepin - 430449 / 430449
    Ramsey - 158207 / 166343
    Scott - 56533 / 56533
    Washington - 106849 / 106849

    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://www.scottcountymn.gov/1183/GIS-Data-and-Maps
    Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

  7. M

    MetroGIS Regional Parcel Dataset (Year End 2006)

    • gisdata.mn.gov
    • data.wu.ac.at
    ags_mapserver, fgdb +4
    Updated Apr 4, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MetroGIS (2024). MetroGIS Regional Parcel Dataset (Year End 2006) [Dataset]. https://gisdata.mn.gov/dataset/us-mn-state-metrogis-plan-regonal-parcels-2006
    Explore at:
    gpkg, shp, ags_mapserver, fgdb, html, jpegAvailable download formats
    Dataset updated
    Apr 4, 2024
    Dataset provided by
    MetroGIS
    Description

    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

  8. a

    Section Corners

    • gis-anokacounty.opendata.arcgis.com
    • hub.arcgis.com
    Updated Mar 8, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    JohnSlusarczyk (2017). Section Corners [Dataset]. https://gis-anokacounty.opendata.arcgis.com/datasets/a2089bc48e36443cb90dcf6482528dc1_1
    Explore at:
    Dataset updated
    Mar 8, 2017
    Dataset authored and provided by
    JohnSlusarczyk
    Area covered
    Description

    This data set contains points representing section corner monuments throughout Anoka County. The monument locations are maintained on an ongoing basis by the Anoka County Surveyors office.

  9. a

    County Geologic Atlas - Anoka Story Map

    • mngs-umn.opendata.arcgis.com
    Updated Dec 12, 2016
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    University of Minnesota (2016). County Geologic Atlas - Anoka Story Map [Dataset]. https://mngs-umn.opendata.arcgis.com/datasets/county-geologic-atlas-anoka-story-map
    Explore at:
    Dataset updated
    Dec 12, 2016
    Dataset authored and provided by
    University of Minnesota
    Area covered
    Description

    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.

  10. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
JohnSlusarczyk (2017). Parcels [Dataset]. https://gis-anokacounty.opendata.arcgis.com/datasets/f17da178a02c4867916c6c685a5b037c

Parcels

Explore at:
Dataset updated
Mar 7, 2017
Dataset authored and provided by
JohnSlusarczyk
Area covered
Description

This data set contains polygons representing the parcel boundaries in Anoka County. The parcel lines are initially drawn by the Anoka County Surveyor's Office using coordinate geometry. The parcel lines are then converted to polygons and added to the GIS parcel basemap where there are given attributes. Parcels are split and merged based on PIN number. Right-of-way (ROW) polygons are removed from the data set so the road right-of-ways are open spaces.

Search
Clear search
Close search
Google apps
Main menu