Text View of ISO 19115/19115-2 Metadata with Links to Guidance on NOAA EDM WikiAlternate Views: Get Data, FAQ, ISO Rubric, DOI Rubric, CSW, HTML, Components, XML

2004 Harrison County, MS Lidar

spatialRepresentationInfo
referenceSystemInfo
referenceSystemInfo
identificationInfo
distributionInfo
dataQualityInfo
metadataMaintenance

 (MI_Metadata)
    fileIdentifier:  gov.noaa.csc.maps:2004_MS_m39
    language:  eng; USA
    characterSet:  (MD_CharacterSetCode) utf8
    hierarchyLevel:  (MD_ScopeCode) dataset
    contact:  Mike Sutherland(author) (CI_ResponsibleParty)
        organisationName:
        role:  (CI_RoleCode) author
    dateStamp:  2013-05-07
    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:  (MD_ReferenceSystem)
        referenceSystemIdentifier:  (RS_Identifier)
            authority:  (CI_Citation)
                title:  North American Datum 1983
                alternateTitle:  NAD83
                date:  (CI_Date)
                    date:  2007-01-19
                    dateType:  (CI_DateTypeCode) revision
                citedResponsibleParty:  (CI_ResponsibleParty)
                    organisationName:
                    contactInfo:  (CI_Contact)
                        onlineResource:  (CI_OnlineResource)
                            linkage: http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269
                            name:  NAD83
                            description:  Link to Geographic Markup Language (GML) description of reference system.
                            function:  (CI_OnLineFunctionCode) information
                    role:  (CI_RoleCode) resourceProvider
                citedResponsibleParty:  (CI_ResponsibleParty)
                    organisationName:  European Petroleum Survey Group
                    contactInfo:  (CI_Contact)
                        onlineResource:  (CI_OnlineResource)
                            linkage: http://www.epsg-registry.org/
                            name:  European Petroleum Survey Group Geodetic Parameter Registry
                            description:  Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations.
                            function:  (CI_OnLineFunctionCode) search
                    role:  (CI_RoleCode) publisher
            code:  urn:ogc:def:crs:EPSG::4269
return to top
    referenceSystemInfo:  (MD_ReferenceSystem)
        referenceSystemIdentifier:  (RS_Identifier)
            code:  Ellipsoid in Meters
            codeSpace:  Local Vertical Reference
return to top
    identificationInfo:  (MD_DataIdentification)
        citation:  (CI_Citation)
            title:  2004 Harrison County, MS Lidar
            date:  (CI_Date)
                date:  2006-11-09
                dateType:  (CI_DateTypeCode) publication
            citedResponsibleParty:  NOAA CSC (originator)
            citedResponsibleParty:  NOAA CSC (publisher) (CI_ResponsibleParty)
                organisationName:
                role:  (CI_RoleCode) publisher
            presentationForm:  (CI_PresentationFormCode) imageDigital
        abstract:  This metadata record describes the topographic mapping of Harrison County, Mississippi during March of 2004. Products generated include lidar point clouds in .LAS format and lidar bare-earth elevation models in .LAS format using lidar collected with a Leica ALS-40 Aerial Lidar Sensor.
        purpose:  The mission of the Center is to support the environmental, social, and economic well being of the coast by linking people, information, and technology. The data produced from this SOW are intended to support the local Coastal Zone Managers in their decision-making processes. This data will be used for flood plain mapping and other coastal management applications.
        status:  (MD_ProgressCode) completed
        pointOfContact:  NOAA CSC (pointOfContact) (CI_ResponsibleParty)
            organisationName:
            role:  (CI_RoleCode) pointOfContact
        resourceMaintenance:  (MD_MaintenanceInformation)
            maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) notPlanned
        descriptiveKeywords:  (MD_Keywords)
            keyword:  Bathymetry/Topography
            keyword:  Lidar Point Cloud
            keyword:  Lidar
            type:  (MD_KeywordTypeCode) theme
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        descriptiveKeywords:  (MD_Keywords)
            keyword:  Mississippi
            keyword:  Harrison County
            type:  (MD_KeywordTypeCode) place
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        resourceConstraints:  Lidar Use Limitation
        resourceConstraints:  NOAA Legal Statement
        aggregationInfo:  (MD_AggregateInformation)
            aggregateDataSetName:  (CI_Citation)
                title:  Lidar QA/QC Report
                date:
                citedResponsibleParty:  (CI_ResponsibleParty)
                    positionName:  Citation URL
                    contactInfo:  (CI_Contact)
                        onlineResource:  (CI_OnlineResource)
                            linkage:  ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/ms/harrison/2004_Harrison_County_QA.pdf
                            name:  Lidar QA/QC Report
                            description:
                            function:  (CI_OnLineFunctionCode) information
                    role:
            associationType:  (DS_AssociationTypeCode) crossReference
        spatialRepresentationType:  (MD_SpatialRepresentationTypeCode) vector
        language:  eng; USA
        topicCategory:  (MD_TopicCategoryCode) elevation
        extent:  (EX_Extent)
            geographicElement:  (EX_GeographicBoundingBox)
                westBoundLongitude:  -89.39
                eastBoundLongitude:  -88.81
                southBoundLatitude:  30.28
                northBoundLatitude:  30.71
            temporalElement:  (EX_TemporalExtent)
                extent:
                  TimePeriod:
                    beginPosition:  2004-03-08
                    endPosition:  2004-03-09
