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 FEMA New Jersey Flood Mitigation Lidar: Hunterdon County
    fileIdentifier:  gov.noaa.csc.maps:2006_NJ_Hunterdon_m547
    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-06-11
    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 FEMA New Jersey Flood Mitigation Lidar: Hunterdon County
            date:  (CI_Date)
                date:  2007-02-26
                dateType:  (CI_DateTypeCode) publication
            edition:  One
            citedResponsibleParty:  NOAA CSC (originator)
            citedResponsibleParty:  (CI_ResponsibleParty)
                organisationName:  DHS/FEMA > Federal Emergency Management Agency, U.S. Department of Homeland Security
                role:  (CI_RoleCode) originator
            citedResponsibleParty:  NOAA CSC (publisher) (CI_ResponsibleParty)
                organisationName: (template)
                role:  (CI_RoleCode) publisher
            presentationForm:  (CI_PresentationFormCode) imageDigital
        abstract:  This metadata record describes the lidar topographic elevation mapping of Hunterdon County, NJ that occurred in July 2006. Products generated include lidar point clouds in LAS 1.0 collected with a Leica ALS-50 Aerial Lidar Sensor.
        purpose:  The purpose of this data is to support floodplain mapping efforts as part of FEMA's Map Modernization Program.
        status:  (MD_ProgressCode) completed
        pointOfContact:  (CI_ResponsibleParty)
            organisationName:  Federal Emergency Management Agency, Region II
            contactInfo:  (CI_Contact)
                address:  (CI_Address)
                    deliveryPoint:  26 Federal Plaza
                    city:  New York
                    administrativeArea:  NY
                    postalCode:  10278
                    country:  U.S.
            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/nj/2006_FEMA_NJ_Lidar_Hunterdon_County.kmz
            fileDescription:  This kmz file shows the extent of coverage for the 2006 FEMA Hunterdon County, NJ lidar data set.
            fileType:  kmz
        descriptiveKeywords:  (MD_Keywords)
            keyword:  Bathymetry/Topography
            keyword:  bare earth
            keyword:  DEM
            keyword:  digital elevation model
            keyword:  elevation
            keyword:  floodplain
            keyword:  lidar
            keyword:  surface model
            type:  (MD_KeywordTypeCode) theme
            thesaurusName:  (CI_Citation)
                title:  None
                date: (unknown)
        descriptiveKeywords:  (MD_Keywords)
            keyword:  US
            keyword:  New Jersey
            keyword:  Hunterdon 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:  -75.195215
                eastBoundLongitude:  -74.703495
                southBoundLatitude:  40.339414
                northBoundLatitude:  40.787876
            temporalElement:  (EX_TemporalExtent)
                    timePosition:  2006-07-17
        supplementalInformation:  Watershed Concepts requested the collection of lidar data over Hunterdon County, NJ. In response, EarthData acquired the data on July 17, 2006 using its aircraft with tail number N806CP. Lidar data was acquired using an ALS-50 Lidar Sensor, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. An additional GPS receiver was in constant operation over a published control point set by EarthData at the base of the operations airport which is a secondary airport control station. Terrasurv was tasked to perform a geodetic control survey in support of lidar mapping in Hunterdon County, NJ. The Global Positioning System (GPS) was used in static differential mode to measure the intersection vectors of the network. In addition to six locations chosen for control, a survey point located at the Lehigh valley International Airport was included in the network. This latter station was used a base station by the flight crew during data acquisition. The horizontal datum was the North American Datum of 1983-CORS (NAD83 CORS) and the vertical datum was the North American Vertical Datum of 1988. During the data acquisition, the receivers collected phase data at an epoch rate of 1 Hz. The use of the airport base station ensured that all data capture was within 50 miles of a base station. The solutions from Hunterdon County, NJ were found to be of high integrity and met the accuracy requirements for the project. These accuracy check also verified that the data meets the guidelines outlined in FEMA's Guidelines and Specifications for Flood Hazard Mapping Partners and Appendix 4B, Airborne Light detection and Ranging Systems. The areas of interest were flown at an altitude of 8500 feet above mean terrain. Airspeed - 145 knots Laser Pulse Rate - 38000 Hz Field of View - 40 degrees Scan Rate - 20 Hz Swath Width - 1996 meters
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 data fully comply with FEMA guidance as published in Appendix A: Guidance for Aerial Mapping and Surveying, April 2003.
            result: (missing)
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy Report
            evaluationMethodDescription:  The lidar data fully comply with FEMA guidance as published in Appendix A: Guidance for Aerial Mapping and Surveying, April 2003 and the National Standard for Spatial Accuracy (NSSDA). When compared to GPS survey grade points in generally flat non-vegetated areas, at least 95% of the positions have an error less than or equal to 36.3 cm (equivalent to a RMSEz of 18.5 if errors are normally distributed).
            result: (missing)
        report:  (DQ_CompletenessCommission)
            evaluationMethodDescription:  - EarthData's proprietary software, Checkedb, was used for verification against ground survey points. - Verification of automated and manual editing, and final QC of products, was performed using Terrascan.
            result: (unknown)
        report:  (DQ_ConceptualConsistency)
            measureDescription:  Compliance with the accuracy standard was ensured by the placement of GPS ground control points prior to lidar data acquisition. The following checks were performed: - The ground control and airborne GPS data stream were validated through a fully analytical boresight analysis. - The Digital Terrain Model (DTM) data were checked against the project control. - Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal).
            result: (unknown)
        lineage:  (LI_Lineage)
            processStep:  (LE_ProcessStep)
                description:  EarthData has developed a unique method for processing lidar data to identify and remove elevation points falling on vegetation, buildings, and other non-ground structures. The algorithms for filtering data were utilized within EarthData's proprietary software and commercially available software written by TerraSolid. This software suite of tools provides efficient processing for small to large scale projects and has been incorporated into ISO 9001 compliant production workflows. The following process was employed: - Using the lidar data provided by EarthData, the technician performed calibrations of the data. - Using the lidar data provided by EarthData, the technician performed a visual inspection of the data verify that the flight lines overlap correctly. The technician also verified that there were no voids, and that the data covered the project limits. The technician then selected a series of areas from the data set and inspected them where adjacent flight lines overlapped. These overlapping areas were merged and a process which utilizes ArcGIS 3D Analyst and EarthData's proprietary software was run to detect and color code the differences in elevation values and profiles. The technician reviewed these plots and located the areas that contained systematic errors or distortions that were introduced by the lidar sensor. - Identified systematic distortions were removed and the data were re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from one type of land cover to another. - The lidar data for each flightline was trimmed for the removal of the overlap areas between flightlines. The data was checked against a control network to ensure that vertical requirements were maintained. Conversion to the client-specified datum and projections were then completed. The lidar flightline datasets were then tiled for batch processing and data management. - The initial batch processing removed 95% of points falling on vegetation. The algorithm also removed the points that fell on the edges of hard features such as buildings, elevated roadways and bridges. - The technician interactively processed the data using lidar editing tools. During this final phase, the data was TINed based on desired thematic layers to evaluate the automated classification previously performed. This allowed the technician to quickly reclassify points from one layer to another and recreate the TIN surface to see the effect of edits. Georeferenced images were toggled on and off to aid in identification of problem areas. The data were also examined with an automated profiling tool to aid in reclassification. - The final DEM was written to las 1.0. - The point cloud data delivered in las 1.0
                  DateTime:  2007-02-26T00:00:00
                processor:  (CI_ResponsibleParty)
                    individualName:  Angela R. Worley
                    organisationName:  EarthData International
                    positionName:  Project Manager
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  301-948-8550 x222
                        address:  (CI_Address)
                            deliveryPoint:  7320 Executive Way
                            city:  Frederick
                            administrativeArea:  Maryland
                            postalCode:  21704
                            country:  USA
                            electronicMailAddress:  aworley@earthdata.com
                        hoursOfService:  Monday to Friday, 8:30 - 5:00, Eastern Time
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The NOAA Coastal Services Center (CSC) received the files in las format. The files contained Lidar elevation and intensity measurements. The data were projected in New Jersey State Plane coordinates, and referenced to NAVD88 using Geoid 03. CSC performed the following processing steps to the data to make it available within the Digital Coast: 1. The data were converted from New Jersey State Plane (NAD83) coordinates to geographic coordinates (NAD83). 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03. 3. The LAS data were sorted by latitude and the headers were updated.
                  DateTime:  2010-09-22T00: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:  2011-04-28T00:00:00
                processor:  (CI_ResponsibleParty)
                    individualName:  Pamela Grothe
                    organisationName:  DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
                    contactInfo:  (CI_Contact)
                        contactInstructions:  Contact Data Center
                    role:  (CI_RoleCode) processor
return to top
    metadataMaintenance:  (MD_MaintenanceInformation)
        maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) annually
        dateOfNextUpdate:  2014-06-11
        maintenanceNote:  This metadata was automatically generated from the FGDC Content Standard 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-06-11T09:44:10.257-06:00
        maintenanceNote:  Last Metadata Review Date: 2011-11-19