| 2017 USGS Topobathy Lidar: Everglades National Park, FL | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:69618 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2024-02-29T00:00:00 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) date: (CI_Date) date: 2008-11-12 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/CoordRefSystem/6318/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6318 version: 6.18.3 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters alternateTitle: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml name: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters description: Link to Geographic Markup Language (GML) description of reference system. function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) resourceProvider citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.epsg.org/ name: European Petroleum Survey Group Geodetic Parameter Registry description: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. function: (CI_OnLineFunctionCode) search role: (CI_RoleCode) publisher VerticalCS: metaDataProperty: CommonMetaData: type: vertical informationSource: OGP revisionDate: 2006-11-28 isDeprecated: false identifier: urn:ogc:def:cs:EPSG::6499 name: Vertical CS. Axis: height (H). Orientation: up. UoM: meter. remarks: Used in vertical coordinate reference systems. axis: CoordinateSystemAxis: descriptionReference: urn:ogc:def:axis-name:EPSG::9904 identifier: urn:ogc:def:axis:EPSG::114 axisAbbrev: H axisDirection: up code: urn:ogc:def:crs:EPSG::5703 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2017 USGS Topobathy Lidar: Everglades National Park, FL alternateTitle: fl2017_everglades_m9818_metadata date: (CI_Date) date: 2017 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2018-08-30 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 69618 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/69618 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/9818/ept.json protocol: WWW:LINK-1.0-http--link name: Entwine Point Tile (EPT) 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. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Everglades_NP_LiDAR_2017_D16/USGS_FL_Everglades_NP_LiDAR_2017_D16_Project_Report.pdf protocol: WWW:LINK-1.0-http--link name: USGS Project Report description: Link to the USGS project report which provides information about the project, the vertical accuracy results, the point classifications and the sensors used. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_S_2017/reports/Everglades_National_Park_Topobathy_Lidar_Project_Report_USGS_20180830.pdf protocol: WWW:LINK-1.0-http--link name: Lidar Report description: Link to the lidar report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Everglades_NP_LiDAR_2017_D16/ protocol: WWW:LINK-1.0-http--link name: USGS Additional Info description: Link to the reports, breaklines, metadata, spatial metadata, and shapefiles. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/9818/ept.json protocol: WWW:LINK-1.0-http--link name: Potree 3D View description: Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/ protocol: WWW:LINK-1.0-http--link name: NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) 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. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles; used to create intensity images, 2D breaklines and Topobathy DEMs as necessary. Geographic Extent: Florida Everglades National Park covering approximately 1,211 square miles. Dataset Description: Florida Everglades National Park 2018 Lidar 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.2. The data was developed based on a horizontal projection/datum of NAD83 (2011), Universal Transverse Mercator, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles, as tiled Intensity Imagery, and as tiled bare earth topobathy DEMs; all tiled to the same 1000 m x 1000 m schema. Ground Conditions: Lidar was collected in early to mid 2017, 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, Dewberry established a total of 47 ground control points that were used to calibrate the lidar to known ground locations established throughout the Florida Everglades National Park project area. An additional 120 independent accuracy checkpoints, 61 in Bare Earth and Urban landcovers (61 NVA points), 59 in Tall Grass and Brushland/Low Trees categories (59 VVA points), 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 reflects the data that are available from the NOAA Digital Coast Data Access Viewer (DAV). The NOAA Office for Coastal Management (OCM) downloaded 3320 laz point data files from these USGS sites: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_N_2017/LAZ/ https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_S_2017/LAZ/ The data were processed to the NOAA Digital Coast Data Access Viewer (DAV) to make the data available for bulk and custom downloads. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. 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 DEM. The purpose of these lidar data was to produce high accuracy 3D Topobathy Digital Elevation Model (DEM) with a 0.5 meter cell size. These lidar point cloud data were used to create intensity images, 2D breaklines, and Topobathy DEMs as necessary. credit: Dewberry, USGS The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed Oct 20, 2024 at https://coast.noaa.gov/dataviewer. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9818/supplemental/fl2017_everglades_np_m9818.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION keyword: EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY keyword: EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) edition: 17.0 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > FLORIDA keyword: VERTICAL LOCATION > LAND SURFACE keyword: VERTICAL LOCATION > SEA FLOOR type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) edition: 17.0 descriptiveKeywords: (MD_Keywords) keyword: LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) edition: 17.2 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 17.2 descriptiveKeywords: (MD_Keywords) keyword: Everglades National Park keyword: Miami-Dade County keyword: Monroe County type: (MD_KeywordTypeCode) place descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Cite As: OCM Partners, [Date of Access]: 2017 USGS Topobathy Lidar: Everglades National Park, FL [Data Date Range], https://www.fisheries.noaa.gov/inport/item/69618. resourceConstraints: (MD_Constraints) useLimitation: NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: 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. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: 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. resourceConstraints: (MD_SecurityConstraints) classification: (MD_ClassificationCode) unclassified classificationSystem: (missing) handlingDescription: (missing) aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 69618 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/69618.pdf protocol: WWW:LINK-1.0-http--link name: NOAA Data Management Plan (DMP) description: NOAA Data Management Plan for this record on InPort. function: (CI_OnLineFunctionCode) information role: (inapplicable) associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -81.167515 eastBoundLongitude: -80.436127 southBoundLatitude: 25.14161 northBoundLatitude: 25.764331 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2017-04-19 endPosition: 2017-06-12 supplementalInformation: USGS Contract No. G16PC00020 CONTRACTOR: Dewberry Lidar data were acquired and calibrated by Dewberry, and all follow-on processing was completed by Dewberry. The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2", "ldrsens" : "Riegl LMS-Q680i", "ldrmaxnr" : "Unlimited", "ldrnps" : "0.35", "ldrdens" : "8", "ldranps" : "0.35", "ldradens" : "8", "ldrfltht" : "400", "ldrfltsp" : "130", "ldrscana" : "60", "ldrscanr" : "191", "ldrpulsr" : "400", "ldrpulsd" : "3", "ldrpulsw" : "0.9", "ldrwavel" : "1550", "ldrmpia" : "1", "ldrbmdiv" : "1", "ldrswatw" : "462", "ldrswato" : "30", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID12B" }, "ldrinfo" : { "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2", "ldrsens" : "Riegl VQ-820G", "ldrmaxnr" : "Unlimited", "ldrnps" : "0.35", "ldrdens" : "8", "ldranps" : "0.35", "ldradens" : "8", "ldrfltht" : "400", "ldrfltsp" : "130", "ldrscana" : "60", "ldrscanr" : "200", "ldrpulsr" : "522", "ldrpulsd" : "1.2", "ldrpulsw" : "0.36", "ldrwavel" : "532", "ldrmpia" : "1", "ldrbmdiv" : "1", "ldrswatw" : "307", "ldrswato" : "30", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID12B" }, "ldraccur" : { "ldrchacc" : "0.227", "rawnva" : "0.085", "rawnvan" : "60", "clsnva" : "0.070", "clsnvan" : "61", "clsvva" : "0.350", "clsvvan" : "59" }, "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 identified in these files using the standard LAS overlap bit.", "lasintrz" : "16", "lasclass" : { "clascode" : "1", "clasitem" : "Processed, but Unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare Earth Ground" }, "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" : "40", "clasitem" : "Submerged Topography/Bathymetry" }, "lasclass" : { "clascode" : "41", "clasitem" : "Water Surface" }, "lasclass" : { "clascode" : "45", "clasitem" : "Water Column/No Bottom Found" } }} return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAS/LAZ - LASer version: (missing) fileDecompressionTechnique: Zip distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9818/details/9818 protocol: WWW:LINK-1.0-http--link 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. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9818/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: 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 at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm in the "bare earth" and "urban" land cover classes. Dewberry Determined Vertical Accuracy The NVA was tested with 60 checkpoints located in bare earth and urban (non-vegetated) areas. These check points were not used in the calibration or post processing of the lidar point cloud data. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. See survey report for additional survey methodologies. 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 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. Tested 0.085 meters NVA at a 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). The NVA of the raw lidar point cloud swath files was calculated against TINs derived from the final calibrated and controlled swath data using 60 independent checkpoints located in Bare Earth and Urban land cover classes. USGS Determined Vertical Accuracy Non-Vegetated Vertical Accuracy (NVA) = 7.29 cm at the 95% Confidence Level or 3.7 cm RMSE Vegetated Vertical Accuracy (VVA) = 33.51 cm at the 95th Percentile Bathymetric Vertical Accuracy = 38.73 cm at the 95% Confidence Level Refer to the USGS project report in the URL section of this metadata record. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: 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 data passes Non-Vegetated Vertical Accuracy specifications. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data covers the entire area specified for this project. result: (missing) lineage: (LI_Lineage) statement: Data were collected and processed by Dewberry and were made available on the USGS rockyweb site. The data were downloaded from the USGS rockyweb site by the NOAA Office for Coastal Management (OCM) where the data were processed to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and bulk download from AWS S3. processStep: (LI_ProcessStep) description: 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 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 technician then analyzed the results and made any necessary additional adjustment until it is 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 match 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 6 cm within individual swaths and less than or equal to 8 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 check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.2, and 2D breaklines were collected for water features. Topobathy DEMs were exported from the classified point cloud. dateTime: DateTime: 2017-01-01T00:00:00 processStep: (LI_ProcessStep) description: LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) and Class 40 (Submerged Topography/Bathymetry) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Inland Water Void breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. Refraction correction was performed on all data within the Land/Water Interface breaklines. All ground (ASPRS Class 2) lidar data were then classified to submerged topography/bathymetry (ASPRS Class 40), and water surface (ASPRS Class 41) were classified using Terrascan macro functionality on both Green sensor and Near Infrared sensor data within the Land/Water Interface breaklines. Submerged topography/bathymetry (ASPRS Class 40) were then classified to water column/ no bottom found (ASPRS Class 45) within the Topobathy Void breaklines. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper us 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. Dewberry 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. dateTime: DateTime: 2018-05-15T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) downloaded 3320 laz point data files from these USGS sites: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_N_2017/LAZ/ https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_S_2017/LAZ/ In the Everglades_S folder, file 17RMJ900210 was found to be corrupt. USGS was notified of the issue. For a workaround, this same file was also included in the https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_S_Hydroflattened_2017/LAZ/ folder. Comparison between the two files indicated that the files were exactly the same. The file in the Hydroflattened folder however, was not corrupt. This non-corrupt file from the Hydroflattened folder was downloaded and used for processing. USGS confirmed this solution. The data were in UTM Zone 17N (NAD83 2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise, 40 - Bathymetric Bottom, 41 - Water Surface, 45 - No bathymetric bottom found (water column). OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 17, 18, 40, 41, 45. 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 NAD83 (2011) ellipsoid elevations using the Geoid12B model b. Convert the laz files from UTM Zone 17N (NAD83 2011), meters coordinates to geographic coordinates c. Assign the geokeys, sort the data by gps time and zip the data to database and AWS S3. dateTime: DateTime: 2023-09-07T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: USGS LAZ Files date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: USGS contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/ protocol: WWW:LINK-1.0-http--link name: USGS Rockyweb description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) publisher processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (https://rapidlasso.de/laszip/) Processing notes: dateTime: DateTime: 2024-10-20T08:11:26 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |