ISO Table View Alternate Views: Get Data, FAQ, ISO Rubric, DOI Rubric, CSW, HTML, Components, XML

Metadata Identifier: gov.noaa.csc.maps:oh2006_ogrip_uplandcounties_m2544

Aggregation Info | Bands | Citations | Constraints | Coverage Descriptions | Dimensions | Extents | Formats | Geographic Bounding Box
Georectified Information | Georeferenceable Information | Identifiers | Instruments | Mediums | OnlineResources | Operations
Platforms | Process Steps | Range Elements | Reference Systems | Responsible Parties | Series | Sources | Spatial Grids | Temporal Extents

MD_DataIdentification

Count Component Title Abstract
1 2006 OSIP OGRIP: Upland Counties LiDAR Survey 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.
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2006 OSIP OGRIP: Upland Counties LiDAR Survey
  • 2013-08-20
2 None
    1 North American Datum 1983
    • 2007-01-19
    Top

    CI_Series

    none found
    Top

    CI_ResponsibleParty

    Count Component Individual Organization Position Email Role Linkage
    1 resourceProvider http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269
    1 NOAA CSC (originator) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov originator
    1 NOAA CSC (publisher) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov publisher
    1 NOAA CSC(distributor) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov distributor
    1 NOAA CSC (processor) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov processor
    1 EPSG Registry European Petroleum Survey Group publisher http://www.epsg-registry.org/
    1 Jeff Smith 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) Project Administrator gis.support@oit.ohio.gov pointOfContact
    1 Mike Sutherland(author) Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov author
    1 Mike Sutherland Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov distributor
    1 Mike Sutherland (processor) Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov processor
    1 State of Ohio Office of Information Technology (OSIP), Ohio Geographically Referenced Information Program (OGRIP) originator
    Top

    CI_OnlineResource

    Count Component Linkage Name Description Function
    1 http://www.epsg-registry.org/ European Petroleum Survey Group Geodetic Parameter Registry Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. search
    1 http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 NAD83 Link to Geographic Markup Language (GML) description of reference system. information
    Top

    MD_Identifier or RS_Identifier

    Count Component Code
    1 Ellipsoid in Meters
    1 urn:ogc:def:crs:EPSG::4269
    Top

    EX_Extent

    Bounding Box Temporal Extent
    Count Component Description West East North South Start End
    1 -84.826131 -80.497619 41.730895 41.176085 2006-03-18 2006-05-07
    Top

    EX_GeographicBoundingBox

    Count Component West East North South
    1 -84.826131 -80.497619 41.730895 41.176085
    Top

    EX_TemporalExtent

    Count Component Start End
    1 2006-03-18 2006-05-07
    Top

    MD_Format

    Count Component Name Version specification
    1 LAZ
    Top

    MD_Medium

    none found
    Top

    MD_Constraints

    Count Component Use Limitation
    1 Lidar Use Limitation These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.
    Top

    MD_ReferenceSystem

    Count Component Code Authority Title
    1 Ellipsoid Ellipsoid in Meters
    1 NAD83 urn:ogc:def:crs:EPSG::4269 North American Datum 1983
    Top

    MD_GridSpatialRepresentation

    none found
    Top

    MD_Georeferenceable or MI_Georeferenceable

    none found
    Top

    MD_Georectified or MI_Georectified

    none found
    Top

    MD_Dimension

    none found
    Top

    MD_CoverageDescription or MI_CoverageDescription

    none found
    Top

    MD_Band or MI_Band

    none found
    Top

    MI_RangeElementDescription

    none found
    Top

    MD_AggregateInformation

    none found
    Top

    LE_Source or LI_Source

    none found
    Top

    LE_ProcessStep or LI_ProcessStep

    Count Component DateTime Description
    1 2013-08-19T00:00:00 The NOAA Coastal Services Center (CSC) 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). CSC 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. 6. The data were converted to LAZ format.
    1 2013-08-28T00:00:00 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.
    1 2013-10-17T00:00:00 The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights.
    Top

    MI_Operation

    none found
    Top

    MI_Platform

    none found
    Top

    MI_Instrument

    none found
    Top