Text View of ISO 19115/19115-2 Metadata with Links to Guidance on NOAA EDM WikiView Metadata As: Get Data, FAQ, HTML, 19139 XML

Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components
spatialRepresentationInfo
referenceSystemInfo
referenceSystemInfo
identificationInfo
distributionInfo
dataQualityInfo
metadataMaintenance

2004 Saginaw Bay, Lake Huron, Michigan Lidar
 (MI_Metadata)
    fileIdentifier:  gov.noaa.csc.maps:2004_MI_m18
    language:  eng; USA
    characterSet:  (MD_CharacterSetCode) utf8
    hierarchyLevel:  (MD_ScopeCode) dataset
    contact:  (CI_ResponsibleParty)
        individualName:  Mike Sutherland
        organisationName:  DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
        contactInfo:  (CI_Contact)
            phone:  (CI_Telephone)
                voice:  303-497-6120
                facsimile:  303-497-6513
            address:  (CI_Address)
                deliveryPoint:  NOAA/NESDIS/NGDC E/GC1 325 Broadway
                city:  Boulder
                administrativeArea:  CO
                postalCode:  80305-3328
                country:  USA
                electronicMailAddress:  mike.sutherland@noaa.gov
            hoursOfService:  7:30am-5:00pm Mountain
        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 Saginaw Bay, Lake Huron, Michigan Lidar
            date:  (CI_Date)
                date:  2006-10-19
                dateType:  (CI_DateTypeCode) publication
            citedResponsibleParty:  (CI_ResponsibleParty)
                organisationName:  DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
                contactInfo:  (CI_Contact)
                    phone:  (CI_Telephone)
                        voice:  843-740-1200
                    address:  (CI_Address)
                        deliveryPoint:  2234 South Hobson Ave.
                        city:  Charleston
                        administrativeArea:  SC
                        postalCode:  29405-2413
                        electronicMailAddress:  csc.info@noaa.gov
                role:  (CI_RoleCode) originator
            citedResponsibleParty:  (CI_ResponsibleParty)
                organisationName:  DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
                contactInfo:  (CI_Contact)
                    phone:  (CI_Telephone)
                        voice:  843-740-1200
                    address:  (CI_Address)
                        deliveryPoint:  2234 South Hobson Ave.
                        city:  Charleston
                        administrativeArea:  SC
                        postalCode:  29405-2413
                        electronicMailAddress:  csc.info@noaa.gov
                role:  (CI_RoleCode) publisher
            presentationForm:  (CI_PresentationFormCode) imageDigital
        abstract:  This metadata document describes the collection and processing of Light Detection and Ranging (LIDAR) data over an area along the coast of Saginaw Bay, Lake Huron, Michigan. Data was collected at a nominal two (2) meter post spacing between points. The elevations in this data set represent the first surface returns. Features that are above the ground - such as buildings, bridges, tree tops, etc. - have NOT been eliminated.
        purpose:  This LIDAR collected under this task order has been supplied to the NOAA, Coastal Services Center (CSC) to support local Coastal Zone Managers in their decision-making processes.
        status:  (MD_ProgressCode) completed
        pointOfContact:  (CI_ResponsibleParty)
            organisationName:  DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
            contactInfo:  (CI_Contact)
                phone:  (CI_Telephone)
                    voice:  843-740-1200
                address:  (CI_Address)
                    deliveryPoint:  2234 South Hobson Ave.
                    city:  Charleston
                    administrativeArea:  SC
                    postalCode:  29405-2413
                    electronicMailAddress:  csc.info@noaa.gov
            role:  (CI_RoleCode) pointOfContact
        resourceMaintenance:  (MD_MaintenanceInformation)
            maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) notPlanned
        descriptiveKeywords:  (MD_Keywords)
            keyword:  Bathymetry/Topography
            keyword:  lidar
            keyword:  laser
            keyword:  beach
            keyword:  topography
            keyword:  digital elevation model
            keyword:  DEM
            keyword:  erosion
            type:  (MD_KeywordTypeCode) theme
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        descriptiveKeywords:  (MD_Keywords)
            keyword:  United States of America (USA)
            keyword:  Saginaw Bay
            keyword:  Lake Huron
            keyword:  Michigan
            type:  (MD_KeywordTypeCode) place
            thesaurusName:  (CI_Citation)
                title:  Geographic Names Information System
                date:
        resourceConstraints:  (MD_Constraints)
            useLimitation:  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.
        resourceConstraints:  (MD_LegalConstraints)
            useLimitation:  While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty.
        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/mi/20041201_QA_REPORT_Saginaw.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:  -83.969892
                eastBoundLongitude:  -82.946673
                southBoundLatitude:  43.551754
                northBoundLatitude:  44.345024
            temporalElement:  (EX_TemporalExtent)
                extent:
                  TimePeriod:
                    beginPosition:  2004-04-27
                    endPosition:  2004-05-04
