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

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 USGS New Jersey Lidar: Somerset County These data support the general geospatial needs of the USGS and other federal agencies. LiDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. By positioning laser range finding with the use of 1 second GPS with 200hz inertial measurement unit corrections, Airborne 1's LiDAR instruments are able to make highly detailed geospatial elevation products of the ground, man-made structures and vegetation. The LiDAR flightlines for this project were planned for a 50% acquisition overlap. The nominal resolution of this project without overlap is 1.203m, with a 0.90m resolution with the 50% overlap, assuming a normal distribution. Two returns were recorded for each pulse in addition to an intensity value. GPS Week Time, Intensity, Flightline and number attributes were recorded for each LiDAR point. Positional values were recorded to the centimeter level, while GPS is recorded to a 10th of a millisecond. Scan angle was recorded to the nearest angle, Intensity is recorded as a 12 Bit dynamic range value and echo is recorded as a numeric value from 0 to 256. The data was originally provided as random points, in LAS v1.1 format, classified according to the following codes: Class 1 Non-ground/Extracted Features Last Pulse Class 2 Bare Earth Ground Features Last Pulse Class 3 Extracted Features First Pulse Class 4 Bare Earth Ground Features First Pulse It should be noted that Class 3 and 4 are not ASPRS classes but since this data is a two pulse system, this is the most efficient format to separate the pulses and classification process. The data was reclassified into 2 distinct classifications: Class 1 Non-ground/Extracted Features First and Last Pulse Class 2 Bare Earth Ground Features First and Last Pulse
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2008 USGS New Jersey Lidar: Somerset County
  • 2008-05-01
1 Lidar QA/QC Report
    2 None
      1 North American Datum 1983
      • 2007-01-19
      Top

      CI_Series

      none found
      Top

      CI_ResponsibleParty

      Count Component Individual Organization Position Email Role Linkage
      1 resourceProvider http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269
      1 Citation URL ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/nj/lidarqaqcreport_somerset_final.pdf
      1 NOAA CSC (originator) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov originator
      1 NOAA CSC (publisher) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov publisher
      1 NOAA CSC(distributor) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov distributor
      1 NOAA CSC (processor) DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce csc.info@noaa.gov processor
      1 DOI/USGS > United States Geological Survey, U.S. Department of the Interior originator
      1 EPSG Registry European Petroleum Survey Group publisher http://www.epsg-registry.org/
      1 Mike Sutherland(author) Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov author
      1 Mike Sutherland Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov distributor
      1 Pamela Grothe DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce processor
      1 Roger Barlow U.S. Geological Survey USGS Geospatial Liason for DC, DE, MD, NJ, and Chesapeake Bay rbarlow@usgs.gov pointOfContact
      Top

      CI_OnlineResource

      Count Component Linkage Name Description Function
      1 ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/nj/lidarqaqcreport_somerset_final.pdf Lidar QA/QC Report information
      1 http://www.epsg-registry.org/ European Petroleum Survey Group Geodetic Parameter Registry Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. search
      1 http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 NAD83 Link to Geographic Markup Language (GML) description of reference system. information
      Top

      MD_Identifier or RS_Identifier

      Count Component Code
      1 Ellipsoid in Meters
      1 urn:ogc:def:crs:EPSG::4269
      Top

      EX_Extent

      Bounding Box Temporal Extent
      Count Component Description West East North South Start End
      1 -74.798045 -74.499545 40.758506 40.373106
      Top

      EX_GeographicBoundingBox

      Count Component West East North South
      1 -74.798045 -74.499545 40.758506 40.373106
      Top

      EX_TemporalExtent

      Count Component Start End
      1
      Top

      MD_Format

      Count Component Name Version specification
      1 LAZ
      Top

      MD_Medium

      none found
      Top

      MD_Constraints

      Count Component Use Limitation
      1 Lidar Use Limitation 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.
      Top

      MD_ReferenceSystem

      Count Component Code Authority Title
      1 Ellipsoid Ellipsoid in Meters
      1 NAD83 urn:ogc:def:crs:EPSG::4269 North American Datum 1983
      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 QA/QC Report crossReference
      Top

      LE_Source or LI_Source

      none found
      Top

      LE_ProcessStep or LI_ProcessStep

      Count Component DateTime Description
      1 2008-02-01T00:00:00 > Airborne GPS Kinematic Airborne GPS kinematic data was post processed at Airborne 1 facilities using POS-GNSS kinematic On-The-Fly (OTF) software. Flights were flown with a minimum of 6 satellites in view (13o above the horizon) and with a PDOP of better than 3.5. Distances from base station to aircraft (differential baselines) were kept to a maximum of 31 km while the mean is 16 km, to ensure a strong OTF (On-The-Fly) solution. For all flights, the GPS data can be classified as excellent, with GPS residuals of 5cm average but no larger than 10 cm being recorded. >Generation and Calibration of laser points (raw data) The initial step of calibration is to verify availability and status of all needed GPS and Laser data against field notes and compile any data if not complete. Subsequently the mission points are output using Optech's REALM, initially with default values from Optech or the last mission calibrated for system. The initial point generation for each mission calibration is verified within Microstation/Terrascan for calibration errors. If a calibration error greater than specification is observed within the mission, the roll pitch and scanner scale corrections that need to be applied are calculated. The missions with the new calibration values are regenerated and validated internally once again to ensure quality. All missions are validated against the adjoining missions for relative vertical biases and collected GPS kinematic ground truthing points for absolute vertical accuracy purposes. On a project level, a coverage check is carried out to ensure no slivers are present. >Data Classification and Editing The data was processed using the software TerraScan, and following the methodology described herein. The initial step is the setup of the TerraScan project, which is done by importing client provided tile boundary index (converted to the native UTM zone for processing)encompassing the entire project areas. The 3D laser point clouds, in binary format, were imported into the TerraScan project and divided in 409 Tiles as specified by 133 Urban Area Ortho tiles in LAS 1.0 format. Once tiled, the laser points were classified using a proprietary routine in TerraScan. This routine removes any obvious outliers from the dataset following which the ground layer is extracted from the point cloud. The ground extraction process encompassed in this routine takes place by building an iterative surface model. This surface model is generated using three main parameters: building size, iteration angle and iteration distance. The initial model is based on low points being selected by a "roaming window" with the assumption is that these are the ground points. The size of this roaming window is determined by the building size parameter. The low points are triangulated and the remaining points are evaluated and subsequently added to the model if they meet the iteration angle and distance constraints. This process is repeated until no additional points are added within an iteration. A second critical parameter is the maximum terrain angle constraint, which determines the maximum terrain angle allowed within the classification model. The data is then manually quality controlled with the use of hillshading, cross-sections and profiles. Any points found to be of class vegetation, building or error during the quality control process, are removed from the ground model and placed on the appropriate layer. An integrity check is also performed simultaneously to verify that ground features such as rock cuts, elevated roads and crests are present. Once data has been cleaned and complete, it is then by a supervisor via manual inspection and through the use of a hillshade mosaic of the entire project area. >Deliverable Product Generation -Deliverable Tiling Scheme All files were converted to LAS 1.1, in the specified projection and units and were delivered in the client provided tiling scheme with a total of 409 tiles. -LAS 1.1 Files LiDAR point data in LAS 1.1, classified according to the following classification scheme: Class 1 Non-ground/Extracted Features Last Pulse Class 2 Bare Earth Ground Features Last Pulse Class 3 Extracted Features First Pulse Class 4 Bare Earth Ground Features First Pulse The data contains the following fields of information (Precision reported in brackets): Class (Integer), GPS WeekTime (0.0001 seconds), Easting (0.01 meter), Northing (0.01 meter), Elevation (0.01 meter), Echo Number (Integer 1 to 2), Echo (Integer 1 to 2), Intensity (12 Bit Dynamic), Flightline, Scan Angle (Integer Degree) All points outside project area were assigned to Class 1 - Non-Ground. -GPS Trajectory Files GPS Trajectory Files were provided in digital copy -ABGPS/IMU Positions ABGPS/IMU combined files containing time,x,y,z,kappa,phi,omega were provided in ASCII format. All positions were provided in NAD83 UTM18, NAVD88(Geoid03), GPS seconds (reported to a 10th of a millisecond), meters (reported to a centimeter) for the XYZ and degrees for the kappa,phi,omega (reported to 6 decimals of a degree).
      1 2010-08-27T00:00:00 The NOAA Coastal Services Center (CSC) received the files in las format. The files contained Lidar elevation and intensity measurements. The data were in projected in UTM coordinates, Zone 18 (NAD83), and referenced to the orthometric datum of NAVD88 utilizing Geoid 03. CSC performed the following processing to the data to make it available within the Digital Coast: 1. The data were converted from UTM Zone 18 (NAD83) coordinates to geographic coordinates (NAD83). 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03. 3. The LAS data were reclassifed from 4 to 2 classes: - Class 1, Non-ground/Extracted Features Last Pulse; Extracted Features First Pulse - Class 2, Bare Earth Ground Features Last Pulse; Bare Earth Ground Features First Pulse 4. The LAS data were sorted by latitude and the headers were updated.
      1 2011-06-30T00: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.
      Top

      MI_Operation

      none found
      Top

      MI_Platform

      none found
      Top

      MI_Instrument

      none found
      Top