2018 - 2020 USGS Lidar: Florida Peninsular FDEM
OCM Partners
Data Set
(DS)
| ID: 69496
| Published / External
Created: 2023-03-27
|
Last Modified: 2025-03-06
Project (PRJ) | ID: 49401
ID: 69496
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
| * » Title | 2018 - 2020 USGS Lidar: Florida Peninsular FDEM |
|---|---|
| Short Name | |
| * Status | Completed |
| Creation Date | 2018 |
| Revision Date | |
| • Publication Date | 2020 |
| * » Abstract |
Product: This project was designed to acquire and produce QL1 lidar data to support the Florida Division of Emergency Management (FDEM) "Florida Statewide Lidar" initiative. These lidar data are processed Classified LAS 1.4 files, formatted to individual 5000 ft x 5000 ft tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. Geographic Extent: The project area covers 35 counties in peninsular Florida. A total of 39,217 tiles were produced for the project, providing approximately 34,950 sq. miles of coverage. Dataset Description: The Florida Peninsular project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1.3. The data were developed based on a horizontal projection/datum of NAD83(2011) / Florida North/East/West (ftUS), Foot US and vertical datum of NAVD88 GEOID12B, Foot US. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to individual 5000 ft x 5000 ft tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 5000 ft x 5000 ft schema. Continuous breaklines were produced in Esri file geodatabase format. Ground Conditions: LiDAR was collected in 2018, 2019 and 2020, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications and meet ASPRS vertical accuracy guidelines ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. Additional independent accuracy checkpoints were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data. This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services for all counties except for Collier. The DAV is using an on prem version of Collier County. |
| * Purpose |
To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create intensity images, breaklines and raster DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 2.5 feet cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. |
| Notes | |
| Other Citation Details | |
| • Supplemental Information |
Contract No. G16PC00016, Task Order No. 140G0218F0443; CONTRACTOR: Quantum Spatial, Inc. The following are the USGS lidar fields in JSON: {
"ldrinfo" : {
"ldrspec" : "USGS-NGP Base Specification v1.3", "ldrsens" : "Leica ALS 80", "ldrmaxnr" : "unlimited", "ldrnps" : "0.316", "ldrdens" : "10.0", "ldranps" : "0.309", "ldradens" : "10.47", "ldrfltht" : "1400", "ldrfltsp" : "150", "ldrscana" : "20", "ldrscanr" : "52", "ldrpulsr" : "585", "ldrpulsd" : "2.5", "ldrpulsw" : "0.31", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.22", "ldrswatw" : "1019.0", "ldrswato" : "60", "ldrgeoid" : "GEOID12B", "ldrcrs" : "NAD83(2011) / Florida East (ftUS), Foot US" }, "ldraccur" : {
"ldrchacc" : "0", "rawnva" : "0", "rawnvan" : "0", "clsnva" : "0", "clsnvan" : "0", "clsvva" : "0", "clsvvan" : "0" }, "lasinfo" : {
"lasver" : "1.4", "lasprf" : "6", "laswheld" : "Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.", "lasolap" : "Swath "overage" points were not classified in these files.", "lasintr" : "16", "lasclass" : {
"clascode" : "1", "clasitem" : "Processed, but Unclassified" }, "lasclass" : {
"clascode" : "2", "clasitem" : "Bare-Earth Ground" }, "lasclass" : {
"clascode" : "6", "clasitem" : "Buildings" }, "lasclass" : {
"clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : {
"clascode" : "9", "clasitem" : "Water" }, "lasclass" : {
"clascode" : "17", "clasitem" : "Bridge Decks" }, "lasclass" : {
"clascode" : "18", "clasitem" : "High Noise" }, "lasclass" : {
"clascode" : "20", "clasitem" : "Ignored Ground" } }} |
| DOI (Digital Object Identifier) | |
| DOI Registration Authority | |
| DOI Issue Date |
Keywords
Theme Keywords
| Thesaurus | Keyword |
|---|---|
| Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION |
| Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
| ISO 19115 Topic Category | elevation |
Temporal Keywords
| Thesaurus | Keyword |
|---|---|
* Spatial Keywords
| Thesaurus | Keyword |
|---|---|
| Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA |
| Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > FLORIDA |
| Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > LAND SURFACE |
Stratum Keywords
| Thesaurus | Keyword |
|---|---|
Instrument Keywords
| Thesaurus | Keyword |
|---|---|
Platform Keywords
| Thesaurus | Keyword |
|---|---|
| Global Change Master Directory (GCMD) Platform Keywords | Airplane > Airplane |
Physical Location
| • » Organization | Office for Coastal Management |
|---|---|
| • » City | Charleston |
| • » State/Province | SC |
| • Country | |
| • » Location Description |
Data Set Information
| * Data Set Scope Code | Data Set |
|---|---|
| • Data Set Type | Elevation |
| • Maintenance Frequency | None Planned |
| Maintenance Note | |
| » Data Presentation Form | Model (digital) |
| • Entity Attribute Overview | |
| Entity Attribute Detail Citation | |
| Entity Attribute Detail URL | |
| Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. |
| Data Set Credit | Florida Dept. of Emergency Management (FDEM), USGS |
Support Roles
| * » Support Role | Data Steward |
|---|---|
| * » Date Effective From | 2021 |
| Date Effective To | |
| Organization | NOAA Office for Coastal Management (NOAA/OCM) |
| Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
| Email Address | coastal.info@noaa.gov |
| Phone | (843) 740-1202 |
| Fax | |
| Mobile | |
| URL | https://coast.noaa.gov |
| Business Hours | |
| Contact Instructions |
| * » Support Role | Distributor |
|---|---|
| * » Date Effective From | 2021 |
| Date Effective To | |
| Organization | NOAA Office for Coastal Management (NOAA/OCM) |
| Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
| Email Address | coastal.info@noaa.gov |
| Phone | (843) 740-1202 |
| Fax | |
| Mobile | |
| URL | https://coast.noaa.gov |
| Business Hours | |
| Contact Instructions |
| * » Support Role | Distributor |
|---|---|
| * » Date Effective From | 2020 |
| Date Effective To | |
| Organization | U.S. Geological Survey |
| Address |
12201 Sunrise Valley Drive Reston, VA 20191 USA |
| Email Address | |
| Phone | |
| Fax | |
| Mobile | |
| URL | https://usgs.gov |
| Business Hours | |
| Contact Instructions |
| * » Support Role | Metadata Contact |
|---|---|
| * » Date Effective From | 2021 |
| Date Effective To | |
| Organization | NOAA Office for Coastal Management (NOAA/OCM) |
| Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
| Email Address | coastal.info@noaa.gov |
| Phone | (843) 740-1202 |
| Fax | |
| Mobile | |
| URL | https://coast.noaa.gov |
| Business Hours | |
| Contact Instructions |
| * » Support Role | Point of Contact |
|---|---|
| * » Date Effective From | 2021 |
| Date Effective To | |
| Organization | NOAA Office for Coastal Management (NOAA/OCM) |
| Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
| Email Address | coastal.info@noaa.gov |
| Phone | (843) 740-1202 |
| Fax | |
| Mobile | |
| URL | https://coast.noaa.gov |
| Business Hours | |
| Contact Instructions |
| * » Support Role | |
|---|---|
| * » Date Effective From | |
| Date Effective To | |
| * » Contact | |
| * Contact Instructions |
| * » Support Role | |
|---|---|
| * » Date Effective From | |
| Date Effective To | |
| * » Contact | |
| * Contact Instructions |
| * » Support Role | |
|---|---|
| * » Date Effective From | |
| Date Effective To | |
| * » Contact | |
| * Contact Instructions |
Extents
| Currentness Reference | Ground Condition |
|---|
Extent Group 1
| Extent Description |
|---|
Extent Group 1 / Geographic Area 1
| * » W° Bound | -84.07 |
|---|---|
| * » E° Bound | -79.95 |
| * » N° Bound | 30.9 |
| * » S° Bound | 25.83 |
| * » Description |
Extent Group 1 / Vertical Extent
| EPSG Code | |
|---|---|
| Vertical Minimum | |
| Vertical Maximum |
Extent Group 1 / Time Frame 1
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-05 |
| End | 2019-12-03 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Alachua County |
Extent Group 1 / Time Frame 2
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-28 |
| End | 2018-12-18 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Nassau County |
Extent Group 1 / Time Frame 3
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-26 |
| End | 2019-01-21 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Collier County |
Extent Group 1 / Time Frame 4
| * » Time Frame Type | Discrete |
|---|---|
| * » Start | 2020-01-15 |
| End | |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Date of collection for Key Biscayne (Miami-Dade County) |
Extent Group 1 / Time Frame 5
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-07 |
| End | 2019-03-04 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Brevard County |
Extent Group 1 / Time Frame 6
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-28 |
| End | 2018-12-28 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Duval County |
Extent Group 1 / Time Frame 7
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-28 |
| End | 2019-03-18 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Clay County |
Extent Group 1 / Time Frame 8
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2019-11-25 |
| End | 2020-01-25 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Columbia County |
Extent Group 1 / Time Frame 9
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-30 |
| End | 2019-01-10 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for DeSoto County |
Extent Group 1 / Time Frame 10
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2019-03-24 |
| End | 2020-01-25 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Dixie County |
Extent Group 1 / Time Frame 11
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-12 |
| End | 2019-04-28 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Glades County |
Extent Group 1 / Time Frame 12
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-30 |
| End | 2020-01-20 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Hardee County |
Extent Group 1 / Time Frame 13
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-11 |
| End | 2019-01-16 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Hendry County |
Extent Group 1 / Time Frame 14
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-06 |
| End | 2020-01-06 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Highlands County |
Extent Group 1 / Time Frame 15
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-24 |
| End | 2020-01-06 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Okeechobee County |
Extent Group 1 / Time Frame 16
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-30 |
| End | 2019-03-24 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for St. Johns County |
Extent Group 1 / Time Frame 17
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-04 |
| End | 2019-04-12 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Orange County |
Extent Group 1 / Time Frame 18
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-24 |
| End | 2019-04-25 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Martin County |
Extent Group 1 / Time Frame 19
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-30 |
| End | 2019-01-10 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Sarasota County |
Extent Group 1 / Time Frame 20
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-30 |
| End | 2020-01-20 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Manatee County |
Extent Group 1 / Time Frame 21
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-26 |
| End | 2020-01-21 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Madison County |
Extent Group 1 / Time Frame 22
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2019-12-21 |
| End | 2020-01-17 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Suwannee County |
Extent Group 1 / Time Frame 23
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-25 |
| End | 2020-01-22 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Union County |
Extent Group 1 / Time Frame 24
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-28 |
| End | 2020-01-22 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Baker County |
Extent Group 1 / Time Frame 25
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-28 |
| End | 2020-01-21 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Bradford County |
Extent Group 1 / Time Frame 26
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-06 |
| End | 2019-01-10 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Charlotte County |
Extent Group 1 / Time Frame 27
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-05 |
| End | 2020-01-08 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection Gilchrist County |
Extent Group 1 / Time Frame 28
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2019-01-25 |
| End | 2019-03-01 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Indian River County |
Extent Group 1 / Time Frame 29
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-24 |
| End | 2019-04-24 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for St. Lucie County |
Extent Group 1 / Time Frame 30
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2019-12-19 |
| End | 2020-01-18 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Hamilton County |
Extent Group 1 / Time Frame 31
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2019-01-05 |
| End | 2019-04-15 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Palm Beach County |
Extent Group 1 / Time Frame 32
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2019-01-25 |
| End | 2020-01-25 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Taylor County |
Extent Group 1 / Time Frame 33
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2019-11-30 |
| End | 2020-01-25 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Date of collection for Lafayette County |
Extent Group 1 / Time Frame 34
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-11-30 |
| End | 2020-01-20 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Polk County |
Extent Group 1 / Time Frame 35
| * » Time Frame Type | Range |
|---|---|
| * » Start | 2018-12-07 |
| End | 2019-04-12 |
| Alternate Start As Of Info | |
| Alternate End As Of Info | |
| Description |
Dates of collection for Osceola County |
Spatial Information
Spatial Resolution
| Angular Distance | |
|---|---|
| Angular Distance Units | |
| Horizontal Distance | |
| Horizontal Distance Units | |
| Vertical Distance | |
| Vertical Distance Units | |
| Equivalent Scale Denominator | |
| Level of Detail Description |
Spatial Representation
| Grid Representation Used? | No |
|---|---|
| Vector Representation Used? | Yes |
| Text / Table Representation Used? | No |
| TIN Representation Used? | No |
| Stereo Model Representation Used? | No |
| Video Representation Used? | No |
Grid Representation
| Dimension Count | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Cell Geometry | |||||||||||||
| Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Vector Representation
| Topology Level | |
|---|---|
| Complex Object Present? | |
| Complex Object Count | |
| Composite Object Present? | |
| Composite Object Count | |
| Curve Object Present? | |
| Curve Object Count | |
| Point Object Present? | |
| Point Object Count | |
| Solid Object Present? | |
| Solid Object Count | |
| Surface Object Present? | |
| Surface Object Count |
Reference Systems
Reference System
| EPSG Code | EPSG:3857 | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Reference System
| EPSG Code | EPSG:5703 | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Reference System
| EPSG Code | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Access Information
| Data License | |
|---|---|
| Data License URL | |
| Data License Statement | |
| * » Security Class | Unclassified |
| * Security Classification System | |
| Security Handling Description | |
| • Data Access Policy | |
| » Data Access Procedure |
Data is available online for bulk and custom downloads. |
| • » Data Access Constraints |
None |
| • Data Use Constraints |
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. |
| Metadata Access Constraints | |
| Metadata Use Constraints |
Distribution Information
| Start Date | 2021-04-12 |
|---|---|
| End Date | Present |
| » Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9275/details/9275 |
| Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2021 - Present) |
| File Name | Customized Download |
| Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. |
| File Date/Time | |
| File Type (Deprecated) | Zip |
| Distribution Format | |
| File Size | |
| Application Version | |
| Compression | Zip |
| Review Status |
| Start Date | 2021 |
|---|---|
| End Date | Present |
| » Download URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Peninsular_FDEM_2018_D19_DRRA/ |
| Distributor | U.S. Geological Survey (2020 - Present) |
| File Name | Bulk Download |
| Description |
Bulk download of data files in LAZ format, Florida State Plane North/East/West NAD83(2011) coordinates and orthometric heights in feet. |
| File Date/Time | |
| File Type (Deprecated) | LAZ |
| Distribution Format | LAS/LAZ - LASer |
| File Size | |
| Application Version | |
| Compression | Zip |
| Review Status |
| Start Date | |
|---|---|
| End Date | |
| » Download URL | |
| Distributor | |
| File Name | |
| Description | |
| File Date/Time | |
| File Type | |
| FGDC Content Type | |
| File Size | |
| Application Version | |
| Compression | |
| Review Status |
| Start Date | |
|---|---|
| End Date | |
| » Download URL | |
| Distributor | |
| File Name | |
| Description | |
| File Date/Time | |
| File Type | |
| FGDC Content Type | |
| File Size | |
| Application Version | |
| Compression | |
| Review Status |
| Start Date | |
|---|---|
| End Date | |
| » Download URL | |
| Distributor | |
| File Name | |
| Description | |
| File Date/Time | |
| File Type | |
| FGDC Content Type | |
| File Size | |
| Application Version | |
| Compression | |
| Review Status |
Archive Information
| Location | |
|---|---|
| File Identifier | |
| File Name | |
| URL | |
| Description | |
| DOI | |
| Archive Date | |
| Archive Update Frequency |
| Location | |
|---|---|
| File Identifier | |
| File Name | |
| URL | |
| Description | |
| DOI | |
| Archive Date | |
| Archive Update Frequency |
| Location | |
|---|---|
| File Identifier | |
| File Name | |
| URL | |
| Description | |
| DOI | |
| Archive Date | |
| Archive Update Frequency |
URLs
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/ |
|---|---|
| Name | USGS Additional Info |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the reports, breaklines, metadata, spatial metadata, vertical accuracy information, and shapefiles. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Alachua_2018/reports/Alachua_County_Report.pdf |
|---|---|
| Name | Lidar Report - Alachua County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Alachua County lidar report. |
| URL | https://coast.noaa.gov/dataviewer/ |
|---|---|
| Name | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
| URL Type | Online Resource |
| File Resource Format | HTML |
| Description |
The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Baker_2018/reports/Baker_County_Report.pdf |
|---|---|
| Name | Lidar Report - Baker County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Baker County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Bradford_2018/reports/Bradford_County_Report.pdf |
|---|---|
| Name | Lidar Report - Bradford County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Bradford County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Brevard_2018/reports/Brevard_County_Report.pdf |
|---|---|
| Name | Lidar Report - Brevard County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Brevard County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Charlotte_2018/reports/Charlotte_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Charlotte County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Charlotte County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Clay_2018/reports/Clay_County_Report.pdf |
|---|---|
| Name | Lidar Report - Clay County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Clay County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Collier_2018/reports/Collier_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Collier County |
| URL Type | |
| File Resource Format | |
| Description |
Link to the Collier County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Columbia_2018/reports/Columbia_County_Report.pdf |
|---|---|
| Name | Lidar Report - Columbia County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Columbia County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Desoto_2018/reports/Desoto_County_Report.pdf |
|---|---|
| Name | Lidar Report - DeSoto County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the DeSoto County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Dixie_2018/reports/Dixie_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Dixie County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Dixie County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Duval_2018/reports/Duval_County_Report.pdf |
|---|---|
| Name | Lidar Report - Duval County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Duval County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Gilchrist_2018/reports/Gilchrist_County_Report.pdf |
|---|---|
| Name | Lidar Report - Gilchrist County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Gilchrist County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Glades_2018/reports/Glades_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Glades County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Glades County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Hamilton_2018/reports/Hamilton_County_Report.pdf |
|---|---|
| Name | Lidar Report - Hamilton County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Hamilton County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Hardee_2018/reports/Hardee_County_Report.pdf |
|---|---|
| Name | Lidar Report - Hardee County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Hardee County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Hendry_2018/reports/Hendry_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Hendry County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Hendry County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Highlands_2018/reports/Highlands_County_Report.pdf |
|---|---|
| Name | Lidar Report - Highlands County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Highlands County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_IndianRiver_2018/reports/Indian_River_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Indian River County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Indian River County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_KeyBiscayne_2020/reports/Key_Biscayne_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Key Biscayne |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Key Biscayne lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Lafayette_2018/reports/Lafayette_County_Report.pdf |
|---|---|
| Name | Lidar Report - Lafayette County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Lafayette County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Madison_2018/reports/Madison_County_Report.pdf |
|---|---|
| Name | Lidar Report - MadisonCounty |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Madison County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Manatee_2018/reports/Manatee_County_Report.pdf |
|---|---|
| Name | Lidar Report - Manatee County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Manatee County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Martin_2018/reports/Martin_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Martin County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Martin County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Nassau_2018/reports/Nassau_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Nassau County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Nassau County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Okeechobee_2018/reports/Okeechobee_County_Report.pdf |
|---|---|
| Name | Lidar Report - Okeechobee County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Okeechobee County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Orange_2018/reports/Orange_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Orange County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Orange County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Osceola_2018/reports/Osceola_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Osceola County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Osceola County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_PalmBeach_2019/reports/Palm_Beach_County_Report.pdf |
|---|---|
| Name | Lidar Report - Palm Beach County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Palm Beach County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Polk_2018/reports/Polk_County_Report.pdf |
|---|---|
| Name | Lidar Report - Polk County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Polk County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Sarasota_2018/reports/Sarasota_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - Sarasota County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Sarasota County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_StJohns_2018/reports/StJohns_County_Report.pdf |
|---|---|
| Name | Lidar Report - St. Johns County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the St. Johns County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_StLucie_2018/reports/St_Lucie_County_Report_USGS.pdf |
|---|---|
| Name | Lidar Report - St. Lucie County |
| URL Type | |
| File Resource Format | |
| Description |
Link to the St. Lucie County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Suwannee_2018/reports/Suwannee_County_Report.pdf |
|---|---|
| Name | Lidar Report - Suwannee County |
| URL Type | |
| File Resource Format | |
| Description |
Link to the Suwannee County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Taylor_2018/reports/Taylor_County_Report.pdf |
|---|---|
| Name | Lidar Report - Taylor County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Taylor County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Union_2018/reports/Union_County_Report.pdf |
|---|---|
| Name | Lidar Report - Union County |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the Union County lidar report. |
| URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Peninsular_FDEM_2018_D19_DRRA/USGS_FL_Peninsular_FDEM_2018_D19_DRRA_Project_Report.pdf |
|---|---|
| Name | USGS Project Report |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to the USGS Project Report that provides information about the project, vertical accuracy results, and the point classes and sensors used. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Alachua_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Alachua County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Baker_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Baker County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Bradford_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Bradford County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Brevard_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Brevard County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Charlotte_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Charlotte County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Clay_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Clay County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Columbia_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Columbia County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_DeSoto_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - DeSoto County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Dixie_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Dixie County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Duval_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Duval County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Gilchrist_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Gilchrist County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Glades_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Glades County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Hamilton_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Hamilton County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Hardee_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Hardee County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Hendry_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Hendry County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Highlands_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Highlands County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_IndianRiver_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Indian River County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_KeyBiscayne_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Key Biscayne County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Lafayette_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Lafayette County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Madison_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Madison County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Manatee_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Manatee County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Martin_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Martin County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Nassau_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Nassau County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Okeechobee_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Okeechobee County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Orange_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Orange County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Osceola_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Osceola County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_PalmBeach_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Palm Beach County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Polk_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Polk County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Sarasota_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Sarasota County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_StJohns_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - St. Johns County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_StLucie_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - St. Lucie County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Suwannee_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Suwannee County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Taylor_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Taylor County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Union_2018/ept.json |
|---|---|
| Name | USGS Entwine Point Tile (EPT) - Union County |
| URL Type | Online Resource |
| File Resource Format | json |
| Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
| URL | https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Alachua_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Baker_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Bradford_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Brevard_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Charlotte_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Clay_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Columbia_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Desoto_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Dixie_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Duval_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Gilchrist_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Glades_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Hamilton_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Hardee_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Hendry_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Highlands_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_IndianRiver_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_KeyBiscayne_2020/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Lafayette_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Madison_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Manatee_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Martin_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Nassau_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Okeechobee_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Orange_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Osceola_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_PalmBeach_2019/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Polk_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Sarasota_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_StJohns_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_StLucie_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Suwannee_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Taylor_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Union_2018/ept.json%22] |
|---|---|
| Name | USGS 3D View |
| URL Type | Online Resource |
| File Resource Format | |
| Description |
Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer. |
| URL | |
|---|---|
| Name | |
| URL Type | |
| File Resource Format | |
| Description |
| URL | |
|---|---|
| Name | |
| URL Type | |
| File Resource Format | |
| Description |
| URL | |
|---|---|
| Name | |
| URL Type | |
| File Resource Format | |
| Description |
Activity Log
| Activity Time | |
|---|---|
| Activity Type | |
| Responsible Party | |
| Description |
| Activity Time | |
|---|---|
| Activity Type | |
| Responsible Party | |
| Description |
| Activity Time | |
|---|---|
| Activity Type | |
| Responsible Party | |
| Description |
Issues
| Issue Date | |
|---|---|
| Author | |
| Issue |
| Issue Date | |
|---|---|
| Author | |
| Issue |
| Issue Date | |
|---|---|
| Author | |
| Issue |
Technical Environment
| Description |
MicroStation Version 8; TerraScan Version 18; TerraModeler Version 18; GeoCue Version 2017.1.14.1; Esri ArcGIS 10.3; Global Mapper 19; Leica Cloud Pro 1.2.4; Windows 10 Operating System \\point_cloud\tilecls\*.las |
|---|
Data Quality
| Representativeness | |
|---|---|
| Accuracy | |
| Analytical Accuracy | |
| Horizontal Positional Accuracy | |
| Vertical Positional Accuracy |
The project specifications require that only Non-Vegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. The required accuracy (ACCz) is: 19.6 cm (0.64 ft) at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm (0.33 ft) in the bare earth and urban land cover classes. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control points. AccuracyZ has been tested to meet 19.6 cm (0.64 ft) or better Non-Vegetated Vertical Accuracy at 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. USGS Determined Vertical Accuracy: Non-Vegetated Vertical Accuracy (NVA) = 11.13 cm at 95% Confidence Level or 5.7 cm RMSE Vegetated Vertical Accuracy (VVA) = 18.01 cm at 95th Percentile |
| Quantitation Limits | |
| Bias | |
| Comparability | |
| Completeness Measure | |
| Precision | |
| Analytical Precision | |
| Field Precision | |
| Sensitivity | |
| Detection Limit | |
| Completeness Report |
These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and the data pass Non-Vegetated Vertical Accuracy specifications. |
| Conceptual Consistency |
Data cover the entire area specified for this project. |
| » Quality Control Procedures Employed |
Data Management
| » Have Resources for Management of these Data Been Identified? | Yes |
|---|---|
| » Approximate Percentage of Budget for these Data Devoted to Data Management | Unknown |
| » Do these Data Comply with the Data Access Directive? | Yes |
| » Is Access to the Data Limited Based on an Approved Waiver? | |
| » If Distributor (Data Hosting Service) is Needed, Please Indicate | |
| » Approximate Delay Between Data Collection and Dissemination | |
| » If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed | |
| » Actual or Planned Long-Term Data Archive Location | NCEI-CO |
| » Approximate Delay Between Data Collection and Archiving | |
| » How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
Data is backed up to tape and to cloud storage. |
Lineage
| » Lineage Statement |
The lidar data were collected for the Florida Department of Emergency Management (FDEM) and provided to the USGS. The NOAA Office for Coastal Management (OCM) ingested references for 34/35 counties that make up this dataset, to the USGS Entwine Point Tile (EPT) files hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container. For Collier County, the DAV is accessing on-prem files. |
|---|
Sources
| Citation Title | Ground Control for the Florida Peninsular FDEM 2018 D19 DRRA Project |
|---|---|
| Contact Role Type | Originator |
| Contact Type | Organization |
| Contact Name | Quantum Spatial Inc. |
| Publish Date | 2019-12-06 |
| Extent Type | Discrete |
| Extent Start Date/Time | 2019-07-12 |
| Extent End Date/Time | |
| Scale Denominator | |
| Citation URL | |
| Citation URL Name | |
| Citation URL Description | |
| Source Contribution |
This data source was used (along with airborne GPS/IMU data) to georeference the LiDAR point cloud data. |
| Citation Title | USGS AWS Entwine Point Tiles |
|---|---|
| Contact Role Type | Publisher |
| Contact Type | Organization |
| Contact Name | USGS |
| Publish Date | |
| Extent Type | |
| Extent Start Date/Time | |
| Extent End Date/Time | |
| Scale Denominator | |
| Citation URL | https://usgs.entwine.io/ |
| Citation URL Name | USGS / Entwine |
| Citation URL Description |
This site provides all the EPT links to the 34 out of the 35 datasets that make up this project. At the time of processing, Collier County was not yet available by EPT. |
| Source Contribution |
| Citation Title | |
|---|---|
| Contact Role Type | |
| Contact Type | |
| Contact Name | |
| Publish Date | |
| Extent Type | |
| Extent Start Date/Time | |
| Extent End Date/Time | |
| Citation URL | |
| Citation URL Name | |
| Citation URL Description | |
| Scale Denominator |
| Citation Title | |
|---|---|
| Contact Role Type | |
| Contact Type | |
| Contact Name | |
| Publish Date | |
| Extent Type | |
| Extent Start Date/Time | |
| Extent End Date/Time | |
| Citation URL | |
| Citation URL Name | |
| Citation URL Description | |
| Scale Denominator |
| Citation Title | |
|---|---|
| Contact Role Type | |
| Contact Type | |
| Contact Name | |
| Publish Date | |
| Extent Type | |
| Extent Start Date/Time | |
| Extent End Date/Time | |
| Citation URL | |
| Citation URL Name | |
| Citation URL Description | |
| Scale Denominator |
Process Steps
| Process Step Number | 1 |
|---|---|
| » Description |
Raw Data and Boresight Processing: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used Quantum Spatial, Inc. proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie, and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technicians then analyzed the results and made any necessary additional adjustment until it was acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps matched for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. |
| Process Date/Time | 2019-12-16 00:00:00 |
| Process Contact | |
| Phone (Voice) | |
| Email Address | |
| Source |
| Process Step Number | 2 |
|---|---|
| » Description |
LAS Point Classification: The point classification was performed as described below. The bare earth surface was manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface was finalized, it was then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All data were manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Quantum Spatial, Inc. proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information. |
| Process Date/Time | 2019-12-16 00:00:00 |
| Process Contact | |
| Phone (Voice) | |
| Email Address | |
| Source |
| Process Step Number | 3 |
|---|---|
| » Description |
The NOAA Office for Coastal Management (OCM) downloaded data sets from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/ The data sets downloaded were: FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Collier_2018/ Number of files: 530 FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_KeyBiscayne_2020/ Number of files: 14 FL_Peninsular_FDEM_2018_D19_DRRA/FL_Peninsular_FDEM_Nassau_2018/ Number of files: 763 These files were processed to the Data Access Viewer (DAV) and https. Additional areas will be downloaded, processed, and added to this data set as they are made available from USGS. The data were in FL State Plane East (NAD83 2011), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. The data were classified as: 1 - Unclassified, 2 - Ground, 6 - Buildings, 7 - Low Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise, 20 - Ignored Ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 6, 7, 9, 17, 18, 20. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model b. Convert the Collier, Key Biscayne, and Nassau laz files from FL State Plane East Zone 0901 (NAD83 2011), US survey foot coordinates to geographic coordinates c. Convert from vertical units of feet to meters d. Filter points outside the elevation range of -100 to 3000 feet e. Filter points outside the geographic range of the bounding coordinates of -89, 24, -79, 31 degrees f. Assign the geokeys, sort the data by gps time and zip the data to database and to https. |
| Process Date/Time | 2021-04-05 00:00:00 |
| Process Contact | Office for Coastal Management (OCM) |
| Phone (Voice) | |
| Email Address | |
| Source |
| Process Step Number | 4 |
|---|---|
| » Description |
With the release of the remainder of the counties in EPT format, the on prem versions of Nassau County and Key Biscayne were removed from the database and the USGS EPT versions were leveraged instead. Collier County was not available as EPT at this time and so the data for it was retained on prem. The dataset was however, converted from ellipsoid elevations to NAVD88 (GEOID12B) elevations in order to be in the same vertical datum as the leveraged USGS EPT county versions. |
| Process Date/Time | 2023-03-03 00:00:00 |
| Process Contact | Office for Coastal Management (OCM) |
| Phone (Voice) | |
| Email Address | |
| Source |
| Process Step Number | 5 |
|---|---|
| » Description |
Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and the vertical units were converted to meters (NAVD88 Geoid12B). |
| Process Date/Time | 2021-01-01 00:00:00 |
| Process Contact | U.S. Geological Survey |
| Phone (Voice) | |
| Email Address | |
| Source |
| Process Step Number | 6 |
|---|---|
| » Description |
The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. At the time of processing, Collier County was not yet available via EPT. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container. These are the AWS URLs being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Alachua_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Baker_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Bradford_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Brevard_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Charlotte_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Clay_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Columbia_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Desoto_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Dixie_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Duval_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Gilchrist_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Glades_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Hamilton_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Hardee_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Hendry_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Highlands_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_IndianRiver_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_KeyBiscayne_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Lafayette_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Madison_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Manatee_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Martin_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Nassau_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Okeechobee_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Orange_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Osceola_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_PalmBeach_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Polk_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Sarasota_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_StJohns_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_StLucie_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Suwannee_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Taylor_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_Peninsular_FDEM_Union_2018/ept.json |
| Process Date/Time | 2023-03-24 00:00:00 |
| Process Contact | Office for Coastal Management (OCM) |
| Phone (Voice) | |
| Email Address | |
| Source |
| Process Step Number | |
|---|---|
| » Description | |
| Process Date/Time | |
| Process Contact | |
| Phone (Voice) | |
| Email Address | |
| Source |
| Process Step Number | |
|---|---|
| » Description | |
| Process Date/Time | |
| Process Contact | |
| Phone (Voice) | |
| Email Address | |
| Source |
| Process Step Number | |
|---|---|
| » Description | |
| Process Date/Time | |
| Process Contact | |
| Phone (Voice) | |
| Email Address | |
| Source |
Acquisition Information
Instruments
| Instrument Unavailable Reason |
|---|
| Identifier | |
|---|---|
| Docucomp UUID | |
| Instrument / Gear | |
| Instrument Type | |
| Description |
| Identifier | |
|---|---|
| Docucomp UUID | |
| Instrument / Gear | |
| Instrument Type | |
| Description |
| Identifier | |
|---|---|
| Docucomp UUID | |
| Instrument / Gear | |
| Instrument Type | |
| Description |
Platforms
| Platform Unavailable Reason |
|---|
| Identifier | |||||||
|---|---|---|---|---|---|---|---|
| Docucomp UUID | |||||||
| Description | |||||||
Mounted Instruments |
|||||||
|
|||||||
| Identifier | |||||||
|---|---|---|---|---|---|---|---|
| Docucomp UUID | |||||||
| Description | |||||||
Mounted Instruments |
|||||||
|
|||||||
| Identifier | |||||||
|---|---|---|---|---|---|---|---|
| Docucomp UUID | |||||||
| Description | |||||||
Mounted Instruments |
|||||||
|
|||||||
FAQs
| Date | |
|---|---|
| Author | |
| Question | |
| Answer |
Child Items
Rubric scores updated every 15m
| Score | Type | Title |
|---|---|---|
Related Items
| Item Type | Relationship Type | Title |
|---|---|---|
| Data Set (DS) | Cross Reference |
2018 - 2019 USGS Lidar: Florida Peninsular |
Catalog Details
| Catalog Item ID | 69496 |
|---|---|
| Metadata Record Created By | Rebecca Mataosky |
| Metadata Record Created | 2023-03-27 14:07+0000 |
| Metadata Record Last Modified By | Rebecca Mataosky |
| » Metadata Record Last Modified | 2025-03-06 20:58+0000 |
| Metadata Record Published | 2023-03-31 |
| Owner Org | OCMP |
| Metadata Publication Status | Published Externally |
| Do Not Publish? | N |
| Metadata Workflow State | Published / External |
| Metadata Last Review Date | 2022-03-16 |
| Metadata Review Frequency | 1 Year |
| Metadata Next Review Date | 2023-03-16 |
| Tags |
|---|