return to top
    distributionInfo:  (MD_Distribution)
        distributionFormat:  (MD_Format)
            name:  LAZ
            version:
        distributor:  (MD_Distributor)
            distributorContact:  NOAA CSC(distributor) (CI_ResponsibleParty)
                organisationName:
                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, February, 2002.
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy Report
            evaluationMethodDescription:  The lidar data fully comply with FEMA guidance as published in Appendix A, February, 2002 and 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 root mean square error of 18.5 cm if errors were normally distributed).
            result:
        report:  (DQ_CompletenessCommission)
            evaluationMethodDescription:  1. EarthData's proprietary software, Checkedb, for verification against ground survey points. 2. Terrascan, for verification of automated and manual editing and final QC of products.
            result:
        report:  (DQ_ConceptualConsistency)
            measureDescription:  Compliance with the accuracy standard was ensured by the placement of GPS ground control prior to the acquisition of lidar data. The following checks were performed. 1. The ground control and airborne GPS data stream were validated through a fully analytical boresight adjustment. 2. The DTM (Digital Terrain Model) data were checked against the project control. 3. Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal).
            result:
        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 aboveground structures. The algorithms for filtering data were utilized within EarthData's proprietary software and commercial software written by TerraSolid. This software suite of tools provides efficient processing for small to large-scale, projects and has been incorporated into ISO 9001compliant production work flows. The following is a step-by-step breakdown of the process. 1. Using the lidar data set provided by EarthData, the technician performs calibrations on the data set. 2. Using the lidar data set provided by EarthData, the technician performed a visual inspection of the data to 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 3-D Analyst and EarthData's proprietary software was run to detect and color code the differences in these plots and located the areas that contained systematic errors or distortions that were introduced by the lidar sensor. 3. Systematic distortions highlighted in step 2 were removed and the data was 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. 4. The lidar data for each flight line was trimmed in batch for the removal of the overlap areas between flight lines. 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 flight line data sets were then segmented into adjoining tiles for batch processing and data management. 5. The initial batch-processing run removed 95% of points falling on vegetation. The algorithm also removed the points that fell on the edge of hard features such as structures, elevated roadways and bridges. 6. The operator interactively processed the data using lidar editing tools. During this final phase the operator generated a TIN based on a desired thematic layers to evaluate the automated classification performed in step 5. This allowed the operator to quickly re-classify points from one layer to another and recreate the TIN surface to see the effects of edits. Geo-referenced images were toggled on or off to aid the operator in identifying problem areas. The data was also examined with an automated profiling tool to aid the operator in the reclassification. 6. The final DEM was written to an ESRI grid format (.flt). 7. The point cloud data were also delivered in LAS format. 8. Project data was clipped to a 500-meter buffer outside of the official project boundary.
                dateTime:
                  DateTime:  2005-07-28T00:00:00
                processor:  (CI_ResponsibleParty)
                    individualName:  Harold Rempel
                    organisationName:  EarthData International
                    positionName:  Senior Project Manager
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  301-948-8550
                        address:  (CI_Address)
                            deliveryPoint:  7320 Executive Way
                            city:  Frederick
                            administrativeArea:  Maryland
                            postalCode:  21704
                            electronicMailAddress:  metadata@earthdata.com
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The NOAA Coastal Services Center (CSC) received LAS files containing the bared-earth elevation and intensity data from URS. CSC performed the following processing on the data to make it available within the Lidar Data Retrieval Tool (LDART): 1. The data were projected from MS State Plane coordinates to geographic decimal degrees using the General Cartographic Transformation Package. 2. The data were sorted based on latitude. 3. The data were converted from NAVD88 elevations to ellipsoid elevations using Geoid 03.
                dateTime:
                  DateTime:  2006-11-01T00:00:00
                processor:  NOAA CSC (processor) (CI_ResponsibleParty)
                    organisationName:
                    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:
                  DateTime:  2006-01-03T00: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
            source:  (LI_Source)
                description:  Source Contribution: Ground Control. Waggoner Engineering in contract to EarthData International established at total of 9 survey points within Harrison County, MS. Source Type: electronic mail system
                sourceCitation:  (CI_Citation)
                    title:  Report of Survey -Harrison County, Mississippi
                    date:  (CI_Date)
                        date:  2005-01-27
                        dateType:  (CI_DateTypeCode) publication
                    citedResponsibleParty:  (CI_ResponsibleParty)
                        organisationName:  Waggoner Engineering
                        role:  (CI_RoleCode) originator
                    presentationForm:  (CI_PresentationFormCode) documentDigital
                sourceExtent:  (EX_Extent)
                    temporalElement:  (EX_TemporalExtent)
                        extent:
                          TimeInstant:
                            timePosition:  2005-01-24
            source:  (LI_Source)
                description:  Source Contribution: Aerial Lidar Acquisition. EarthData Aviation., was contracted by EarthData International to collect ALS-40 Lidar data over Harrison County, Mississippi. The project site was flown on March 8th and 9th 2004 using a Horizons, Inc. aircraft with tail number N97HC. Lidar data was captured using an ALS-40 Lidar system, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. Lidar was obtained at an altitude of 11,100 feet above mean terrain, at an average airspeed of 120 knots. Sensor pulse rate was set at 20 kHz with a field of view of 45 degrees and a rate of 11.0 Hz. Average swath width of the collected raw lines is 9,112.7 feet. Point spacing was 5 meters. Lidar data was recorded in conjunction with airborne GPS and IMU; the stationary GPS receiver was positioned over a control point located at the Gulfport airport. Recorded digital data was shipped via external hard drive to the production facility for processing. During airborne data collection, an additional 46 GPS control points were established throughout the airport. During the data acquisition, the receivers collected phase data at an epoch rate of 1 Hz. All GPS phase data was post processed with continuous kinematic survey techniques using "On the Fly" (OTF) integer ambiguity resolution. The GPS data was processed with forward and reverse processing algorithms. The results from each process, using the data collected at the airport, were combined to yield a single fixed integer phase differential solution of the aircraft trajectory. Source Type: Firewire Drive
                sourceCitation:  (CI_Citation)
                    title:  Harrison County, Mississippi, Lidar Acquisition Report
                    date:  (CI_Date)
                        date:  2005-07-28
                        dateType:  (CI_DateTypeCode) publication
                    citedResponsibleParty:  (CI_ResponsibleParty)
                        organisationName:  EarthData Aviation, LLC
                        role:  (CI_RoleCode) originator
                    presentationForm:  (CI_PresentationFormCode) modelDigital
                sourceExtent:  (EX_Extent)
                    temporalElement:  (EX_TemporalExtent)
                        extent:
                          TimePeriod:
                            beginPosition:  2004-03-08
                            endPosition:  2004-03-09
return to top
    metadataMaintenance:  (MD_MaintenanceInformation)
        maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) annually
        dateOfNextUpdate:  2014-05-07
        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-05-07T15:17:02.35-06:00
        maintenanceNote:  Last Metadata Review Date: 2011-11-19