<?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>50036</catalog-item-id>
      <title>2006 Texas Water Development Board (TWDB) Lidar: Chambers County</title>
      <short-name>tx2006_chambers_m90_metadata</short-name>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49401</parent-catalog-item-id>
      <parent-title>Lidar - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <publication-date>2007-08</publication-date>
      <abstract>Using a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, flight lines of standard density (1.4 meter ground
sample distance) data were collected over areas in Chambers County, TX (approximately 633 square miles). Multiple returns
were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in missions
between April 22, 2006, and June 12, 2006. The data was collected by Sanborn Mapping Company, Inc. for the Texas Water
Development Board (TWDB) and the Federal Emergency Management Agency (FEMA).

Original contact information: 
   Contact Name: Ryan Mitchell
   Contact Org: Texas Natural Resources Information System (TNRIS)
   Phone: 512-463-8337
   Email: lidar@tnris.state.tx.us</abstract>
      <purpose>This LIDAR operation was designed to provide a high density set of masspoints within the defined areas. The data
sets are suitable for the development of contours for use in hydraulic/hydrologic model development, and for assessing
environmental impacts. Typical uses for the data set include: FEMA Flood Plain Map Modernization, DFIRM map updates,
watersheds and other hydro studies per FEMA specifications, county mapping projects, and flood mitigation assessment.</purpose>
      <notes>10680</notes>
      <supplemental-information>The Chambers County data set was received from the Texas Water Development Board (TWDB). It was reviewed by the
NOAA Office for Coastal Management at the macro level, which included checking for format and point characteristics for approximately
5% of the tiles. In addition, the entire data set was reviewed to establish that bare earth processing and proper classification
of the points had been performed. It did not include accuracy or data processing (e.g. bare earth quality, flightline
mismatch, feature removal) assessments. Based on the limited review, the data set on average appeared to be of fair quality.
Again, no accuracy assessment was performed. The results of this review are detailed below. The results may also be viewed as
a formatted document. This document is entitled "Lidar Fact Sheet: Chambers County, Texas" and may be viewed at:

https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/90/supplemental/ChambersCounty_factsheet.pdf

Some of the issues noted in the fact sheet are the following:
Tile Review:
Formatting issues: a) no flightline source information, b) some noisy two-return data, and c) the majority of ground
points were first of two (i.e., first of many) returns. These issues all appeared to be systematic, which, although does not
necessarily affect accuracy, it raises flags about the overall data quality. Also the water in some areas (tiles) is classified
as 'unclassified," which is acceptable, but doesn't conform to the American Society for Photogrammetry and Remote Sensing (ASPRS)
standard for class 9 for water values. High elevation values also remain in the data set, although correctly classified as
"unclassified."
Bare Earth Point Density Review:
There appears to be a strong "tile-specific" level of classification as evidenced by the bare-earth densities (see color variations
in Figure 1 of the pdf). Water points have been removed to some degree in many tiles; however, in adjacent tiles no
apparent effort was made to remove water points. In either case, bare-earth points in the water still largely remain.
The larger issue is the lack of proper return number information, which raises flags about the accuracy of the data.
Additional data issues include the coastal portions of the county where water was randomly classified and a tile-to-tile
variation in classification "aggressiveness." There are also some missing data on the southwestern edge of the county and a
low density strip (yellow) running through the middle-eastern portion of the county.

A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/90/supplemental/2006_TWDB_Lidar_Chambers_County.kmz</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Drainage Area</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Hydraulic</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Hydrographic</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Hydrology</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>TNRIS (Texas Natural Resources Information System)</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>
      <maintenance-frequency>None Planned</maintenance-frequency>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Data collected by Sanborn Mapping Company, Inc. for the Texas Water Development Board (TWDB) and the Federal
