Text View of ISO 19115/19115-2 Metadata with Links to Guidance on NOAA EDM WikiBack to Collection NOAA/NESDIS/NGDC/MGG/Lidar

View Metadata As: Get Data, FAQ, HTML, 19139 XML

Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

2006 OSIP OGRIP: Upland Counties LiDAR Survey
    fileIdentifier:  gov.noaa.csc.maps:oh2006_ogrip_uplandcounties_m2544
    language:  eng; USA
    characterSet:  (MD_CharacterSetCode) utf8
    hierarchyLevel:  (MD_ScopeCode) dataset
    contact:  Mike Sutherland(author) (CI_ResponsibleParty)
        organisationName: (template)
        role:  (CI_RoleCode) author
    dateStamp:  2013-10-17
    metadataStandardName:  ISO 19115-2 Geographic Information - Metadata - Part 2: Extensions for Imagery and Gridded Data
    metadataStandardVersion:  ISO 19115-2:2009(E)
return to top
    spatialRepresentationInfo:  (MD_VectorSpatialRepresentation)
        geometricObjects:  (MD_GeometricObjects)
            geometricObjectType:  (MD_GeometricObjectTypeCode) point
return to top
    referenceSystemInfo:  NAD83
return to top
    referenceSystemInfo:  Ellipsoid
return to top
    identificationInfo:  (MD_DataIdentification)
        citation:  (CI_Citation)
            title:  2006 OSIP OGRIP: Upland Counties LiDAR Survey
            date:  (CI_Date)
                date:  2013-08-20
                dateType:  (CI_DateTypeCode) publication
            citedResponsibleParty:  NOAA CSC (originator)
            citedResponsibleParty:  (CI_ResponsibleParty)
                organisationName:  State of Ohio Office of Information Technology (OSIP), Ohio Geographically Referenced Information Program (OGRIP)
                role:  (CI_RoleCode) originator
            citedResponsibleParty:  NOAA CSC (publisher) (CI_ResponsibleParty)
                organisationName: (template)
                role:  (CI_RoleCode) publisher
            presentationForm:  (CI_PresentationFormCode) imageDigital
        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.
        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.
        credit:  This data set was acquired for the State of Ohio by Woolpert Inc. Subcontractors for LiDAR data acquisition included Horizons, Inc.
        status:  (MD_ProgressCode) completed
        pointOfContact:  (CI_ResponsibleParty)
            individualName:  Jeff Smith
            organisationName:  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)
            positionName:  Project Administrator
            contactInfo:  (CI_Contact)
                phone:  (CI_Telephone)
                    voice:  614.466.4747
                    facsimile:  614.728.5297
                address:  (CI_Address)
                    deliveryPoint:  77 South High Street - Room 1990
                    city:  Columbus
                    administrativeArea:  Ohio
                    postalCode:  43215
                    country:  USA
                    electronicMailAddress:  gis.support@oit.ohio.gov
                hoursOfService:  8:00 am - 5:00 pm
            role:  (CI_RoleCode) pointOfContact
        resourceMaintenance:  (MD_MaintenanceInformation)
            maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) unknown
        graphicOverview:  (MD_BrowseGraphic)
            fileName:  ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/oh/oh2006_ogrip_uplandcounties.kmz
            fileDescription:  This kmz file shows the extent of coverage for the 2006 OGRIP Upland Ohio lidar data set.
            fileType:  kmz
        descriptiveKeywords:  (MD_Keywords)
            keyword:  Bathymetry/Topography
            keyword:  LiDAR
            keyword:  imageryBaseMapsEarthCover
            keyword:  statewide imagery
            keyword:  Georectification
            keyword:  OSIP
            keyword:  Statewide LiDAR
            type:  (MD_KeywordTypeCode) theme
            thesaurusName:  (CI_Citation)
                title:  None
                date: (unknown)
        descriptiveKeywords:  (MD_Keywords)
            keyword:  United States
            keyword:  Ohio
            keyword:  Geauga County
            keyword:  Summit County
            keyword:  Columbiana County
            keyword:  Portage County
            keyword:  Wayne County
            keyword:  Trumbull County
            keyword:  Mahoning County
            keyword:  Medina County
            keyword:  Stark County
            keyword:  Defiance County
            keyword:  Fulton County
            keyword:  Henry County
            keyword:  Hancock County
            keyword:  Huron County
            keyword:  Paulding County
            keyword:  Putnam County
            keyword:  Seneca County
            keyword:  Van Wert County
            keyword:  Williams County
            keyword:  Woods County
            keyword:  Allen County
            keyword:  Crawford County
            keyword:  Richland County
            keyword:  Ashland County
            keyword:  Wyandot County
            keyword:  Auglaize County
            keyword:  Hardin County
            keyword:  Marion County
            keyword:  Shelby County
            keyword:  Mercer County
            type:  (MD_KeywordTypeCode) place
            thesaurusName:  (CI_Citation)
                title:  None
                date: (unknown)
        resourceConstraints:  Lidar Use Limitation
        resourceConstraints:  NOAA Legal Statement
        spatialRepresentationType:  (MD_SpatialRepresentationTypeCode) vector
        language:  eng; USA
        topicCategory:  (MD_TopicCategoryCode) elevation
        extent:  (EX_Extent)
            geographicElement:  (EX_GeographicBoundingBox)
                westBoundLongitude:  -84.826131
                eastBoundLongitude:  -80.497619
                southBoundLatitude:  41.176085
                northBoundLatitude:  41.730895
            temporalElement:  (EX_TemporalExtent)
                    beginPosition:  2006-03-18
                    endPosition:  2006-05-07
