<?xml version="1.0" encoding="UTF-8"?>
<inport-metadata xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 version="1.11"
                 source="https://www.fisheries.noaa.gov">
   <item-identification>
      <catalog-item-id>76200</catalog-item-id>
      <title>2023 USGS Lidar DEM: Lower Rio Grande, TX</title>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49404</parent-catalog-item-id>
      <parent-title>DEMs - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <creation-date>2023</creation-date>
      <publication-date>2024</publication-date>
      <abstract>Original Data Products: This TX_LowerRioGrande_D22 project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at an aggregate nominal pulse spacing (ANPS) of 0.18 meters(30ppsm) and 0.35 meters (8ppsm). Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification 2022 Rev A. The data was developed based on a horizontal projection/datum of NAD83 (2011), UTM14N (EPSG 6343), meters and vertical datum of NAVD88 (GEOID18), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to individual 500 m x 500 m tiles for the 30 ppsm AOI and 1000 m x 1000 m tiles for the 8ppsm AOI, and as tiled intensity imagery and tiled bare earth DEMs; all tiled to the same schemas.  Hydro-flattening breaklines, building footprints, building models, vegetation canopy rasters, and ortho imagery (10 cm and 20cm GSDs) were also included in deliverables.

The TX_LowerRioGrande_D22 task is for a high-resolution data set of QL1+ (30ppsm) and QL1 (8ppsm) lidar of approximately 3,122 square miles in four counties in the state of Texas. These counties include parts of Starr, Hidalgo, Willacy, and Cameron. 

The dataset is broken up into four blocks. They are:
TX_LowerRioGrande_1 (Work Unit 300257) - data is in Starr and Hidalgo counties
TX_LowerRioGrande_2 (Work Unit 300630) - data is in Cameron and Hidalgo counties
TX_LowerRioGrande_3 (Work Unit 300446) - data is in Cameron, Hidalgo, Starr and Willacy counties
TX_LowerRioGrande_4 (Work Unit 300469) - data is in Cameron, Hidalgo, Starr and Willacy counties

This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the GeoTIFF files hosted by USGS on Amazon Web Services.

</abstract>
      <purpose>This high resolution lidar data will support the United States Geological Survey (USGS) initiatives.</purpose>
      <supplemental-information>USGS Contract No. 140G0221D0010 CONTRACTOR: Fugro USA Land, Inc. SUBCONTRACTOR: Terrasurv, Inc. Ground control and checkpoints collected by Terrasurv, Inc. All processing was completed by the prime contractor. DEM Raster File Type = GeoTIFF Bit Depth/Pixel Type = 32-bit float Raster Cell Size = 0.25 meter Interpolation or Resampling Technique = Triangulated Irregular Network (TIN) Network Required Vertical Accuracy = 19.6 cm NVA </supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="74ed1690-968e-444c-8a31-7b8344a2aad3">EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="395372ad-2883-4b6a-a481-6383a310ca47">EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION &gt; DIGITAL ELEVATION/TERRAIN MODEL (DEM)</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="1fbf5df2-ab7c-43fc-9bb2-8eb3f8891f7b">EARTH SCIENCE &gt; OCEANS &gt; COASTAL PROCESSES &gt; COASTAL ELEVATION</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="753f915c-70d4-49e1-9bd5-83e75f461e30">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="0f01d3b9-3691-471e-b21b-3f42c512dcd2">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; TEXAS</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="90761f8d-6abe-499c-b711-acec394daa59">VERTICAL LOCATION &gt; LAND SURFACE</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Instrument</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Instrument Keywords</thesaurus>
         <keyword identifier="7166c458-f935-4bd9-a322-d92830cf0c33">LIDAR &gt; Light Detection and Ranging</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Platform</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Platform Keywords</thesaurus>
         <keyword identifier="8b7834c1-2c66-414e-a655-2298e7dcc479">Airplane &gt; Airplane</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office for Coastal Management</organization>
      <city>Charleston</city>
      <state-province>SC</state-province>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <data-set-type>Elevation</data-set-type>
      <maintenance-frequency>None Planned</maintenance-frequency>
      <data-presentation-form>Model (digital)</data-presentation-form>
      <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.</distribution-liability>
      <data-set-credit>USGS</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1393653" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2025</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1393652" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2025</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1393656" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2024</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>U.S. Geological Survey</contact-name>
         <contact-address>12201 Sunrise Valley Drive </contact-address>
         <contact-address-city>Reston</contact-address-city>
         <contact-address-state>VA</contact-address-state>
         <contact-address-zip>20191</contact-address-zip>
         <contact-address-country>USA</contact-address-country>
         <contact-url>https://usgs.gov</contact-url>
         <contact-url-name>USGS Home</contact-url-name>
         <contact-url-description>Home page for USGS</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1393654" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2025</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1393655" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2025</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
   </support-roles>
   <extents>
      <currentness-reference>Ground Condition</currentness-reference>
      <extent cc-id="1393684">
         <geographic-areas>
            <geographic-area cc-id="1393686">
               <west-bound>-99.18</west-bound>
               <east-bound>-97.12</east-bound>
               <north-bound>26.8</north-bound>
               <south-bound>25.83</south-bound>
               <description>Data extent for the Lower Rio Grande project in Texas.</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1393685">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2023-01-22</start-date-time>
               <end-date-time>2023-03-03</end-date-time>
               <description>Dates of collection for the Lower Rio Grande project in Texas.</description>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <grid>Yes</grid>
            <vector>No</vector>
            <text-table>No</text-table>
            <tin>No</tin>
            <stereo-model>No</stereo-model>
            <video>No</video>
         </representations-used>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Vertical</crs-type>
               <epsg-code>EPSG:5703</epsg-code>
               <epsg-name>NAVD88 height</epsg-name>
               <datum-name>North American Vertical Datum 1988</datum-name>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Gravity-related height</name>
                     <abbreviation>H</abbreviation>
                     <units>metre</units>
                     <orientation>up</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Projected</crs-type>
               <epsg-code>EPSG:6343</epsg-code>
               <epsg-name>NAD83(2011) / UTM zone 14N</epsg-name>
               <base-crs-name>NAD83(2011)</base-crs-name>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Easting</name>
                     <abbreviation>E</abbreviation>
                     <units>metre</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Northing</name>
                     <abbreviation>N</abbreviation>
                     <units>metre</units>
                     <orientation>north</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <data-license-type>Custom</data-license-type>
      <data-license>Universal (CC0 1.0) Public Domain Dedication</data-license>
      <data-license-url>https://creativecommons.org/publicdomain/zero/1.0/</data-license-url>
      <data-license-statement>To the extent possible under law, the U.S. Government has waived all copyright and related or neighboring rights to this dataset.</data-license-statement>
      <security-class>Unclassified</security-class>
      <data-access-procedure>Data is available online for bulk and custom downloads.</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <data-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.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="1393657">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10354/details/10354</download-url>
         <distributor cc-id="1393652">
            <from-date>2025</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, map projection, file format, etc. A new metadata will be produced to reflect your request using this record as a base.</description>
         <distribution-format>Not Applicable</distribution-format>
         <compression>Zip</compression>
      </distribution>
      <distribution cc-id="1393658">
         <download-url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/TX_LowerRioGrande_D22/</download-url>
         <distributor cc-id="1393656">
            <from-date>2024</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>U.S. Geological Survey</contact-name>
         </distributor>
         <file-name>Bulk Download</file-name>
         <description>Bulk download of data files in GeoTIFF format, UTM Zone 14N NAD83(2011) meters coordinates and elevations in NAVD88(GEOID18) meters.</description>
         <distribution-format>GeoTIFF</distribution-format>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="1393659">
         <url>https://coast.noaa.gov/dataviewer/</url>
         <name>NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>HTML</file-resource-format>
         <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.</description>
      </url>
      <url cc-id="1393662">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/TX_LowerRioGrande_D22/TX_LowerRioGrande_1_D22/reports/lidar_mapping_report/LidarMappingReport_TX_LowerRioGrande_D22_WU_300257.pdf</url>
         <name>Lidar Report - TX_LowerRioGrande_1</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the lidar report for the TX_LowerRioGrande_1.</description>
      </url>
      <url cc-id="1393663">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/TX_LowerRioGrande_D22/TX_LowerRioGrande_2_D22/reports/lidar_mapping_report/LidarMappingReport_TX_LowerRioGrande_D22_WU_300360.pdf</url>
         <name>Lidar Report - TX_LowerRioGrande_2</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the lidar report for the TX_LowerRioGrande_2.</description>
      </url>
      <url cc-id="1393664">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/TX_LowerRioGrande_D22/TX_LowerRioGrande_3_D22/reports/lidar_mapping_report/LidarMappingReport_TX_LowerRioGrande_D22_WU_300446.pdf</url>
         <name>Lidar Report - TX_LowerRioGrande_3</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the lidar report for the TX_LowerRioGrande_3.</description>
      </url>
      <url cc-id="1393665">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/TX_LowerRioGrande_D22/TX_LowerRioGrande_4_D22/reports/lidar_mapping_report/LidarMappingReport_TX_LowerRioGrande_D22_WU_300469.pdf</url>
         <name>Lidar Report - TX_LowerRioGrande_4</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the lidar report for the TX_LowerRioGrande_4.</description>
      </url>
      <url cc-id="1393660">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/TX_LowerRioGrande_D22/USGS_TX_LowerRioGrande_D22_Project_Report.pdf</url>
         <name>USGS Project Report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the USGS Project Report that provides information about the project, vertical accuracy results, and the point classes and sensors used.</description>
      </url>
      <url cc-id="1393661">
         <url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/metadata/TX_LowerRioGrande_D22/</url>
         <name>USGS Additional Info</name>
         <url-type>Online Resource</url-type>
         <description>Link to the reports, breaklines, metadata, and spatial metadata.</description>
      </url>
      <url cc-id="1393666">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/TX_LowerRioGrande_1_D22/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - TX_LowerRioGrande_1</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <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.</description>
      </url>
      <url cc-id="1393667">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/TX_LowerRioGrande_2_D22/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - TX_LowerRioGrande_2</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <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.</description>
      </url>
      <url cc-id="1393668">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/TX_LowerRioGrande_3_D22/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - TX_LowerRioGrande_3</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <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.</description>
      </url>
      <url cc-id="1393669">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/TX_LowerRioGrande_4_D22/ept.json</url>
         <name>USGS Entwine Point Tile (EPT) - TX_LowerRioGrande_4</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <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.</description>
      </url>
      <url cc-id="1393670">
         <url>https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/TX_LowerRioGrande_1_D22/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/TX_LowerRioGrande_2_D22/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/TX_LowerRioGrande_3_D22/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/TX_LowerRioGrande_4_D22/ept.json%22]</url>
         <name>3D View (Potree USGS)</name>
         <url-type>Online Resource</url-type>
         <description>Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer.</description>
      </url>
   </urls>
   <technical-environment>
      <description>POSPac 8.7 PP-RTX; 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.6; Global Mapper 17.1.2; ERDAS Imagine 2016; PhotoShop CS8; Fugro proprietary software; Windows 10 64-bit Operating System
