| 2022 NOAA NGS Topobathy Lidar: Big Bend WMA, FL | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:73046 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation contact: (CI_ResponsibleParty) organisationName: National Geodetic Survey 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-07-10T18:38:01 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: 2022 NOAA NGS Topobathy Lidar: Big Bend WMA, FL date: (CI_Date) date: 2023 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: (missing) dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 73046 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/73046 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: National Geodetic Survey contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) deliveryPoint: 1315 East-West Hwy city: Silver Spring administrativeArea: MD postalCode: 20910 country: (missing) electronicMailAddress: (missing) onlineResource: (CI_OnlineResource) linkage: https://geodesy.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: National Geodetic Survey Website description: Website listed for National Geodetic Survey function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) originator presentationForm: (unknown) abstract: These data were collected by Dewberry using a CZMIL Super Nova system. The data were acquired from 20221027 through 20221129. The data include topobathy data in LAS 1.4 format classified as unclassified (1); ground (2); low noise (7); high noise (18); bathymetric bottom (40); water surface (41); derived water surface (42); and submerged object, not otherwise specified (e.g., wreck, rock, submerged piling) (43) in accordance with project specifications. The project consists of approximately 1,373 square miles of data along the shores of Big Bend and contains 17,482 500 m x 500 m lidar tiles. This North Block dataset contains 8,054 500 m x 500 m tiles. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The National Geodetic Survey (NGS) Remote Sensing Division (RSD) Coastal Mapping Program (CMP) requires the collection of airborne topographic/bathymetric Light Detection and Ranging (lidar) and digital camera imagery data to enable accurate and consistent measurement of the national shoreline. credit: We request that you credit the National Oceanic and Atmospheric Administration (NOAA) when you use these data in a report, publication, or presentation. 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 Jul 11, 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) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10149/supplemental/extent_ngs_big_bend_2022_m10149.kmz fileDescription: This graphic shows the lidar footprint for this dataset. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > TOPOGRAPHICAL RELIEF MAPS keyword: EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY > COASTAL 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 > FLORIDA 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: DOC/NOAA/NOS/NGS > National Geodetic Survey, National Ocean Service, NOAA, U.S. Department of Commerce type: (MD_KeywordTypeCode) dataCentre thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Data Center Keywords date: (CI_Date) date: 2017-04-24 dateType: (CI_DateTypeCode) publication edition: 8.5 citedResponsibleParty: GCMD Landing Page descriptiveKeywords: (MD_Keywords) keyword: NGS Lidar type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Cite As: National Geodetic Survey, [Date of Access]: 2022 NOAA NGS Topobathy Lidar: Big Bend WMA, FL [Data Date Range], https://www.fisheries.noaa.gov/inport/item/73046. 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 National Geodetic Survey, 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: 73046 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ngs/dmp/pdf/73046.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 environmentDescription: OS Independent extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -84.340385 eastBoundLongitude: -83.340036 southBoundLatitude: 29.357615 northBoundLatitude: 30.092101 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2022-10-27 endPosition: 2022-11-29 supplementalInformation: Data include all lidar returns. Outliers or false returns (e.g., returns from birds, atmospheric particles, and/or system noise) may be present in the data. An automated ground classification algorithm was used to determine bare earth point classification. It should be noted that not all returns were correctly classified; therefore the user should examine for acceptability. return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureTypes: LocalName: Other featureCatalogueCitation: https://www.fisheries.noaa.gov/inport/item/73047 (CI_Citation) title: NOAA NGS Topobathy Lidar Class Scheme: Big Bend WMA, FL date: (CI_Date) date: 2024-07-10 dateType: (CI_DateTypeCode) publication 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: LAZ 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=10149 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. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10149/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: Lidar vendors calibrate their lidar systems during installation of the system and then again for every project acquired. Typical calibrations include cross flights that capture features from multiple directions that allow adjustments to be performed so that the captured features are consistent between all swaths and cross flights from all directions. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Only checkpoints photo-identifiable in the intensity imagery can be used to test the horizontal accuracy of the lidar. Photo-identifiable checkpoints in intensity imagery typically include checkpoints located at the ends of paint stripes on concrete or asphalt surfaces or checkpoints located at 90 degree corners of different reflectivity, e.g. a sidewalk corner adjoining a grass surface. The xy coordinates of checkpoints, as defined in the intensity imagery, are compared to surveyed xy coordinates for each photo-identifiable checkpoint. These differences are used to compute the tested horizontal accuracy of the lidar. As not all projects contain photo-identifiable checkpoints, the horizontal accuracy of the lidar cannot always be tested. This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 41 cm RMSEx/RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 1 meter at a 95% confidence level. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The vertical accuracy of the classified lidar will be tested by Dewberry with 61 independent survey checkpoints. The survey checkpoints are evenly distributed throughout the project area and are located in areas of non-vegetated terrain, including bare earth, open terrain, and urban terrain (40); and submerged bottom areas (21). The interim North Block delivery contained 16 Non-vegetated Vertical Accuracy (NVA) points and 7 Bathymetric Vertical Accuracy(BVA) points. The vertical accuracy is tested by comparing survey checkpoints to a triangulated irregular network (TIN) that is created from the lidar ground and submerged bottom points. Checkpoints are always compared to interpolated surfaces created from the lidar point cloud because it is unlikely that a survey checkpoint will be located at the precise location of a discrete lidar point. All checkpoints located in non-vegetated terrain were used to compute the NVA. Project specifications require a NVA of 19.6 cm at the 95% confidence level based on RMSEz (10 cm) x 1.9600. All checkpoints located in bathymetric areas were used to compute an accuracy value for the BVA. Project specifications require the vertical accuracy for bathymetric data to be 58.8 cm or better at the 95% confidence level based on depth-dependent RMSEz (30.0 cm) x 1.9600. This interim lidar dataset was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10 cm RMSEz Vertical Accuracy Class. Actual NVA accuracy was found to be RMSEz = 4.0 cm, equating to +/- 7.7 cm at the 95% confidence level. This interim lidar dataset was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 30.0 cm RMSEz Vertical Accuracy Class. Actual Bathymetric accuracy was found to be RMSEz = 22.5 cm, equating to +/- 44.2 cm at the 95% confidence level. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Not applicable result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Data were processed to an initial LAS format using Teledyne CARIS software. CARIS was also utilized for GPS and inertial processing, and Terrasolid and LAStools were used for data visualization, 3D editing, and export to final LAS/LAZ. Data were processed using NAD83(2011) horizontal and vertical datums. The data are in UTM Zone 17 coordinates and ellipsoid elevations in meters. The data classifications are: unclassified (1); ground (2); noise (7); water surface (topographic sensor) (18); bathymetric bottom (40); water surface (41); derived water surface (42); and submerged object, not otherwise specified (e.g., wreck, rock, submerged piling) (43) in accordance with project specifications. dateTime: DateTime: 2023-01-10T00:00:00 processor: (CI_ResponsibleParty) organisationName: National Geodetic Survey role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The initial points for each mission calibration were inspected for flight line errors, flight line overlap, slivers or gaps in the data, point data minimums, or issues with the lidar unit or GPS. Roll, pitch and scanner scale were optimized during the calibration process until the relative accuracy was met. Dewberry utilized Bayesmap StripAlign for this alignment procedure. This alignment procedure corrected systematic issues globally, per aircraft lift, per flightline, and finally based on local errors along the flight trajectory. Error adjustments included internal sensor parameters. Due to the complex geometric relationship of the elliptical scan pattern the forward and reverse directions must be aligned independently. Additionally, since the green and NIR scanner map different surfaces, they were also aligned independently, then corrected to match each other. Difference rasters (DZ orthos) were generated, adjustment parameters were reviewed, and registration/match regions were reviewed to ensure data quality. A final vertical accuracy check of the boresighted flight lines was completed against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level was met. Point classification was performed according to USGS Lidar Base Specification 2022 Rev A. Bare earth DEMs were exported from the classified point cloud. Synthetic points generated by CZMIL refraction correction algorithms are present in this dataset. Please see the final project report for more details on the synthetic points. dateTime: DateTime: 2023-10-10T00:00:00 processor: (CI_ResponsibleParty) organisationName: National Geodetic Survey role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: Dewberry used algorithms in TerraScan to create the initial ground/submerged topography surface. Dewberry used rasterized aggregate extents of refracted points to create automated 2-D breaklines with LAStools and ArcGIS. Light travels at different speeds in air versus water and its speed and direction of travel change when it enters the water column. The refraction correction process accounts for this difference by adjusting the depth (distance traveled) and horizontal position (change of angle/direction) of the lidar points acquired within water. These breaklines delineate areas where the refraction correction was applied to the lidar data by CZMIL's automated refraction correction software based on the software's detection of water. The class 42 synthetic surface is generated by the software as a reference surface from which to perform the correction. Dewberry used the 2-D refraction extents and additional bathy features to classify the bathymetric bottom and ground points properly in TerraScan. Synthetically generated class 42 (synthetic water surface) points were flagged using the synthetic bit. The withheld bit was set on class 7 and class 18 in TerraScan after all classification was complete. All lidar data was peer-reviewed. Dewberry's QAQC also included creating void polygons for use during review. All necessary edits were applied to the dataset. LASTools software was used to update LAS header information, including all projection and coordinate reference system information. The final lidar data are in LAS format 1.4 and point data record format 6. All data was then verified by an Independent QC department within Dewberry. The independent QC was performed by separate analysts who did not perform manual classification or editing. The independent QC involved quantitative and qualitative reviews. dateTime: DateTime: 2023-10-11T00:00:00 processor: (CI_ResponsibleParty) organisationName: National Geodetic Survey role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received files in laz format. The files contained lidar elevation and intensity measurements from the Big Bend Wildlife Management Area. The data were in UTM Zone 17 coordinates and ellipsoid elevations in meters. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Converted from UTM Zone 18 to geographic coordinates 2. Sorted by gps time dateTime: DateTime: 2024-07-30T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: Acquisition and Processing date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Dewberry role: (CI_RoleCode) originator 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 (laszip.org) Processing notes: dateTime: DateTime: 2024-07-11T23:36:55 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |