| 2019 - 2020 USGS/NOAA Topobathy Lidar: CNMI (Aguijan, Rota, Saipan, Tinian) | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:66790 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: 2023-02-21T18:41:16 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: Northern Marianas Vertical Datum of 2003 (NMVD03) (GEOID12B) meters alternateTitle: Northern Marianas Vertical Datum of 2003 (NMVD03) (GEOID12B) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/6640/?api_key=gml name: Northern Marianas Vertical Datum of 2003 (NMVD03) (GEOID12B) 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::6640 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2019 - 2020 USGS/NOAA Topobathy Lidar: CNMI (Aguijan, Rota, Saipan, Tinian) alternateTitle: cnmi2019_islands_m9473_metadata date: (CI_Date) date: 2019 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2022 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 66790 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/66790 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://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9475/details/9475 protocol: WWW:LINK-1.0-http--link name: Custom DEM Download description: Link to custom download, from the Data Access Viewer (DAV), the raster Digital Elevation Model (DEM) topo hydro-flattened data that were created from this lidar data set for the islands of Aguijan, Rota, Saipan and Tinian. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9474/details/9474 protocol: WWW:LINK-1.0-http--link name: Custom DEM Download description: Link to custom download, from the Data Access Viewer (DAV), the raster Digital Elevation Model (DEM) topobathy data that were created from this lidar data set for the islands of Aguijan, Rota, Saipan, and Tinian. 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/PI_CNMI_2019_D19/ protocol: WWW:LINK-1.0-http--link name: Hydro Breaklines description: Link to the USGS rockyweb metadata folder which contains the breakline data. 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/PI_CNMI_2019_D19/PI_CNMI_hydroflattened_ellipsoid_2019/reports/PI_CNMI_2019_D19_Lidar_Mapping_Report_Hydroflattened_Ellipsoid_WU219835.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://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: Topo-bathy lidar acquisition and processing in the Mariana Islands covering Aguijan, Rota, Saipan, and Tinian. This product is a classified lidar point cloud data tiles in LAS 1.4 format, delivered in 500m x 500m tiles with FileSourceID set to 0, headers in OGC(2001) WKT, intensity normalized to 16-bit, and linear rescaling. Lidar is clipped to the extent of the area of interest for the topo-bathy data. Woolpert Inc. (Woolpert) was contracted for a two-part lidar data acquisition and lidar data processing effort in the Commonwealth of the Northern Mariana Islands. Part one required lidar data acquisition, initial data processing, and data coverage verification in the field performed under the United States Geological Survey (USGS). Part two is for the final data processing, derivative lidar products, and QA/QC and is performed under the NOAA Office of Coastal Management (NOAA) Contract. Woolpert collected lidar using their Hawkeye 4X topo-bathy lidar sensor, to provide high density topographic lidar to meet National Geospatial Program Lidar Base Specification Version 1.3 QL1 standard, while simultaneously acquiring bathymetric lidar data at National Coastal Mapping Strategy 1.0 QL2b standard. In addition to these lidar point data, the hydro-flattened and topobathy versions of the Digital Elevation Models (DEMs) created from the lidar point data, are also available. These data are available for custom download at the links provided in the URL section of this metadata record. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: Provision of topo-bathy lidar. credit: Woolpert, USGS, NOAA 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 01, 2023 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) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9473/supplemental/cnmi2019_islands_m9473.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: KML descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION 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: 12.3 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: OCEAN > PACIFIC OCEAN > WESTERN PACIFIC OCEAN > MICRONESIA > NORTHERN MARIANA ISLANDS 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: 12.3 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: 14.9 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 14.9 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]: 2019 - 2020 USGS/NOAA Topobathy Lidar: CNMI (Aguijan, Rota, Saipan, Tinian) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/66790. 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 useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None | 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. | 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: 2019 - 2020 USGS/NOAA Lidar DEM (Hydro-Flattened): CNMI (Aguijan, Rota, Saipan, Tinian) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 66839 associationType: (DS_AssociationTypeCode) crossReference aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: 2019 - 2020 USGS/NOAA Topobathy Lidar DEM: CNMI (Aguijan, Rota, Saipan, Tinian) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 66821 associationType: (DS_AssociationTypeCode) crossReference 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: 66790 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/66790.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: Collected using a Leica Hawkeye 4X sensor. Processed in Leica's survey studio, edited in TerraScan and LP360. Other software: QT Modeler, ArcMap, LASTools, proprietary software. extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: 145.12015 eastBoundLongitude: 145.835372 southBoundLatitude: 14.107529 northBoundLatitude: 15.294082 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-07-05 endPosition: 2019-08-25 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2020-02-12 endPosition: 2020-02-26 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2020-06-19 endPosition: 2020-07-14 supplementalInformation: Contractor: Woolpert, Inc. The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "USGS NGP Base Specifications v1.3", "ldrsens" : "Hawkeye4X", "ldrmaxnr" : "4", "ldrnps" : "0.35", "ldrdens" : "8", "ldranps" : "0.35", "ldradens" : "8", "ldrfltht" : "600", "ldrfltsp" : "130", "ldrscana" : "40", "ldrscanr" : "70", "ldrpulsr" : "500", "ldrpulsd" : "5", "ldrpulsw" : "0.27", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.5", "ldrswatw" : "435", "ldrswato" : "15", "ldrcrs" : "NAD83 (MA11) UTM 55N", "ldrgeoid" : "GEOID12B" }, "ldraccur" : { "ldrchacc" : "This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a ___(cm) RMSEx / RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy =+/- ___cm at a 95% confidence level", "rawnva" : "NA", "rawnvan" : "NA", "clsnva" : "NA", "clsnvan" : "NA" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "6", "laswheld" : "Geometrically unreliable points were identified using the standard LAS Withheld bit.", "lasolap" : "Overage points were identified using the standard LAS Overlap bit.", "lasintr" : "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" : "topo water surface" }, "lasclass" : { "clascode" : "17", "clasitem" : "bridge deck" }, "lasclass" : { "clascode" : "18", "clasitem" : "high noise" }, "lasclass" : { "clascode" : "40", "clasitem" : "bathymetric point, submerged topography" }, "lasclass" : { "clascode" : "41", "clasitem" : "bathy water surface" }, "lasclass" : { "clascode" : "42", "clasitem" : "derived water surface" }, "lasclass" : { "clascode" : "43", "clasitem" : "submerged object" }, "lasclass" : { "clascode" : "44", "clasitem" : "IHO objects" }, "lasclass" : { "clascode" : "45", "clasitem" : "water column" } }} return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAZ version: (missing) 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=9473/details/9473 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/geoid12b/9473/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. 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: Data collected under this Task Order shall meet the National Standard for Spatial Database Accuracy (NSSDA) accuracy standards. The NSSDA standards specify that vertical accuracy be reported at the 95% confidence level for data tested by an independent source of higher accuracy. Non-Vegetated Vertical Accuracy (NVA) of the Lidar Point Cloud data shall be calculated against TINs derived from the final calibrated and controlled swath data. The required accuracy (ACCZ) is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSEz of 10 cm in the open terrain and/or Urban land cover categories. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The data is programmatically and visually inspected for completeness. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: All formatted data cover the entire area specified for this project and are validated using a combination of commercial lidar processing software, GIS software, and proprietary programs to ensure proper formatting and loading prior to delivery. result: (missing) lineage: (LI_Lineage) statement: This data was collected by Woolpert, Inc. for the USGS and NOAA Office for Coastal Management (OCM). processStep: (LI_ProcessStep) description: All lidar data were acquired using a HE4X sensor (Figure 4). The HE4X is a latest generation topographic and bathymetric lidar sensor. The system provides denser data than previous traditional bathymetric lidar systems. It is unique in its ability to acquire bathymetric lidar, topographic lidar and 4-band digital camera imagery simultaneously. The HE4X provided up to 500 kHz topographic data and an effective 140 kHz shallow bathymetric data and a 40 kHz deep channel. While not a required deliverable for this survey, 4-band 80 MP digital camera imagery was also collected simultaneously with the sensor's RCD-30 camera and utilized during data editing in some cases. The bathymetric and topographic lasers are independent and do not share an optical chain or receivers, so they are optimized for their specific function. As with any bathymetric lidar, maximum depth penetration is a function of water clarity and seabed reflectivity. The HE4X is designed to penetrate to 3 times the secchi depth. This is also represented as Dmax = 4/K, where K is the diffuse attenuation coefficient, and assuming K is between 0.1 and 0.3, a normal sea state and 15% seabed reflectance. Both the topographic and bathymetric sub-systems use a palmer scanner to produce an elliptical scan pattern of laser points with a degree of incidence ranging from +/-14 degrees (front and back) to +/-20 degrees (sides), providing a 40 degree field of view. This has the benefit of providing multiple look angles on a single pass and helps to eliminate shadowing effects. This can be of particular use in urban areas, where all sides of a building are illuminated, or for bathymetric features such as the sides of narrow water channels, or features on the seafloor such as smaller objects and wrecks. It also assists with penetration in the surf zone where the back scan passes the same ground location a couple of seconds after the front scan, allowing the areas of whitewater to shift. processStep: (LI_ProcessStep) description: Position and orientation data were acquired in the aircraft using a NovAtel SPAN with LCI-100C IMU. All data were post-processed using NovAtel Inertial Explorer software to provide a tightly coupled position and orientation solution. A single base station was used to control trajectory processing providing final trajectories for Saipan and Tinian on NAD83 (MA11), Epoch 2010, located in the Saipan airport. This base station was replaced for each of the three separate collects of the project (Table 11). SPN1, SPN2 and SPN3 were occupied with a Trimble GNSS receiver by Woolpert. Due to the distance of Rota, Aguijan, Farallon de Medinilla, and Pagan from the single base station on Saipan and their remoteness a precise point positioning (PPP) solution was used for them on ITRF2014. To establish a reliable coordinate for SPN1 data were uploaded to the National Geodetic Service (NGS) Online Positioning User Service (OPUS), and for SPN2 and SPN3 Trimble CenterPoint RTX Post-Processing service was used. The average OPUS or RTX coordinate from multiple days of observations was used to process the final trajectories. processStep: (LI_ProcessStep) description: Initial data coverage analysis and quality checks to ensure there were no potential system issues were carried out in the field prior to demobilization of the sensor. Final processing was conducted in Woolpert's offices. In general data were initially processed in Leica's Lidar Survey Studio (LSS) using final processed trajectory information. LAS files from LSS were then imported to a Terrascan project where spatial algorithms were used to remove noise and classify bare earth/ground. Manual review was conducted in both Terrascan and LP360 prior to product creation. processStep: (LI_ProcessStep) description: Lidar processing was conducted using the Leica Lidar Survey Studio (LSS) software. Calibration information, along with processed trajectory information were combined with the raw laser data to create an accurately georeferenced lidar point cloud for the entire survey in LAS v1.4 format. All points from the topographic and bathymetric laser include 16-bit intensity values. During this LSS processing stage, an automatic land/water discrimination is made for the bathymetric waveforms. This allows the bathymetric (green) pulses over water to be automatically refracted for the pulse hitting the water surface and travelling through the water column, producing the correct depth. Another advantage of the automatic land/water discrimination is that it permits calculation of an accurate water surface over smaller areas, allowing simple bathymetric processing of smaller, narrower streams and drainage channels. Sloping water surfaces are also handled correctly. Prior to processing, the hydrographer can adjust waveform sensitivity settings dependent on the environment encountered and enter a value for the refraction index to be used for bathymetry. The index of refraction is an indication of the water type. Values used for sensitivity settings and the index of refraction are included in the LSS processing settings files. A value of 1.34206 was used for the index of refraction, indicating saltwater. In the field, default waveform sensitivity settings were used for processing. In order to determine the optimal waveform sensitivity settings for final processing, sample areas were selected and processed with multiple different settings, to iteratively converge on the best possible settings. This is done by reviewing the processed point cloud and waveforms within sample areas. A sample waveform is provided in Figure 6, while a sample LSS editing screen is provided in Figure 7. Settings affect which waveform peaks are classified as valid seabed, and which peaks are classified as noise. Optimal settings strike a balance between the amount of valid data that is classified as seabed bottom, and the amount of noise that is incorrectly classified due to peaks in the waveforms. Ideally all valid data is selected, while only a small amount of noise remains to be edited out. Once optimal threshold settings were chosen, these were used for the entire project. It is important to note that all digitized waveform peaks are available to be reviewed by the hydrographer; both valid seabed bottom and peaks classed as noise. This allows the hydrographer to review data during TerraScan and LP360 editing for valid data such as objects that may have been misclassified as noise. LSS processing produced LAS files in 1.4 format. Additional QC steps were performed prior to import to TerraScan. Firstly, the derived water surface was reviewed to ensure a water surface was correctly calculated for all bathymetry channels. No significant issues were apparent. Spot checks were also made on the data to ensure the front and back of the scans remained in alignment and no calibration or system issues were apparent prior to further data editing in TerraScan. LSS stores data in multiple LAS files for a single flight line. Each file corresponds to a single .dat file from the raw airborne data. Woolpert merged these multiple files into a single file per flight line and moved data into a standard class definition in preparation for data editing using Woolpert's proprietary scripts within SAFE's FME software. Data produced by LSS for flights over Saipan and Tinian were processed on the NAD83 (MA11) Epoch 2010 datum in UTM 55N Zone with units in meters, and elevations on the ellipsoid also in meters. Data produced for Aguijan and Rota were processed on the ITRF2014 datum in UTM 55N Zone with units in meters, with elevations on the ellipsoid also in meters. processStep: (LI_ProcessStep) description: After data were processed in LSS and the data integrity reviewed, Aguijan, and Rota were transformed from the ITRF2014 ellipsoid to the NAD83 (MA11) Epoch 2010 ellipsoid using VDatum. With the entire project now on the correct ellipsoid, data were organized into tiles within a TerraScan project. The tile layout is the same as that provided with the project deliverables. Data classification and spatial algorithms were applied in Terrasolid's TerraScan software. Customized spatial algorithms, such as isolated points and low point filters, were run to remove gross fliers in the topographic and bathymetric data. A grounding algorithm was also run on the topographic data to distinguish between points representing the bare earth, and other valid topo lidar points representing features such as vegetation, buildings, and so forth. Algorithms were run on the entire dataset. Data were reviewed manually to reclassify any valid bathy points incorrectly identified by the automated routines in LSS as invalid, and vice versa. In addition, any topo points over the water were reclassified to correct the ground representation. Manual editing was conducted both in TerraScan and LP360. Steps for manual editing included: - Re-class any topo unclassified laser data and bathy seabed data from the water surface to a water surface class - Review bathymetry in cross section. - Re-class suitable data to Seabed (Class 40). - Re-class any noise in the bathy ground class to bathy noise (Class 45). - Review topo ground points in areas of gaps or spikes. - Add points to ground (Class 2) from the topo laser if points are available to fill gaps in the ground model. - Re-class any noise in the ground class to Topo Unclassified (Class 1) if valid vegetation or other feature, or Noise if the point is not valid (Low Noise (Class 7) or High Noise (Class 18)). - Review topo ground points for bridges and re-class to Bridge Deck (Class 17). - Review bathymetry using imagery and nautical charts and re-class obvious man-made objects to Submerged Object (Class 43). Once editing was completed in TerraScan the islands of Saipan, Tinian, Aguijan, and Rota were vertically transformed to the NMVD03 datum using GEOID12B. processStep: (LI_ProcessStep) description: Although the bathymetry data includes intensity values, these are raw values. For intensity (reflectance) to correctly represent the reflectance of the seabed, the intensities must be normalized for any losses in signal as the light travels through the water column, so that the intensity value better reflects the intensity of the seabed itself. One of the fundamental issues that exists with reflectance imagery is the variance in return due to water clarity differences occurring spatially along line, and temporally from day to day. This is challenging for any bathymetric lidar sensor. If water clarity is relatively consistent along a line, then it is possible to achieve an overall homogenous reflectance image for an area. To a certain extent, variation in reflectivity intensity can be minimized by limiting the size of flight blocks and trying to ensure similar environmental parameters exist within a single flight block. In other words, where changes in water clarity or environment may be expected, flight blocks should be split to allow different normalization parameters to be used per block for the reflectance processing. Where this is not possible, and water clarity varies significantly along a line, variation in reflective intensity will be seen in the output imagery. While this imagery can still be analyzed and used for manual seabed classification, it prohibits the use of unsupervised, or semi-automated classification. For this survey, cloud shadows (ambient light) had an effect on the resulting reflectance images. Woolpert used proprietary in-house scripts developed in MATLAB to compute project specific correction parameters and normalize the raw intensity data for depth. This provides intensities that more closely represent the reflectance of the actual seabed. Corrected values were used to create 1m reflectance images per flightline using Applied Imager's QT Modeler software. Individual flightline reflectance images were then used in Trimble's OrthoVista software to create a final reflectance image for the entire area. OrthoVista was used to improve radiometric balancing between lines and the seamline editor was used to improve the joins between lines to remove as much line to line edge matching and cloud artifact issues as possible. processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the lidar point cloud data in las format from Woolpert, Inc. The data for the islands of Aguijan, Rota, Saipan, and Tinian were in UTM Zone 55 NAD83(MA11), meters coordinates and NMVD03 (Geoid 12B) elevations in meters. The point classifications were: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 17 - Bridge Deck, 18 - High Noise, 20 - Ignored Ground, 40 - Bathymetric Point, 41 - Water Surface, 42 - Derived Water Surface, 43 - Submerged Object, 45 - No Bottom At. OCM processed all point classes to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing 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 las files to: a. Convert from orthometric (NMVD03) elevations to ellipsoid elevations using the Geoid12B model b. Convert from UTM Zone 55 (NAD83 MA11), meters coordinates to geographic coordinates c. Assign the geokeys, to sort the data by gps time and zip the data to database and to the s3 Amazon bucket. dateTime: DateTime: 2022-03-11T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: Woolpert, Inc. date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Woolpert, Inc. role: (CI_RoleCode) originator processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference Northern Marianas Vertical Datum of 2003 (NMVD03) (GEOID12B) meters, using the GEOID12B 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: 2023-07-01T05:28:13 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |