This data set contains small-scale base GIS data layers compiled by the National Park Service Servicewide Inventory and Monitoring Program and Water Resources Division for use in a Baseline Water Quality Data Inventory and Analysis Report that was prepared for the park. The report presents the results of surface water quality data retrievals for the park from six of the United States Environmental Protection Agency's (EPA) national databases: (1) Storage and Retrieval (STORET) water quality database management system; (2) River Reach File (RF3) Hydrography; (3) Industrial Facilities Discharges; (4) Drinking Water Supplies; (5) Water Gages; and (6) Water Impoundments. The small-scale GIS data layers were used to prepare the maps included in the report that depict the locations of water quality monitoring stations, industrial discharges, drinking intakes, water gages, and water impoundments. The data layers included in the maps (and this dataset) vary depending on availability, but generally include roads, hydrography, political boundaries, USGS 7.5' minute quadrangle outlines, hydrologic units, trails, and others as appropriate. The scales of each layer vary depending on data source but are generally 1:100,000.

Web map used in Delaware County GIS Data Extract application that allows users to extract Delaware County, Ohio GIS data in various formats.

The Digital Surficial Geologic-GIS Map of Hopewell Culture National Historical Park and Vicinity, Ohio 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 (hocu_surficial_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 (hocu_surficial_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 (hocu_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (hocu_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 (hocu_surficial_geology_metadata_faq.pdf). Please read the hocu_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: Ohio Department of Natural Resources, Division of 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 (hocu_surficial_geology_metadata.txt or hocu_surficial_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 Surficial Geologic-GIS Map for Cuyahoga Valley National Park and Vicinity, Ohio 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 (cuva_surficial_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 and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (cuva_surficial_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.) this file (cuva_geology.gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (cuva_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 (cuva_surficial_geology_metadata_faq.pdf). Please read the cuva_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: http://www.google.com/earth/index.html. 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: Ohio Division of 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 (cuva_surficial_geology_metadata.txt or cuva_surficial_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, 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).

Download .zipThese data were derived from multiple sources, one of which was the USGS DLG data which was captured at 1:24,000-scale. The accuracy for DLG data is ± 40 feet. Although the USGS does not claim legal responsibility for the accuracy of these data.These files were obtained from the GIS Support Center, Ohio Department of Administrative Services and were originally prepared by the Ohio State University Center for Mapping in cooperation with the United States Geological Survey with additional funding from several state agencies and other groups. These files were augmented in a few instances with hand digitizing where small missing line segments were found. Originally the Lake Erie shoreline and islands in Lake Erie were added from the Hydrography layer (hy). At the time, the quadrangles used varied over a wide rangle of years this line does not represent a particular water level and is for illustrative purposes only. For example there is a wide offset between the shoreline on the Metzger Marsh Quadrangle and that of the Oak Harbor Quadrangle. This distance is so large that no attempt was made to edgematch the two quadrangles. The line connecting the two shorelines represents the quadrangle boundary. For the purposes of this map Sandusky Bay and Muddy Creek Bay were included as a part of Lake Erie. The Lake Erie shoreline is not meant to represent any Lake Erie shoreline which may be used for regulatory puposes. This has since been modified to be more accurate and inline with the NOAA project that mapped the bathymetry of the Great Lakes. The boundaries were modified to better match these data. An updated boundary for Fairfield-Licking-Perry Counties within Buckeye Lake was included by digitizing the boundary from a more recently updated quadrangle map.

Conversion from the dlg format to ArcInfo was accomplished using ArcInfo software in conjuction with an AML program to adjust the quadrangles so that their corners fall on the exact coordinates of the quadrangle corners. Due to the way in wihich coordinates are stored in the dlg's there is some variation in the quadrangle corner coordinates.

Since 200; additional edits to these data were made in 2002 by ODNR staff through the creation of the Public Lands Survey digitization project.

Further edits were made in 2012 in conjunction with a BLM project to establish cadastral standards.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesOffice of Information TechnologyGIS Records2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

The United States Public Land Survey (PLS) divided land into one square mile units, termed sections. Surveyors used trees to locate section corners and other locations of interest (witness trees). As a result, a systematic ecological dataset was produced with regular sampling over a large region of the United States, beginning in Ohio in 1786 and continuing westward.
We digitized and georeferenced archival hand drawn maps of these witness trees for 27 counties in Ohio. This dataset consists of a GIS point shapefile with 11,925 points located at section corners, recording 26,028 trees (up to four trees could be recorded at each corner). We retain species names given on each archival map key, resulting in 70 unique species common names. PLS records were obtained from hand-drawn archival maps of original witness trees produced by researchers at The Ohio State University in the 1960’s. Scans of these maps are archived as “The Edgar Nelson Transeau Ohio Vegetation Survey” at The Ohio State University: http://hdl.handle.net/1811/64106.
The 27 counties are: Adams, Allen, Auglaize, Belmont, Brown, Darke, Defiance, Gallia, Guernsey, Hancock, Lawrence, Lucas, Mercer, Miami, Monroe, Montgomery, Morgan, Noble, Ottawa, Paulding, Pike, Putnam, Scioto, Seneca, Shelby, Williams, Wyandot. Coordinate Reference System: North American Datum 1983 (NAD83). This material is based upon work supported by the National Science Foundation under grants #DEB-1241874, 1241868, 1241870, 1241851, 1241891, 1241846, 1241856, 1241930.

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. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

Geospatial data about Ohio City Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

Vector polygon map data of property parcels from Columbus, Ohio containing 735,806 features.

​

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

​

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

​

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

The Digital Glacial and Surficial Geologic-GIS Map of Summit County and Parts of Cuyahoga County, Ohio 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 (cuva_glacial_surficial_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 and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (cuva_glacial_surficial_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.) this file (cuva_geology.gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (cuva_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 (cuva_glacial_surficial_geology_metadata_faq.pdf). Please read the cuva_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: http://www.google.com/earth/index.html. 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: Ohio Division of 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 (cuva_glacial_surficial_geology_metadata.txt or cuva_glacial_surficial_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:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 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).

Download .zipThis data set contains the bedrock-topography GIS data for the state of Ohio. This data set was created as part of a project to create the new state bedrock-geology map for Ohio. The contours come from a number of different sources, which include new mapping done at the 1:24,000 scale and existing mapping done at 1:24,000 and 1:62,500 scale. Existing county bedrock topography maps were photo-enlarged to 1:24,000 scale to match individual 7.5-minute quadrangles. Dataset includes the following features: 1:24,000-scale bedrock-topography data points for Ohio and 1:24,000-scale bedrock-topography contours for Ohio. All these features will have an individual metadata (xml) record associated with them.Contact Information:Geological Survey, Customer ServiceOhio Department of Natural ResourcesDivision of Geological SurveyGeologic Records2045 Morse RoadColumbus, OH, 43229-6693Telephone: 614-265-6576Email: geo.survey@dnr.ohio.gov

Vector polygon map data of property parcels from Scioto County, Ohio containing 58,630 features.

​

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

​

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

​

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

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

A web map used to access tax parcel, boundary, ownership, acreage, survey, zoning and tax information. Errors and Omissions Do Exist.The information provided is for reference only and subject to independent verification. User assumes all responsibility for its use.https://www.fayette-co-oh.com/Fayette County ProfileFayette County is a county located in the U.S. state of Ohio. Its county seat is Washington Court House. Fayette County was formed on March 1, 1810 from portions of Highland County and Ross County. It was named after Marie-Joseph Motier, Marquis de La Fayette, a French general and politician who took the side of the Colonials during the American Revolutionary War and who played an important role in the French Revolution.Fayette County is a part of the Virginia Military survey, which was reserved in 1783, to be allotted to Virginia soldiers. This district includes the entire counties of Adams, Brown, Clermont, Clinton, Highland, Fayette, Madison and Union; and a portion of the counties of Scioto, Pike, Ross, Pickaway, Franklin, Delaware, Marion, Hardin, Logan, Champaign, Clarke, Greene, Warren and Hamilton.Fayette County was formed January 19, 1810 (took effect March 1st) from Ross and Highland counties. Beginning at the southwest corner of Pickaway, running north “with the line of said county to the corner of Madison; thence west with the line of said Madison county to the line of Greene county; thence south with the line of Greene county to the southeast corner thereof; thence east five miles; thence south to the line of Highland county; thence east with said line to Paint Creek; thence in a straight line to the beginning.” All the lower portion was taken from Highland and the upper from Ross.The first portion of land entered within the territory of what is now Fayette county, was a part of original surveys Nos. 243 and 772, lying partly in Clinton county. The first survey lying wholly within Fayette county was No. 463, in what is now Madison township, surveyed for Thomas Overton by John O’Bannon June 30, 1776.The original townships were Jefferson, Greene, Wayne, Madison, Paint and Union. Concord township was formed in April 1818, from Greene. Marion township was formed in June, 1840 from Madison. Perry township was formed June 4, 1845, from Wayne and Greene. Jasper township was formed from Jefferson and Concord December 2, 1845.Washington C.H. was laid out originally on a part of entry 757, which contained 1200 acres and belonged to Benjamin Temple, of Logan county, Kentucky, who donated 150 acres to Fayette county, on condition that it be used as the site of the county seat. The deed of conveyance was made December 1, 1810, by Thomas S. Hind, attorney for Temple, to Robert Stewart, who was appointed by the legislature as director for the town of Washington. The town was laid off some time between December 1, 1810, and February 26, 1811, the latter being the date of the record of the town plat.Bloomingburg (originally called New Lexington) was laid out in 1815, by Solomon Bowers, and originally contained 34 and ¾ acres. On March 4, 1816, Bowers laid out and added twenty more lots. The name of the town was later changed to Bloomingburg by act of the legislature. The town was incorporated by act of the legislature, February 5, 1847.Jeffersonville was laid out March 1, 1831, by Walter B. Write and Chipman Robinson, on 100 acres of land belonging to them, they started selling the lots at $5 each. The town incorporated March 17, 1838. The first house was erected by Robert Wyley.The first railroad, now the C. & M. V., was completed in 1852; the second, now the Detroit Southern, in 1875; the third, now the C.H. & D. in 1879; and the fourth, now the B. & O. S. W., in 1884.The first permanent settler (probably) was a Mr. Wolf who settled in what is now Wayne township, in about the year 1796. - Circa 1886 - Map of Fayette County, Ohio. Issued by the Fayette County Record.

Fayette County Ohio GIS Addresses Location Based Response System (LBRS). The information provided is for reference only and subject to independent verification. User assumes all responsibility for its use.https://das.ohio.gov/technology-and-strategy/ogrip/projects/lbrsOHIO'S LOCATION BASED RESPONSE SYSTEMThe Location Based Response System (LBRS) is an initiative of the Ohio Geographically Referenced Information Program (OGRIP). The LBRS establishes partnerships between State and County government for the creation of spatially accurate street centerlines with address ranges and field verified site-specific address locations.Funding to support the development of LBRS compliant systems is available to counties through a Memorandum of Agreement (MOA) that establishes roles and responsibilities for program participation. Participating counties provide project management and QA/QC on road names, addresses, etc to develop data that is compatible with the state's legacy roadway inventory.The Ohio Department of Transportation is the LBRS Program Sponsor, providing technical guidance, support, and QA/QC services. The program is being administered by OGRIP, the state's coordinating body for Geographic Information System (GIS) activities.Through the collaborative efforts of State and Local government the LBRS program is producing highly accurate field verified data that is current, complete, consistent, and accessible. LBRS data is maintained as an Ohio asset by local resources and is provided to the state as part of a coordinated long-term effort by OGRIP to reduce redundant data collection by developing data that meets the needs of several levels of government.The LBRS supports a multi-jurisdictional approach to protecting the health, safety and welfare of the state’s constituents.LBRS FAQsWhat is the LBRS? The LBRS is a County/State partnership that gathers accurate locational information on all roads and addresses in a county. The information is used to save lives and save taxpayer dollars by reducing redundant data collection activities. The information is web-based, and is therefore current for all stakeholders as agencies or local governments gather new information.Who is using LBRS data? 9-1-1 Dispatch/First Responders, County Auditors, County Commissioners and Engineers, Ohio Highway Patrol/MARCS, County Emergency Management Agencies, Ohio Department of Transportation, US Department of Homeland Security, US Census Bureau, Ohio Department of Natural Resources, Ohio Department of Agriculture, Ohio Utilites Protection Service.“Both disaster planning and emergency response efforts will benefit from the LBRS. By participating, counties may reduce redundant mapping projects while ensuring that Ohio’s citizens do not pay for multiple mapping initiatives.” - Shawn Smith, Ohio 911 Coordinator - Public Utilities Commission of Ohio.How is the state share determined per county? Each county that participates is assigned a ceiling amount, based on number of addressable structures and miles of public roads. The state share does not exceed 50% of the county’s cost of gathering data, and never exceeds the pre-determined ceiling.What other funding sources are available to support a county's LBRS development? The Ohio Department of Transportation (ODOT) and the County Engineers Association of Ohio (CEAO) each administer Safety Grant programs with funds that can be applied to LBRS projects. How are LBRS funds distributed? Counties enter into a Memorandum of Agreement with the state to secure funding. Counties may contract with a vendor or collect information on their own, with OIT/OGRIP and ODOT providing technical guidance throughout the process. Monies are deliverable based, as a County provides data that meets the State defined standards for program acceptance, the monies are released to the County.

Download .zipThis grid dataset is a digital-elevation model (DEM) for Ohio and portions of Pennsylvania, West Virginia, Kentucky, Indiana, and Michigan. The grid dataset was initially extracted from the United States Geological Survey (USGS) National Elevation Dataset (NED), which has a grid cell size of 30 meters.

Even though the NED dataset was produced to provide a seamless and consistent DEM data across the United States, there were still visible errors associated with USGS Level 1 DEM's. These errors were removed and replaced with new grids derived from the USGS Digital Line Graph (DLG) hypsography. The resulting DEM will be used in the analysis of geological features with respect to the earth's surface, and will be one component of cartographic basemaps.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesOffice of Information TechnologyGIS Records2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Geospatial data about Ohio Road Inventory. Export to CAD, GIS, PDF, CSV and access via API.

Vector polygon map data of mileposts from the state of Ohio containing 19608 features.

Milepost GIS data consists of points along a linear feature, such as roads or railways. They serve as reference points to measure distances along these features. Mile markers are often labeled with numbers indicating their distance from a starting point, such as a highway's origin or a railway station.

These mileposts are invaluable for navigation, route planning, emergency response, and data collection. For example, they help drivers and emergency services identify their location precisely on a road. In transportation planning, mile markers aid in analyzing traffic patterns, determining optimal routes, and estimating travel times. Additionally, they facilitate maintenance activities by providing clear reference points for inspecting and repairing infrastructure.

This data is available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

​

Geospatial data about Ohio Townships. Export to CAD, GIS, PDF, CSV and access via API.

A GIS database of geologic units and structural features in Ohio, with lithology, age, data structure, and format written and arranged just like the other states.