Link to State of South Dakota GIS Data.

12/06/2024 - Updates to Ellendale, Fargo, Kindred, Lincoln, Mandan, Rugby and Tappen.12/06/2024 - Update to Lincoln and Bismarck Corporate Boundaries based on requests from Lincoln.6/27/2024 - Update to the Valley City and Dickinson Corporate Boundary based on requests from their GIS personal.4/8/2024 - Update to the Valley City Corporate Boundary12/04/2023 - Update to Fargo City Boundary7/23/2023 - Removed Church’s Ferry due to proclamation and notice of dissolution.7/01/2023 - Changes to Binford - Ordinance 51; Lidgerwood - Ordinance 2022-1; Killdeer Golf Course annexation; Bismarck based on current City of Bismarck GIS boundary9/26/2022 - Changes to Steele boundary per Kidder County 911 coordinator.9/23/2022 - Updates to Grand Forks, Mandan and Fargo7/01/2022 - Updates to Killdeer, Mandan and Williston per State Tax Dept changes. 2/14/2022- Updates to Minot -13th ST SE/31st AVE SE, Updates to Elgin, Horace and St. John.11/16/2021 -Updates to Bismarck, Fargo and Killdeer based on city ordinances.7/2/21 – Changes were made to the City of Bismarck, Fargo and Hillsboro to include local taxing jurisdiction boundary changes from the State Tax Commissioner.5/4/21 - Updates were made to the City of Wahpeton due to an annexation.4/29/21 - Updated Minot and Makoti3/5/21 - Updated an annexation to Arnegard that was submitted to the DOT by Mackenzie's County Public Works GIS Coordinator.1/21/21 - Update to Sentinel Butte per Golden Valley 911 Coordinator7/17/20 - Updates to Bismarck, Linton and Stanley6/1/20 - Updates to Killdeer, New Town and Surrey1/17/2020 - Boundary changes have been updated for Bismarck, Bowman Fargo, Garrison, Linton, and New Salem.3/5/19 - The corporate boundary of Surrey has been updated.12/26/18 - The following corporate boundaries have been updated: Bismarck, Lincoln, Grand Forks, Horace, Casselton, Fargo, Oxbow, Tioga and Stanley.6/19/18 - City of Maza is not incorporated based on the 2011-2013 North Dakota Blue book. Removed Maza.5/14/18 - Updated Dickinson, Watford City, Berthold, Minnewauken, and Cavalier.1/31/18 - Updated Dickinson, Mandan, Minot, Tioga, Devils Lake, Belfield, Washburn, Mohall, Minnewauken, Lincoln, Bismarck and Casselton. 10/24/17 - Updated Watford City and Makoti10/16/17 - The following cities have been updated: Jamestown, Milnor, Bismarck, Carrington, Casselton, Mandan, Minot, Stanley, Larimore, Crosby, and Watford City.1/10/17 - The following cities have been updated: Lehr, Grand Forks, Langdon, Drayton, Flasher, Glen Ullin, Watford City, Zap, Lignite, Hankinson, Beach, Underwood, South Heart, Devils Lake, all cities in Ward County, Cavalier, Bismarck, Lincoln, Fargo, West Fargo, Ayr, Briarwood, Casselton, Davenport, Enderlin, Grandin, Horace, and North River.9/19/16 - Updated the following cities: Watford City, Steele, Richardton, Berthold, Carpio, Burlington, Des Lacs, Donnybrook, Douglas, Kenmare, Makoti, Ryder, Sawyer, and Surrey.6/23/16 - Updated cities are as follows: All cities in Pembina, Morton, Richland, and Williams Counties. The cities of Bismarck, West Fargo, Harwood, Oxbow, Beach, Minot, Stanley, Jamestown, Fargo, Dickinson and New Town.9/28/15 - The following cites have had annexation: Stanley, Bottineau, Minot, Casselton, Belfield and Watford City.7/24/15 - Updated Grafton, Stanley, Bismarck, Williston, Horace, Fargo, Grand Forks, Watford City, Turtle Lake, Leeds, Maxbass and Medora1/16/15 - Updated Grafton, Stanley and Bismarck.11/3/2014 - Updated Bismarck, Mandan, Minot, Stanley, and Watford City7/16/14 - Corporate limits updated include: Mandan, Towner, Fargo, West Fargo, Grand Forks, Bismarck, Bowman, Watford City, Stanley, Tioga, Kenmare, Casselton, Minot, Carrington, Kindred, and Killdeer. The corporate limit updates consisted of receiving from the cities, shape files, CADD files, scanned images of annexations or by converting pdf files into images, rectifying them within ArcGIS, then heads-up digitizing. 7/29/13 - updated Stanley, Williston, Minot, and Bismarck.4/30/13 - updated Williston, Hazen, Minot, Dickinson, Valley City, Velva, Rugby, Bismarck, and Lincoln1/28/13 - updated Valley City, Grand Forks, Bismarck, Williston, Jamestown, Harvey, Mohall, Park River, Ray, Rugby, Stanley, Tioga, Mayville and Glenfield10/9/12 - updated Williston and Dickinson6/20/12 - updated Williston via shapefile from city.3/20/12 - updated Bismarck and Minot10/3/2011 - Edited corporate limits for Bottineau, Grand Forks, Bismarck, Grafton, Fargo, West Fargo, Horace, Dickinson, Williston, Valley City and Devils Lake.2/4/11 - Removed urban areas so only corporate boundaries remain. Removed boolean field named URBAN_AREA. Updated corporate limist in Dickinson and cities with Cass county. 6/24/10 - Stanley, Lincoln, Oakes, Hankinson, Enderlin, Ellendale, Linton, Carrington, Minot, and Kulm corportate limits were changed 6/18/09 - Stanley, Wahpeton, Center, Watford City, Williston, Grand Forks, Killdeer, Beulah, Beach, Hazen, Garrison, Washburn, Bismarck and Lincoln corporate limits were changed 3/24/08 - Added Milton, Drayton, and Cavalier Boudaries updated: Park River 1/16/08 - Boundaries updated: Devils Lake, Glen Ullin, Langdon, Minnewaukan, Northwood, Thompson 2/13/07 - Boundaries updated: Amenia, Arthur, Bismarck, Bottineau, Buffalo, Casstleton, Davenport, Dickinson, Enderlin, Gardner, Grand Forks, Grandin, Harvey, Harvey, Hillsboro, Horace, Hunter, Jamestown, Kindred, Mapleton, Mayville, New Rockford, Oxbox, Page, Prairie Rose, Relies Acres, Tappen, Towner City 1/10/06 - Boundaries updated: Wishek, Fargo, Lincoln, Bottineau, Williston, Grand Forks, Granville, Velva, Stanley, urban areas in Fargo, West Fargo, Bismarck and Mandan. Deleted Larson This data came from the NDDOT's Mapping Section. The original data was digitized from hand scribed maps and registered to the 1:24000 USGS PLSS data. It was converted from a projection (NAD 1983 UTM Zone 14N) to a Geographic coordinate system.

