Web map displaying Wisconsin DNR-produced Digital Elevation Model (DEM) and Hillshade image services, along with their index layer, in formats that are clickable and can be symbolized and filtered. This map can also be used as a starting point to create a new map. To open the web map from DNR's GIS Open Data Portal, click the View Metadata: link to the right of the description, then click Open in Map Viewer.

This data set provides a generalized outline of the 72 counties in Wisconsin. The data is derived from 1:24,000-scale sources.

Wisconsin municipal ward data collected in January 2025 by LTSB that was dissolved into municipal boundaries (cities, towns, and villages). [Attribute Definitions]. This data has been collected in regards to state statute 15(4)(br)1. County clerks will transmit municipal, municipal ward, and county supervisory districts in GIS format to LTSB by January 15th and July 15th* per statute 5.15(4)(br)1: "...no later than January 15 and July 15 of each year*, the county clerk shall transmit to the Legislative Technology Services Bureau a report confirming the boundaries of each municipality, ward, and supervisory district in the county together with a map of the county, in an electronic format approved by the Legislative Technology Services Bureau. Each report shall be current to the nearest January 1 or July 1* preceding the date of the report”. (*with the exception of years ending in “01” where data collection will align closer to typical redistricting timelines of March and October 15)Municipal clerks need to notify the county clerk within 5 days of any boundary change per statute 5.15(4)(b): "Within 5 days after adoption or enactment of an ordinance or resolution under this section or any amendment thereto, the municipal clerk shall transmit one copy of the ordinance or resolution or the amendment to the county clerk of each county in which the municipality is contained, accompanied by the list and map specified in par. (a). Each copy shall identify the name of the municipality and the county or counties in which it is located."Municipal data collected in the January collections will be used by LTSB to update municipal boundaries the U.S. Census Bureau’s TIGER database via the Boundary Annexation Survey (BAS). Counties and municipalities are no longer required to submit boundary changes directly to the Census Bureau. LTSB will submit data to the Census Bureau for the state as a whole.Section 13.96(1)(b) of the Wisconsin Statutes requires LTSB to “upon receipt of municipal boundary information at each reporting interval, reconcile and compile the information received to produce a statewide data base consisting of municipal boundary information for the entire state”.Section 13.96(1)(c) states that LTSB shall “Participate, on behalf of this state, in geographic boundary information programs when offered by the U.S. bureau of the census”.LTSB will publish Municipal Wards, Municipal Boundaries (cities, towns, villages), and County Supervisory Districts to the LTSB GIS Hub website.This data has been collected with the LTSB GeoData Collector.*with the exception of years ending in “01” where data collection will align closer to typical redistricting timelines of March and October 15.

This dataset contains boundaries for the Family Care Geographic Service Regions. Family Care is a Medicaid long-term care program for frail elders, and adults with physical, developmental, or intellectual disabilities. People in the program receive long-term care services to help them live in their own home whenever possible.For more information please visit the Wisconsin Department of Health Services website: https://www.dhs.wisconsin.gov/familycare/index.htm

The Digital Geologic-GIS Map of Saint Croix National Riverway and Vicinity, Minnesota and Wisconsin is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (sacn_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (sacn_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (sacn_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (sacn_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (sacn_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (sacn_geology_metadata_faq.pdf). Please read the sacn_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Minnesota Geological Survey, Wisconsin Geological and Natural History Survey and National Park Service. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (sacn_geology_metadata.txt or sacn_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:250,000 and United States National Map Accuracy Standards features are within (horizontally) 127 meters or 416.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Geospatial data about Grant County, Wisconsin Addresses. Export to CAD, GIS, PDF, CSV and access via API.

This data set is a polygon shapefile representing Public Land Survey System (PLSS) townships. The data are a subset of the Wisconsin DNR's 'Landnet' database, automated from 1:24,000-scale sources.*DNR staff have added an alpha field for the range direction field in this layer called DIR_ALPHA which uses W and E instead of numerical direction codes.

A Groundwater Nitrate Decision Support Tool (GW-NDST) for wells in Wisconsin was developed to assist resource managers with assessing how legacy and possible future nitrate leaching rates, combined with groundwater lag times and potential denitrification, influence nitrate concentrations in wells (Juckem et al. 2024). The GW-NDST relies on several support models, including machine-learning models that require numerous GIS input files. This data release contains all GIS files required to run the GW-NDST and its machine-learning support models. The GIS files are packaged into three ZIP files (WI_County.zip, WT-ML.zip, and WI_Buff1km.zip) which are contained in this data release. Before running the GW-NDST, these ZIP files need to be downloaded and unzipped inside the "data_in/GIS/" subdirectory of the GW-NDST. The GW-NDST can be downloaded from the official software release on GitLab (https://doi.org/10.5066/P13ETB4Q). Further instructions for running the GW-NDST, and for acquiring ...

Geospatial data about Racine County, Wisconsin Parcels. Export to CAD, GIS, PDF, CSV and access via API.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

This data set is intended to be paired with the CBRS Polygons and CBRS Prohibitions data sets to illustrate the stated horizontal accuracy of the boundaries therein. Users should pair this data with the CBRS Polygons or CBRS Prohibitions data and an orthoimage when inspecting areas that are within or in close proximity to the CBRS. Users are advised to contact the Service for an official determination as to whether a particular property or structure that falls either partially or completely within the CBRS Buffer Zone is located within the CBRS. For more information, see the metadata for the CBRS Polygons and CBRS Prohibitions available at https://www.fws.gov/media/digital-coastal-barrier-resources-system-boundaries.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

Geospatial data about La Crosse County, Wisconsin Address Points. Export to CAD, GIS, PDF, CSV and access via API.

Improving the quality of water discharged from agricultural watersheds requires comprehensive and adaptive approaches for planning and implementing conservation practices. These measures will need to consider landscape hydrology, distributions of soil types, land cover, and crop distributions in an integrated manner. The two most consistent challenges to these efforts will be consistency and reliability of data, and the capacity to translate conservation planning from watershed to farm and field scales. The translation of scale is required because, while conservation practices can be planned based on a watershed scale framework, they must be implemented by landowners in specific fields and riparian sites that are under private ownership. To support these goals, it has been necessary to develop planning approaches, high-resolution spatial datasets, and conservation practice assessment tools that will allow the agricultural and conservation communities to characterize and mitigate these challenges. The field boundary dataset represents a spatial framework for assembling and maintaining geospatial data to support conservation planning at the scale where conservation practices are implemented. This field boundaries dataset has been assembled to support field-scale agricultural conservation planning using the USDA/ARS Agricultural Conservation Planning Framework (ACPF). The original data used to create this database are the pre-2008 Farm Bill FSA common land unit (CLU) datasets. A portion of metadata found herein pertains to the USDA FSA CLU. The remaining information has been developed to reflect the repurposing of the data in its aggregated form. It is important to note that all USDA programmatic and ownership information that was associated with the original data have been removed. Beyond that, these data has been extensively edited to reflect crop-specific land use and no longer reflects discrete ownership patterns. Resources in this dataset:Resource Title: Wisconsin Field Boundaries 2019. File Name: WI_ACPF_fieldBoundaries_2019.pdfResource Description: Wisconsin Field Boundaries 2019Resource Title: Wisconsin ACPF Crop History 2010-2019. File Name: WI_ACPFfields_CropHistory2010_2019.pdfResource Description: Wisconsin ACPF Crop History 2010-2019Resource Title: Wisconsin ACPF Land Use 2014-2019. File Name: WI_ACPFfields_LandUse2014_2019.pdfResource Description: Wisconsin ACPF Land Use 2014-2019Resource Title: Agricultural land use by field: Wisconsin 2010-2019. File Name: WI_ACPFfields2019.zipResource Description: This field boundaries dataset has been assembled to support field-scale agricultural conservation planning using the USDA/ARS Agricultural Conservation Planning Framework (ACPF).Resource Software Recommended: ArcGIS,url: https://www.esri.com

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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

This polygon feature class is a representation of Public Land Survey System (PLSS) quarter sections. The data are a subset of the Wisconsin DNR's 'Landnet' database, automated from 1:24,000-scale sources.*DNR staff have added an alpha field for the range direction field in this layer called DIR_ALPHA which uses W and E instead of numerical direction codes.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

This Coastal Barrier Resources System (CBRS) data set, produced by the U.S. Fish and Wildlife Service (Service), contains areas designated as undeveloped coastal barriers in accordance with the Coastal Barrier Resources Act (CBRA), 16 U.S.C. 3501 et seq., as amended. The boundaries used to create the polygons herein were compiled from the official John H. Chafee Coastal Barrier Resources System CBRS maps, which are accessible at the Service’s Headquarters office or https://www.fws.gov/program/coastal-barrier-resources-act/maps-and-data. These digital polygons are only representations of the CBRS boundaries shown on the official CBRS maps and are not to be considered authoritative. The Service is not responsible for any misuse or misinterpretation of this digital data set, including use of the data to determine eligibility for federal financial assistance such as federal flood insurance. As maps are revised, this data set will be updated with the new boundaries. CBRS boundaries viewed using the CBRS Mapper or the shapefile are subject to misrepresentations beyond the Service’s control, including misalignments of the boundaries with third party base layers and mis-projections of spatial data. The official CBRS map is the controlling document and should be consulted for all official determinations. Official determinations are recommended for all properties that are in close proximity (within 20 feet) of a CBRS boundary. For an official determination of whether or not an area or specific property is located within the CBRS, please follow the procedures found at https://www.fws.gov/service/coastal-barrier-resources-system-property-documentation. For any questions regarding the CBRS, please contact your local Service field office or email CBRA@fws.gov. Contact information for Service field offices can be found at https://www.fws.gov/our-facilities.Data Set Contact: U.S. Fish and Wildlife Service Natural Resource Program Center, GIS Team Lead, richard_easterbrook@fws.gov

This dataset contains locations and attributes of rural health clinics licensed by the state of Wisconsin. The data is used for planning, management and analysis by Wisconsin Department of Health Services staff and by other government agencies.For more information please visit the Wisconsin Department of Health Services website: https://www.dhs.wisconsin.gov/regulations/rhc/introduction.htm