| 2018 TWDB Lidar: Coastal Texas | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:58236 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2023-05-30T18:10:31 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 222155377202 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 identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2018 TWDB Lidar: Coastal Texas alternateTitle: tx2018_coastal_m8898_metadata date: (CI_Date) date: 2018-12-17 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 58236 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/58236 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8899 protocol: WWW:LINK-1.0-http--link name: Citation URL description: Link to custom download, from the Data Access Viewer (DAV), the raster Digital Elevation Model (DEM) data that were created from this lidar data set. 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/8898/supplemental/2018CoastalTexasLiDAR_FinalQAQCReport_20181221.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8898/supplemental/580-18-SOW0050_Coastal_Texas_Lidar_GroundControlSurveyReport_04202018.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8898/breaklines/ protocol: WWW:LINK-1.0-http--link name: Citation URL description: Link to download the breaklines. 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: The Texas Water Development Board (TWDB) in cooperation with their project partners tasked Fugro Geospatial, Inc. (Fugro) under the Department of Information Resources (DIR) Geographic Information Systems (GIS) Hardware, Software and Services contract also known as the Texas Strategic Mapping (StratMap) Contract to acquire high resolution elevation data and associated products from airborne lidar systems during the 2017-2018 leaf-off season. The StratMap Program promotes inter-governmental collaboration and partnerships to purchase geospatial data products that provide cost savings and project efficiencies. Both the StratMap Program and the StratMap Contract are administered by the Texas Natural Resources Information System (TNRIS), a division of TWDB. Project partners include: Houston-Galveston Area Council (H-GAC), Harris County Flood Control District (HCFCD), and the United States Geological Survey (USGS). This Coastal Texas project consists of approximately 9,758 DO4Q tiles and is located on the Texas Coast covering much of Orange to Matagorda County along with Harris County and the surrounding area. The project includes large metropolitan areas as well as coastal areas. The Urban and Coastal AOIs consist of approximately 4.045 square miles and were acquired between January 12 and March 22, 2018 utilizing both Riegl LMS-Q680i and Riegl LMS-Q780 sensors; collecting multiple return x, y, and z as well as intensity data. Specialized in-house and commercial software processes the native lidar data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. The data were delivered with the horizontal datum of North American Datum of 1983 (NAD83, 2011) in meters and the vertical datum is the North American Vertical Datum of 1988 (NAVD88) in meters realized with GEOID12B. The NOAA Office for Coastal Management (OCM) downloaded this data set from this TNRIS site: https://data.tnris.org/collection/b5bd2b96-8ba5-4dc6-ba88-d88133eb6643 These files were processed to the Data Access Viewer (DAV) and https. The total number of files downloaded and processed was 9071. In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data and the breaklines are available for download at the links provided in the URL section of this metadata record. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: Data products generated from this project will be used for floodplain management and planning, feature extraction, water quality modeling, stream restoration potential analysis, change detection and emergency management services and will be made available in the public domain through TNRIS. credit: Texas Water Development Board, Fugro Geospatial, Inc. 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 Aug 01, 2023 at https://coast.noaa.gov/dataviewer. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8898/supplemental/tx2018_coastal_m8898.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: KML descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) edition: 12.3 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > TEXAS 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: Austin County keyword: Brazoria County keyword: Chambers County keyword: Fort Bend County keyword: Galveston County keyword: Grimes County keyword: Harris County keyword: Jefferson County keyword: Liberty County keyword: Matagorda County keyword: Montgomery County keyword: Orange County keyword: Walker County keyword: Waller County type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Geographic Names Information System date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Surface keyword: Terrain keyword: erosion type: (MD_KeywordTypeCode) theme descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Cite As: OCM Partners, [Date of Access]: 2018 TWDB Lidar: Coastal Texas [Data Date Range], https://www.fisheries.noaa.gov/inport/item/58236. 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 the TWDB or its partners, 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: 2018 TWDB Lidar DEM: Coastal Texas date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 57961 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: 58236 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/58236.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: POSGNSS 5.2; POSPac 8.0; RiProcess 1.8.3; RiWorld 5.0.2; RiAnalyze 6.2; RiServer 1.99.5; Microstation 8.5.2.55 and MicroStation CONNECT 10.00.00.25; TerraScan 018.008; TerraModeler 018.002; Lasedit 1.36.01; GeoCue 2014.1.21.5; ArcMap 10.3; Global Mapper 17; ERDAS Imagine 2016; PhotoShop CS8; Fugro proprietary software; Windows 7 64-bit Operating System \\triton\lidar\17004800_TNRIS_CoastalTX_Lidar\5_4_5_Delivery\Pilot\DEM_Raster \\triton\lidar\17004800_TNRIS_CoastalTX_Lidar\5_4_5_Delivery\Pilot\Hydro_Flattened_Breaklines \\triton\lidar\17004800_TNRIS_CoastalTX_Lidar\5_4_5_Delivery\Pilot\Intensity_Images\*.tif/tfw \\triton\lidar\17004800_TNRIS_CoastalTX_Lidar\5_4_5_Delivery\Pilot\LAS_Point_Cloud\*.las extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -96.609375 eastBoundLongitude: -93.687525 southBoundLatitude: 28.59375 northBoundLatitude: 31.031225 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-13 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-14 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-15 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-17 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-18 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-22 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-23 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-24 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-25 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-28 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-29 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-30 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-01-31 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-02-02 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-02-08 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-02-19 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-02-23 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-02-26 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-01 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-02 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-03 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-06 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-07 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-08 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-11 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-12 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-13 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-14 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-19 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-20 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-21 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2018-03-22 supplementalInformation: N/A The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "USGS-NGP Base Lidar Specification v1.2", "ldrsens" : "Riegl LMS-Q680i", "ldrmaxnr" : "7", "ldrnps" : "? 0.5", "ldrdens" : "? 4", "ldranps" : "? 0.5", "ldradens" : "? 4", "ldrfltht" : "991", "ldrfltsp" : "140", "ldrscana" : "60", "ldrscanr" : "100", "ldrpulsr" : "250", "ldrpulsd" : "3", "ldrpulsw" : "0.8994", "ldrwavel" : "1550", "ldrmpia" : "1", "ldrbmdiv" : "? 0.5", "ldrswatw" : "825", "ldrswato" : "31", "ldrcrs" : "NAD 1983 2011 UTM Zone 15N Meters", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID12B" }, "ldrinfo" : { "ldrspec" : "USGS-NGP Base Lidar Specification v1.2", "ldrsens" : "Riegl LMS-Q780i-Agg", "ldrmaxnr" : "7", "ldrnps" : "? 0.71", "ldrdens" : "2", "ldranps" : "? 0.5", "ldradens" : "? 4", "ldrfltht" : "991", "ldrfltsp" : "140", "ldrscana" : "60", "ldrscanr" : "100", "ldrpulsr" : "250", "ldrpulsd" : "3", "ldrpulsw" : "0.8994", "ldrwavel" : "1550", "ldrmpia" : "1", "ldrbmdiv" : "? 0.25", "ldrswatw" : "1150", "ldrswato" : "60", "ldrcrs" : "NAD 1983 2011 UTM Zone 15N Meters", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID12B" }, "ldraccur" : { "ldrchacc" : "RMSEx = 0.189 m; RMSEy = 0.186 m", "rawnva" : "N/A", "rawnvan" : "N/A", "clsnva" : "0.048", "clsnvan" : "0.049", "clsvva" : "0.062", "clsvvan" : "0.059" }, "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" : "1", "clasitem" : "Processed, but unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare-earth Ground" }, "lasclass" : { "clascode" : "3", "clasitem" : "Low Vegetation (0.01m to 1.00m above ground)" }, "lasclass" : { "clascode" : "4", "clasitem" : "Medium Vegetation (1.01m to 3.00m above ground)" }, "lasclass" : { "clascode" : "5", "clasitem" : "High Vegetation (greater than 3.01m above ground)" }, "lasclass" : { "clascode" : "6", "clasitem" : "Building" }, "lasclass" : { "clascode" : "7", "clasitem" : "Low Point (noise)" }, "lasclass" : { "clascode" : "9", "clasitem" : "Water" }, "lasclass" : { "clascode" : "10", "clasitem" : "Ignored Ground" }, "lasclass" : { "clascode" : "14", "clasitem" : "Culverts" }, "lasclass" : { "clascode" : "17", "clasitem" : "Bridge Decks" } }} 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=8898 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/8898/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_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: During lidar data collection the airborne GPS receiver was collecting data at 2 Hz frequency and the Dilution of Precision (PDOP) was monitored. GPS base stations were also running at the operational airports and were recording data at 1 Hz. The airborne GPS data was post-processed in DGPS mode together with the base station data to provide high accuracy aircraft positions. The GPS trajectory then was combined with the IMU data using loosely coupled approach to yield high accuracy aircraft positions and attitude angles. Then the lidar data was processed using the aircraft trajectory and raw lidar data. After boresighting the lidar data, the ground control points were measured against the lidar data by technicians using TerraScan and proprietary software and the lidar data was adjusted vertically to the ground control. The horizontal datum is NAD83(2011) in meters and the vertical datum is the North American Vertical Datum of 1988 (NAVD88) in meters. The vertical datum was realized through the use of the published/calculated ellipsoidal heights of the base station to process the aircraft trajectory and then later applying the GEOID12B model to the processed LiDAR data to obtain orthometric heights. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Horizontal accuracy of LiDAR data will be achieved by identifying coincident locations between the Intensity rasters and the horizontal checkpoints. Deviations exhibited by the LiDAR Intensity rasters relative to the checkpoints were reported as an RMSE. RMSEr is 0.265 m. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: AECOM followed the 2014 ASPRS Accuracy Standards for Digital Geospatial Data to compute the Non-vegetated Vertical Accuracy (NVA) RMSEz and Accuracyz at a 95% confidence interval (RMSEz*1.96) for checkpoints located in non-vegetated open terrain; the required NVA RMSEz is < 10 cm and the required NVA Accuracyz 95% is < 19.6 cm. AECOM utilized the 95th percentile method to determine the Vegetated Vertical Accuracy (VVA) for checkpoints located in vegetated terrain, regardless of vegetation type; the required VVA Accuracyz 95% is < 29.4 cm. The NVA RMSEz of the DEM was 4.9 cm calculated using 238 independent checkpoints. The VVA of the DEM at a 95th percentile of the absolute value of vertical errors in all vegetated land cover categories combined using 136 independent checkpoints is 11.64 cm. VVA RMSEz is 5.9 cm. 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. A sensor anomaly caused a few small areas of voids within tile stratmap17-50cm-2996134a1. 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. The Intensity Image files cover the entire project delivery boundary. A visual qualitative assessment was performed to ensure data completeness. The Intensity Image product is of good quality. 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. The DEM raster files cover the entire project delivery boundary. A visual qualitative assessment was performed to ensure data completeness. 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) Fugro proprietary software; 20870430. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: 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. 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 the 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 NPS. Visual checks of the intensity images against the project boundary were performed to ensure full coverage to the 300 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 0.5 meter NPS as well as making sure no clustering in point distribution. dateTime: DateTime: 2018-04-01T00:00:00 processStep: (LI_ProcessStep) description: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used Fugro proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas 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 ? 3 cm RMSDz within swath overlap (between adjacent swaths) with a maximum difference of ± 17 cm. 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed ground control 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: 2018-05-11T00:00:00 processStep: (LI_ProcessStep) description: Once boresighting was completed, the project was set up for automatic classification. First, the lidar data was cut into production tiles and the flight line overlap points, noise points, ground points, and building points were classified automatically. 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. These parameters were also customized to capture multiple categories of vegetation based on height (low, medium, and high vegetation). After all “low” points are classified, points remaining are reclassified automatically based on height from the ground. 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 and culvert 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, cut to the approved tile layout, and formatted to LAS v1.4. It was also re-projected to UTM Zone 15 north; NAD83(2011), meters; NAVD88(GEOID12B), meters. The file header was formatted to meet the project specification. 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. Georeferencing information is included in all LAS file headers. Each tile has File Source ID assigned to zero. 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 (0.01m to 1.00m above ground); Class 4 – Medium Vegetation (1.01m to 3.00m above ground); Class 5 – High Vegetation (greater than 3.01m above ground); Class 6 – Building; Class 7 – Low Point (Noise); Class 9 – Water; Class 10 – Ignored Ground; Class 14 – Culverts; and Class 17 – Bridge Decks. The classified point cloud data was delivered in tiles without overlap using the project tiling scheme. dateTime: DateTime: 2018-05-29T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) downloaded this data set from this TNRIS site: https://data.tnris.org/collection/b5bd2b96-8ba5-4dc6-ba88-d88133eb6643 The total number of files downloaded and processed was 9071. There were 913 files in UTM Zone 14 and 8158 files in UTM Zone 15. The data were in UTM Zone 14 and 15 North (NAD83 2011) meters coordinates and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 3 - Low Veg (0.01 - 1m above ground), 4 - Medium Veg (1.01 - 3 m above ground), 5 - High Veg (greater than 3.01 m above ground), 6 -Buildings, 7 - Low Noise, 9 - Water, 10 - Ignored Ground, 14 - Culverts, 17 - Bridge Decks. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 3, 4, 5, 6, 7, 9, 10, 14, 17. 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 Geoid 12B model, to convert from UTM Zone 14 and 15 North (NAD83 2011) coordinates in meters to geographic coordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http. dateTime: DateTime: 2019-11-19T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: Fugro collected Riegl-derived lidar over the Coastal Texas project AOI with a 0.5 meter Nominal Pulse Spacing (NPS). Data was collected when environmental conditions met the specified criteria: leaf-off and no significant snow cover or flood conditions; cloud, smoke, dust, and fog-free between the aircraft and ground. The collection for the Urban and Coastal AOIs was accomplished on January 13, 14, 15, 17, 18, 22, 23, 24, 25, 28, 29, 30, and 31, February 2, 8, 19, 23, and 26, and March 1, 2, 3, 6, 7, 8, 11, 12, 13, 14, 19, 20, 21, and 22 2018; 982 flight lines were acquired in 117 lifts. The lines were flown at an average of 3,250 feet above mean terrain. The collection was performed using the Riegl LMS-Q680i and Riegl LMS-Q780i lidar systems, serial numbers 163, 165, 421, and 961. sourceCitation: (CI_Citation) title: Coastal TX Acquisition date: (CI_Date) date: 2018-12-17 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Fugro Geospatial, Inc. role: (CI_RoleCode) originator source: (LI_Source) description: Source Contribution: All surveying activities were performed by Fugro USA Land, Inc. A total of 219 ground control points to support the lidar collection were collected in the Urban and Coastal AOIs; the points were a combination of gravel, dirt, asphalt, and concrete all in open terrain. The horizontal Datum was the North American Datum of 1983 (NAD83, 2011). The vertical datum was the North American Datum of 1988 (NAVD88). The geoid model, GEOID12B, was used to obtain the NAVD88 orthometric heights from the GRS 1980 ellipsoidal heights. sourceCitation: (CI_Citation) title: Coastal Texas; Ground Control Survey Report date: (CI_Date) date: 2018-04-06 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Fugro USA Land, inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2018-01-24 endPosition: 2018-03-16 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-08-01T06:53:53 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |