| 2018 USGS Lidar: Matagorda Bay, TX | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:58921 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2020-09-15T00:00:00 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 11117888002 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) date: (CI_Date) date: 2008-11-12 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/CoordRefSystem/6318/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6318 version: 6.18.3 (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters alternateTitle: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml name: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters description: Link to Geographic Markup Language (GML) description of reference system. function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) resourceProvider citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.epsg.org/ name: European Petroleum Survey Group Geodetic Parameter Registry description: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. function: (CI_OnLineFunctionCode) search role: (CI_RoleCode) publisher VerticalCS: metaDataProperty: CommonMetaData: type: vertical informationSource: OGP revisionDate: 2006-11-28 isDeprecated: false identifier: urn:ogc:def:cs:EPSG::6499 name: Vertical CS. Axis: height (H). Orientation: up. UoM: meter. remarks: Used in vertical coordinate reference systems. axis: CoordinateSystemAxis: descriptionReference: urn:ogc:def:axis-name:EPSG::9904 identifier: urn:ogc:def:axis:EPSG::114 axisAbbrev: H axisDirection: up code: urn:ogc:def:crs:EPSG::5703 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2018 USGS Lidar: Matagorda Bay, TX alternateTitle: TX_MatagordaBay_2018 date: (CI_Date) date: 2019-09-17 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 58921 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9029/supplemental/TX_Matagorda%20Bay_2018_D18_2018_D18_Process_Descriptions.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9029/supplemental/Matagorda_TX_report.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9029/supplemental/TX_Matagorda_Bay_2018_D18_Accuracy_Report_20191022.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9029/supplemental/TX_Matagorda%20Bay_2018_D18_Accuracy_Report.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9029/supplemental/TX_Matagorda%20Bay_2018_D18_Collection_Report.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/ protocol: WWW:LINK-1.0-http--link name: NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) description: The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: Geographic Extent: The entire project area covers 705 square miles in coastal Texas along Matagorda Bay. Dataset Description: This TX_Matagorda Bay_2018_D18 project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at an aggregate nominal pulse spacing (ANPS) of 1.0 meters (4ppsm). Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2. The data was developed based on a horizontal projection/datum of NAD83 (2011), Universal Transverse Mercator zone 14N, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 1500 m x 1500 m tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 1500 m x 1500 m schema. Ground Conditions: Lidar data was collected from January 24 through January 29, 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, Terrasurv, Inc. established a total of 12 ground control points that were used to calibrate the lidar to known ground locations established throughout the entire project area. An additional 80 independent accuracy checkpoints, 45 NVA points and 35 VVA points, were used to assess the vertical accuracy of the data. One additional NVA checkpoint collected by Terrasurv in 2018 was used to assess the vertical accuracy of the raw point cloud data along with the 45 NVA points collected in 2019. These checkpoints were not used to calibrate or post process the data. NOAA's OCM retrieved the data from the USGS RockyFTP website. Data were in UTM zones 14 & 15N and had the following classificaitons; 1 - Never Classified, 2 - Ground, 3 - Low Vegetation, 4 - Medium Vegetation, 5 - High Vegetation, 6 - Building, 7 - Low Noise, 9 - Water, 10 - Ignored Ground, 14 - Culvert, 17 - Bridge Deck. All files and classifications were processed to the Digital Coast. Derived products may be retrieved from the USGS National Map. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: This high resolution lidar data will support the Natural Resources Conservation Service (NRCS) initiatives. credit: USGS, Fugro The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed Oct 20, 2020 at https://coast.noaa.gov/dataviewer. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9029/supplemental/extent_MatagordaBay2018_m9029.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: KML descriptiveKeywords: (MD_Keywords) keyword: Earth Science > Land Surface > Topography > Terrain Elevation keyword: Earth Science > Oceans > Bathymetry/Seafloor Topography > Bathymetry > Coastal Bathymetry keyword: Earth Science > Oceans > Coastal Processes > Coastal Elevation type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America keyword: U.S. Coastline keyword: Vertical Location > Land Surface type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America > Texas > Matagorda Bay type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Geographic Names Information System date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Earth Remote Sensing Instruments > Active Remote Sensing > Profilers/Sounders > Lidar/Laser Sounders > LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Aircraft > Aircraft type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_Constraints) useLimitation: NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None | Use Constraints: Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners resourceConstraints: (MD_SecurityConstraints) classification: (MD_ClassificationCode) unclassified classificationSystem: (missing) handlingDescription: (missing) aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 58921 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/58921.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 spatialResolution: (MD_Resolution) distance: Distance: .5 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: POSGNS 5.2; POSPac 6.2; RiProcess 1.8.3; RiWorld 5.0.2; RiAnalyze 6.2; RiServer 1.99.5; Microstation CONNECT 10.00.00.25; TerraScan 017.039 and 016.013; TerraModeler 016.001; Lasedit 1.35.07; GeoCue 2014.1.21.5; ArcMap 10.3; Global Mapper 17.1.2; ERDAS Imagine 2016; PhotoShop CS8; Fugro proprietary software; Windows 7 64-bit Operating System \\server\directory path\*.las \\server\directory path\*.las \\server\directory path\*.img \\server\directory path\*.gdb \\server\directory path\*.tif/tfw 1440 GB extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -96.392059 eastBoundLongitude: -95.936004 southBoundLatitude: 28.358147 northBoundLatitude: 29.141899 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Collection Dates | Currentness: Ground Condition timePosition: 2019-01-24 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Collection dates. | Currentness: Ground Condition timePosition: 2019-01-25 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Collection dates. | Currentness: Ground Condition timePosition: 2019-01-27 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Collection dates. | Currentness: Ground Condition timePosition: 2019-01-28 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Collection dates. | Currentness: Ground Condition timePosition: 2019-01-29 supplementalInformation: USGS Contract No. G17PC00015 CONTRACTOR: Fugro Geospatial, Inc. SUBCONTRACTOR: Terrasurv, Inc. Ground control and checkpoints collected by Terrasurv, Inc. All processing was completed by the prime contractor. Breakline File Type = GDB Breakline Elevation Units = Meters Downhill Treatment Applied = Monotonic Type of Hydro Treatment Required = Hydro-flattened DEM Raster File Type = ERDAS IMAGINE Bit Depth/Pixel Type = 32-bit float Raster Cell Size = 1.0 Meter Interpolation or Resampling Technique = Triangulated Irregular Network (TIN) Network Required Vertical Accuracy = 19.6 cm NVA Intensity Imagery Raster File Type = GeoTIFF Bit Depth/Pixel Type = 8 bit Raster Cell Size = 1.0 Meter Intensity Values Normalized To = 16 BIT The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "USGS-NGP Base Lidar Specification v1.2", "ldrsens" : "ALS80", "ldrmaxnr" : "6", "ldrnps" : "0.5", "ldrdens" : "4", "ldranps" : "0.5", "ldradens" : "4", "ldrfltht" : "2800", "ldrfltsp" : "150", "ldrscana" : "29", "ldrscanr" : "53", "ldrpulsr" : "610", "ldrpulsd" : "2.5", "ldrpulsw" : "0.75", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.26", "ldrswatw" : "1400", "ldrswato" : "15", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID12B" }, "ldraccur" : { "ldrchacc" : "0.237", "rawnva" : "0.081", "rawnvan" : "46", "clsnva" : "0.068", "clsnvan" : "36", "clsvva" : "0.236", "clsvvan" : "17" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "6", "laswheld" : "There were no withheld points identified in this project. All points were used in the classification.", "lasolap" : "Swath "overage" points were identified in these files using the standard LAS overlap bit.", "lasintr" : "16 bit", "lasclass" : { "clascode" : "0", "clasitem" : "Collected, never classified" }, "lasclass" : { "clascode" : "1", "clasitem" : "Processed, but unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare-earth ground" }, "lasclass" : { "clascode" : "3", "clasitem" : "Low Vegetation" }, "lasclass" : { "clascode" : "4", "clasitem" : "Medium Vegetation" }, "lasclass" : { "clascode" : "5", "clasitem" : "High Vegetation" }, "lasclass" : { "clascode" : "6", "clasitem" : "Buidling" }, "lasclass" : { "clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : { "clascode" : "9", "clasitem" : "Water" }, "lasclass" : { "clascode" : "10", "clasitem" : "Ignored Ground" }, "lasclass" : { "clascode" : "14", "clasitem" : "Culverts" }, "lasclass" : { "clascode" : "17", "clasitem" : "Bridge Decks" }, "lasclass" : { "clascode" : "18", "clasitem" : "High Noise" } }} return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAZ version: (missing) distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9029 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9029 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: 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 2774 m flying altitude above ground, the estimated horizontal accuracy is RMSEr = 0.354. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The project specifications require that the Non-Vegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. The required accuracy (ACCz) is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSEz of 10 cm in the “open terrain” and/or “Urban” land cover categories. This is a required accuracy. The NVA for the AOI was tested with 46 checkpoints. The checkpoints were independent and not used in the calibration or post processing of the lidar point cloud data. The surveyed checkpoints were distributed throughout the project area. Tested quantitative value = 0.081 meters NVA at 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). The NVA of the raw lidar point cloud swath files was calculated against TINs derived from the final calibrated and controlled swath data using 46 independent checkpoints. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: A complete iteration of processing (GPS/IMU Processing, Raw Lidar Data Processing, and Verification of Coverage and Data Quality) was performed to ensure that the acquired data was complete, uncorrupted, and that the entire project area had been covered without gaps between flight lines. No void areas or missing data exist. The raw point cloud is of good quality and data passes Vertical Accuracy requirements. 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. No void areas or missing data exist. The classified point cloud is of good quality and data passes Vertical Accuracy requirements. The Hydro Breaklines cover the entire project delivery boundary and extend beyond the boundary in a few locations. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The Hydro Breakline product is of good quality. 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 GPS base stations in the project area. 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). The following software was used for the validation: 1) RiProcess 1.8.3, RiWorld 5.0.2, RiAnalyze 6.2, RiServer 1.99.5; and 2) Fugro proprietary software; 20180607. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Flight status was communicated during data collection. All acquired lidar data went through a preliminary review to assure that complete coverage had been 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 processed using the airport GPS base station data. The following GPS base station was utilized: Fugro (FGI_8003, TXPV, TXBC, FUSAL_100, temp_LBX). 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 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.5 meter ANPS. Visual checks of the intensity images against the project boundary were performed to ensure full coverage to the 100 meter buffer beyond the project boundary. The intensity histogram was analyzed to ensure the quality of the intensity values. 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 1.0 meter ANPS as well as making sure there is no clustering in point distribution. dateTime: DateTime: 2019-02-15T00: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 within 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 the matching between flight line overlaps 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. The relative accuracy was 6 cm within individual swaths (smooth surface repeatability) and 8 cm RMSD within swath overlap (between adjacent swaths) with a maximum difference of ± 16 cm. 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 RMSEz (non-vegetated) 10 cm, NVA 19.6 cm 95% Confidence Level was met. dateTime: DateTime: 2019-03-30T00: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 low noise points, high 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. Bridge deck points were classified as well during the interactive editing 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). 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 14 north; 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 6 with Adjusted Standard GPS Time at a precision sufficient to allow unique timestamps for each pulse. Correct and properly formatted georeference information as Open Geospatial Consortium (OGC) well known text (WKT) was assigned in all LAS file headers. Each tile has unique File Source ID assigned. The Point Source ID matches to the flight line ID in the flight trajectory files. Intensity values are included for each point, normalized to 16-bit. The following classifications are included: Class 1 – Processed, but unclassified; Class 2 – Bare earth ground; Class 3, Low Vegetation; Class 4, Medium Vegetation; Class 5, High Vegetation; Class 6, Building; Class 7 – Low Noise; Class 9 – Water; Class 10 – Ignored Ground; Class 14, Culverts; Class 17 – Bridge Decks; and Class 18 – High Noise. The classified point cloud data was delivered in tiles without overlap using the project tiling scheme. dateTime: DateTime: 2019-03-30T00:00:00 processStep: (LI_ProcessStep) description: NOAA's OCM retrieved the data from the USGS RockyFTP website. Data were in UTM zones 14 & 15N and had the following classificaitons; 1 - Never Classified, 2 - Ground, 3 - Low Vegetation, 4 - Medium Vegetation, 5 - High Vegetation, 6 - Building, 7 - Low Noise, 9 - Water, 10 - Ignored Ground, 14 - Culvert, 17 - Bridge Deck. All files and classifications were processed to the Digital Coast. Derived products may be retrieved from the USGS National Map. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12b model, to convert from UTM 14 & 15, NAD83 (2011), meters coordinates to geographic coordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http. processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: Under Fugro’s direction, all surveying activities were performed by Fugro's approved ID/IQ subcontractor Terrasurv, Inc. A total of 12 ground control points to support the lidar collection, along with 45 NVA and 35 VVA checkpoints were collected. The National Spatial Reference System (NSRS) was used to provide control for the network. Three Continuously Operating Reference Stations (CORS) were included in the network, as well as two existing NSRS benchmarks. The horizontal datum was the North American Datum of 1983 – NAD83 (2011), epoch 2010.0. The vertical datum was the North American Vertical Datum of 1988 (NAVD88), realized with GEOID12B. sourceCitation: (CI_Citation) title: Matagorda, TX Report of Survey date: (CI_Date) date: 2019-03-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Terrasurv, Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2019-01-15 endPosition: 2019-03-01 source: (LI_Source) description: Source Contribution: Fugro collected ALS-derived lidar over the TX_Matagorda Bay_2018_D18 AOI with 1.0 meter ANPS. Data was collected when environmental conditions meet the criteria specified. To be specific, the following conditions existed prior to launch of the aircraft: 1) Cloud and fog-free between the aircraft and ground, 2) Snow free, 3) No unusual flooding or inundation, and 4) Leaf off. The collection for the TX_Matagorda Bay_2018_D18 AOI was accomplished on January 24, 25, 27, 28 and 29; data was acquired in 7 lifts. Lift 190124_133_33780026_01; lift 190125_130_33780026_01; lift 190125_130_33780026_02, lift 190125_133_33780026_02, lift 190127_130_33780026_03, lift 190128_130_33780026_04, and lift 190129_130_33780026_05. The collection was performed using Leica ALS80 lidar systems, serial numbers 130 and 133. sourceCitation: (CI_Citation) title: TX_Matagorda Bay_2018_D18 date: (CI_Date) date: 2019-09-17 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Fugro role: (CI_RoleCode) originator processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org) Processing notes: dateTime: DateTime: 2020-10-20T05:12:52 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |