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:fl2005_swfwmd_marionco_m2546

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 2005 Southwest Florida Water Management District (SWFWMD) LiDAR: Marion County Digital terrain models (DTM) provide a 3-dimensional representation of the earth's surface. The DTM for the Southwest Florida Water Management District project was used for orthoimagery rectification and to create a surface from which to interpolate contours. The DTM was derived from LIDAR data points and supplemental 3D breaklines. The files are provided in ESRI generate format (.gen).
Top

SV_Identification

none found
Top

CI_Citation

Count Component Title Date Citation Identifier
1 2005 Southwest Florida Water Management District (SWFWMD) LiDAR: Marion County
    2013-08-30
1 None
    1 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(distributor) distributor
      2 NOAA CSC (processor) processor
      1 Brian Holzworth Merrick & Company Project Manager brian.holzworth@merrick.com processor
      1 Southwest Florida Water Management District data.maps@watermatters.org pointOfContact
      1 Southwest Florida Water Management District (SWFWMD) 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[3]
      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[2]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      Mike Sutherland (processor) at: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[3]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      Top

      CI_OnlineResource

      none found
      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 -82.545499 -81.629324 29.528310 28.954762
      Top

      EX_GeographicBoundingBox

      Count Component West East North South
      1 -82.545499 -81.629324 29.528310 28.954762
      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

      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

      none found
      Top

      LE_Source or LI_Source

      none found
      Top

      LE_ProcessStep or LI_ProcessStep

      Count Component DateTime Description
      1 2005-02-11T00:00:00 LIDAR data was collected using Merrick's ALS40 sensor. The data was field-verified for complete coverage of the project area. Raw data files were parsed into manageable client-specific tiles. These tiles were then processed through automated filtering that separates the data into different classification groups: error points, ground points, and canopy/building points. The data was next taken into a graphic environment to reclassify the erroneous points that may remain in the LIDAR point cloud after auto filter. The surface was then normalized into a digital surface model (DSM). Final data extraction for the client's keypoint (statistically significant points) and canopy-building files were then generated. Using orthophotography, planimetric features were compiled as breaklines to supplement the LIDAR data. The LIDAR digital surface model was then processed with the breaklines, and contour lines were interpolated. The contours were exported from Merrick's MARS software into Microstation. The contour data was checked for spikes and holes. ASCII text files were exported from MicroStation in x,y, z format (.xyz). A custom program is used to reformat these files into ESRI generate format (.gen). A single hard breakline .gen file was produced for the entire project area for linear breaklines. A single hard replace polygon breakline .gen file was also produced for the entire project area. A model key point .gen file was produced for each tile in the project area and includes a 100' buffered area around the tile's extent. LIDAR data was collected using Merrick's ALS40 sensor. The data was field-verified for complete coverage of the project area. Raw data files were parsed into manageable client-specific tiles. These tiles were then processed through automated filtering that separates the data into different classification groups: error points, ground points, and canopy/building points. The data was next taken into a graphic environment to reclassify the erroneous points that may remain in the LIDAR point cloud after auto filter. The surface was then normalized into a digital surface model (DSM). Final data extraction for the client's keypoint (statistically significant points) and canopy-building files were then generated. Using orthophotography, planimetric features were compiled as breaklines to supplement the LIDAR data. The LIDAR digital surface model was then processed with the breaklines, and contour lines were interpolated. The contours were exported from Merrick's MARS software into Microstation. The contour data was checked for spikes and holes. ASCII text files were exported from MicroStation in x,y, z format (.xyz). A custom program is used to reformat these files into ESRI generate format (.gen). A single hard breakline .gen file was produced for the entire project area for linear breaklines. A single hard replace polygon breakline .gen file was also produced for the entire project area. A model key point .gen file was produced for each tile in the project area and includes a 100' buffered area around the tile's extent.
      1 2012-08-20T00: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 Florida State Plane West coordinates and NAVD88 (orthometric) heights in feet. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from FL State Plane West coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 03. 3. The LAS data were sorted by latitude and the headers were updated. 4. The data were converted to LAZ format.
      NOAA CSC (processor) at Xpath: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[2]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      1 2013-10-17T00: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.
      Mike Sutherland (processor) at Xpath: /gmi:MI_Metadata/gmd:dataQualityInfo[1]/gmd:DQ_DataQuality[1]/gmd:lineage[1]/gmd:LI_Lineage[1]/gmd:processStep[3]/gmi:LE_ProcessStep[1]/gmd:processor[1]
      Top

      MI_Operation

      none found
      Top

      MI_Platform

      none found
      Top

      MI_Instrument

      none found
      Top