| 2018 USGS Lidar: Santa Barbara, CA | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:59332 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: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2020-09-15T00:00:00 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 6816485755 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 (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: 2018 USGS Lidar: Santa Barbara, CA date: (CI_Date) date: 2018-04-27 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 59332 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar1_z/geoid18/data/9078/supplemental/Santa_Barbara_Mudslide_Emergency_Response_LiDAR_Technical_Data_Report_Signed.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar1_z/geoid18/data/9078/supplemental/LiDARFinalDeliveryCheck_20180502_174750.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set 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: Geographic Extent: This dataset and derived products encompass an area covering approximately 48,766 acres of Southern California. On January 9th, 2018, heavy rains resulted in a large mudslide running down the destabilized, post-wildfire hillsides above the community of Montecito, California. In order to assist with emergency response efforts and post-landslide analysis, Quantum Spatial (QSI) utilized assets and crews in the area to rapidly collect Light Detection and Ranging (LiDAR) data on January 11th, 2018, for the Santa Barbara County Mudslide site in California. Data were collected as quickly as possible to aid in mapping the topographic and geophysical properties of the study area to support emergency response efforts, as well as future analysis of post-slide assessment. Dataset Description: RAW flight line swaths were processed to create 236 classified LAS 1.4 files delineated in 1,000 m x 1,000 m National Grid tiles. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. Additional derived products include intensity images, hydro-flattened DEMs, highest hit surface models, and 3D breaklines of rivers and lakes within the study area. Ground Conditions: Data was acquired during conditions with an absence of snow, high water, ground fog and/or clouds below the flight altitudes. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The purpose of the lidar data was to produce a high accuracy 3D dataset that meets all necessary standards laid out by the 3DEP initiative. The raw lidar point cloud data were used to create classified lidar LAS files, intensity images, hydro-flattened DEMs, highest hit surface models, and 3D breaklines of rivers and lakes within the study area. credit: Quantum Spatial, Inc. coordinated the LiDAR acquisition and processed the data., USGS, FEMA The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed Oct 20, 2020 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: 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: 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://coast.noaa.gov/htdata/lidar1_z/geoid18/data/9078/supplemental/extent_2018_SantaBarb_lidar_m9078.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) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America keyword: Continent > North America > United States Of America > California keyword: Continent > North America > United States Of America > U.S. Coastline keyword: Vertical Location > Land Surface keyword: Vertical Location > Seafloor type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Earth Remote Sensing Instruments > Active Remote Sensing > Profilers/Sounders > Lidar/Laser Sounders > LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Aircraft > Aircraft type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) 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: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 59332 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/59332.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 topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: LASTools, TerraPOS, Cloudpro 1.2.4, Microstation Version 8i, TerraScan Version 17, TerraModeler Version 17, ESRI ArcGIS 10.3, Windows 7 Operating System extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -119.73258 eastBoundLongitude: -119.465499 southBoundLatitude: 34.408132 northBoundLatitude: 34.514913 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-11 supplementalInformation: CONTRACTOR: Quantum Spatial, Inc. Ground Control Points were acquired and calibrated by Quantum Spatial, Inc. Data acquisition was coordinated by Quantum Spatial and all Lidar data calibration, and follow-on processing were completed by Quantum Spatial. The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "LIDAR Base Specification, Version 1.2", "ldrsens" : "Riegl VQ-1560i", "ldrmaxnr" : "15", "ldrnps" : "0.7", "ldrdens" : "4", "ldranps" : "0.35", "ldradens" : "8", "ldrfltht" : "2100", "ldrfltsp" : "100", "ldrscana" : "58.5", "ldrscanr" : "154 lines per second", "ldrpulsr" : "500 per channel", "ldrpulsd" : "3", "ldrpulsw" : "0.899", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.18 - 0.25", "ldrswatw" : "600", "ldrswato" : "60", "ldrgeoid" : "Geoid12B" }, "ldraccur" : { "ldrchacc" : "0.196", "rawnva" : "0.051", "rawnvan" : "22", "clsnva" : "0.087", "clsnvan" : "22", "clsvva" : "0.145", "clsvvan" : "8" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "6", "laswheld" : "Witheld points are identified in these files using the standard LAS Witheld bits.", "lasolap" : " Swath overage points are identified in these files using the standard LAS Witheld and Overlap bits.", "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" : "Water" }, "lasclass" : { "clascode" : "10", "clasitem" : "Ignored Ground Near Breakline" }, "lasclass" : { "clascode" : "17", "clasitem" : "Bridge Decks" } }} 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: 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=9078 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://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9078 protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The specifications require that Non-vegetated Vertical Accuracy (NVA) be computed from the both the raw lidar point cloud swath files and the derived DEMs. Additionally, Vegetated Vertical Accuracy (VVA) is also to be computed from the derived DEMS. The NVA was tested with 22 independent check points located in open terrain, and distributed throughout the project as feasible. These check points were not used in the calibration or post processing of the lidar point cloud data. Specifications for this project require that the NVA be 0.196 meters or better AccuracyZ at 95% confidence level. The VVA was tested with 8 independent check points located in vegetated terrain, also witheld from the calibration and post processing of the lidar point cloud data and distributed throughout the project area as feasible. Specifications for this project require that the NVA be 0.196 meters or better AccuracyZ at the 95% confidence level and that the VVA be 0.294 meters or better AccuracyZ at the 95th percentile. Quantitative value: 0.051 meters AccuracyZ at the 95 percent Confidence Interval for Raw LAS NVA. 0.087 meters AccuracyZ at the 95 percent Confidence Interval for DEM NVA., Test that produced the value: The 22 independent NVA check points were surveyed using the closed level loop technique. Elevations interpolated from the unclassified lidar surface were compared to the elevation values of the surveyed NVA check points. The RMSE was computed to be 0.026 meters resulting in an AccuracyZ at the 95% confidence level of 0.051 meters. The 22 NVA check points were also compared to the elevations of the derived bare earth DEMs. The RMSE was computed to be 0.045 meters resulting in an AccuracyZ of 0.087 meters at the 95% confidence level. NVA AccuracyZ has been tested and meets the required 0.196 meter NVA at 95% confidence level using (RMSEz * 1.9600) for both the raw lidar point cloud and derived DEMs, as defined by the National Standards for Spatial Data Accuracy (NSSDA) and herein reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. The 8 VVA check points were also surveyed using the closed level loop technique. Elevations for these points were compared to the elevations of the derived bare earth DEMs. The RMSE was computed to be 0.091 meters resulting in an AccuracyZ of 0.145 meters at the 95th percentile. AccuracyZ has been tested on the derived bare earth DEMs and meets the required 0.294 meter VVA using the 95th percentile of the absolute value of all vertical errors in all combined vegetation classes as defined by the National Standards for Spatial Data Accuracy (NSSDA); and herein reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: LAS files include all data points collected. No points have been removed or excluded. Shaded relief images have been visually inspected for data errors such as pits, border artifacts, and shifting. LiDAR flight lines have been examined to ensure consistent elevation values across overlapping flight lines. The raw point cloud is of good quality and data passes Vertical Accuracy specifications. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Classified LAS files were tested by QSI for both vertical and horizontal accuracy. All data is seamless from one tile to the next, no gaps or no data areas. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: LiDAR Pre-Processing: 1. Review flight lines and data to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 3. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. 4. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las format. Convert data to orthometric elevations by applying a geoid12b correction. 5. Import raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. 6. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. 7. Adjust the point cloud by comparing ground classified points to supplemental ground control points. dateTime: DateTime: 2018-01-11T00:00:00 processStep: (LI_ProcessStep) description: LiDAR Post-Processing: 1. Classify data to ground and other client designated classifications using proprietary classification algorithms. 2. Manually QC data classification 3. After completion of classification and final QC approval, calculate NVA for the project using ground control quality check points and density information. dateTime: DateTime: 2018-04-27T00:00:00 processStep: (LI_ProcessStep) description: Intensity Image creation: Intensity images were created for each tile from all valid first returns as 8 bit TIFFs using Quantum Spatial and ArcGIS software. dateTime: DateTime: 2018-01-11T00:00:00 processStep: (LI_ProcessStep) description: Hydroflattening Breaklines and Hydroflattened DEM creation: Water boundary polygons were developed using an algorithm which weights LiDAR-derived slopes, intensities, and return densities to detect the water's edge. The water's edge was then manually reviewed and edited as necessary. Elevations were assigned to the water’s edge through neighborhood statistics identifying the lowest LiDAR return from the water surface. Lakes were assigned a consistent elevation for an entire polygon while rivers were assigned consistent elevations on opposing banks and smoothed to ensure downstream flow through the entire river channel. These breaklines were incorporated into the hydro-flattened DEM by enforcing triangle edges (adjacent to the breakline) to the elevation values derived from the breakline. This implementation corrected interpolation along the hard edge. Breaklines were also used to classify all ground points within the identified water bodies to class 9 (water). dateTime: DateTime: 2018-01-11T00:00:00 processStep: (LI_ProcessStep) description: NOAA OCM retrieved 236 laz files from the USGS rockyftp website for the 2018 Montecito/Santa Barbara project area. The files were in UTM Zone 11 N, NAD83(2011) coordinates in meters, and NAVD88, geoid 12B elevations in US Survey Feet. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 12B model, to convert to geographic coordinates, to assign the geokeys, to sort the data by gps time, and zip the data to database and to http. dateTime: DateTime: 2018-01-11T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: This data source was used (along with the airborne GPS/IMU data) to georeference the LiDAR point cloud data. sourceCitation: (CI_Citation) title: Base Station Control date: (CI_Date) date: 2018-04-27 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-04-27 source: (LI_Source) description: Source Contribution: This data source was used to assess the accuracy of LiDAR point cloud data. sourceCitation: (CI_Citation) title: Ground Control Quality Check Points date: (CI_Date) date: 2018-04-27 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-04-27 source: (LI_Source) description: Source Contribution: This data source was used to populate the LiDAR point cloud data. sourceCitation: (CI_Citation) title: LiDAR RAW Data date: (CI_Date) date: 2018-04-27 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-01-11 source: (LI_Source) description: Source Contribution: This data source was used (along with base station control data) to georeference the LiDAR point cloud data. sourceCitation: (CI_Citation) title: Smooth Best Estimate Trajectories date: (CI_Date) date: 2018-04-27 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-04-27 source: (LI_Source) description: Source Contribution: This data source was used to refine airborne GPS positional accuracy during the calibration process. sourceCitation: (CI_Citation) title: Supplemental Ground Control Points date: (CI_Date) date: 2018-04-27 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-04-27 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: 2020-10-20T04:38:17 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |