| 2019 USGS Topobathy Lidar: Potomac River, MD | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:70734 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-09-06T13:27:21 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) 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 spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2019 USGS Topobathy Lidar: Potomac River, MD alternateTitle: md2019_potomac_tb_m9892_metadata date: (CI_Date) date: 2019 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2020-03-31 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 70734 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/70734 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/geoid18/9892/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://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/MD_PotomacRiverTopoBathy_2019_D19/MD_PotomacRiver_Bathy_2019/reports/Potomac_Lidar_Project_Report_USGS.pdf protocol: WWW:LINK-1.0-http--link name: Lidar Report description: Link to the Dewberry lidar report function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/MD_PotomacRiverTopoBathy_2019_D19/MD_PotomacRiver_Bathy_2019/ protocol: WWW:LINK-1.0-http--link name: USGS Additional Info description: Link to the reports, metadata, breaklines, and spatial metadata. 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/geoid18/9892/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: Product: These lidar data are processed Classified LAS 1.4 files, formatted to 247 individual 1000 m x 1000 m tiles; used to create intensity images, land/water interface breaklines and topobathymetric DEMs as necessary. Geographic Extent: Potomac River and margins in Maryland, West Virginia, and Virginia, covering approximately 39.2 square miles. Dataset Description: The Maryland Potomac River Topobathymetric Lidar project called for the planning, acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, version 1.3. The data was developed based on a horizontal projection/datum of NAD83 (2011), Universal Transverse Mercator zone 18, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 247 individual 1000 m x 1000 m tiles, as tiled Intensity Imagery, and as tiled topobathymetric DEMs; all tiled to the same 1000 m x 1000 m schema. A merged topobathymetric DEM was also delivered. Ground Conditions: Lidar was collected in October 2019, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Dewberry established a total of 39 checkpoints that were used to calibrate the lidar to known ground locations established the project area and assess the vertical accuracy of the data. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images, Breaklines and Raster DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 1 meter cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. credit: U.S. Geological Survey 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 Sep 06, 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/geoid18/9892/supplemental/il2019_potomac_m9892.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: kmz 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: 12.3 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MARYLAND keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > WEST VIRGINIA 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: 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]: 2019 USGS Topobathy Lidar: Potomac River, MD [Data Date Range], https://www.fisheries.noaa.gov/inport/item/70734. 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: 2021 USGS Topobathy Lidar: Potomac River, MD date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 69921 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: 70734 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/70734.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: Leica LSS; Bayesmap; LAStools; Microstation; Terrascan; ArcGIS 10.x; Microsoft Windows 10 Enterprise Service Pack 1 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -77.805817 eastBoundLongitude: -77.115929 southBoundLatitude: 38.918843 northBoundLatitude: 39.457914 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2019-10-21 endPosition: 2019-10-26 supplementalInformation: USGS Contract No. G16PC00020 CONTRACTOR: Dewberry Engineers SUBCONTRACTOR: IIC Technologies Lidar data were acquired and calibrated by IIC. All follow-on processing was completed by the prime contractor. A complete description of this dataset is available in the Final Project Report that was submitted to the U.S. Geological Survey. The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "USGS-NGP Lidar Base Specification V1.3", "ldrsens" : "Leica Hawkeye 4X (Topo Channels)", "ldrmaxnr" : "15", "ldrnps" : "0.35", "ldrdens" : "8", "ldranps" : "0.35", "ldradens" : "8", "ldrfltht" : "400", "ldrfltsp" : "140", "ldrscana" : "40", "ldrscanr" : "140", "ldrpulsr" : "500", "ldrpulsd" : "Unreported", "ldrpulsw" : "Unreported", "ldrwavel" : "1064", "ldrmpia" : "0", "ldrbmdiv" : "0.5", "ldrswatw" : "280", "ldrswato" : "30", "ldrcrs" : "NAD 1983 (2011) UTM Zone 18 Meters", "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B" }, "ldrinfo" : { "ldrspec" : "USGS-NGP Lidar Base Specification V1.3", "ldrsens" : "Leica Hawkeye 4X (Shallow/Deep Bathy Channels)", "ldrmaxnr" : "15", "ldrnps" : "0.71", "ldrdens" : "2", "ldranps" : "0.71", "ldradens" : "2", "ldrfltht" : "400", "ldrfltsp" : "140", "ldrscana" : "40", "ldrscanr" : "140", "ldrpulsr" : "35/10", "ldrpulsd" : "Unreported", "ldrpulsw" : "Unreported", "ldrwavel" : "515", "ldrmpia" : "0", "ldrbmdiv" : "4", "ldrswatw" : "280", "ldrswato" : "30", "ldrcrs" : "NAD 1983 (2011) UTM Zone 18 Meters", "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B" }, "ldraccur" : { "ldrchacc" : "0", "rawnva" : "0", "rawnvan" : "0", "clsnva" : "0", "clsnvan" : "0", "clsvva" : "0", "clsvvan" : "0" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "6", "laswheld" : "Withheld points were identified in these files using the standard LAS Withheld bit", "lasolap" : "The LAS overlap bit was not utilized for this dataset", "lasintr" : "16", "lasclass" : { "clascode" : "1", "clasitem" : "Processed, Unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare Earth, Ground" }, "lasclass" : { "clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : { "clascode" : "17", "clasitem" : "Bridge Deck" }, "lasclass" : { "clascode" : "18", "clasitem" : "High Noise" }, "lasclass" : { "clascode" : "40", "clasitem" : "Bathymetric Point" }, "lasclass" : { "clascode" : "41", "clasitem" : "Water Surface" }, "lasclass" : { "clascode" : "42", "clasitem" : "Synthetic Water surface" }, "lasclass" : { "clascode" : "45", "clasitem" : "Water Column" } }} 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: 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=9892/details/9892 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/geoid18/9892/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. 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: Horizontal Positional Accuracy evaluationMethodDescription: Six checkpoints were determined to be photo-identifiable in the intensity imagery and were used to test the horizontal accuracy of the lidar dataset. As only six checkpoints were photo-identifiable, the results are not statistically significant enough to report as a final tested value. Using NSSDA methodology (endorsed by the ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014)), horizontal accuracy at the 95% confidence level (called ACCURACYr) is computed by the formula RMSEr * 1.7308 or RMSExy * 2.448. No horizontal accuracy requirements or thresholds were provided for this project. However, lidar datasets are generally calibrated by methods designed to ensure a horizontal accuracy of 1 meter or less at the 95% confidence level. This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 41 cm RMSEx/RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 1 meter at a 95% confidence level. Six checkpoints were photoidentifiable but do not produce a statistically significant tested horizontal accuracy value. Using this small sample set of photo-identifiable checkpoints, positional accuracy of this dataset was found to be RMSEx = 28.5 cm and RMSEy = 38.5 cm which equates to +/- 82.8 cm at 95% confidence level. While not statistically significant, the results of the small sample set of checkpoints are within the produced to meet horizontal accuracy. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The topographic portion of this lidar dataset was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10 cm RMSEz Vertical Accuracy Class. Actual NVA accuracy was found to be RMSEz =3.9 cm, equating to +/- 7.6 cm at 95% confidence level. Actual VVA accuracy was found to be +/- 5.9 cm at the 95th percentile. The bathymetric portion of this lidar dataset was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for an 18.5 cm RMSEz Vertical Accuracy Class. Actual bathymetric vertical accuracy was found to be RMSEz = 8.4 cm, equating to +/- 16.5 cm at 95% confidence level. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Topobathymetric data covers the project boundary to the fullest extent possible depending on water clarity, environmental conditions, and sensor signal returns. 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: Data covers the entire area specified for this project. result: (missing) lineage: (LI_Lineage) statement: The NOAA Office for Coastal Management (OCM) downloaded this data from the USGS rockyweb site. OCM processed the data to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from AWS S3. processStep: (LI_ProcessStep) description: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The initial points for each mission calibration were inspected for flight line errors, flight line overlap, slivers or gaps in the data, point data minimums, or issues with the lidar unit or GPS. Roll, pitch and scanner scale were optimized during the calibration process until the relative accuracy was met. Dewberry utilized Bayesmap StripAlign for this alignment procedure. This alignment procedure corrected systematic issues globally, per aircraft lift, per flightline, and finally based on local errors along the flight trajectory. Error adjustments included internal sensor parameters. Due to the complex geometric relationship of the elliptical scan pattern the forward and reverse directions must be aligned independently. Additionally, since the green and NIR scanner map different surfaces, they were also aligned independently, then corrected to match each other. Difference rasters (DZ orthos) were generated, adjustment parameters were reviewed, and registration/match regions were reviewed to ensure data quality. A final vertical accuracy check of the boresighted flight lines was completed against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level was met. Point classification was performed according to USGS Lidar Base Specification 1.3. Bare earth DEMs were exported from the classified point cloud. Synthetic points generated by Leica refraciton correction algorithms are present in this dataset. Please see the final project report for more details on the synthetic points dateTime: DateTime: 2020-03-01T00:00:00 processStep: (LI_ProcessStep) description: Dewberry used algoritms in TerraScan to create the intial ground/submerged topography surface. Dewberry used rasterized aggregate extents of refracted points to create automated 2-D breaklines with LAStools and ArcGIS. Light travels at different speeds in air versus water and its speed and direction of travel change when it enters the water column. The refraction correction process accounts for this difference by adjusting the depth (distance traveled) and horizontal position (change of angle/direction) of the lidar points acquired within water. These breaklines delineate areas where the refraction correction was applied to the lidar data by Riegl's automated refraction correction software based on the software's detection of water. Where the automated process missed discrete water bodies that did not contain valid bathymetry (submerged topography) data, breaklines were manually drawn and added to a separate feature class to ensure the correct classification of the point cloud. Dewberry used the 2-D refraction extents and additional bathy features to classify the bathymetric bottom and ground points properly in TerraScan. Geometrically unused points at the edges of flight lines were flagged using the withheld bit. This includes synthetically generated class 42 (synthetic water surface) points at the edges of flight lines. All class 42 points were flagged using the synthetic bit. All lidar data was peer-reviewed. Dewberry's QAQC also included creating void polygons for use during review. All necessary edits were applied to the dataset. GeoCue software was used to update LAS header information, including all projection and coordinate reference system information. The final lidar data are in LAS format 1.4 and point data record format 6. All data was then verified by an Independent QC department within Dewberry. The independent QC was performed by separate analysts who did not perform manual classification or editing. The independent QC involved quantitative and qualitative reviews. dateTime: DateTime: 2020-03-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) downloaded 247 laz point data files from this USGS site: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/MD_PotomacRiverTopoBathy_2019_D19/MD_PotomacRiver_Bathy_2019/LAZ/ The data were in UTM Zone 18N (NAD83 (2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 17 - Bridge Deck, 18 - High Noise, 40 - Bathymetry bottom, 41 - Water Surface, 42 - Synthetic Water Surface, 45 - No bathymetry bottom found. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 17, 18, 40, 41 ,42, 45. 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 NAD83 (2011) ellipsoid elevations using the Geoid12B model b. Convert from UTM Zone 18N (NAD83 (2011), meters coordinates to geographic coordinates c. Assign the geokeys, sort the data by gps time and zip the data to database and to AWS S3 dateTime: DateTime: 2023-09-01T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: USGS LAZ Download - MD_PotomacRiverTopoBathy_2019 date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: USGS contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/MD_PotomacRiverTopoBathy_2019_D19/MD_PotomacRiver_Bathy_2019/LAZ/ protocol: WWW:LINK-1.0-http--link name: USGS LAZ download description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) publisher 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-09-06T10:26:22 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |