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

2008 US Army Corps of Engineers (USACE) National Coastal Mapping Program Topobathy Lidar: Lake Michigan

spatialRepresentationInfo
referenceSystemInfo
referenceSystemInfo
identificationInfo
distributionInfo
dataQualityInfo
metadataMaintenance

 (MI_Metadata)
    fileIdentifier:  gov.noaa.csc.maps:2008_GL_Bathymetry_m518
    language:  eng; USA
    characterSet:  (MD_CharacterSetCode) utf8
    hierarchyLevel:  (MD_ScopeCode) dataset
    contact:  Mike Sutherland(author) (CI_ResponsibleParty)
        organisationName:
        role:  (CI_RoleCode) author
    dateStamp:  2013-06-05
    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:  2008 US Army Corps of Engineers (USACE) National Coastal Mapping Program Topobathy Lidar: Lake Michigan
            date:  (CI_Date)
                date:  2009-01-01
                dateType:  (CI_DateTypeCode) publication
            citedResponsibleParty:  NOAA CSC (originator)
            citedResponsibleParty:  JALBTCX (originator)
            citedResponsibleParty:  NOAA CSC (publisher) (CI_ResponsibleParty)
                organisationName:
                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 west coast of Michigan from Berrien County to Leelanau County, along the Lake Michigan coastline from 28 July - 16 Sept 2008. Lidar intensity data was also collected. 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.
        purpose:  These data were collected as a part of the National Coastal Mapping Program to depict the elevations above the water for the First Return, 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:
            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:  LiDAR
            keyword:  Elevation
            keyword:  ASCII XYZ
            keyword:  Intensity
            type:  (MD_KeywordTypeCode) theme
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        descriptiveKeywords:  (MD_Keywords)
            keyword:  United States
            keyword:  Michigan
            keyword:  Allegan County
            keyword:  Benzie County
            keyword:  Berrien County
            keyword:  Lake Michigan
            keyword:  Leelanau County
            keyword:  Manistee County
            keyword:  Mason County
            keyword:  Muskegon County
            keyword:  Oceana County
            keyword:  Ottawa County
            keyword:  Van Buren County
            type:  (MD_KeywordTypeCode) place
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        descriptiveKeywords:  (MD_Keywords)
            keyword:  2008
            keyword:  July
            keyword:  August
            keyword:  September
            type:  (MD_KeywordTypeCode) temporal
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        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:  -86.838156
                eastBoundLongitude:  -85.915215
                southBoundLatitude:  41.748285
                northBoundLatitude:  44.989667
            temporalElement:  (EX_TemporalExtent)
                extent:
                  TimePeriod:
                    beginPosition:  2008-07-28
                    endPosition:  2008-09-16
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 data positions were obtained using post processed KGPS methods. The horizontal accuracy of the data is better than +/- 0.75m.
            result:
        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.20m.
            result:
        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:
        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:
        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 9kHz, bathymetric lidar data at 1kHz and RGB imagery at 1Hz. 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. The National Geodetic Survey's (NGS) GEOID03 model was used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The 3-D position data were sub-divided into a series of ASCII file products, with each covering approximately 5 kilometers of shoreline. The file index was provided by the shape file, "mi_michigan_boxes.shp", and the numbers used to identify files are in the "Box" field of the shape file. The data file naming convention is based on the year, project, area name, "Box" number and product type (topographic or bathymetric). An example file name is "2008_NCMP_MI_Michigan_07_ASCII", where 2008 is the year of data collection, NCMP is the project under which data were collected, MI_Michigan is the area of data collection, 07 is the "Box" number and ASCII is the product type. The ASCII columns are Longitude, Latitude, UTM Zone, Easting, Northing, Elevation (orthometric), Elevation (ellipsoid), Date, Time, and Intensity.
                dateTime:
                  DateTime:  2009-01-01T00:00:00
                processor:  JALBTCX (processor) (CI_ResponsibleParty)
                    organisationName:
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The NOAA Coastal Services Center (CSC) received topo and hydro files in ASCII format. The files contained LiDAR elevation and intensity measurements. The points were classed as 'never classified.' The data were provided in Geographic coordinates and ellipsoidal heights and in orthometric heights. CSC performed the following processing to the ellipsoidal height data to make it available within the Digital Coast: 1. LASEdit was used to convert the ASCII formatted files to las format. 2. The hydro points classification was changed from 'never classified' to class 11, 'bathymetry'. The topo points classification remains as class 0, 'never classified'. 3. The LAS data were sorted by latitude and the headers were updated.
                dateTime:
                  DateTime:  2009-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:  2011-05-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
return to top
    metadataMaintenance:  (MD_MaintenanceInformation)
        maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) annually
        dateOfNextUpdate:  2014-06-05
        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-06-05T15:37:59.466-06:00
        maintenanceNote:  Last Metadata Review Date: 2011-11-19