Emergency Management Agency (FEMA). Acknowledgement of TNRIS (Texas Natural Resources Information System) would be appreciated
in products derived and used from this data. Sanborn Mapping Company asks to be credited in derived products.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="687941" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2007-08</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="687943" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2007-08</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="687944" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2007-08</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="687942" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2007-08</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>Publication Date</currentness-reference>
      <extent cc-id="1143516">
         <geographic-areas>
            <geographic-area cc-id="1143518">
               <west-bound>-94.986985</west-bound>
               <east-bound>-94.350885</east-bound>
               <north-bound>29.906285</north-bound>
               <south-bound>29.499985</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1143517">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2006-04-22</start-date-time>
               <end-date-time>2006-06-12</end-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
      </spatial-representation>
   </spatial-information>
   <access-information>
      <security-class>Unclassified</security-class>
      <data-access-procedure>This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer;</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="742718">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=90</download-url>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, product type, map projection, file format, datum, etc.</description>
      </distribution>
      <distribution cc-id="742719">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/90/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="742722">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="742721">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="687966">
         <activity-date-time>2016-05-23</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="687965">
         <activity-date-time>2017-11-14</activity-date-time>
         <description>Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.</description>
      </activity-log>
      <activity-log cc-id="718642">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="742720">
         <activity-date-time>2018-03-13</activity-date-time>
         <description>Partial upload to move data access links to Distribution Info.</description>
      </activity-log>
   </activity-logs>
   <technical-environment>
      <description>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>FEMA LiDAR Specifications</horizontal-positional-accuracy>
      <vertical-positional-accuracy>FEMA LiDAR Specifications; +/- 18 cm in open terrain</vertical-positional-accuracy>
      <completeness-report>None</completeness-report>
      <conceptual-consistency>None</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-process-steps>
         <lineage-process-step cc-id="1143509">
            <sequence-number>1</sequence-number>
            <description>Data Collection:
Using a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, flight lines of standard density (1.4 meter ground
sample distance) data were collected over areas in Chambers County, TX (approximately 633 square miles). Multiple returns
were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in missions
between April 22, 2006, and June 12, 2006. During the LIDAR campaign, the Sanborn field crew conducted a GPS field survey
to establish final coordinates of the ground base stations for final processing of the base-remote GPS solutions.</description>
            <process-date-time>2007-08-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143510">
            <sequence-number>2</sequence-number>
            <description>Airborne GPS Processing:
Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best
estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface
for each flight line. The overlap between flight lines was removed to provide a homogeneous coverage, and the coverage was
classified to extract a bare earth digital elevation model (DEM).
Airborne GPS is differentially processed using the GrafNAV V7.50 software by Waypoint Consulting of Calgary, Alberta, Canada.
The PDOP and distance separation is as follows:
IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada.
The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS &amp; Mapping Division of Atlanta,
Georgia.
The classification and quality control (QC) of LiDAR data is carried out using TerraScan software by Terrasolid Limited of
Helsinki, Finland.</description>
            <process-date-time>2007-08-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143511">
            <sequence-number>3</sequence-number>
            <description>IMU data Processing:
IMU data provides information concerning roll, pitch, and yaw of collection platform during collection event. IMU information
allows the pulse vector to be properly placed in 3D space allowing the distance from the aircraft reference point to be properly
positioned on the elevation model surface. IMU data is processed using the PosPac V4.2 software by Applanix Corporation of
Richmond Hill, Ontario, Canada.</description>
            <process-date-time>2007-08-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143512">
            <sequence-number>4</sequence-number>
            <description>Reflective Surface Generation:
The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS &amp; Mapping Division of Atlanta,
Georgia.</description>
            <process-date-time>2007-08-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143513">
            <sequence-number>5</sequence-number>
            <description>LIDAR Point Classification
The classification and quality control (QC) of LiDAR data is carried out using TerraScan software by Terrasolid Limited of
Helsinki, Finland.</description>
            <process-date-time>2007-08-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143514">
            <sequence-number>6</sequence-number>
            <description>Output LAS Files
The product output of LiDAR data is carried out using TerraScan software by Terrasolid Limited of Helsinki, Finland. LAS Binary,
ascii xyz, and intensity images were created.</description>
            <process-date-time>2007-08-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143515">
            <sequence-number>7</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained Lidar
elevation and intensity measurements. The data was in UTM projection, and NAVD88 Geoid 03 vertical datum. OCM performed
the following processing to the data to make it available within the Digital Coast:
1. The data were converted from UTM coordinates to geographic coordinates.
2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03.
3. The LAS data were sorted by latitude and the headers were updated.

NOAA OCM also performed a macro level review of this data set. This review involved checking for format and point characteristics
in about 5% of the tiles. In addition, the entire data set was reviewed to establish that bare-earth processing and proper
classification of the points had been performed. This review did not include accuracy or data-processing (e.g., bare-earth
quality, flightline mismatch, feature removal) assessments. Please refer to the Supplemental_Information field for more information
about this review.</description>
            <process-date-time>2008-08-13T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:50036</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:23:54</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2022-08-09T17:11:37</metadata-record-last-modified>
      <record-published>2022-03-16</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>2022-03-16</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2023-03-16</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
