ISO Table View Alternate Views: Get Data, FAQ, ISO Rubric, DOI Rubric, CSW, HTML, Components, XML

Metadata Identifier: gov.noaa.csc.maps:2001_NC_PhaseI_m1397

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 2001 North Carolina Floodplain Mapping Program (NCFMP) Lidar: Phase 1A (Neuse, Pasquotank, Tar-Pamlico, White Oak River Basins) This airborne LiDAR terrain mapping data was acquired January through March 2001. The data were collected for the floodplain mapping program for the state of North Carolina. The data were collected for the state in three phases: 1, 2, and 3. This metadata record describes that data that were in phase 1 of collection and fall within the Neuse, Pasquotank, Tar-Pamlico, and White Oak River Basins in central and eastern North Carolina. This area consists of 33 counties which are listed below in the Place Keywords field. The data were received by the NOAA Coastal Services Center from the U.S. Geological Survey (USGS) Center for Lidar Coordination and Knowledge (CLICK). For data storage and Digital Coast provisioning purposes, the CSC converted the data to geographic coordinates and ellipsoid (Geoid99) elevations. The data are unclassified.
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2001 North Carolina Floodplain Mapping Program (NCFMP) Lidar: Phase 1A (Neuse, Pasquotank, Tar-Pamlico, White Oak River Basins)
  • 2012-12-01
1 Geographic Names Information System
    1 Keywords
      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 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 EPSG Registry European Petroleum Survey Group publisher http://www.epsg-registry.org/
      1 Floodplain Mapping Program, North Carolina Division of Emergency Management originator
      4 Harold Rempel EarthData International of North Carolina LIDAR Production Manager hrempel@earthdata.com 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
      1 NC Floodplain Mapping Program hmorgan@ncem.org pointOfContact
      Top

      CI_OnlineResource

      Count Component Linkage Name Description Function
      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 -79.241832 -75.451653 36.563854 34.464308 2001-01-03 2001-03-23
      Top

      EX_GeographicBoundingBox

      Count Component West East North South
      1 -79.241832 -75.451653 36.563854 34.464308
      Top

      EX_TemporalExtent

      Count Component Start End
      1 2001-01-03 2001-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

      none found
      Top

      LE_Source or LI_Source

      none found
      Top

      LE_ProcessStep or LI_ProcessStep

      Count Component DateTime Description
      1 Tiling Automated filtering for point classification, Manual editing to classify points, Quality control, Removal of all points not classified as bare earth
      1 The methods used to develop these data for the North Carolina Floodplain Mapping Program are documented in LIDAR Bare Earth Mass Points and Breaklines Technical Document, available online at www.ncfloodmaps.com.
      1 2001-02-01T00:00:00 All data collection flights were initialized and finalized during periods of GPS Position Dilution of Precision greater than 4. GPS data quality was evaluated post-flight to ensure sufficient quality for LIDAR data requirements and integration. GPS base maximum allowable distance between stations was established such that no more than a 50 mile radius occurred between occupations. Swath width of terrain covered in a single flightline for inland areas at an altitude of 12,000 feet AMT was approximately 3,411 meters, coastal areas at an altitude of 8,000 feet AMT was approximately 2,274 meters. Field of View for the Leica GeoSystems Aeroscan system used was 50 degrees project wide, or 25 degrees from nadir with a maximum of 5 returns collected for each pulse. Ground distance between flightlines for inland areas at 12,000 feet AMT was approximately 2,388 meters, for coastal areas at 8,000 feet AMT was approximately 1,592 meters. Nominal post spacing for finalized Bare Earth product was 3 meters. An average of 10-20 rapid static GPS survey collected ground control points were established per base airport project wide to detect and correct horizontal and vertical bias. Typically, 3 or more flightlines of LIDAR returns were collected for each airport lift, one of which being bi-directional for use in optimizing instrument boresight angles to account for aircraft pitch, yaw and roll. All post process collection quality assurance is achieved aided by airport cross and bi-directional flightlines, entire lift cross flightlines, and the use of surveyed ground control points.
      1 2001-02-01T00:00:00 Checking for coverage and anomalies, Airport calibration, Production flightline calibration, and Removal of blunders
      1 2012-12-01T00:00:00 The lidar point data were received by the NOAA Coastal Services Center from the USGS Center for Lidar Coordination and Knowledge (CLICK) in las format. The files contained lidar elevation and intensity measurements. The data were unclassified, in State Plane coordinates, and were vertically referenced to NAVD88. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from State Plane coordinates to geographic coordinates. 2. The data were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid99. 3. The data were sorted by time. 4. The data were converted to LAZ format.
      1 2013-02-20T00: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