\\fgaibrowns\lidar\00218030_USGS_TX_LowerRioGrande_D22\Lidar\04_Delivery\Block1\300034\300257\*\*\*.laz, *tif, *shp, *gdb
275 GB</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>This data was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 20.2 (cm) RMSEx/RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 49.4 cm at 95% confidence level.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>This data was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.

USGS Determined DEM Vertical Accuracy:

Non-Vegetated Vertical Accuracy (NVA) = 3.27 cm RMSE

Vegetated Vertical Accuracy (VVA) = 21.80 cm at the 95th Percentile</vertical-positional-accuracy>
      <completeness-report>A complete iteration of processing (GNSS/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 Breakline cover the entire project delivery boundary. 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. The pixels that fall outside the project delivery boundary are set to Void with a unique NODATA value. The value is identified in the file headers. There are no void pixels	inside the project boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The bare earth surface is of good quality and passes Vertical Accuracy requirements.
	
The Intensity Image files cover the entire project delivery boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The Intensity Image product is of good quality.
	
The Vegetation Raster files cover the entire project delivery boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The Vegetation Raster product is of good quality.
	
The Building Vector files cover the entire project delivery boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The Building Vector product is of good quality.</completeness-report>
      <conceptual-consistency>Compliance with the accuracy standard was ensured by the collection of ground control and utilization of a web based GNSS correction service of a global network of tracking stations to compute corrections of satellite ephemeris, clock information and atmospheric models. Using this method, cm-level trajectory accuracy without the use of local base-stations. 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</conceptual-consistency>
   </data-quality>
   <data-management>
      <resources-identified>Yes</resources-identified>
      <resources-budget-percentage>Unknown</resources-budget-percentage>
      <data-access-directive-compliant>Yes</data-access-directive-compliant>
      <archive-location>NCEI-NC</archive-location>
      <data-protection-plan>Data is backed up to cloud storage.</data-protection-plan>
   </data-management>
   <lineage>
      <lineage-statement>The NOAA Office for Coastal Management (OCM) ingested references to the USGS GeoTIFF files that are hosted on Amazon Web Services (AWS), into the Digital Coast Data Access Viewer (DAV). The DAV accesses the raster data as it resides on AWS.</lineage-statement>
      <lineage-sources>
         <lineage-source cc-id="1393677">
            <citation-title>USGS GeoTIFF Files - TX_LowerRioGrande_1</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/TX_LowerRioGrande_D22/TX_LowerRioGrande_1_D22/TIFF/</citation-url>
            <citation-url-name>USGS GeoTIFF files for TX_LowerRioGrande_1</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1393678">
            <citation-title>USGS GeoTIFF Files - TX_LowerRioGrande_2</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/TX_LowerRioGrande_D22/TX_LowerRioGrande_2_D22/TIFF/</citation-url>
            <citation-url-name>USGS GeoTIFF files for TX_LowerRioGrande_2</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1393679">
            <citation-title>USGS GeoTIFF Files - TX_LowerRioGrande_3</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/TX_LowerRioGrande_D22/TX_LowerRioGrande_3_D22/TIFF/</citation-url>
            <citation-url-name>USGS GeoTIFF files for TX_LowerRioGrande_3</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1393680">
            <citation-title>USGS GeoTIFF Files - TX_LowerRioGrande_4</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/TX_LowerRioGrande_D22/TX_LowerRioGrande_4_D22/TIFF/</citation-url>
            <citation-url-name>USGS GeoTIFF files for TX_LowerRioGrande_4</citation-url-name>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1393681">
            <sequence-number>1</sequence-number>
            <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 and formatted to LAS v1.4. 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 (0 - 1 meter; automated classification); Class 4 - Medium Vegetation (1-3 meters; automated classification); Class 5 - High Vegetation (&gt;3 meters; automated classification) Class 6 - Buildings (automated classification) Class 7 - Low Noise; Class 9 - Water; Class 17 - Bridge Decks; Class 18 - High Noise (high, manually identified, if necessary); Class 20 - Ignored ground (breakline proximity). The classified point cloud data was delivered in tiles without overlap using the project tiling scheme.</description>
            <process-date-time>2023-04-06T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1393682">
            <sequence-number>3</sequence-number>
            <description>The bare earth DEM was generated using the lidar bare earth points and 3D hydro breaklines to a resolution of 0.25 meter. The bare earth points that fell within 1*NPS along the hydro breaklines (points in class 20) were excluded from the DEM generation process. This is analogous to the removal of mass points for the same reason in a traditional photogrammetrically compiled DTM. This process was done in batch using proprietary software. The technicians then used Fugro proprietary software for the production of the lidar-derived hydro flattened bare earth DEM surface in initial grid format at 2 foot GSD. Water bodies (inland ponds and lakes), inland streams and rivers, and island holes were hydro flattened within the DEM. Hydro flattening was applied to all water impoundments, natural or man-made, that are larger than approximately 2 acres in area and to all streams that are nominally wider than 100 feet. This process was done in batch. Once the initial, hydro flattened bare earth DEM was generated, the technicians checked the tiles to ensure that the grid spacing met specifications. The technicians also checked the surface to ensure proper hydro flattening. The entire data set was checked for complete project coverage. Once the data was checked, the tiles were then converted to industry-standard, GIS-compatible, 32-bit floating point raster format. Georeferenced information is included in the raster files. Void areas (i.e., areas outside the project boundary but within the tiling scheme) are coded using a unique NODATA value.</description>
            <process-date-time>2023-07-17T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1393683">
            <sequence-number>4</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) created references to the USGS GeoTIFF files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the raster data as it resides on Amazon Web Services (AWS).

These are the GeoTIFF files that are being accessed:
https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/TX_LowerRioGrande_D22/TX_LowerRioGrande_1_D22/TIFF/
https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/TX_LowerRioGrande_D22/TX_LowerRioGrande_2_D22/TIFF/
https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/TX_LowerRioGrande_D22/TX_LowerRioGrande_3_D22/TIFF/
https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/TX_LowerRioGrande_D22/TX_LowerRioGrande_4_D22/TIFF/</description>
            <process-date-time>2025-07-18T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Organization</contact-type>
               <contact-name>NOAA Office for Coastal Management</contact-name>
               <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
               <contact-email>coastal.info@noaa.gov</contact-email>
               <contact-address>2234 South Hobson Ave</contact-address>
               <contact-address-city>Charleston</contact-address-city>
               <contact-address-state>SC</contact-address-state>
               <contact-address-zip>29405-2413</contact-address-zip>
               <contact-phone-number>(843) 740-1202</contact-phone-number>
               <contact-url>https://coast.noaa.gov</contact-url>
               <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
               <contact-url-function>Online Resource</contact-url-function>
            </process-contact>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <related-items>
      <related-item>
         <catalog-item-id>76197</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2023 USGS Lidar: Lower Rio Grande, TX</title>
         <relationship-type>Cross Reference</relationship-type>
      </related-item>
   </related-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:76200</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2025-06-23T20:50:15</metadata-record-created>
      <metadata-record-last-modified-by pers-id="20143">Rebecca Mataosky</metadata-record-last-modified-by>
      <metadata-record-last-modified>2025-07-18T21:53:48</metadata-record-last-modified>
      <record-published>2025-07-18</record-published>
      <owner-organization>OCM Partners</owner-organization>
      <owner-organization-acronym>OCMP</owner-organization-acronym>
      <owner-organization-address/>
      <owner-organization-address-city/>
      <owner-organization-address-state/>
      <owner-organization-address-zip/>
      <owner-organization-address-country/>
      <owner-organization-phone/>
      <owner-organization-url/>
      <owner-organization-business-hours/>
      <owner-organization-group-id>1002</owner-organization-group-id>
      <publication-status>Public</publication-status>
      <limited-metadata-available>No</limited-metadata-available>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2025-06-23</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2026-06-23</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
