ISO Table View Back 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

Metadata Identifier: gov.noaa.csc.maps:2008_USACE_Huron_m587

Aggregation Info | Bands | Citations | Constraints | Coverage Descriptions | Dimensions | Extents | Formats | Geographic Bounding Box
Georectified Information | Georeferenceable Information | Identifiers | Instruments | Mediums | OnlineResources | Operations
Platforms | Process Steps | Range Elements | Reference Systems | Responsible Parties | Series | Sources | Spatial Grids | Temporal Extents

MD_DataIdentification

Count Component Title Abstract
1 2008 USACE Great Lakes Topo/Bathy Lidar: Lake Huron, Michigan 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).
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2008 USACE Great Lakes Topo/Bathy Lidar: Lake Huron, Michigan
    2011-07-01
1 Geographic Names Information System
    2 None
      Top

      CI_Series

      none found
      Top

      CI_ResponsibleParty

      Count Component Individual Organization Position Email Role Linkage
      1 Mike Sutherland(author) author
      1 NOAA CSC (publisher) publisher
      1 JALBTCX (pointOfContact) pointOfContact
      1 NOAA CSC(distributor) distributor
      3 JALBTCX (processor) processor
      Unresolved Xlinks
      Mike Sutherland(author) at: /gmi:MI_Metadata/gmd:contact[1]
      NOAA CSC (originator) at: /gmi:MI_Metadata/gmd:identificationInfo[1]/gmd:MD_DataIdentification[1]/gmd:citation[1]/gmd:CI_Citation[1]/gmd:citedResponsibleParty[1]
      JALBTCX (originator) at: /gmi:MI_Metadata/gmd:identificationInfo[1]/gmd:MD_DataIdentification[1]/gmd:citation[1]/gmd:CI_Citation[1]/gmd:citedResponsibleParty[2]
      NOAA CSC (publisher) at: /gmi:MI_Metadata/gmd:identificationInfo[1]/gmd:MD_DataIdentification[1]/gmd:citation[1]/gmd:CI_Citation[1]/gmd:citedResponsibleParty[3]
      JALBTCX (pointOfContact) at: /gmi:MI_Metadata/gmd:identificationInfo[1]/gmd:MD_DataIdentification[1]/gmd:pointOfContact[1]
      NOAA CSC(distributor) at: /gmi:MI_Metadata/gmd:distributionInfo[1]/gmd:MD_Distribution[1]/gmd:distributor[1]/gmd:MD_Distributor[1]/gmd:distributorContact[1]
      Mike Sutherland at: /gmi:MI_Metadata/gmd:distributionInfo[1]/gmd:MD_Distribution[1]/gmd:distributor[2]/gmd:MD_Distributor[1]/gmd:distributorContact[1]
      JALBTCX (processor) at: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[1]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      NOAA CSC (processor) at: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[3]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      Mike Sutherland (processor) at: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[4]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      Top

      CI_OnlineResource

      none found
      Top

      MD_Identifier or RS_Identifier

      none found
      Top

      EX_Extent

      Bounding Box Temporal Extent
      Count Component Description West East North South Start End
      1 -82.880709 -82.413509 44.057515 42.999615 2008-08-12 2008-08-17
      Top

      EX_GeographicBoundingBox

      Count Component West East North South
      1 -82.880709 -82.413509 44.057515 42.999615
      Top

      EX_TemporalExtent

      Count Component Start End
      1 2008-08-12 2008-08-17
      Top

      MD_Format

      Count Component Name Version specification
      1 LAZ
      Top

      MD_Medium

      none found
      Top

      MD_Constraints

      Unresolved Xlinks
      Lidar Use Limitation at: /gmi:MI_Metadata/gmd:identificationInfo[1]/gmd:MD_DataIdentification[1]/gmd:resourceConstraints[1]
      NOAA Legal Statement at: /gmi:MI_Metadata/gmd:identificationInfo[1]/gmd:MD_DataIdentification[1]/gmd:resourceConstraints[2]
      Top

      MD_ReferenceSystem

      Unresolved Xlinks
      NAD83 at: /gmi:MI_Metadata/gmd:referenceSystemInfo[1]
      Ellipsoid at: /gmi:MI_Metadata/gmd:referenceSystemInfo[2]
      Top

      MD_GridSpatialRepresentation

      none found
      Top

      MD_Georeferenceable or MI_Georeferenceable

      none found
      Top

      MD_Georectified or MI_Georectified

      none found
      Top

      MD_Dimension

      none found
      Top

      MD_CoverageDescription or MI_CoverageDescription

      none found
      Top

      MD_Band or MI_Band

      none found
      Top

      MI_RangeElementDescription

      none found
      Top

      MD_AggregateInformation

      none found
      Top

      LE_Source or LI_Source

      none found
      Top

      LE_ProcessStep or LI_ProcessStep

      Count Component DateTime Description
      1 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.
      JALBTCX (processor) at Xpath: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[1]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      1 2011-06-01T00:00:00 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.
      1 2014-01-09T00:00:00 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.
      NOAA CSC (processor) at Xpath: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[3]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      1 2014-03-14T00:00:00 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.
      Mike Sutherland (processor) at Xpath: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[4]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      Top

      MI_Operation

      none found
      Top

      MI_Platform

      none found
      Top

      MI_Instrument

      none found
      Top