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

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 St. Johns County, Florida Lidar This dataset is the bare earth lidar data for St. Johns County, Florida, acquired in early January and February of 2004. This data was collected to develop comprehensive countywide base mapping and perform other GIS enhancements to support master drainage planning, transportation planning, preliminary engineering and wetland preservation studies. The surveyed area included all of St. Johns County, approximately 610 square miles. Eighty-seven (87) flight lines of high density lidar data (average GSD is 3.3 feet) were obtained at an altitude of 3000 feet AGL. This data set contains only model keypoints (points that are a thinned data set that is intended to remove extraneous data such as trees and points that are deemed redundant to the final bare earth product) that are classified as ground points. As a result, there are a lower number of points than in a full mass point lidar data set; and it is recommended that the data be downloaded as points and used with a TIN (Triangulated Irregular Network) or similar algorithm to produce a bare earth surface.
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2004 St. Johns County, Florida Lidar
  • 2004-01-01
1 Lidar Final 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/fl/st_johns/2004_MTS_Final_Report_stjohns.pdf
      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 coastal.info@noaa.gov originator http://coast.noaa.gov
      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 coastal.info@noaa.gov publisher http://coast.noaa.gov
      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 coastal.info@noaa.gov distributor http://coast.noaa.gov
      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 coastal.info@noaa.gov processor http://coast.noaa.gov
      1 EPSG Registry European Petroleum Survey Group publisher http://www.epsg-registry.org/
      1 Mike Campbell St. Johns County Florida GIS St. Johns County GIS Manager gis@sjcfl.us pointOfContact
      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 Savo Slijepcevic Woolpert, Inc. Project Director savo.slijepcevic@woolpert.com processor
      1 St. Johns County, Florida Public Works Department originator
      Top

      CI_OnlineResource

      Count Component Linkage Name Description Function
      1 ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/fl/st_johns/2004_MTS_Final_Report_stjohns.pdf Lidar Final Report information
      4 http://coast.noaa.gov
      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.669173 -81.212673 30.259696 29.621896 2004-01-17 2004-02-07
      Top

      EX_GeographicBoundingBox

      Count Component West East North South
      1 -81.669173 -81.212673 30.259696 29.621896
      Top

      EX_TemporalExtent

      Count Component Start End
      1 2004-01-17 2004-02-07
      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 Final Report crossReference
      Top

      LE_Source or LI_Source

      none found
      Top

      LE_ProcessStep or LI_ProcessStep

      Count Component DateTime Description
      1 2004-01-01T00:00:00 The LiDAR data was acquired in 93 flight lines acquired in 6 sessions between January 17 and February 7, 2004 from an altitude of 3,000 feet above ground level (AGL) to provide an average ground sample distance (GSD) of 3.3 feet. Three concurrent airborne GPS base stations were used for each acquisition session. The ABGPS data were reduced using the GrafNav software package by Waypoint Consulting, Inc. The IMU data was reduced using the PosProc software package by Applanix Corporation. The initial lidar "point cloud" was derived through the ALS Post Processor software package by Leica Geosystems. The aircraft, lidar system and associated computer hardware and software are owned and operated by Woolpert LLP. Once the initial lidar "point cloud" was derived, Woolpert performed QC to look for any systematic error within the lidar flights using proprietary software. After systematic error was identified and removed, the individual lidar flights were clipped to remove overlap between adjacent flight lines and provide a homogeneous coverage over the project extents. Using the homogeneous coverage, above ground features were classified and removed using proprietary software to produce the bare-earth coverage.
      1 2008-11-03T00:00:00 The NOAA Coastal Services Center (CSC) received the files in ASCII format. The data was in Florida State Plane Projection, NAVD88 vertical datum and the vertical units of measure were feet. CSC performed the following processing to the data to make it available within Digital Coast: 1. The data were converted from Florida State Plane East, Zone 0901 coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03. 3. The vertical unit of measure for the data was converted from feet to meters. 4. The LAS data were sorted by latitude and the headers were updated.
      1 2009-07-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