| 2012 U.S. Geological Survey Topographic Lidar: Northeast Atlantic Coast Post-Hurricane Sandy | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49845 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset 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: 2022-08-09T17:11:36 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: return to top referenceSystemInfo: 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 identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2012 U.S. Geological Survey Topographic Lidar: Northeast Atlantic Coast Post-Hurricane Sandy alternateTitle: ne2012_usgs_postsandy_m2488_metadata date: (CI_Date) date: 2013-06 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49845 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49845 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 protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource 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: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: Binary point-cloud data were produced for a portion of the New York, Delaware, Maryland, Virginia, and North Carolina coastlines, post-Hurricane Sandy (Sandy was an October 2012 hurricane that made landfall as an extratropical cyclone on the 29th), from remotely sensed, geographically referenced elevation measurements collected by Photo Science, Inc. (Delaware, Maryland, Virginia, and North Carolina) and Woolpert, Inc. (Fire Island, New York) using airborne lidar sensors. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The purpose of this project was to derive mean-high-water shoreline, dune crest (DHIGH) and dune toe (DLOW) elevation for a portion of the Eastern United States coastline following Hurricane Sandy, for use as a management tool and to make these data available to natural-resource managers and research scientists.Processed data products are used by the USGS Coastal and Marine Geology Program's National Assessments of Coastal Change Hazards project to quantify the vulnerability of shorelines to coastal change hazards such as severe storms, sea-level rise, and shoreline erosion and retreat. credit: Acknowledgment of the U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center, as a data source would be appreciated in products developed from these data, and such acknowledgment as is standard for citation and legal practices. Sharing of new data layers developed directly from these data would also be appreciated by the U.S. Geological Survey staff. Users should be aware that comparisons with other datasets for the same area from other time periods may be inaccurate due to inconsistencies resulting from changes in photo interpretation, mapping conventions, and digital processes over time. These data are not legal documents and are not to be used as such. 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 descriptiveKeywords: (MD_Keywords) keyword: Cessna 206 keyword: Cessna 310 keyword: Dhigh keyword: Dlow keyword: dune crest keyword: dune toe keyword: extratropical cyclone keyword: shoreline type: (MD_KeywordTypeCode) theme 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]: 2012 U.S. Geological Survey Topographic Lidar: Northeast Atlantic Coast Post-Hurricane Sandy [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49845. 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. These data depict the heights at the time of the survey and are only accurate for that time. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of Photo Science Inc., USGS, 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: 49845 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49845.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: -76.680203 eastBoundLongitude: -72.70305 southBoundLatitude: 34.566094 northBoundLatitude: 40.790453 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-05 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-08 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-09 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-10 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-11 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-12 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-16 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-26 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-28 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-11-29 supplementalInformation: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2488/supplemental/ne2012_usgs_postsandy_footprint.KMZ return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: see process steps within this record date: (unavailable) return to top distributionInfo: (MD_Distribution) 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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2488/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2488 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 return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: The project area required lidar to be collected on 1-meter ground sample distance (GSD) or better and processed to meet a bare earth vertical accuracy of 12.5-centimeters root mean square error (RMSEz) or better. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Horizontal accuracy is +/- 0.194 meter at the 95% confidence level. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Lidar file format (LAS) data were compared to survey control points to determine the FVA of the LAS Swath and of the DEM. LAS Swath Fundamental Vertical Accuracy (FVA) Tested 0.147 m (14.7 cm) fundamental vertical accuracy at a 95 percent confidence level, derived according to NSSDA (National Standard for Spatial Data Accuracy), in open terrain using 0.075 m (7.5 cm) (RMSEz x 1.96000), tested against the TIN. ; Quantitative Value: 0.075 meters, Test that produced the value: RMSEz in meters result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: These data span from Long Island, New York to Cape Hatteras, North Carolina. The State of New Jersey data were collected using the EAARL-B sensor and those data will be published separately. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data for Fire Island was visually inspected by Woolpert, Inc. Data for Delaware, Maryland, Virginia, and North Carolina were tested by Photo Science, Inc. for both vertical and horizontal accuracy. Although collected on a tile-by-tile basis, breaklines are merged together to produce a single dataset deliverable. Checks are done to ensure that the data is seamless from one tile to the next before being combined and that breaklines meeting the project requirements have been collected across the entire project area. Combining the breaklines with lidar data to create other deliverables is another check of the data. All data are seamless from one tile to the next, containing no gaps or "no data" areas. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Using an Optech Gemini lidar sensor, 11 flight lines of high-density data, at a nominal pulse spacing (NPS) of 1 meter, were collected by Woolpert along the southern shore of Long Island, New York (approximately 15 square miles). Data Acquisition Height = 3,500 feet Above Ground Level (AGL) - Aircraft Speed = 125 Knots. Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of one mission was flown on November 5th. Two airborne global positioning system (GPS) base stations were used in support of the lidar data acquisition. Eight ground control points were surveyed through static methods. The GEOID used to reduce satellite-derived elevations to orthometric heights was GEOID96. Data for the task order is referenced to the UTM Zone 18N, North American Datum of 1983 (NAD83), and North American Vertical Datum of 1988 (NAVD88), in meters. Airborne GPS data was differentially processed and integrated with the post-processed inertial measurement unit (IMU) data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the lidar slant range measurements to a raw reflective surface for each flight line. The coverage was classified to extract a bare earth digital elevation model (DEM) and separate last returns. In addition to the LAS deliverables, one layer of coverage was delivered in the ERDAS Imagine (IMG) Format: bare earth. dateTime: DateTime: 2012-11-05T00:00:00 processStep: (LI_ProcessStep) description: The lidar calibration and system performance are verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy are calculated through comparison of lidar data against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw lidar data are reduced using the refined misalignment angles. dateTime: DateTime: 2012-01-01T00:00:00 processStep: (LI_ProcessStep) description: Once the data acquisition and GPS processing phases are complete, the lidar data were processed immediately by Woolpert to verify the coverage had no voids. The GPS and IMU data were post-processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project. dateTime: DateTime: 2012-11-07T00:00:00 processStep: (LI_ProcessStep) description: The individual flight lines were inspected by Woolpert to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" lidar returns. This process determined Default (Class 1), Ground (Class 2), Noise (Class 7), Water (Class 9), Ignored Ground (Class 10), Overlap Default (Class 17), and Overlap Ground (Class 18) classifications. The bare-earth (Class 2 - Ground) lidar points underwent a manual QA/QC step to verify that artifacts have been removed from the bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the lidar dataset. dateTime: DateTime: 2012-11-07T00:00:00 processStep: (LI_ProcessStep) description: Photo Science, Inc. located a total of 29 calibration control points used in the post processing of the lidar data. The points were located on relatively flat terrain on surfaces that generally consisted of grass, gravel, or bare earth. Applanix software (PosPAC MMS) was used in the post processing of the airborne GPS and inertial data, which are critical to the positioning and orientation of the sensor during all flights. POSPac MMS provides the smoothed best estimate of trajectory (SBET) that is necessary for the post processor to develop the point cloud from the lidar missions. The point cloud is the mathematical three-dimensional collection of all returns from all laser pulses as determined from the aerial mission. The GEOID used to reduce satellite derived elevations to orthometric heights was GEOID96. Data for the task order is referenced to the UTM Zone 18N, NAD83, and NAVD88, in meters. At this point the data are ready for analysis, classification, and filtering to generate a bare-earth surface model in which the above ground features are removed from the data set. The point cloud was manipulated by the Optech or Leica software; GeoCue, TerraScan, and TerraModeler software were used for the automated data classification, manual cleanup, and bare-earth generation from the data. Project specific macros were used to classify the ground and to remove the side overlap between parallel flight lines. All data were manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. All Lake Pond and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) were reclassified to the correct classification after the automated classification was completed. All overlap data were processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data were classified to Class 17 (USGS Overlap Default) and Class 18 (USGS Overlap Ground). These classes were created through automated processes only and were not verified for classification accuracy. Data were then run through additional macros to ensure deliverable classification levels matching the ASPRS LAS Version 1.2 Classification structure. GeoCue functionality was then used to ensure correct LAS Versioning. In-house software was used as a final QA/QC check to provide LAS Analysis of the delivered tiles. QA/QC checks were performed on a per tile level to verify final classification metrics and full LAS header information. dateTime: DateTime: 2012-01-01T00:00:00 processStep: (LI_ProcessStep) description: All Woolpert, Inc. LAZ files were extracted to LAS and converted to ASCII xyz point files using LASTools las2las.exe. The ASCII point files were then written to netcdf format using MATLAB 8.0.0.783. dateTime: DateTime: 2013-02-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received topographic files in LAS format. The files contained lidar elevation and intensity measurements. The data were received in UTM Zone 18N coordinates and were vertically referenced to NAVD88 using the Geoid96 model. The vertical units of the data were meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The topographic las files were horizontally converted from UTM Zone 18N to Geographic Coordinates. 2. The horizontal units of the data were converted from meters to decimal degrees. 3. The topographic las files were vertically converted from orthometric (NAVD88) heights to ellipsoidal (NAD83) heights. 4. Classes 11 (Unknown), 15 (Unknown) and 17 (Default Overlap) were combined to Class 12 (Overlap). Class 11 points were assigned a User Data value of '1', Class 15 points were assigned a User Data value of '2', and Class 17 points were assigned a User Data value of '3'. dateTime: DateTime: 2013-05-01T00:00:00 processStep: (LI_ProcessStep) description: The original data received from USGS had several corrupted tiles. Replacement files were received from USGS in March 2014. These tiles had been processed using GEOID09, but were otherwise the same projection and classes. Files were converted as previously, but using GEOID09 to transform to ellipsoid heights. Replacement tiles were 18SVH486232, 18TXL600015, 18SUD350836, 18SUD358828, and 18SVH494254. dateTime: DateTime: 2014-05-20T00:00:00 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: 2023-07-01T06:06:38 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |