| 2012 USGS Lidar: Juneau (AK) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49625 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: 2024-02-29T00: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: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) / UTM zone 8N 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/6337/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6337 version: 6.18.3 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2012 USGS Lidar: Juneau (AK) alternateTitle: ak2012_usgs_juneau_m5021_metadata date: (CI_Date) date: 2016-03-11 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49625 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49625 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: This task order is for planning, acquisition, processing, and derivative products of LiDAR data to be collected for Juneau, Alaska. LiDAR data, and derivative products produced in compliance with this task order are part of the data to be obtained under Contract number G10PC00025, Order number G12PD00481. Specifications listed below are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 13. This data set contains point cloud data(' in LAZ (compressed LAS) format', ''). The data may have been reprojected or otherwise modified from the original data in an automated process. Disregard projection information in this abstract and refer to the spatial reference section. purpose: USGS has a requirement for LiDAR data in Juneau, Alaska and vicinity. Data is to be collected at a nominal pulse spacing (NPS) of 1.0 meters or less. The Juneau, Alaska LiDAR Acquisition project is to provide high accuracy bare-earth processed LiDAR data suitable for the project area. The project consisted of acquisition, post-processing, classification of LiDAR data, and creation of final deliverable products. All areas shall be collected at a nominal pulse spacing (NPS) of 1.0 meters or less based on UTM 8, related to the North American Datum of 1983. Vertical accuracy was to achieve a RMSE Z of 12.5 cm (95% confidence level of less than 24.5 cm) or better in the "Open Terrain" land cover category for all areas. Accuracy statement is based on areas of moderate to flat terrain. Diminished accuracies are to be expected in areas in dense vegetation. The accuracy of the LiDAR data as tested met or exceeded the vertical accuracy requirements, however, derived products may be less accurate in areas of dense vegetation due to a lesser number of points defining the bare-earth in such areas. 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) unknown graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/5021/supplemental/ak2012_usgs_juneau_m5021.kmz fileDescription: This graphic shows the lidar coverage for the 2012 USGS lidar project for Juneau (AK). fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Ground keyword: Terrain 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: This data set was compiled dynamically. It will be removed 10 days after 2025-06-20 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2012 USGS Lidar: Juneau (AK) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49625. 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 otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-06-20 from the NOAA system. Access Constraints: None resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-06-20 from the NOAA system. 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. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-06-20 from the NOAA system. Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of Aero-Metric, 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: 49625 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49625.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: -134.84996 eastBoundLongitude: -134.26305 southBoundLatitude: 58.21335 northBoundLatitude: 58.54946 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Publication Date beginPosition: 2012-04-25 endPosition: 2012-06-22 supplementalInformation: A full report for this project is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/5021/supplemental/ak2012_usgs_juneau_m5021_lidarreport.pdf A quality report for this project is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/5021/supplemental/ak2012_usgs_juneau_m5021_qualityreport.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/5021/supplemental/ak2012_usgs_juneau_m5021.kmz 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=5021 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/geoid12b/5021/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: The vertical accuracy assessment of the data has a project requirement to achieve a Fundamental Vertical Accuracy (FVA) of 24.5 cm 95% confidence level, a requirement to achieve a Consolidated Vertical Accuracy (CVA) of 36.3 cm 95th Percentile and a target value for Supplemental Vertical Accuracies (SVA) of 36.3 cm 95th Percentile. The FVA of the LAS Swath Data achieved 20.9 cm at a 95% confidence level with an RMSE of 10.7 cm utilizing (29) ground survey check points in the evaluation. The SVA results in Short Grass achieved 15.6 cm at the 95th Percentile where (30) checkpoints were used in the evaluation. The SVA results Brush achieved 32.2 cm at the 95th Percentile where (80) checkpoints were used in the evaluation. The SVA results Trees achieved 25.2 cm at the 95th Percentile where (92) checkpoints were used in the evaluation. The SVA results Urban achieved 13.8 cm at the 95th Percentile where (252) checkpoints were used in the evaluation. The CVA results for all Land Cover Classes combined achieved 21.8 cm at the 95th Percentile where (483) checkpoints were evaluated. An additional (20) ground control check points are held in reserve and supplied to the client. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Area data products collected with the Optech Gemini were acquired at or below 1500 meters above mean terrain (AMT) and have a horizontal accuracy of 0.30 meters (per manufacturers system specifications), with a nominal point spacing of 1.0 meters.; Quantitative Value: 0.3 meters, Test that produced the value: 30 cm per manufacturer system specifications result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The FVA of the LAS Swath Data achieved 20.9 cm at a 95% confidence level with an RMSE of 10.7 cm utilizing (29) ground survey check points in the evaluation.; Quantitative Value: 0.107 meters, Test that produced the value: RMSE of 0.107 m (10.7 cm) result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Complete result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: None result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: The LiDAR data was captured using AeroMetric's twin-engine fixed wing aircraft equipped with an Optech LiDAR system. The LiDAR systems includes a differential GPS unit and inertial measurement system to provide superior accuracy. Acquisition parameters: 1. Flight Height - 1500 meters or lower above mean terrain 2. Swath Width - 28 degrees 3. Sidelap - 55% 4. Nominal Post Spacing - 1.0 meters GPS and IMU processing parameters 1. Maximum baseline length - Not greater than 100 kilometers. 2. Number of base stations during LiDAR collection - A minimum of 1. 3. Maximum positional RMS of trajectory during LiDAR collection - 0.10 meters 4. IMU processing monitored for consistency and smoothness - Yes. Point Cloud Processing: 1. Horizontal Datum - NAD83 2. Horizontal Coordinates - Universal Transverse Mercator, Zone 8, in meters. 3. Vertical Datum - NAVD88 4. Geoid Model used to reduce satellite derived elevations to orthometric heights - NGS Geoid09. LiDAR Processing: 1. Point Cloud data is imported to TerraScan in a Microstation V8 (V) CAD environment on a specified 1500 meter by 1500 meter tiling scheme. 2. Analyze the data for overall completeness and consistency. This is to ensure that there are no voids in the data collection. 3. Inspect for calibration errors in the dataset using the TerraMatch software. This is accomplished by sampling the data collected across all flight lines and classify the individual lines to ground. The software will use the ground-classified lines to compute corrections (Heading, Pitch, Roll, and Scale). 4. Orientation corrections (i.e. Calibration corrections) are then applied (if needed) to the entire dataset. 5. Automatic ground classification is performed using algorithms with customized parameters to best fit the project area. Several areas of varying relief and planimetric features were inspected to verify the final ground surface. 6. AeroMetric, Inc. provided Quality Assurance and Quality Control (QA/QC) data for this project. AeroMetric captured QA/QC points in 'open terrain' land cover category that were used to test the accuracy of the LiDAR ground surface. TerraScan's Output Control Report (OCR) was used to compare the QA/QC data to the LiDAR data. This routine searches the LiDAR dataset by X and Y coordinate, finds the closest LiDAR point and compares the vertical (Z) values to the known data collected in the field. Based on the QA/QC data, a bias adjustment was determined, and the results were applied (if necessary) to the LiDAR data. A final OCR was performed with a resulting RMSE of 10.7 cm for the project. 7. After the LiDAR data is finalized for vertical placement, a macro is run via TerraScan to output a dataset generated on a per swath basis as part of the final deliverables. All points of the swath are reclassified to class 0 during this step. 8. Each tile is reviewed for accuracy and consistency of the macro ground classification. During this phase, MicroStation is used to generate line work representing water bodies and rivers. Separate line work is also placed in instances where overpasses have blocked enough valid ground returns or water gave too few ground returns to reasonably portray the ground surface. A proprietary in-house software program is then run to drape the river line work in a flowing fashion. Contours are generated on the river breaklines to review monotonicity of the draped line work. 9. Once the automatic processing and the testing of LiDAR is complete, AeroMetric meticulously reviews the generated bare-earth surface data to ensure that proper classification was achieved as part of a Quality Control process. 10. Final deliverables are generated and output to a client specified 1500 meter by 1500 meter tiling scheme. dateTime: DateTime: 2012-10-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the files in laz format via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in UTM Zone 8, NAVD88 (orthometric) heights in meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from UTM coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in meters using Geoid 09. 3. The LAS data were sorted by latitude and the headers were updated. 4. Erroneous elevations were removed. dateTime: DateTime: 2016-03-01T00:00:00 processStep: (LI_ProcessStep) description: The dataset has been mosaiced, reprojected, and clipped as needed from the original input files using PDAL and GDAL commands. dateTime: DateTime: 2025-06-20 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |