| 2014 U.S. Geological Survey CMGP LiDAR: Post Sandy (Virginia) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:50135 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:38 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: 2014 U.S. Geological Survey CMGP LiDAR: Post Sandy (Virginia) alternateTitle: va2014_usgs_cmgp_sandy_m4970_metadata date: (CI_Date) date: 2016-01-09 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 50135 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/50135 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 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 protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: USGS Contract Number: G10PC00093, Task Order: G14PD00222 Digital Aerial Solutions LLC was tasked to collect and process 4607 sq. miles of Light Detection and Ranging (LiDAR) dataset in Virginia. The LiDAR Survey encompasses 4607 sq. miles of area in Eastern Virginia inclusive of the counties and cities of Spotsylvania, Caroline, Hanover, Henrico, Chesterfield, Dinwiddie, Sussex, Richmond City, Hopewell City, Colonial Heights City, Petersburg City, portions of Orange and Louisa, Amelia, Nottoway and Prince Edward. The LiDAR point cloud was flown at a nominal post spacing of 0.7 meters for un-obscured areas. The LiDAR data and derivative products produced are in compliance with the U.S. Geological Survey National Geospatial Program Guidelines and Base Specifications, Version 1.0. The final LAS point cloud classified as 1-Unclassified, 2-Ground, 7-Noise, 9-Water, 10-Ignored Ground due to breakline proximity, 17-overlap ground points and 18 - overlap unclassified points. The GPS Survey was completed by ESP Associates for 3 block acquisition area, and 2 blocks acquisition area by Michale Baker Surveying totaling 4607 square miles through the project area. Breaklines were delivered with the lidar dataset. These have not been reviewed by NOAA OCM, therefore are only available by request. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: Evaluation of coastal storm damage impacts; aid in post-event reconstruction, and mitigation planning for future events, and collect LiDAR for counties heavily impacted by storm and flooding for which data is incomplete or inadequate to conduct proper analysis, as part of USGS Hurricane Sandy Response. 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/4970/supplemental/va2014_usgs_cmgp_sandy_m4970.kmz fileDescription: This graphic shows the lidar coverage for the 2014 lidar acquisition for mainland Virginia. A separate project was contracted and tasked for the Delmarva peninsula portion of Virginia. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Bare earth 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]: 2014 U.S. Geological Survey CMGP LiDAR: Post Sandy (Virginia) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50135. 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. The data depicts the elevations at time of survey and are accurate only for that time. Exercise professional judgment in using this data. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of Digital Aerial Solutions LLC, 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: 50135 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50135.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: -78.692546 eastBoundLongitude: -76.953543 southBoundLatitude: 36.70765 northBoundLatitude: 38.39291 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2014-03-24 endPosition: 2014-04-21 supplementalInformation: A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4970/supplemental/va2014_usgs_cmgp_sandy_m4970.kmz A report for this the project may be viewed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4970/supplemental/va2014_usgs_cmgp_sandy_m4970_lidarreport.pdf A survey report for this the project may be viewed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4970/supplemental/va2014_usgs_cmgp_sandy_m4970_qualityreport.pdf return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: none 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://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4970 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/4970/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: Newly processed vectors were entered into the StarNet Least Squares adjustment program holding the NAD83-2011(epoch 2010) CORS and existing monumented NGS published coordinates, along with the inclusion of the Geoid12A model. A horizontal accuracy of 2nd Order Class I (1:50,000) and the vertical NAVD88 accuracy at 3rd Order (+/- 0.06') were achieved.+ result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: There is not a systematic method of testing when testing horizontal accuracy in LiDAR. However this is tested during calibration of the sensor and is rechecked during the comparing of parallel and perpendicular flight lines. Additionally the horizontal accuracy is checked by collecting building corners during the survey. Lines are then digitized representing the building outline and the differences are measure from each individual survey point to the corner of the building outline. Stats are calculated to ensure horizontal tolerances are met. These measurements resulted in an RMSE of .42 meters and equals a .73 meter horizontal accuracy at the 95 % confidence level. Accuracy defined by NSSDA at the 95 % confidence level would be multiplier by 1.7308 times the RMSE. The accuracy assessment was performed using the NSSDA standard method to compute the root mean square error (RMSE) based on a comparison of ground control points (GCP) and filtered LiDAR data points. Filtered LiDAR data has had vegetation and cultural features removed and by analysis represent bare earth elevations. Testing was performed prior to gridding of the filtered LiDAR data points and construction of the 32-bit ERDAS Imagine format bare earth tiles. The RMSEz figure was used to compute the vertical National Standard for Spatial Data Accuracy (NSSDA). A spatial proximity analysis was used to select edited LiDAR data points contiguous to the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error and adequate sample size. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: (7.5 cm) 0.2806 ft RMSE; Quantitative Value: 0.147 meters, Test that produced the value: Tested 14.7 cm (0.55 ft.) fundamental vertical accuracy (FVA) at the 95% confidence level in open terrain, based on RMSEz x 1.9600. Tested against the DEM.; Quantitative Value: 0.202 meters, Test that produced the value: Tested 20.2 cm supplemental vertical accuracy (SVA) at the 95th percentile in Tallweed categories. Tested against the DEM.; Quantitative Value: 0.205 meters, Test that produced the value: Tested 20.5 cm supplemental vertical accuracy (SVA) at the 95th percentile in Brush Land catagories. Tested against the DEM.; Quantitative Value: 0.231 meters, Test that produced the value: Tested 23.1 cm supplemental vertical accuracy (SVA) at the 95th percentile in Forested catagories. Tested against the DEM.; Quantitative Value: 0.166 meters, Test that produced the value: Tested 16.6 cm supplemental vertical accuracy (SVA) at the 95th percentile in urban catagories. Tested against the DEM.; Quantitative Value: 0.187 meters, Test that produced the value: Tested 18.7 cm consolidated vertical accuracy (CVA) at the 95th percentile in all categories of data. Tested against the DEM. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: GPS points were taken for five separate classes on flat or uniformly sloping terrain at least five meters away from any breakline. Output results are in NAD83-2011(epoch 2010) and UTM Zone 18, in meters, and VA State Plane North, in feet. There were a total 250 points in this Geodetic network. There are 18 existing and CORS marks utilized to control this network. There are 104 Control Points (CP), 29 Bear Earth, 25 Tall Weeds, 26 Brush areas, 26 Canopy (forest), , and 22 Urban locations. The vegetation height ranges were 0 - 0.5ft, 0.5 - 5ft, 5 - 6.5ft, > 6.5ft, 0 ft, respectively. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Digital Aerial Solutions LLC was tasked to collect and process 4607 sq. miles of Light Detection and Ranging (LiDAR) dataset in Virginia. The LiDAR Survey encompasses 4607 sq. miles of area in Eastern Virginia inclusive of the counties and cities of Spotsylvania, Caroline, Hanover, Henrico, Chesterfield, Dinwiddie, Sussex, Richmond City, Hopewell City, Colonial Heights City, Petersburg City, portions of Orange and Louisa, Amelia, Nottoway and Prince Edward. The LiDAR point cloud was flown at a nominal post spacing of 0.7 meters for un-obscured areas. The LiDAR data and derivative products produced are in compliance with the U.S. Geological Survey National Geospatial Program Guidelines and Base Specifications, Version 1.0. The final LAS point cloud classified as 1-Unclassified, 2-Ground, 7-Noise, 9-Water, 10-Ignored Ground due to breakline proximity, 17-overlap ground points and 18 - overlap unclassified points. The GPS Survey was completed by ESP Associates for 3 block acquisition area, and 2 blocks acquisition area by Michale Baker Surveying totaling 4607 square miles through the project area. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: The primary collection of LiDAR data was done by two Cessna 421 aircrafts. There were three LiDAR sensors used to acquire this mission; ALS60, ALS70 and an Optech Pegasus system. 35 flight missions were required to collect the entire area of the project area. The ABGPS, inertial measurement unit (IMU), and raw scans are collected during the LiDAR aerial survey. The ABGPS monitors the xyz position of the sensor and the IMU monitors the orientation. During the aerial survey, laser pulses reflected from features on the ground surface are detected by the receiver optics and collected by the data logger. GPS locations are based on data collected by receivers on the aircraft and base stations on the ground. The ground base stations are placed no more than 40 km radius from the flight survey area. dateTime: DateTime: 2014-04-02T00:00:00 processStep: (LI_ProcessStep) description: The ABGPS, IMU, and raw scans are integrated using proprietary software developed by Leica and delivered with the Leica System. The resultant file is in a LAS binary file format. The LAS version 1.2 file format can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return number, intensity value, xyz, etc.). The resultant points are produced in UTM18/ NAD83 coordinate system, with units in Meters and Vertical datum referenced to the NAVD88 datum. The LiDAR mass points were processed in American Society for Photogrammetry and Remote Sensing LAS 1.2 format. The header file for each dataset is complete as defined by the LAS 1.2 specification. The datasets were divided into 1500 Meters by 1500 Meters tiling scheme, based on United States National Grid Index. The tiles are contiguous, do not overlap, and are suitable for seamless topographic data mosaics that include no "no data" areas. dateTime: DateTime: 2014-04-10T00:00:00 processStep: (LI_ProcessStep) description: The unedited data are classified to facilitate the application of the appropriate feature extraction filters. Digital Aerial Solutions used Terrasolids Terrascan and Terramodel softwares to classify and edit the LAS data and a combination of proprietary filters are applied as appropriate for the production of bare earth digital elevation models (DEMs). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. DAS classified the LAS data as follows: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 2 = Ground Class 7 = Noise Class 9 = Water Class 10 = Ignored Ground Class 17 = overlap ground Class 18 = overlap unclassified dateTime: DateTime: 2014-04-25T00:00:00 processStep: (LI_ProcessStep) description: Filtered and edited data are subjected to rigorous QA/QC, A series of quantitative and visual procedures are employed to validate the accuracy and consistency of the filtered and edited data. Ground control is established by DAS and GPS-derived ground control points (GCPs) in various areas of dominant and prescribed land cover. These points are coded according to land cover, surface material, and ground control suitability. A suitable number of points are selected for calculation of a statistically significant accuracy assessment, as per the requirements of the National Standard for Spatial Data Accuracy. A spatial proximity analysis is used to select edited LiDAR data points within a specified distance of the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error, and adequate sample size. Accuracy validation and evaluation is accomplished using proprietary software to apply relevant statistical routines for calculation of Root Mean Square Error (RMSE) and the National Standard for Spatial Data Accuracy (NSSDA), according to Federal Geographic Data Committee (FGDC) specifications. dateTime: DateTime: 2014-05-22T00:00:00 processStep: (LI_ProcessStep) description: The Bare Earth DEM was extracted from the raw LIDAR products and attributed with the bare earth elevation for each cell of the DEM. Bare Earth DEMs do not include buildings, vegetation, bridges or overpass structures in the bare earth model. Where abutments were clearly delineated, this transition occurred at the junction of the bridge and abutment. Where this junction was not clear, the extractor used their best estimate to delineate the separation of ground from elevated bridge surface. In the case of bridges over water bodies, if the abutment was not visible, the junction was biased to the prevailing stream bank so as not to impede the flow of water in a hydrographic model. Bare earth surface includes the top of water bodies not underwater terrain, if visible. dateTime: DateTime: 2014-05-25T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the topographic files in classified LAZ format from USGS' ftp site. The data were received in UTM Zone 18N NAD83 coordinates (meters) and vertically referenced to NAVD88 using the Geoid12a model in meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. LAS files were compressed to LAZ format with LASTools. 2. LAS files were removed of any duplicated points and extraneous points were reclassified to noise. 3. The LAS files were transformed to geographic (decimal degrees), ellipsoidal coordinates (meters) referenced to the Geoid12a model. dateTime: DateTime: 2016-05-01T00: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-01T07:21:06 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |