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:2007_SC_Jas_Col_Chas_m56

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 2007 South Carolina LiDAR: Charleston (partial), Jasper, and Colleton Counties LiDAR data collection was performed utilizing a Leica ALS-50 sensor, collecting multiple return x, y, and z data as well as intensity data. LiDAR data was processed to achieve a bare ground surface, and was delivered in LAS format. Classified LAS data was also used as a base for collection of hydro features, delivered in MicroStation v8 format. The dates of collection are: 1. JASPER COUNTY (full county): 20061227 to 20070216 2. COLLETON COUNTY (full county: 20070216 to 20070323 3. CHARLESTON COUNTY (Partial County): 20070222 to 20070223
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2007 South Carolina LiDAR: Charleston (partial), Jasper, and Colleton Counties
  • 2008-03-26
1 Lidar Dataset Supplemental Information
    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://csc.noaa.gov/pub/DigitalCoast/lidar1_z/geoid12a/data/56/supplemental/
      1 NOAA CSC (originator) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce ocm.info@noaa.gov originator
      1 NOAA CSC (publisher) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce ocm.info@noaa.gov publisher
      1 NOAA CSC(distributor) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce ocm.info@noaa.gov distributor
      1 NOAA CSC (processor) DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce ocm.info@noaa.gov processor
      1 South Carolina Department of Natural Resources (originator) Dr. Jim Scurry South Carolina Department of Natural Resources Technology Development Program Director scurryj@dnr.sc.gov originator
      1 South Carolina Department of Natural Resources (pointOfContact) Dr. Jim Scurry South Carolina Department of Natural Resources Technology Development Program Director scurryj@dnr.sc.gov pointOfContact
      1 EPSG Registry European Petroleum Survey Group publisher http://www.epsg-registry.org/
      3 Mark Meade Photo Science, Inc processor
      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 Mike Sutherland (processor) Mike Sutherland DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce mike.sutherland@noaa.gov processor
      Top

      CI_OnlineResource

      Count Component Linkage Name Description Function
      1 ftp://csc.noaa.gov/pub/DigitalCoast/lidar1_z/geoid12a/data/56/supplemental/ Where it exists, the supplemental information folder will include acquisition and QA/QC reports, a footprint of the spatial extent of the data and other relevant related information 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 -81.283784 -79.697630 33.182564 32.035599 2006-12-27 2007-03-23
      Top

      EX_GeographicBoundingBox

      Count Component West East North South
      1 -81.283784 -79.697630 33.182564 32.035599
      Top

      EX_TemporalExtent

      Count Component Start End
      1 2006-12-27 2007-03-23
      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 Dataset Supplemental Information crossReference
      Top

      LE_Source or LI_Source

      none found
      Top

      LE_ProcessStep or LI_ProcessStep

      Count Component DateTime Description
      1 2007-03-23T00:00:00 JASPER COUNTY: Utilizing Photo Science's two ALS-50 LiDAR sensors, data was collected to cover Jasper County, South Carolina. Data was collected in a total of 111 flightlines at a pulse rate of 75,000 points per second. COLLETON COUNTY: Utilizing Photo Science's two ALS-50 LiDAR sensors, data was collected to cover Colleton County, South Carolina. Data was collected in a total of 160 flightlines at a pulse rate of 75,000 points per second. CHARLESTON COUNTY: Utilizing Photo Science's two ALS-50 LiDAR sensors, data was collected to cover Charleston County, South Carolina. Data was collected in a total of 77 flightlines at a pulse rate of 75,000 points per second.
      1 2007-10-30T00:00:00 Raw LiDAR data (collected as Process Step 1) was processed to create a bare ground surface. Process included calibration of LiDAR data to remove systematic errors (utilizing Leica's ALS Processor software), adjustment of elevation data to control positions (utilizing TerraScan software for control comparisons and adjustments), and both automatic and manual editing to correctly classify ground and non-ground data (utilizing TerraScan and TerraModeler software). In addition, QC steps were performed before and after processing. QC steps included line-to-line vertical comparisons and coverage checks, and were performed with TerraScan and GeoCue software.
      1 2007-10-30T00:00:00 Following bare ground surface creation (Process Step 2),Photo Science utilized the resulting dataset as a source for collection of hydrographic features, including double-line drains, single-line drains, and bodies of water. Hydro features were collected from bare ground surface models in MicroStation v8 software. After collection was complete, Photo Science adjusted elevation of all hydro features to ensure proper monotonicity using FME and proprietary software.
      1 2008-03-21T00: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 Digital Coast: 1. The data were converted from UTM (Zone 17) coordinates to geographic coordinates. 2. The data were converted from orthometric elevations (NAVD88) to ellipsoidal heights using Geoid 03. 3. The LAS data were sorted by latitude and the headers were updated. 4. The data were converted to LAZ format.
      1 2014-02-12T00: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