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:2004_CT_m20

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 2004 Connecticut Lidar LIDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. Using a combination of laser rangefinding, GPS positioning and inertial measurement technologies; LIDAR instruments are able to make highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures and vegetation. This data was collected at submeter resolution to provide nominal 1m spacing of collected points. Two returns were recorded for each pulse in addition to an intensity value. This data set is a raster file of z values with 153 columns and 61 rows. The data set was generated from a larger data set and includes all valid points within the requested geographic bounds.
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2004 Connecticut Lidar
    2006-08-14
1 Collection System Calibration

1 Lidar Final Report
    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 NOAA CSC (pointOfContact) pointOfContact
      1 Citation URL ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/ct/20040415_QA_REPORT_Connecticut.pdf
      1 NOAA CSC(distributor) distributor
      1 NOAA CSC (processor) processor
      1 Pamela Grothe DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce processor
      1 Woolpert LLP originator
      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]
      NOAA CSC (publisher) at: /gmi:MI_Metadata/gmd:identificationInfo[1]/gmd:MD_DataIdentification[1]/gmd:citation[1]/gmd:CI_Citation[1]/gmd:citedResponsibleParty[2]
      NOAA CSC (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]
      NOAA CSC (processor) at: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[7]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      Top

      CI_OnlineResource

      Count Component Linkage Name Description Function
      1 ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/ct/20040415_QA_REPORT_Connecticut.pdf Lidar Final Report information
      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 -72.908092 -72.279933 41.453890 41.240042
      1
      Top

      EX_GeographicBoundingBox

      Count Component West East North South
      1 -72.908092 -72.279933 41.453890 41.240042
      Top

      EX_TemporalExtent

      Count Component Start End
      2
      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

      Count Component Title Code Association Type Code
      1 Lidar Final Report crossReference
      Top

      LE_Source or LI_Source

      Count Component Title Date Description
      1 Collection System Calibration Source Contribution: System Calibration. Minimizes horizontal error caused by IMU mis-alignment by checking over known range and by comparing positional results from adjacent flight lines to compute error adjustment function. Source Type: Validation Report
      Top

      LE_ProcessStep or LI_ProcessStep

      Count Component DateTime Description
      1 2004-10-01T00:00:00 Data Collection: Using a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, 41 flight lines of high density (submeter ground sample distance) data were collected over areas in coastal Connecticut (approximately 300 square kilometers). Two returns were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in one (1) mission on October 8, 2004. Three (3) airborne global positioning system (GPS) base stations were used to support the LiDAR data acquisition: Moriches 1 continuously operating reference station (CORS) ARP, NGS point P36, and one station Woolpert located using static GPS positioning methods, Madison CP. In addition, twenty-two control points were surveyed through fast-static GPS methods to support the final accuracy analysis and tied into the National Geodetic Survey (NGS) points Moriches CORS and P36.
      1 2004-11-01T00:00:00 Airborne GPS Processing: Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The overlap between flight lines was removed to provide a homogeneous coverage, and the coverage was classified to extract a bare earth digital elevation model (DEM). Airborne GPS is differentially processed using the GrafNAV V4.10 software by Waypoint Consulting of Calgary, Alberta, Canada. The PDOP and distance separation is as follows: P36: Maximum PDOP = 3.58 (maximum) Average Distance Separation: 17 km Madison CP: Maximum PDOP = 3.58 (maximum) Average Distance Separation: 19 km IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS & Mapping Division of Atlanta, Georgia. The classification and quality control (QC) of LiDAR data is carried out using a combination of proprietary software and TerraScan software by Terrasolid Limited of Helinski, Finland. Two (2) coverages were delivered in the LAS file format: bare-earth and above ground features.
      1 2004-11-01T00:00:00 IMU data Processing: IMU data provides information concerning roll, pitch and yaw of collection platform during collection event. IMU information allows the pulse vector to be properly placed in 3D space allowing the distance from the aircraft reference point to be properly positioned on the elevation model surface. IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada.
      1 2004-11-01T00:00:00 Reflective Surface Generation: The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS & Mapping Division of Atlanta, Georgia.
      1 2004-12-01T00:00:00 LIDAR Point Classification The classification and quality control (QC) of LiDAR data is carried out using a combination of proprietary software and TerraScan software by Terrasolid Limited of Helinski, Finland.
      1 2005-01-01T00:00:00 Output LAS Files Random LIDAR points maintained in UTM coordinate system converted to Geographic projection with units of Decimal Degrees
      1 2006-01-03T00: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.
      1 2006-09-27T00:00:00 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 las files were converted from State Plane coordinates to Geographic coordinates. 2. The las header fields were sorted by latitude and updated. 3. The data were converted from orthometric to ellipsoidal heights using Geoid03.
      NOAA CSC (processor) at Xpath: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[7]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      Top

      MI_Operation

      none found
      Top

      MI_Platform

      none found
      Top

      MI_Instrument

      none found
      Top