return to top
    distributionInfo:  (MD_Distribution)
        distributionFormat:  (MD_Format)
            name:  LAZ
            version:
        distributor:  (MD_Distributor)
            distributorContact:  (CI_ResponsibleParty)
                organisationName:  DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
                contactInfo:  (CI_Contact)
                    phone:  (CI_Telephone)
                        voice:  843-740-1200
                    address:  (CI_Address)
                        deliveryPoint:  2234 South Hobson Ave.
                        city:  Charleston
                        administrativeArea:  SC
                        postalCode:  29405-2413
                        electronicMailAddress:  csc.info@noaa.gov
                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:  (CI_ResponsibleParty)
                individualName:  Mike Sutherland
                organisationName:  DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
                contactInfo:  (CI_Contact)
                    phone:  (CI_Telephone)
                        voice:  303-497-6120
                        facsimile:  303-497-6513
                    address:  (CI_Address)
                        deliveryPoint:  NOAA/NESDIS/NGDC E/GC1 325 Broadway
                        city:  Boulder
                        administrativeArea:  CO
                        postalCode:  80305-3328
                        country:  USA
                        electronicMailAddress:  mike.sutherland@noaa.gov
                    hoursOfService:  7:30am-5:00pm Mountain
                role:  (CI_RoleCode) distributor
            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 horizontal accuracy of this lidar data was not assessed. The high vertical accuracy is indicative of good horizontal accuracy, though slight horizontal inaccuracies are difficult to detect using these check points because they were located in relatively flat terrain.
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy Report
            evaluationMethodDescription:  Thirty check points collected on generally flat open terrain with a reported accuracy of 0.03 meters were compared to the lidar points. The Guidelines for Digital Elevation Data by NDEP recommends interpolation from a surface generated from a triangulated irregular network (TIN) derived from the lidar point data surrounding the check point for assessing the accuracy of mass points. This method was employed in this evaluation. Elevation values at the location of each of the 30 check points were interpolated from the triangulated bare earth point data. The vertical error at each check point location was calculated by subtracting the interpolated lidar elevation value from the check point elevation value. The 95th percentile error was used to calculate the overall accuracy of the lidar data because the errors were distributed non-parametrically.
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy
            measureDescription:  Tested 0.26 meter fundamental vertical accuracy at 95th percentile in open terrain. The fundatmental vertical accuracy at the 95th percentile was calculated with the following equation: Vertical Accuracy = 95th percentile error
            result:  (DQ_QuantitativeResult)
                valueUnit:
                  BaseUnit:
                    identifier:  meters
                    unitsSystem:
                value:
                  Record:  0.26
        report:  (DQ_CompletenessCommission)
            evaluationMethodDescription:  None available.
            result:
        report:  (DQ_ConceptualConsistency)
            measureDescription:  The data were evaluated to ensure no voids exisit and the data covers the entire project area.
            result:
        lineage:  (LI_Lineage)
            processStep:  (LE_ProcessStep)
                description:  EarthData has developed a unique method for processing LIDAR data. 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 9001 compliant production work flows. POINT CLOUD The following is a step-by-step breakdown of the process utilized to produce the variably-spaced point cloud surface data set. 1. Processing of the LIDAR data begins with refinement of the initial boresight alignment parameters provided by EarthData Aviation in the LITES configuration file delivered with the raw data. The technician also verifies that there are no voids, and that the data covers the entire project area. Calibration is accomplished using the tri-directional flight lines over the project airport, which is generally flat and free of major obstructions, trees or brush. Two overlapping bi-directional lines are flown along the length of the runway, and the cross flight line is perpendicular to both. All three lines are examined to ensure that they agree, within expected system tolerances, in the overlapping areas. The technician will review flight lines and locate the areas that contained systematic errors or distortions that were introduced by the LIDAR sensor. 2. Systematic distortions highlighted in step 1 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 on type of land cover to another. 3. All flight lines are processed with the refined calibration parameters obtained thru steps 1 and 2. All flight line are examined to ensure that they agree, within expected system tolerances, in the overlapping areas (side lap). 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 data was then edited for Blunder removal. 6. The data was processed interactively by the operator 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. The use of 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. 7. The data was separated into (1) variably-spaced point cloud in LAS files. The files were written to PC readable CD-ROM.
                dateTime:
                  DateTime:  2004-09-27T00:00:00
                processor:  (CI_ResponsibleParty)
                    organisationName:  EarthData International of Maryland
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  1-301-948-8550
                            facsimile:  1-301-963-2064
                        address:  (CI_Address)
                            deliveryPoint:  7320 Executive Way
                            city:  Frederick
                            administrativeArea:  Maryland
                            postalCode:  21704
                            country:  USA
                            electronicMailAddress:  metadata@earthdata.com
                        hoursOfService:  9 AM - 5 PM Mon. - Fri.
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The NOAA Coastal Services Center (CSC) received files in LAS format. The files contained lidar intensity and elevation measurements. 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 UTM to geographic decimal degrees using the General Cartopgraphic Transformation Package. 2. The las files were sorted by latitude and the las header fields were completed. 3. The data were converted from orthometric to ellipsoidal heights using Geoid03.
                dateTime:
                  DateTime:  2005-01-05T00:00:00
                processor:  (CI_ResponsibleParty)
                    organisationName:  DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  843-740-1200
                        address:  (CI_Address)
                            deliveryPoint:  2234 South Hobson Ave.
                            city:  Charleston
                            administrativeArea:  SC
                            postalCode:  29405-2413
                            electronicMailAddress:  csc.info@noaa.gov
                    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: GPS Ground Control. Twenty-four (24) ground control points were established by Terrasurv, Inc. using GPS for vertical and horizontal coordinate values. Ground control references NAD83, NAVD88, Geoid99, in meters. An additional thirty (30) independent check ground control points were acquired by Terrasurv, Inc. and provided directly to NOAA, CSC to support an independent analysis of the accuracy of the Lidar data. Source Type: electronic mail system
                sourceCitation:  (CI_Citation)
                    title:  Ground Control Survey of Saginaw Bay, Michigan
                    date:  (CI_Date)
                        date:  2004-09-27
                        dateType:  (CI_DateTypeCode) publication
                    edition:  1st
                    citedResponsibleParty:  (CI_ResponsibleParty)
                        organisationName:  EarthData International of Maryland
                        contactInfo:  (CI_Contact)
                            address:  (CI_Address)
                                city:  Frederick
                                administrativeArea:  MD
                        role:  (CI_RoleCode) publisher
                    citedResponsibleParty:  (CI_ResponsibleParty)
                        organisationName:  Terrasurv, Inc
                        role:  (CI_RoleCode) originator
                    presentationForm:  (CI_PresentationFormCode) modelDigital
                sourceExtent:  (EX_Extent)
                    temporalElement:  (EX_TemporalExtent)
                        extent:
                          TimePeriod:
                            beginPosition:  2004-06-08
                            endPosition:  2004-06-10
            source:  (LI_Source)
                description:  Source Contribution: Aerial Lidar Acquisition. The project area was flown using EarthData Aviation's Piper Navajo aircraft with tail number 62912. LIDAR data was captured using an ALS40 LIDAR system, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. The acquisition was flown during the period of April 27 2004 through May 4, 2004. One ground based GPS receivers was in constant operation during each flight. During the data acquisition, all 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: CD-ROM
                sourceCitation:  (CI_Citation)
                    title:  Saginaw Bay, Michigan LIDAR Scanning Project
                    date:  (CI_Date)
                        date:  2004-09-27
                        dateType:  (CI_DateTypeCode) publication
                    citedResponsibleParty:  (CI_ResponsibleParty)
                        organisationName:  EarthData Aviation
                        contactInfo:  (CI_Contact)
                            address:  (CI_Address)
                                city:  Hagerstown
                                administrativeArea:  MD
                        role:  (CI_RoleCode) publisher
                    citedResponsibleParty:  (CI_ResponsibleParty)
                        organisationName:  EarthData Aviation
                        role:  (CI_RoleCode) originator
                    presentationForm:  (CI_PresentationFormCode) modelDigital
                sourceExtent:  (EX_Extent)
                    temporalElement:  (EX_TemporalExtent)
                        extent:
                          TimePeriod:
                            beginPosition:  2004-04-27
                            endPosition:  2004-05-04
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:01.703-06:00
        maintenanceNote:  Last Metadata Review Date: 2011-11-19