The Unpublished Digital Geologic-GIS Map of Theodore Roosevelt National Park and Vicinity, North Dakota is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (thro_geology.gdb), a 10.1 ArcMap (.mxd) map document (thro_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (thro_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (thro_geology_gis_readme.pdf). Please read the thro_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 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. Google Earth software is available for free at: http://www.google.com/earth/index.html. 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). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: North Dakota Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (thro_geology_metadata.txt or thro_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:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 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 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: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 13N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Theodore Roosevelt National Park.

The Unpublished Digital Geologic-GIS Map of the North Unit of Theodore Roosevelt National Park, North Dakota is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (thrn_geology.gdb), a 10.1 ArcMap (.mxd) map document (thrn_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (thro_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (thro_geology_gis_readme.pdf). Please read the thro_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). Presently, a GRI Google Earth KMZ/KML product doesn't exist for this map. 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). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: North Dakota Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (thrn_geology_metadata.txt or thrn_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:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 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 ArcGIS 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: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 13N. The data is within the area of interest of Theodore Roosevelt National Park.

11/22/2024- County-wide road updates were completed in Golden Valley and Billings Counties. Intersecting routes throughout the state were cartographically realigned in preparation of MIRE intersections 6/27/2024 - The data was prepared for HPMS submittal which included updated 2023 AADT values and to keep certain segments consistent with HPMS segments, mainly sample sections and the NHS, values of "BOTH", "NHS" and "SAMPLE" were added to the field HPMS_ROUTE_ID to distinguish these segments from other segments. 3/19/2024 - Miscellaneous updates were done in Dunn County. County wide updates to Grand Forks and Golden Valley counties along with route realignments at intersections throughout the state.12/04/2023 - County wide updates to Walsh, Dunn and Grand Forks Counties and various updates to county/local roads throughout the state including street names in Westhope8/23/2023 - Function Class changes were updated in McLean and Mountrail Counties. Function Class updates also occurred in the cities of Fargo, Valley City, West Fargo and Williston. County-wide updates completed for: Towner, Cavalier, Pembina, Pierce, Benson, Ramsey. 2022 AADTs updated. A road was also removed in Bottineau County at the request off a landowner.5/19/22 - Dunn County contacted the NDDOT with data updates ,Rolette County was updated, and the 2021 AADT's were updated. 2/14/22 - Contacted by the Dunn County Road Dept., updates were made on newly paved road segments. 1/20/2022 - Since the August 2021 update, Morton, Stark, Hettinger, Bowman, Adams, Slope, Grant and Sioux Counties have been updated using 2020 imagery. Surface type has been checked and updated on all functionally classified roads statewide. Function Class changes have been made in the Bismarck/Mandan Metro, Grand Forks County and Burleigh County.6/15/21 - Since the 2019 update, trails and seldom used trails were updated statewide using 2018,and 2019 imagery. Steele, Traill and Griggs Counties have also been updated using 2020 imagery. Surface type has been checked and updated on all functionally classified roads statewide New roads added includes roads in the Fargo, West Fargo, Grand Forks, Jamestown, Bismarck, Mandan, Minot, Dickinson, Watford City and Williston. Ownership on Federal jurisdiction roads were also updated based on an dataset received for FHWA in conjunction with the HPMS submittal. HPMS (Highway Performance Monitoring System) fields were also added in an effort to integrate the roads county data into HPMS and MIRE (Model Inventory Roadway Elements). 9/14/20 - Added the following fields - AADT, AADT_YR, HPMS_MAINTENANCE_OPERATIONS, HPMS_THROUGH_LANES, FUNCTIONAL_CLASS (replaces FUNCTION_CLASS)8/13/19 - The following counties were updated by using a variety of aerial photography: Eddy, Foster and Barnes. Seldom used trails have been added to Barnes, Benson, Billings, Bottineau, and Bowman Counties. Mercer County had (2) 61STAvenues, this has been corrected.12/26/18 - The following counties have had their roads updated by a variety of aerial photography, McHenry, Wells, Kidder, Cass (with aid of Cass county website) and McKenzie (with aid of McKenzie County GIS Coordinator)8/14/18 - Counties updated using 2017 NAIP Imagery are Ward, Mountrail, Burke and Renville counties. Seldom used trails are also being digitized into the dataset. They are being added as counties are being checked, so it will take some time for all seldom used trails to be added statewide. Also since the last update, all local roads that are in the corporate boundaries have been broken at the boundaries so it is easier to query to determine which roads go with each community.5/21/18 - removed CITY_INT_ID column - no longer used because of CITY_FIPS and HPMS_URBAN_CODE attributes. Removed SERVICE_LEVEL field, never used/maintained.4/19/18 - added HPMS_OWNERSHIP and HPMS_FACILITY fields for HPMS submittal1/24/18 - added CITY_FIPS and HPMS_URBAN_CODE attributes/domains. These columns will replace CITY_INT_ID and SOURCE_ID columns (eventually).11/15/17 - Williams, Divide and Bottineau counties have been updated. Great effort has been taken to update attributes and QC null fields. Functional Classified roads in Bismarck and Mandan have been updated as have local roads in Bismarck, Mandan, Williston, Fargo – West Fargo and Minot. 1/25/17 - started to maintain roads in Esri's Road and Highways. The shapes now contain measures in miles along with the associated linear referencing/roads and highways fields. Removed INSET_ASSOC field and added COUNTY_FIPS field.Updates include the counties of Emmons, Logan, McIntosh, Lamoure, Dickey, Ransom, Sargent and Richland. These counties were updated using a combination of the available NAIP aerials, the DES aerials, and by car within the insets. In addition to these updates, the whole county dataset was edited using Data Reviewer checks. The checks ran included unnecessary nodes, non-linear segments, invalid geometry, Duplicate vertices with a tolerance of .5 meters, polyline closes of self, checked for cutbacks using a 15 degree minimum angle, checked for polyline length check using a distance less than 10 meters, checked for multipart lines, inspected dangles with a tolerance of 10 meters, and checked for orphans. All checks were inspected and fixed where appropriate.7/16/14 - updates include: Traill, Barnes, Stutsman, Kidder, Bowman, Slope, Stark, Hettinger, Adams, Grant, Sioux and Morton. These datasets were updated using a combination of the available NAIP aerials, the DES aerials, and by car within the insets.10/22/12 - city streets were updated in Bismarck, Dickinson, Minot and Williston. GIS data from the city of Bismarck was used to update Bismarck, GIS data and 2012 aerial photography was used to update the city of Williston, Minot’s city map and the 2010 aerial photography from Ward County was used to update Minot, and 2011 aerial photography and Dickinson’s "working" city map was used to update Dickinson. The counties updated were Williams, Burke, Bottineau, Mountrail, Ward, Wells, Eddy, Foster, Griggs, Steele, and Cass. At the time of this updated, approximately 50% of Stutsman and 50% of Traill Counties are updated. Williams, Bottineau, Ward, and Mountrail roads were inspected from the air and the 2009 NAIP photos were also used to assist the updates. The roads in Williams County were also recoded to match Williams County naming conventions. Williams County CADD map which is on the Williams county web site was used in updating the road names. In Ward County, the 2010 image from Ward County was used to assist in updating Ward County. The 2010 NAIP photos were used to update Wells, Eddy, Foster, Griggs and Steele Counties. Cass was updated with the assistance of the Cass County GIS layer and the 2011 Cass county imagery. 10/3/2011 - County roads were edited in the cities of Fargo, West Fargo, Horace, Minot, Bismarck, Devils Lake, Grafton, Williston, Valley City, and Dickinson. Also, a part of Ward and Mchenry Counties was edited and the county of Renville has been updated. The business routes through Bismarck and Jamestown were also edited. 5/9/2011 - Updated streets in Bismarck, Mandan, Jamestown, Dickinson, West Fargo ( not quite finished yet), and Valley City. Also, corrected the north - south roads in Township 144N Ranges 49 - 53 E, (in Traill County) 10/5/10 - The original Roads_County data was maintained in two separate ArcInfo coverages and then combined each year and exported to the NDHUB infrastructure. These two coverages have now been combined into one SDE feature class and is being edited within the SDE environment. The following changes have been made to feature class. Deleted all the A1 and A2 Fields so a person would have to hunt back and forth to find a road name. Road names consist of the following fields: RTE_ID, STR_TYP, SUF_DIR, & LAN_DIR. The CMC route numbers were moved from the A1_ prefixed fields to the CMC field to better track the CMC route. Created a County Highway field so we can enter the county road number. It consists of the counties name and number. This is still a work in progress. Created FS_RD_Number and FS_RD_Name fields to better track Forest Service roads. Created Bia-RD_Number and BIA_RD_Name fields to better track Bureau of Indian Affairs roads. The following field changes are used for NDDOT specific processes: Created a service level field which is something that may be used in the future. Currently it contains how Walsh County prioritizes their roads. Created a Through and Connecting Route field so we can so select routes through the towns and cities. This was created exclusively for the county base maps. Created an Inset Associated field. This was created so the information in the rd_misc would come into the county routes. In the future, it is planned to be deleted. 6/18/09 - Updated county routes from aerial observation and photo interpretation using 2003, 2005, 2006 NAIP photos and 2008 photography from Designs camera. Counties updated were Golden Valley, Billings, McKenzie, Dunn, Mercer, Oliver, McLean, Sheridan and Burleigh. City streets were rectified in these counties using the 2003 NAIP photos. Observations were performed by Steven Nelson. 4/17/08 - Updated road surface types in NE. Rolette, Pierce, Benson, Towner, Ramsey, Cavalier, Pembina, Walsh, Grand Forks and Nelson from the 2006 aerial observations by Dewaine Olson 2/13/07 - Updated via 2004 NAIP photos: Barnes, Cass, Eddy, Foster, Griggs, Kidder, Steele, Stutsman, Traill, Wells. Combined Misc Roads and County Roads. Blank fields mean unknown attribute. Use P_STREET_NAME for dynamic labeling. We are also in the process of removing all proposed roads. 12/28/05 - Counties updated: Emmons, Logan, Mcintosh, Lamoure, Dickey, Ransom, Sargent, Richland, Divide, Williams, Burke, Mountrail, Ward, Renville, Bottineau, and Mchenry This data came from the NDDOT's Mapping Section. The original data was digitized from hand scribed maps and registered

Government boundaries of North Dakota, U.S.A. Includes North Dakota counties, cities, tribal lands, PLSS and other administrative boundaries that is provided by data stewards for North Dakota state agencies and commissions.

The Unpublished Digital Geologic-GIS Map of the Roosevelt Creek West Quadrangle, North Dakota is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (rcwe_geology.gdb), a 10.1 ArcMap (.mxd) map document (rcwe_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (thro_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (thro_geology_gis_readme.pdf). Please read the thro_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). Presently, a GRI Google Earth KMZ/KML product doesn't exist for this map. 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). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: North Dakota Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (rcwe_geology_metadata.txt or rcwe_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:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 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 ArcGIS 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: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 13N. The data is within the area of interest of Theodore Roosevelt National Park.

From the Department of Environmental Quality data and maps portal: The Department of Environmental Quality (DEQ) has made many of our records available on-line for self-serve. The quickest and easiest way to find the records you are looking for is to search the databases, maps, and datasets located on this site. If you wish for more specific information related to a site or record please contact the Department for those records.

Originally produced by the Farm Security Administration, these are georeferenced aerial images from Morton County, North Dakota. Historic print images housed at the Mandan, North Dakota ARS Long-Term Agricultural Research facility were digitized, georeferenced, and processed for use in both professional and consumer level GIS applications, or in photo-editing applications. The original images were produced by the Farm Security Administration to monitor government compliance for farm land agreements. Current applications include assessing land use change over time with regard to erosion, land cover, and natural and man-made structures. Not for use in high precision applications. Resources in this dataset:Resource Title: 1938_AZY_3_89. File Name: 1938_AZY_3_89_0.zipResource Description: Contains IIQ, JPG, OVR, XML, AUX, and TIF files processed in ArcMap / ArcGIS that can be used in ArcGIS applications, or in other photo or geospatial applications. Resource Title: 1938 Mosaic Index. File Name: 1938_mosaic_index_1.zipResource Description: This is the index key for the 1938 Mandan aerial images from Morton County, ND. To find the geographic location for each uploaded 1938 image, consult this map. File titles are arranged as follows: Year_Area_Roll_Frame. The mosaic map displays Roll_Frame coordinates to correspond to these images. Contains TIF, OVR, JPG, AUX, IIQ, and XML files. Resource Title: 1938_AZY_5_113. File Name: 1938_AZY_5_113_2.zipResource Description: Contains IIQ, JPG, OVR, XML, AUX, and TIF files processed in ArcMap / ArcGIS.

description:

Maps and other GIS products and related information provided by the North Dakota Department of Transportation

Constraints:
Not to be used for navigation, for informational purposes only. See full disclaimer for more information

Maps and other GIS products and related information provided by the North Dakota Department of Transportation

Constraints:
Not to be used for navigation, for informational purposes only. See full disclaimer for more information

Representation of tax parcel boundaries with associated attributes in Cass County, ND.

Geometry may be duplicated where one-to-many relationships exist, such as condominium units. Mobile homes are represented by 6-digit parcel identification numbers.For more information contact Cass County GIS.For tax parcel information contact the Tax Equalization office.

The Unpublished Digital Geologic-GIS Map of the Hanks Gully Quadrangle, North Dakota is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (hagu_geology.gdb), a 10.1 ArcMap (.mxd) map document (hagu_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (thro_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (thro_geology_gis_readme.pdf). Please read the thro_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). Presently, a GRI Google Earth KMZ/KML product doesn't exist for this map. 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). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: North Dakota Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (hagu_geology_metadata.txt or hagu_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:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 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 ArcGIS 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: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 13N. The data is within the area of interest of Theodore Roosevelt National Park.

Water-related data in North Dakota including river miles, water monitoring sites, rivers, streams, ponds,lakes, aquifers, and watershed boundaries.

6/12/13 - Errors in section attributes were corrected in the PLSS poly layer (primarily in the Sisseton Reservation and along the Red River) and this new section corner layer was generated from the corrected PLSS section polygon layer. This coverage represents the section corners in the US Public Land Survey System for North Dakota. It is derived from the PLSS layer compiled from ND Public Service Commission data by staff of the North Dakota Geological Survey in 1993.When my predecessors at the North Dakota Geological Survey left in 1993, they left little or no documentation as to how they compiled any of their GIS coverages. I took posession of their data early in 1994, and in my experience, this layer is a reasonable representation of the North Dakota PLSS. Bear in mind that it was developed at the 1:24,000 scale, which National Map Standards, (simply stated and generalizing to a certain extent) approximate a plus/minus 40ft accuracy. Having worked extensively with, maintained, and been the steward for this layer over the last 19 years, I know that it has a few areas that need some corrections, however, as a whole, it is a decent product. Currently, I plan to replace this layer with a GCDB based representation, but work on that will only progress once the GCDB is complete for North Dakota.- Rod Bassler, GIS Coordinator, North Dakota State Water Commission, formerly GIS Coordinator for the North Dakota Geological Survey

Geospatial data about North Dakota Parcels. Export to CAD, GIS, PDF, CSV and access via API.

The Digital Geologic-GIS Map of Knife River Indian Villages National Historic Site and Vicinity, North Dakota is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (knri_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 3.X map file (.mapx) file (knri_geology.mapx) and individual Pro 3.X layer (.lyrx) 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 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 readme file (knri_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (knri_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 (knri_geology_metadata_faq.pdf). Please read the knri_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: 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: University of North Dakota, Department of Anthropology and Archeology. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (knri_geology_metadata.txt or knri_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:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 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 Pro, 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).

🇺🇸 미국

The Digital Geologic-GIS Map of Fort Union Trading Post National Historic Site and Vicinity, Montana and North Dakota is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (fous_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 (fous_geology.mapx) and individual Pro layer (.lyrx) 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 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 readme file (fous_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (fous_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 (fous_geology_metadata_faq.pdf). Please read the fous_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: 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: Montana Bureau of Mines and Geology. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (fous_geology_metadata.txt or fous_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:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.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 Pro, 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).

North Dakota Department of Environmental Quality's (NDDEQ)'s geospatial information is available either via this Arcgis online site, or may be downloaded from the ND GIS hub data portal, https://gishubdata.nd.gov/. Please consult the NDDEQ's Open Records Request website for a list of available online resources. Note that by law, there are exemptions limiting the release of some specific information pertaining to well location information by the department. Refer to the Open Records Request web page for more details.

The North Dakota state coverage was created by the North Dakota State Water Commission and is a subset of the ND GIS Hub county dataset.

Constraints:
Not to be used for navigation, for informational purposes only. See full disclaimer for more information.