Open Data source for places and boundaries for Pennington County, SD region.

This data set contains the latest available version of the boundary line for Pennington County, South Dakota, based on legal property descriptions. The areas and boundaries depicted were created primarily from aerial mapping methods and do not represent a legal survey of the land.

This data set was developed to provide a current map of the Pennington County boundary for general use within the Pennington County - Rapid City GIS. View-only copy for the Pennington County Public Safety Hub.

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.

Open Data source for environment data for Pennington County, SD.

Topography layers for Pennington County, South Dakota

Open Data source for places and boundaries for Pennington County, SD region.

This data set was created as part of the Black Hills Hydrology Study (BHHS). The BHHS is a long-term investigation that was initiated in 1990 as a cooperative effort between the U.S. Geological Survey (USGS), the South Dakota Department of Environment and Natural Resources (DENR), and the West Dakota Water Development District. West Dakota represents various local and county cooperators. The purpose of the study is to assess the quantity, quality, and distribution of surface and ground water in the Black Hills area of western South Dakota (Driscoll, 1992). The study area includes parts of Butte, Custer, Fall River, Lawrence, Meade, and Pennington counties in South Dakota.

This dataset describes wells completed in the Madison Limestone that were used to create a potentiometric surface for the Madison aquifer.

This data set contains the latest available version of the area within the city limits for Quinn, South Dakota, based on legal property descriptions. The areas and boundaries depicted were created primarily from aerial mapping methods and do not represent a legal survey of the land.

This feature class contains a map of existing railroads within Pennington County, South Dakota. It was developed by heads up digitizing of orthophotos.

This data set contains the latest available version of the area within the city limits for Wall, South Dakota, based on legal property descriptions. The areas and boundaries depicted were created primarily from aerial mapping methods and do not represent a legal survey of the land.

Topography layers for Pennington County, South Dakota

This data set contains the latest available version of the area within the city limits for Keystone, South Dakota, based on legal property descriptions. The areas and boundaries depicted were created primarily from aerial mapping methods and do not represent a legal survey of the land.

Open Source data for National Flood Hazard Layer (NFHL) for Pennington County, SD region.

This data set contains the latest available version of the area within the city limits for Hill City, South Dakota, based on legal property descriptions. The areas and boundaries depicted were created primarily from aerial mapping methods and do not represent a legal survey of the land.

Open Source data for National Flood Hazard Layer (NFHL) for Pennington County, SD region.

Thie feature class contains a map of all existing roads within the platted public right of way. Additionally, it contains a number of roads on private land and a select number of roads maintained by the U.S. Forest Service in both the Black Hills National Forest and the Bufallo Gap National Grasslands. A limited number of private driveways have also been included, mainly to show access routes for emergency vehicles

Orthos2021

View-only copy of current road closures due to unplanned events in Pennington County, SD. Data is featured in the PennCo Public Safety Hub.

SDCL 11-6-26 provides for a three mile jurisdiction for approving subdivision plats around cities. This map layers shows the three mile buffer around New Underwood. It is updated when annexations to New Underwood occur.