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
spatialRepresentationInfo
referenceSystemInfo
referenceSystemInfo
identificationInfo
distributionInfo
dataQualityInfo
metadataMaintenance

2008 USACE Great Lakes Topo/Bathy Lidar: Lake Huron, Michigan
 (MI_Metadata)
    fileIdentifier:  gov.noaa.csc.maps:2008_USACE_Huron_m587
    language:  eng; USA
    characterSet:  (MD_CharacterSetCode) utf8
    hierarchyLevel:  (MD_ScopeCode) dataset
    contact:  Mike Sutherland(author) (CI_ResponsibleParty)
        organisationName: (template)
        role:  (CI_RoleCode) author
    dateStamp:  2014-03-14
    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:  2008 USACE Great Lakes Topo/Bathy Lidar: Lake Huron, Michigan
            date:  (CI_Date)
                date:  2011-07-01
                dateType:  (CI_DateTypeCode) publication
            citedResponsibleParty:  NOAA CSC (originator)
            citedResponsibleParty:  JALBTCX (originator)
            citedResponsibleParty:  NOAA CSC (publisher) (CI_ResponsibleParty)
                organisationName: (template)
                role:  (CI_RoleCode) publisher
            presentationForm:  (CI_PresentationFormCode) imageDigital
        abstract:  These files contain topographic and bathymetric lidar data collected by the Compact Hydrographic Airborne Rapid Total Survey (CHARTS) system along the Lake Huron coast of Michigan in Huron, Sanilac, and St. Clair Counties during August 12-17, 2008. CHARTS integrates topographic and bathymetric lidar sensors, a digital camera, and a hyperspectral scanner on a single remote sensing platform for use in coastal mapping and charting activities. Data coverage generally extends along the coastline from the waterline inland 500 meters (topography) and offshore 1,000 meters or to laser extinction (bathymetry). The topographic lidar sensor has a pulse repetition rate of 9 kHz at 1064 nm (near-infrared wavelength). The bathymetric lidar sensor has a pulse repetition rate of 1 kHz at 532 nm (green wavelength). Native lidar data is not generally in a format accessible to most Geographical Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 (NAD83). Vertical positions are referenced to the NAD83 ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID03 model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). Upon receipt at the NOAA Coastal Services Center, the data were converted to las format and to ellipsoid heights using GEOID03 for data storage and Digital Coast provisioning purposes. Additionally, the bathymetric lidar data points were classified according to the ASPRS LAS 1.2 classification scheme as 11 (bathymetry) and the topographic last return lidar data points were classified as 1 (unclassified).
        purpose:  These data were collected as a part of the NCMP (National Coastal Mapping Program) to depict the elevations ABOVE AND/OR BELOW the water for the First Return OR Last Return OR Hydro in the Michigan coastal zone.
        credit:  Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products.
        status:  (MD_ProgressCode) completed
        pointOfContact:  JALBTCX (pointOfContact) (CI_ResponsibleParty)
            organisationName: (template)
            role:  (CI_RoleCode) pointOfContact
        resourceMaintenance:  (MD_MaintenanceInformation)
            maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) asNeeded
        descriptiveKeywords:  (MD_Keywords)
            keyword:  Bathymetry/Topography
            keyword:  U.S. Army Corps of Engineers, Mobile District
            keyword:  JALBTCX
            keyword:  CHARTS
            keyword:  SHOALS
            keyword:  Topography
            keyword:  Bathymetry
            keyword:  ASCII XYZ
            keyword:  Lidar
            type:  (MD_KeywordTypeCode) theme
            thesaurusName:  (CI_Citation)
                title:  None
                date: (unknown)
        descriptiveKeywords:  (MD_Keywords)
            keyword:  United States
            keyword:  Michigan
            keyword:  Huron County
            keyword:  Saint Clair County
            keyword:  Sanilac County
            keyword:  Bay City
            keyword:  Port Huron
            type:  (MD_KeywordTypeCode) place
            thesaurusName:  (CI_Citation)
                title:  Geographic Names Information System
                date: (unknown)
        descriptiveKeywords:  (MD_Keywords)
            keyword:  August
            keyword:  2008
            type:  (MD_KeywordTypeCode) temporal
            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:  -82.880709
                eastBoundLongitude:  -82.413509
                southBoundLatitude:  42.999615
                northBoundLatitude:  44.057515
            temporalElement:  (EX_TemporalExtent)
                extent:
                  TimePeriod:
                    beginPosition:  2008-08-12
                    endPosition:  2008-08-17
        supplementalInformation:  Sensor malfunction in the survey area hindered the acquisition of bathymetric data in boxes 08, 09, 10, and 11 which and resulted in incomplete coverage.
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 data positions were obtained using post processed KGPS methods. The horizontal accuracy of the data is better than +/- 0.75 m.
            result: (missing)
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Horizontal Positional Accuracy
            measureDescription:  1 Sigma
            result:  (DQ_QuantitativeResult)
                valueUnit:
                  BaseUnit:
                    identifier:  meters
                    unitsSystem:
                value:
                  Record:  0.75
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy Report
            evaluationMethodDescription:  The data positions were obtained using post processed KGPS methods. The vertical accuracy of the data is better than +/- 0.20 m.
            result: (missing)
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy
            measureDescription:  1 Sigma
            result:  (DQ_QuantitativeResult)
                valueUnit:
                  BaseUnit:
                    identifier:  meters
                    unitsSystem:
                value:
                  Record:  0.20
        report:  (DQ_CompletenessCommission)
            evaluationMethodDescription:  Not provided
            result: (unknown)
        report:  (DQ_ConceptualConsistency)
            measureDescription:  The data provided in this file were tested against ground truth data. At these locations the lidar data matched within 0.20 meters, and different flight line data agreed within 0.20 meters.
            result: (unknown)
        report:  (DQ_QuantitativeAttributeAccuracy)
            nameOfMeasure:  Quantitative Attribute Accuracy Assessment
            measureDescription:  These data are not attributed.
            evaluationMethodDescription:  These data are not attributed.
            result:  (DQ_QuantitativeResult)
                valueUnit:
                  BaseUnit:
                    identifier:  meters
                    unitsSystem:
                value:
                  Record:  N/A
        lineage:  (LI_Lineage)
            processStep:  (LE_ProcessStep)
                description:  These data were collected using the CHARTS system. It is owned by the Naval Oceanographic Office and operated through contract. The system collects topographic lidar data at 9 kHz, bathymetric lidar data at 1 kHz and RGB imagery at 1 Hz. A CASI-1500 hyperspectral line scanner is integrated with the system as well. Aircraft position, velocity and acceleration information are collected through a combination of Novatel and POS A/V 410 equipment. All raw data streams are transferred to the office for downloading and processing in SHOALS GCS software. Aircraft position data are processed using POSPac software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. Upon inspection and QA/QC in the software packages Fledermaus and PFM_ABE, anomalous data are flagged as invalid. PFM_ABE's chartsLAS module then converts all valid data from ellipsoid to orthometric heights based on the NGS' GEOID03 model and exports data as a series of first return topography (TF), last return topography (TL) and bathymetry (H) ASCII files. The bathymetry files contain all of the returns from the bathymetric sensor which include returns both above and below the water.
                dateTime: (unknown)
                processor:  JALBTCX (processor) (CI_ResponsibleParty)
                    organisationName: (template)
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The NOAA Coastal Services Center (CSC) received unclassified files in ASCII format. The files contained LiDAR intensity and elevation measurements. CSC performed the following processing on the data for data storage and Digital Coast provisioning purposes: 1. The data (topographic last return and hydrographic lidar points) were converted from ASCII format to las format. 2. The data were converted from NAVD88 heights to ellipsoid heights using GEOID03. 3. The hydrographic lidar data points were classified according to the ASPRS LAS 1.2 classification scheme as 11 (bathymetry) and the topographic last return lidar data points were classified as 1 (unclassified). 4. The LAS header fields were sorted by latitude and updated.
                dateTime:
                  DateTime:  2011-06-01T00:00:00
            processStep:  (LE_ProcessStep)
                description:  Times had originally been stored as POSIX seconds when converted to LAS. This was switched to adjusted GPS time (GPS seconds - 1e9) to conform to the LAS 1.2 standard. The data were also converted to LAZ format.
                dateTime:
                  DateTime:  2014-01-09T00: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:
                  DateTime:  2014-03-14T00: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:  2015-03-14
        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 2014-03-14T08:09:18.127-04:00