Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2022: 2006 OSIP OGRIP: Upland Counties LiDAR Survey, https://www.fisheries.noaa.gov/inport/item/49893.

Item Identification

Title: 2006 OSIP OGRIP: Upland Counties LiDAR Survey
Short Name: oh2006_ogrip_uplandcounties_m2544_metadata
Status: Completed
Publication Date: 2013-08-20
Abstract:

The 2006 OSIP digital LiDAR data was collected during the months of March and May (leaf-off conditions). The LiDAR covers the entire land area of the northern tier of Ohio (approximately 23,442 square miles. The LiDAR is delivered in county sets, consisting of 5,000' x 5,000' size tiles. Where the State borders other states (land only), the entire border of the State is buffered by at least 1,000-feet. Along the Lake Erie Shoreline ortho coverage is buffered beyond the shoreline a minimum distance of 2,500-feet. Adjacent flight lines overlap by an average of 30 percent. LiDAR was collected with Leica ALS50 digital LiDAR Systems. The file naming convention is as follows: Nxxxxyyy = 5,000' x 5,000' LiDAR Tiles located in the Ohio State Plane Coordinate System (North Zone). Sxxxxyyy = 5,000' x 5,000' LiDAR Tiles located in the Ohio State Plane Coordinate System (South Zone). Please note that xxxx and yyy represent the easting and northing coordinates (respectively) in state plane feet, The naming convention for each LiDAR tile is based upon (the bottom most-left pixel). The LiDAR was provided in LAS Format containing the above ground and bare-earth LiDAR features. Ownership of the data products resides with the State of Ohio. Orthophotography and ancillary data products produced through this contract are public domain data. LiDAR was acquired Statewide to provide a solid and very accurate base to use during the image rectification process. This same LiDAR can be supplemented with 3D breaklines to generate 2-foot and/or 4/5-foot contours. The average post spacing between LiDAR points is 7-feet. The flying altitude was 7,300-feet AMT, with the targeted flying speed at 170 knots.

Original contact information:

Contact Name: Jeff Smith

Contact Org: State of Ohio, through the Office of Information Technology, Investment and Governance Division, for the Office of Information Technology, Services Delivery Division and the Ohio Geographically Referenced Information Program (OGRIP)

Title: Project Administrator

Phone: 614.466.4747

Email: gis.support@oit.ohio.gov

Purpose:

The State of Ohio has a goal to develop and maintain a seamless statewide base map, referred to as OSIP (Ohio Statewide Imagery Program). OSIP is an initiative partnered through several State Agencies (i.e. ODOT, ODNR) through OGRIP. Data from this project forms the foundation of the Statewide base map, and was developed primarily to support multi-use applications, including homeland security, emergency management, economic development, and the business of government.

Notes:

10537

Supplemental Information:

A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2544/supplemental/oh2006_ogrip_uplandcounties.KMZ

Keywords

Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
elevation
UNCONTROLLED
None Georectification
None imageryBaseMapsEarthCover
None OSIP
None statewide imagery

Physical Location

Organization: Office for Coastal Management
City: Charleston
State/Province: SC

Data Set Information

Data Set Scope Code: Data Set
Maintenance Frequency: Unknown
Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility of the State of Ohio Office of Information Technology (OSIP), Ohio Geographically Referenced Information Program (OGRIP), the Office for Coastal Management or its partners.

Data Set Credit: This data set was acquired for the State of Ohio by Woolpert Inc. Subcontractors for LiDAR data acquisition included Horizons, Inc.

Support Roles

Data Steward

CC ID: 682197
Date Effective From: 2013-08-20
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Distributor

CC ID: 682199
Date Effective From: 2013-08-20
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Metadata Contact

CC ID: 682200
Date Effective From: 2013-08-20
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Point of Contact

CC ID: 682198
Date Effective From: 2013-08-20
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address: coastal.info@noaa.gov
Phone: (843) 740-1202
URL: https://coast.noaa.gov

Extents

Currentness Reference: LiDAR Acquisition

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 1134399
W° Bound: -84.826131
E° Bound: -80.497619
N° Bound: 41.730895
S° Bound: 41.176085

Extent Group 1 / Time Frame 1

CC ID: 1134398
Time Frame Type: Range
Start: 2006-03-18
End: 2006-05-07

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Access Information

Security Class: Unclassified
Data Access Procedure:

This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2544

This data set is dynamically generated based on user-specified parameters.

;

Data Access Constraints:

None

Data Use Constraints:

Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.

Distribution Information

Distribution 1

CC ID: 741936
Download URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2544
Distributor:
File Name: Customized Download
Description:

Create custom data files by choosing data area, product type, map projection, file format, datum, etc.

Distribution 2

CC ID: 741937
Download URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2544/index.html
Distributor:
File Name: Bulk Download
Description:

Simple download of data files.

URLs

URL 1

CC ID: 741939
URL: https://coast.noaa.gov/dataviewer
URL Type:
Online Resource

URL 2

CC ID: 741940
URL: https://coast.noaa.gov
URL Type:
Online Resource

URL 3

CC ID: 741941
URL: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2544/supplemental/oh2006_ogrip_coastalcounties_geo.KMZ
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz
Description:

This graphic shows the lidar coverage for the collaborated Lake Erie coastal counties from the OGRIP OSIP.

Activity Log

Activity Log 1

CC ID: 682245
Activity Date/Time: 2016-05-23
Description:

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 682244
Activity Date/Time: 2017-11-14
Description:

Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.

Activity Log 3

CC ID: 718474
Activity Date/Time: 2018-02-08
Description:

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 741938
Activity Date/Time: 2018-03-13
Description:

Partial upload to move data access links to Distribution Info.

Data Quality

Horizontal Positional Accuracy:

The LiDAR, meeting NMAS.

Vertical Positional Accuracy:

The LiDAR was acquired to meet +/- 1-foot (0.03 m) vertical accuracy (RMSE of 0.5-foot - 95% confidence level). This is suitable for rectification of digital orthophotography and for the creation of 2- and 5-foot contours (with the addition of 3D compiled breaklines).

Completeness Report:

The following methods are used to assure LiDAR accuracy. 1. Use of IMU and ground control network utilizing GPS techniques. 2. Use of airborne GPS in conjunction with the imagery and LiDAR acquisition. 3. The following software is used for validation of the surface modeling 4. LiDAR Data - Terrascan, TerraModeler, Leica, Microstation, ESRI - ArcInfo, ERDAS Imagine, Woolpert Proprietary software

Conceptual Consistency:

Compliance with the accuracy standard was validated by the collection of photo identifiable GPS ground control points during the acquisition of LiDAR. The following checks were performed. The LiDAR data was checked against the project ground control. The technical staff confirmed the accuracy of the points during initial processing. Airborne GPS was also utilized during processing.

Lineage

Process Steps

Process Step 1

CC ID: 1134395
Description:

Data was dowloaded from http://gis5.oit.ohio.gov/geodatadownload/

Standard OSIP imagery and elevation products were collected from 2006 - 2008. The CPA

benefits the state by providing enhanced resolution products OSIP while saving

participating counties an estimated 4.5 million in taxpayer dollars over the cost of

obtaining these imagery, LiDAR and elevation products individually. The savings are

due in large part to the economy of scale realized through a statewide program and

the fact that the state is responsible for the cost of project administration.

Any information regarding acquisition, dissemination or updates should be directed

to the contact information within this metadata or found on the OSIP OGRIP website.

Process Date/Time: 2013-08-28 00:00:00

Process Step 2

CC ID: 1134396
Description:

The NOAA Office for Coastal Management (OCM) receieved the data from:

http://gis5.oit.ohio.gov/geodatadownload/ Downloaded in las format. The files contained LiDAR elevation and

intensity measurements. The decision to use these 30 counties as "upland" in support of the "coastal"

counties previously processed was set based on the Ohio River-Lake Erie divide at the watershed boundaries

at the southern extent of this dataset. The data were in Ohio State Plane North (SP83 3401, feet) and

NAVD88 vertical datum (in feet, assumed Geoid03). OCM performed the following processing for data

storage and Digital Coast provisioning purposes:

1. The data were converted from Ohio State Plane North (3401, feet) coordinates to geographic coordinates.

2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid03.

3. The data were sorted by time and zipped to laz format.

4. The data were then cleaned of errant points, determinant of specific county high and low values, as follows,

County, Points above elevation removed (meters), Points below elevation removed (meters):

Geauga County,154,459; Summit County,601,1528 (feet); Columbiana County,165,700; Portage County,230,584; Wayne County,none,448;

Trumbull County,203,399; Mahoning County,205,573; Medina County,198,448; Stark County,235,466; Defiance County,161,328;

Fulton County,173,297; Allen County,188,417; Henry County,158,303; Hancock County,175,330; Huron County,142,363;

Paulding County,148,285; Putnam County,174,302; Seneca County,148,310; Van Wert County,155,287; Williams County,171,350;

Woods County,103,283; Crawford County,210,407; Richland County,247,505; Ashland County,241,488; Wyandot County,182,366;

Auglaize County,206,380; Hardin County,222,390; Marion County,222,387; Shelby County,211,385; Mercer County,202,353;

5. The individually obtained counties from the Lake Erie coast were combined to form an eight county entity for NOAA's

archiving and storage.

Process Date/Time: 2013-08-19 00:00:00

Catalog Details

Catalog Item ID: 49893
GUID: gov.noaa.nmfs.inport:49893
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-15 15:23+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2022-03-16
Owner Org: OCMP
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2022-03-16
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2023-03-16