return to top
    distributionInfo:  (MD_Distribution)
        distributionFormat:  (MD_Format)
            name:  LAZ
            version: (unknown)
        distributor:  (MD_Distributor)
            distributorContact:  NOAA CSC(distributor) (CI_ResponsibleParty)
                organisationName: (template)
                role:  (CI_RoleCode) distributor
            distributionOrderProcess:  (MD_StandardOrderProcess)
                orderingInstructions:  The National Geophysical Data Center serves as the archive for this LIDAR data. NGDC should only be contacted for this data if it cannot be obtained from NOAA Coastal Services Center.
        distributor:  (MD_Distributor)
            distributorContact:  Mike Sutherland
            distributionOrderProcess:  (MD_StandardOrderProcess)
                orderingInstructions:  The National Geophysical Data Center serves as the archive for this LIDAR dataset. NGDC should only be contacted for the data if it cannot be obtained from NOAA Coastal Services Center.
return to top
    dataQualityInfo:  (DQ_DataQuality)
        scope:  (DQ_Scope)
            level:  (MD_ScopeCode) dataset
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Horizontal Positional Accuracy Report
            evaluationMethodDescription:  The LiDAR, meeting NMAS.
            result: (missing)
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy Report
            evaluationMethodDescription:  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).
            result: (missing)
        report:  (DQ_CompletenessCommission)
            evaluationMethodDescription:  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
            result: (unknown)
        report:  (DQ_ConceptualConsistency)
            measureDescription:  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.
            result: (unknown)
        lineage:  (LI_Lineage)
            processStep:  (LE_ProcessStep)
                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.
                  DateTime:  2013-08-28T00:00:00
            processStep:  (LE_ProcessStep)
                description:  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.
                  DateTime:  2013-08-19T00:00:00
                processor:  NOAA CSC (processor) (CI_ResponsibleParty)
                    organisationName: (template)
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  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.
                  DateTime:  2013-10-17T00:00:00
                processor:  Mike Sutherland (processor) (CI_ResponsibleParty)
                    organisationName: (template)
                    role:  (CI_RoleCode) processor
return to top
    metadataMaintenance:  (MD_MaintenanceInformation)
        maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) annually
        dateOfNextUpdate:  2014-10-17
        maintenanceNote:  This metadata was automatically generated from the FGDC Content Standards for Digital Geospatial Metadata standard (version FGDC-STD-001-1998) using the 2013-01-04 version of the FGDC RSE to ISO 19115-2 for LiDAR transform.
        maintenanceNote:  Translated from FGDC 2013-10-17T11:36:49.025-06:00