| 2015-2016 Lake County, California Lidar; Classified Point Cloud | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:55316 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-05-30T18:10:31 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: 22111559354 return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: EPSG code 6318 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: 2015-2016 Lake County, California Lidar; Classified Point Cloud alternateTitle: 2015-2016 Lake_Co_CA_LiDAR_m8661.xml date: (CI_Date) date: 2016-06-01 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 55316 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/55316 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: NOAA's Office for Coastal Management (OCM) website description: Information on the NOAA Office for Coastal Management (OCM) function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8661/supplemental/LakeCountyCalifornia_LiDAR_Collection_Report_20160601.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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8661/supplemental/LakeCountyCalifornia_LiDAR_QAQC_Report_20160601.pdf protocol: WWW:LINK-1.0-http--link name: QA/QC report description: Link to the quality assurance / quality control 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: Compass PTS JV was tasked by FEMA to plan, acquire, process, and produce derivative products of LiDAR data at a nominal pulse spacing (NPS) of 0.7 meters based on the “U.S. Geological Survey National Geospatial Program LiDAR Base Specification Version 1.2”. The project consists of approximately 1,329 square miles (1,342 with 100 meter buffer). Fugro acquired 83 flight lines in 14 lifts between December 29th, 2015 and February 14th, 2016. LiDAR data collection was performed with a twin engine aircraft, utilizing a Leica ALS-70 sensor; collecting multiple return x, y, and z as well as intensity data. Specialized in-house and commercial software processes the native LiDAR data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: This high resolution LiDAR data will support the FEMA initiatives. credit: Compass PTS JV, FEMA, USGS 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) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8661/supplemental/2015_lakeCo_extent_m8661.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 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: VERTICAL LOCATION > LAND SURFACE 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: Elevation keyword: Model keyword: Surface keyword: Terrain type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: California keyword: Lake County keyword: US type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Geographic Names Information System date: (missing) descriptiveKeywords: (MD_Keywords) keyword: erosion 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]: 2015-2016 Lake County, California Lidar; Classified Point Cloud [Data Date Range], https://www.fisheries.noaa.gov/inport/item/55316. 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: 55316 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/55316.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 spatialResolution: (MD_Resolution) distance: Distance: .7 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: POSGNS 5.2; POSPac 6.2; CloudPro 1.2; Microstation 8.5.2.65; TerraScan 16.001; TerraModeler 16.001; Lasedit 1.35.07; ArcMap 10.3; GeoCue 2014.1.21.4; Global Mapper 14; ERDAS Imagine 2015; Fugro proprietary software; Windows XP and 7 Operating Systems Flight Lines: \\triton\lidar\22_15005400_LakeCountyCA\Delivery\Final_to_FEMA\04282016\FlightLines_LAS1pt4\*.las LAS Tiles: \\triton\lidar\22_15005400_LakeCountyCA\Delivery\Final_to_FEMA\06012016\LAS_Tiles\*.las Hydro Flattened DEM: \\triton\lidar\22_15005400_LakeCountyCA\Delivery\Final_to_FEMA\06012016\Hydro_Flattened_DEM\*.img Hydro Enforced DEM: \\triton\lidar\22_15005400_LakeCountyCA\Delivery\Final_to_FEMA\06012016\Hydro_Enforced_DEM\*.img Hydro Breaklines: \\triton\lidar\22_15005400_LakeCountyCA\Delivery\Final_to_FEMA\06012016\Hydro\LakeCo_hydro_breaklines_05202016.gdb 1,335 GB extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -123.09338 eastBoundLongitude: -122.34202 southBoundLatitude: 38.66872 northBoundLatitude: 39.58116 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2015-12-29 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2015-12-31 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2016-01-31 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2016-02-01 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2016-02-05 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2016-02-06 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2016-02-07 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2016-02-08 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2016-02-09 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2016-02-13 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2016-02-14 supplementalInformation: The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "U.S. Geological Survey National Geospatial Program LiDAR Base Specification Version 1.2", "ldrsens" : "Leica ALS70", "ldrmaxnr" : "unlimited", "ldrnps" : "0.7", "ldrdens" : "2", "ldranps" : "0.7", "ldradens" : "2", "ldrfltht" : "2500", "ldrfltsp" : "145", "ldrscana" : "27", "ldrscanr" : "57", "ldrpulsr" : "230", "ldrpulsd" : "9", "ldrpulsw" : ".46", "ldrwavel" : "1064", "ldrmpia" : "2", "ldrbmdiv" : ".22", "ldrswatw" : "1200", "ldrswato" : "45", "ldrcrs" : "NAD_1983_2011_UTM_10_Meters", "ldrgeoid" : "NAVD88 GEIOD12B" }, "ldraccur" : { "ldrchacc" : "0.196", "rawnva" : "0.11", "rawnvan" : "81", "clsnva" : "0.10", "clsnvan" : "8", "clsvva" : "0.213", "clsvvan" : "6" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "6", "laswheld" : "No points were ignored. All points were used in the classification.", "lasolap" : "No points were assigned as overlap points. All points were used in the classification.", "lasintr" : "16", "lasclass" : { "clascode" : "1", "clasitem" : "Processed, but unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare-earth ground" }, "lasclass" : { "clascode" : "7", "clasitem" : "Noise" }, "lasclass" : { "clascode" : "9", "clasitem" : "Water" }, "lasclass" : { "clascode" : "10", "clasitem" : "Ignored Ground" }, "lasclass" : { "clascode" : "17", "clasitem" : "Bridges" }, "lasclass" : { "clascode" : "18", "clasitem" : "High Noise" } }} return to top distributionInfo: (MD_Distribution) 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=8661 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. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8661/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. Note that the vertical datum (hence elevations) of the files here are different than described in this document. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The horizontal errors in LiDAR data are largely a function of the Global Navigation Satellite System (GNSS) positional errors, the Inertial Measurement Unit (IMU) angular errors, and the flying altitude. If the accuracy of the GNSS/IMU solution is known for the specific POS system, using the flying altitude of the project the expected horizontal errors in the LiDAR data can be estimated. Following the formula in the ASPRS Positional Accuracy Standards for Digital Geospatial Data (Edition 1, Version 1.0. - November, 2014), using the specifications of the POS system used and 2500 m flying altitude above ground, the estimated horizontal accuracy is RMSEr = 0.63 m. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The project specifications require that the reporting of absolute vertical accuracy in the form of non-vegetated vertical accuracy (NVA) and vegetated vertical accuracy (VVA). Tested 0.11 meters Non-vegetated Vertical Accuracy (NVA) (95% confidence). The project design for NVA is 0.196 meters. The NVA of the raw LiDAR point cloud was calculated against TINs derived from the final calibrated and controlled swath data using 81 independent checkpoints located in open terrain. Tested 0.213 meters Vegetated Vertical Accuracy (VVA) from the TINs from classified LIDAR. The VVA of the DEM was calculated using 62 independent checkpoints located in Cover (41 Tall) and 21 (Woods). The project design for VVA is 0.296 meters. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The Raw Point Cloud data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and data passes accuracy specifications. The Classified Point Cloud data files include all data points collected except the ones from Cross ties and Calibration lines. The points that have been removed or excluded are the points fall outside the project delivery boundary. Points are classified. A visual qualitative assessment was performed to ensure data completeness. Void areas that exist are a reult of snow in the northern reaches (accepted by client) and fire areas is the south (acceptable). The classified point cloud is of good quality and data passes accuracy requirements. The DEM raster files cover the entire project delivery boundary. The pixels fall that outside the project delivery boundary are set to Void with a unique “NODATA” value. The value is identified in the file headers. There are no void pixels inside the project boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The bare earth surface is of good quality and passes accuracy requirements. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of a GPS base station at the operational airport. The following checks were performed: 1) The LiDAR data accuracy was validated by performing a full boresight adjustment and then checking it against the ground control prior to generating a digital terrain model (DTM) or other products. 2) LiDAR elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Fugro was tasked with planning, acquiring, processing, and producing derivative products of LiDAR data collected at a NPS of 0.7 meters, including overlap, for an Area of Interest (AOI) covering a portion of Lake County, California. The AOI covers approximately 1,329 square miles. A 100-meter buffer was added to the AOI covering approximately 1,342 square miles; all products were generated to the limit of this buffered boundary. LiDAR data was acquired using a twin engine aircraft equipped with an antenna and receiver for airborne GPS collection. Flight status was communicated during data collection. All acquired LiDAR data went through a preliminary review to assure that complete coverage was obtained and that there were no gaps between flight lines before the flight crew left the project site. Once back in the office, the data was run through a complete iteration of processing to ensure that it is complete, uncorrupted, and that the entire project area has been covered without gaps between flight lines. There are essentially three steps to this processing: 1) GPS/IMU Processing - Airborne GPS and IMU data was immediately processed using the airport GPS base station data, which was available to the flight crew upon landing the plane. This ensures the integrity of all the mission data. These results were also used to perform the initial LiDAR system calibration test. 2) Raw LiDAR Data Processing - Technicians processed the raw data to LAS format flight lines with full resolution output before performing QC. A starting configuration file is used in this process, which contains the latest calibration parameters for the sensor. The technicians also generated flight line trajectories for each of the flight lines during this process. 3) Verification of Coverage and Data Quality - Technicians checked flight line trajectory files to ensure completeness of acquisition for the flight lines, calibration lines, and cross flight lines. The intensity images were generated for the entire lift at the required 0.7 meter nominal post spacing for the project. The technician visually checked the intensity images against the acquisition boundary to ensure full coverage to the 100 meter buffer beyond the project boundary. The technician also thoroughly reviewed the data for any gaps in project area. The technician generated a sample TIN surface to ensure no anomalies were present in the data. Turbulence was inspected for each flight line; if any adverse quality issues were discovered, the flight line was rejected and re-flown. The technician also evaluated the achieved post spacing against project specified 0.7 meter nominal post spacing as well as making sure no clustering in point distribution. dateTime: DateTime: 2016-06-01T00:00:00 processStep: (LI_ProcessStep) description: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used Fugro proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 (Required Accuracy) was met. dateTime: DateTime: 2016-06-01T00:00:00 processStep: (LI_ProcessStep) description: Once boresighting was complete for the project, the project was first set up for automatic classification. The LiDAR data was cut to production tiles. The flight line Overlap points, Noise points and Ground points were classified automatically in this process. Fugro utilized commercial software, as well as proprietary, in-house developed software for automatic filtering. The parameters used in the process were customized for each terrain type to obtain optimum results. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain were filtered out, the data was either run through a different filter within local area or was corrected during the manual filtering process. Interactive editing was completed in visualization software that provides manual and automatic point classification tools. Fugro utilized commercial and proprietary software for this process. All manually inspected tiles went through a peer review to ensure proper editing and consistency. After the manual editing and peer review, all tiles went through another final automated classification routine. This process ensures only the required classifications are used in the final product (all points classified into any temporary classes during manual editing will be re-classified into the project specified classifications). During this process, the points originally classified as flight line overlap were tagged as withheld points. Once manual inspection, QC and final autofilter is complete for the LiDAR tiles, the LAS data was packaged to the project specified tiling scheme, clipped to project boundary including the 100 meter buffer and formatted to LAS v1.4. It was also re-projected to UTM Zone 10; NAD83(2011), meters; NAVD88(GEOID12B), meters. The file header was formatted to meet the project specification with File Source ID assigned. This Classified Point Cloud product was used for the generation of derived products. This product was delivered in fully compliant LAS v1.4, Point Record Format 1 with Adjusted Standard GPS Time at a precision sufficient to allow unique timestamps for each return. Georeference information is included in all LAS file headers. Intensity values are included for each point. Each tile has unique File Source ID assigned. The Point Source ID matches to the flight line ID in flight trajectory files. The following classifications are included: Code 1 – Processed, but unclassified; Code 2 – Bare-earth ground; Code 7 – Noise (low or high, manually identified, if needed); Code 9 – Water; and Code 10 – Ignored Ground (Breakline Proximity); Code 17 - Bridges; Code 18 - High noise. dateTime: DateTime: 2016-06-01T00:00:00 processStep: (LI_ProcessStep) description: NOAA downloaded the lidar point cloud from USGS in NAD82(2011) UTM zone 11 meters with vertical coordinates in meters NAVD88 (Geoid12b). Data were converted to geographic coordinates and ellipsoid heights for ingest in the NOAA Digital Coast Data Access Viewer. processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: Source of lidar point cloud downloaded by NOAA sourceCitation: (CI_Citation) title: Classified Point Cloud date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: USGS contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/NED/LPC/Projects/USGS_LPC_CA_LakeCounty_2015_LAS_2017/ protocol: WWW:LINK-1.0-http--link name: Lake County, CA Lidar Point Cloud description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2018-11 source: (LI_Source) description: Source Contribution: Fugro collected Leica ALS-70 derived lidar over portions of Lake County, California with 0.7 meters ANPS using a twin engine aircraft. The collection was performed using a Leica ALS-70 lidar system, serial number 7108. There are data voids due to snow in the north (client accepted) adn lowered density in fire areas in the south (accepted) due to areas of low near infrared (NIR) reflectivity. sourceCitation: (CI_Citation) title: Lake County, California LiDAR Aerial Acquisition date: (CI_Date) date: 2016-06-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Fugro role: (CI_RoleCode) originator source: (LI_Source) description: Source Contribution: All surveying activities were performed by Fugro. A total of 18 ground control points to support the lidar collection, along with 81 NVA and 63 VVA checkpoints were collected. The static data collected at the RTK base station was downloaded and submitted to the office to be post processed utilizing the NGS Online Positioning User Service (OPUS). The horizontal datum was the North American Datum of 1983 (2011) and the vertical datum was the North American Vertical Datum of 1988 (NAVD 1988), using Geoid 12B. sourceCitation: (CI_Citation) title: Lake County, California Report of Survey date: (CI_Date) date: 2016-06-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Fugro role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2016-01-14 endPosition: 2016-01-21 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-01T09:01: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 | |