| 2023 NOAA Lidar: AK Coastal Communities (Dillingham/Aleknagik, Ekuk, Ekwok, Koliganek, Manokotak, New Stuyahok) | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:77581 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation contact: (CI_ResponsibleParty) organisationName: Office for Coastal Management 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: 2025-08-28T12:43:54 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) / UTM zone 4N 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/6333/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6333 version: 6.18.3 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2023 NOAA Lidar: AK Coastal Communities (Dillingham/Aleknagik, Ekuk, Ekwok, Koliganek, Manokotak, New Stuyahok) alternateTitle: ak2023_cstl_comms_m10424 date: (CI_Date) date: 2023-01-01 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2025 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 77581 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/77581 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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid12b/10424/ept.json protocol: WWW:LINK-1.0-http--link name: Entwine Point Tile (EPT) description: Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. 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/10424/supplemental/AK_Communities_2024_NIR_lidar_Report_REVISED_08062024.pdf protocol: WWW:LINK-1.0-http--link name: Lidar Report description: Link to the NV5 lidar 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/10424/breaklines/index.html protocol: WWW:LINK-1.0-http--link name: Breaklines description: Link to the hydro breaklines in Esri gdb and OGC GeoPackage formats. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid12b/10424/ept.json protocol: WWW:LINK-1.0-http--link name: Potree 3D View description: Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. 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: Original Product: Classified LAZ 1.4 files, formatted to 1611 individual 750m x 750m tiles covering the NOAA AK Communities 2023 project area. Original Geographic Extent: This dataset and derived products encompass six areas in southwest Alaska, covering approximately 183,738 acres. Original Dataset Description: The NOAA AK Coastal Communities 2023 Lidar project called for the planning, acquisition, and processing of lidar data collected to Quality Level 1 (QL1) standards. Project specifications are based on the U.S. Geological Survey National Geospatial Program Lidar Base Specification Version 2023, Revision A. The data was developed based on the NAD83 2011 horizontal datum and the NAVD88 Geoid 12b vertical datum. Data was projected in UTM Zone 4N, Meters. Lidar data was delivered as calibrated and classified LAZ 1.4 files. Non-Vegetated Vertical Accuracy (NVA) was assessed using 124 check points located on bare earth in clear, unobstructed areas. Vegetated Vertical Accuracy (VVA) was assessed using 37 check points in Tall Grass, Forest, and Shrub landcover types. Single swath nominal pulse spacing (NPS) was designed to be 0.35 at nadir. Aggregate Nominal Pulse Spacing (ANPS) was calculated to be 0.269 using all valid first return points. Derived products include: Intensity Imagery, Hydro-flattened Bare Earth Digital Elevation Models (DEMs), Highest Hit Digital Surface Models (DSMs), and 3D waters edge breaklines. Ground Condition: Ground conditions were free of snow and acquisition occurred free of smoke, fog and cloud cover. 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: The purpose of the lidar data was to produce a high accuracy 3D dataset that meets all necessary standards laid out by the 3D Elevation Program and the NOAA AK Communities 2023 contract. The lidar point cloud data were used to create classified lidar LAZ files, intensity images, hydro-flattened DEMs, highest hit DSMs, and 3D breaklines of rivers and lakes within the study area. credit: NOAA Office for Coastal Management (OCM), NV5 Geospatial 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 2025-08-28 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 descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION 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) edition: 17.0 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > ALASKA keyword: VERTICAL LOCATION > LAND SURFACE type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) edition: 20.8 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: 17.2 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 17.2 descriptiveKeywords: (MD_Keywords) keyword: DOC/NOAA/NOS/OCM > Office of Coastal Management, National Ocean Service, NOAA, U.S. Department of Commerce type: (MD_KeywordTypeCode) dataCentre thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Data Center Keywords date: (CI_Date) date: 2017-04-24 dateType: (CI_DateTypeCode) publication edition: 8.5 citedResponsibleParty: GCMD Landing Page descriptiveKeywords: (MD_Keywords) keyword: Lidar 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-08-28 from the NOAA system. Cite As: Office for Coastal Management, [Date of Access]: 2023 NOAA Lidar: AK Coastal Communities (Dillingham/Aleknagik, Ekuk, Ekwok, Koliganek, Manokotak, New Stuyahok) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/77581. 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) useConstraints: (MD_RestrictionCode) license otherConstraints: Anchor: Universal (CC0 1.0) Public Domain Dedication To the extent possible under law, the U.S. Government has waived all copyright and related or neighboring rights to this dataset. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-08-28 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-08-28 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. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-08-28 from the NOAA system. 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: 2023 NOAA Lidar DEM: AK Coastal Communties (Dillingham/Aleknagik, Ekuk, Ekwok, Koliganek, Manokotak, New Stuyahok) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 77586 associationType: (DS_AssociationTypeCode) crossReference 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: 77581 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocm/dmp/pdf/77581.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 environmentDescription: LiDAR Mapping Suite 2.4, Applanix PosPac 7.1, Microstation CONNECT version, TerraScan Version 20, TerraModeler Version 20, TerraMatch Version 20, ESRI ArcGIS 10.3, Windows 10 Operating System extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -159.09 eastBoundLongitude: -158.81 southBoundLatitude: 58.91 northBoundLatitude: 59.05 geographicElement: (EX_GeographicDescription) geographicIdentifier: (MD_Identifier) code: Manokotak collection area geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -158.86 eastBoundLongitude: -158.42 southBoundLatitude: 58.98 northBoundLatitude: 59.37 geographicElement: (EX_GeographicDescription) geographicIdentifier: (MD_Identifier) code: Dillingham/Aleknagik collection area geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -158.57 eastBoundLongitude: -158.43 southBoundLatitude: 58.77 northBoundLatitude: 58.96 geographicElement: (EX_GeographicDescription) geographicIdentifier: (MD_Identifier) code: Ekuk collection area geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -157.53 eastBoundLongitude: -157.44 southBoundLatitude: 59.32 northBoundLatitude: 59.39 geographicElement: (EX_GeographicDescription) geographicIdentifier: (MD_Identifier) code: Ekwok collection area geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -157.4 eastBoundLongitude: -157.29 southBoundLatitude: 59.43 northBoundLatitude: 59.47 geographicElement: (EX_GeographicDescription) geographicIdentifier: (MD_Identifier) code: New Stuyahok collection area geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -157.31 eastBoundLongitude: -157.19 southBoundLatitude: 59.68 northBoundLatitude: 59.73 geographicElement: (EX_GeographicDescription) geographicIdentifier: (MD_Identifier) code: Koliganek collection area temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Date of collection for Mankotak | Currentness: Ground Condition timePosition: 2023-08-22 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Date of collection for Manokotak | Currentness: Ground Condition timePosition: 2023-09-04 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Date of collection for Dillingham/Aleknagik | Currentness: Ground Condition timePosition: 2023-09-04 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: Dates of collection for Dillingham/Aleknagik | Currentness: Ground Condition beginPosition: 2023-09-17 endPosition: 2023-09-18 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Date of collection for Ekuk | Currentness: Ground Condition timePosition: 2023-09-17 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Date of collection for Ekwok | Currentness: Ground Condition timePosition: 2023-09-06 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Date of collection for New Stuyahok | Currentness: Ground Condition timePosition: 2023-09-06 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Date of collection for Koliganek | Currentness: Ground Condition timePosition: 2023-08-22 supplementalInformation: USGS Contract No. 1305M221DNCNP0018 CONTRACTOR: NV5 Geospatial. Notes: Tile UTM4_0331_0749_4 does not have a .laz file associated with it. Due to the area being completely encompassed by a water body, this tile has no lidar returns and therefore no file was generated. Ground Control Points were acquired and calibrated by NV5 Geospatial. All lidar data acquisition, calibration, and follow-on processing were completed by NV5 Geospatial. The following are the USGS lidar fields in JSON: { "ldrinfo " :{ "ldrspec " :" U.S. Geological Survey National Geospatial Program Lidar Base Specification Version 2023, Revision A ", "ldrsens " :" Riegl VQ-780ii-S ", "ldrmaxnr " :" 14 ", "ldrnps " :" 0.35 ", "ldrdens " :" 8 ", "ldranps " :" 0.269 ", "ldradens " :" 13.843 ", "ldrfltht " :" 2058 ", "ldrfltsp " :" 145 ", "ldrscana " :" 58.5 ", "ldrscanr " :" Uniform Point Spacing ", "ldrpulsr " :" 1285 ", "ldrpulsd " :" 3 ", "ldrpulsw " :" 0.473 ", "ldrwavel " :" 1064 ", "ldrmpia " :" 1 ", "ldrbmdiv " :" 0.23 ", "ldrswatw " :" 2305 ", "ldrswato " :" 57 ", "ldrgeoid " :" Geoid 12b " }, "ldraccur " :{ "ldrchacc " :" 2.01 ", "rawnva " :" 0.096 ", "rawnvan " :" 124 " }, "lasinfo " :{ "lasver " :" 1.4 ", "lasprf " :" 6 ", "laswheld " :" Withheld (ignore) points are identified in these files using the standard LAS Withheld bit. ", "lasolap " :" Swath "overage" points were identified in these files using the standard LAS overlap bit. ", "lasintr " :" 16 ", "lasclass " :{ "clascode " :" 1 ", "clasitem " :" Processed, but Unclassified " }, "lasclass " :{ "clascode " :" 2 ", "clasitem " :" Bare earth ground " }, "lasclass " :{ "clascode " :" 5 ", "clasitem " :" High Vegetation " }, "lasclass " :{ "clascode " :" 6 ", "clasitem " :" Building " }, "lasclass " :{ "clascode " :" 7 ", "clasitem " :" Low Noise " }, "lasclass " :{ "clascode " :" 9 ", "clasitem " :" Water " }, "lasclass " :{ "clascode " :" 17 ", "clasitem " :" Bridge Decks " }, "lasclass " :{ "clascode " :" 18 ", "clasitem " :" High Noise " }, "lasclass " :{ "clascode " :" 20 ", "clasitem " :" Ignored Ground Near Breaklines " }, "lasclass " :{ "clascode " :" 22 ", "clasitem " :" Temporal Water Surface " } } } return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: (inapplicable) version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAS/LAZ - LASer version: (missing) fileDecompressionTechnique: LAZ 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=10424 /details/10424 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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/10424/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, UTM Zone 4N NAD83(2011) meters coordinates and elevations in NAVD88(GEOID12B) meters. 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: Lidar horizontal accuracy is a function of Global Navigation Satellite System (GNSS) derived positional error, flying altitude, and INS derived attitude error. The obtained RMSEr value is multiplied by a conversion factor of 1.7308 to yield the horizontal component of the National Standards for Spatial Data Accuracy (NSSDA) reporting standard where a theoretical point will fall within the obtained radius 95 percent of the time. Based on a flying altitude of 2478 meters, an IMU error of 0.015 decimal degrees, and a GNSS positional error of 0.027 meters, this project was produced to meet 2.009 m horizontal accuracy at the 95% confidence level (1.161 m RMSEr). result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class. The NVA was tested with 124 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 124 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.049 meters resulting in an AccuracyZ at the 95% confidence level of 0.096 meters. NVA AccuracyZ has been tested and meets the required 0.196 meter NVA at 95% confidence level using (RMSEz * 1.9600) for the unclassified lidar point cloud 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: These LAZ 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 Non-Vegetated Vertical Accuracy specifications. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Classified LAS files were tested by NV5 for vertical accuracy. All data is seamless from one tile to the next, no gaps or no data areas. result: (missing) lineage: (LI_Lineage) statement: This data was collected by NV5 Geospatial for the NOAA Office for Coastal Management (OCM). 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 Geoid 12b correction. 5. Import raw laser points into manageable blocks 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: 2024-04-04T00: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 final NVA, VVA, and density information for the project using ground control quality check points. dateTime: DateTime: 2024-04-04T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) processed 1611 LAZ files collected by NV5 Geospatial. The files were in UTM Zone 4N NAD83(2011), meters coordinates and the elevations were in NAVD88 (GEOID12B) meters. The LAZ files had these classifications: 1 = unclassified; 2 = ground (or Bare Earth); 5 = high vegetation (greater than 2 m), 6 = buildings, 7 = low point (noise); 9 = water; 17 = bridges; 18 = high noise; 20 = ignored ground, 22 = temporal exclusion. Some of the class 1 and all of the class 7 points also had the withheld bit set. Those withheld points were not included in the OCM processing. NOAA OCM processed the 1, 2, 5, 6, 9, 17, 18, 20, and 22 point classes to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to ellipsoid elevations using the GEOID12B model b. Convert from UTM Zone 4N (NAD83 2011) meters coordinates to geographic coordinates c. Assign the geokeys, to sort the data by gps time and zip the data to database and to AWS S3. dateTime: DateTime: 2025-08-27T00:00:00 processor: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: NOAA OCM Lidar date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: NOAA OCM role: (CI_RoleCode) originator 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-08-28 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |