<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE metadata SYSTEM "http://thor-f5.er.usgs.gov/ngtoc/metadata/fgdc-std-001-1998.dtd">
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Dewberry</origin>
        <pubdate>20190808</pubdate>
        <title>Texas West Central Lidar; Classified Point Cloud</title>
        <geoform>Lidar point cloud</geoform>
      </citeinfo>
    </citation>
    <descript>
      <abstract>Product: These lidar data are processed Classified LAS 1.4 files, formatted to 50,901 individual 1500 m x 1500 m tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.
      	Geographic Extent: Texas West Central, covering approximately 42,557 square miles, spanning across three UTM zones (13, 14, and 15).  Blocks 1-4 fall within UTM zone 13, Blocks 5-14 fall within UTM zone 14, and Block 15 falls within UTM zone 15. Dataset Description: Texas West Central 2018 Lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2. The data was developed based on a horizontal projection/datum of NAD83 (2011), Universal Transverse Mercator, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 50,901 individual 1500 m x 1500 m tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 1500 m x 1500 m schema. Ground Conditions: Lidar was collected between February 1, 2018 and May 27, 2018, with reflights collected on November 5, 2018, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Dewberry established a total of 372 ground control points that were used to calibrate the lidar to known ground locations established throughout the Texas West Central project area. An additional 1183 independent accuracy checkpoints, 705 in Bare Earth and Urban landcovers (705 NVA points), 478 in Tall Grass and Brushland/Low Trees categories (478 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.</abstract>
      <lidar>
        <ldrinfo>
          <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2</ldrspec>
          <ldrsens>Leica ALS-70 HP (Precision Aerial Reconnaissance LLC) Block 1</ldrsens>
          <ldrmaxnr>7</ldrmaxnr>
          <ldrnps>0.7</ldrnps>
          <ldrdens>2</ldrdens>
          <ldranps>0.7</ldranps>
          <ldradens>2</ldradens>
          <ldrfltht>1800</ldrfltht>
          <ldrfltsp>150</ldrfltsp>
          <ldrscana>40</ldrscana>
          <ldrscanr>53.4</ldrscanr>
          <ldrpulsr>151.7</ldrpulsr>
          <ldrpulsd>9</ldrpulsd>
          <ldrpulsw>0.2</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.22</ldrbmdiv>
          <ldrswatw>1310.29</ldrswatw>
          <ldrswato>30</ldrswato>
          <ldrgeoid>National Geodetic Survey (NGS) GEOID12B</ldrgeoid>
        </ldrinfo>
        <ldrinfo>
          <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2</ldrspec>
          <ldrsens>Riegl LMS-Q1560 (Airborne Imaging Inc.) Blocks 2 and 3</ldrsens>
          <ldrmaxnr>15</ldrmaxnr>
          <ldrnps>0.7</ldrnps>
          <ldrdens>2</ldrdens>
          <ldranps>0.7</ldranps>
          <ldradens>2</ldradens>
          <ldrfltht>2000</ldrfltht>
          <ldrfltsp>150</ldrfltsp>
          <ldrscana>60</ldrscana>
          <ldrscanr>185</ldrscanr>
          <ldrpulsr>800</ldrpulsr>
          <ldrpulsd>3</ldrpulsd>
          <ldrpulsw>0.9</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.25</ldrbmdiv>
          <ldrswatw>2241</ldrswatw>
          <ldrswato>30</ldrswato>
          <ldrgeoid>National Geodetic Survey (NGS) GEOID12B</ldrgeoid>
        </ldrinfo>
        <ldrinfo>
          <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2</ldrspec>
          <ldrsens>Riegl VQ-Q1560i (Axis Geospatial, LLC) Blocks 4 and 5</ldrsens>
          <ldrmaxnr>15</ldrmaxnr>
          <ldrnps>0.7</ldrnps>
          <ldrdens>2</ldrdens>
          <ldranps>0.7</ldranps>
          <ldradens>2</ldradens>
          <ldrfltht>5700</ldrfltht>
          <ldrfltsp>147</ldrfltsp>
          <ldrscana>58</ldrscana>
          <ldrscanr>201</ldrscanr>
          <ldrpulsr>1000</ldrpulsr>
          <ldrpulsd>3</ldrpulsd>
          <ldrpulsw>0.43</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.25</ldrbmdiv>
          <ldrswatw>1947</ldrswatw>
          <ldrswato>15</ldrswato>
          <ldrgeoid>National Geodetic Survey (NGS) GEOID12B</ldrgeoid>
        </ldrinfo>
        <ldrinfo>
          <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2</ldrspec>
          <ldrsens>Riegl LMS-Q1560 (Eagle Mapping) Blocks 6, 7, 8, and 14</ldrsens>
          <ldrmaxnr>15</ldrmaxnr>
          <ldrnps>0.7</ldrnps>
          <ldrdens>2</ldrdens>
          <ldranps>0.7</ldranps>
          <ldradens>2</ldradens>
          <ldrfltht>2000</ldrfltht>
          <ldrfltsp>150</ldrfltsp>
          <ldrscana>58</ldrscana>
          <ldrscanr>183</ldrscanr>
          <ldrpulsr>800</ldrpulsr>
          <ldrpulsd>3</ldrpulsd>
          <ldrpulsw>0.9</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.25</ldrbmdiv>
          <ldrswatw>2217</ldrswatw>
          <ldrswato>25</ldrswato>
          <ldrgeoid>National Geodetic Survey (NGS) GEOID12B</ldrgeoid>
        </ldrinfo>
        <ldrinfo>
          <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2</ldrspec>
          <ldrsens>Riegl VQ780i (Leading Edge Geomatics) Blocks 9-13</ldrsens>
          <ldrmaxnr>15</ldrmaxnr>
          <ldrnps>1</ldrnps>
          <ldrdens>1</ldrdens>
          <ldranps>0.70</ldranps>
          <ldradens>2</ldradens>
          <ldrfltht>1800</ldrfltht>
          <ldrfltsp>100</ldrfltsp>
          <ldrscana>60</ldrscana>
          <ldrscanr>68</ldrscanr>
          <ldrpulsr>280</ldrpulsr>
          <ldrpulsd>5</ldrpulsd>
          <ldrpulsw>1.50</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.25</ldrbmdiv>
          <ldrswatw>1996</ldrswatw>
          <ldrswato>55</ldrswato>
          <ldrgeoid>National Geodetic Survey (NGS) GEOID12B</ldrgeoid>
        </ldrinfo>
          <ldrinfo>
          <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2</ldrspec>
          <ldrsens>Riegl Q1560 (Leading Edge Geomatics) Block 13</ldrsens>
          <ldrmaxnr>15</ldrmaxnr>
          <ldrnps>0.7</ldrnps>
          <ldrdens>2</ldrdens>
          <ldranps>0.7</ldranps>
          <ldradens>2</ldradens>
          <ldrfltht>1600</ldrfltht>
          <ldrfltsp>100</ldrfltsp>
          <ldrscana>57</ldrscana>
          <ldrscanr>80</ldrscanr>
          <ldrpulsr>700</ldrpulsr>
          <ldrpulsd>5</ldrpulsd>
          <ldrpulsw>.43</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.25</ldrbmdiv>
          <ldrswatw>1737</ldrswatw>
          <ldrswato>55</ldrswato>
          <ldrgeoid>National Geodetic Survey (NGS) Geoid12B</ldrgeoid>
        </ldrinfo>
          <ldrinfo>
          <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2</ldrspec>
          <ldrsens>Leica ALS-70 HP (Aerial Services Inc.) Block 15</ldrsens>
          <ldrmaxnr>4</ldrmaxnr>
          <ldrnps>0.7</ldrnps>
          <ldrdens>2</ldrdens>
          <ldranps>0.7</ldranps>
          <ldradens>2</ldradens>
          <ldrfltht>1400</ldrfltht>
          <ldrfltsp>150</ldrfltsp>
          <ldrscana>50</ldrscana>
          <ldrscanr>47</ldrscanr>
          <ldrpulsr>379.8</ldrpulsr>
          <ldrpulsd>9</ldrpulsd>
          <ldrpulsw>2.7</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.22</ldrbmdiv>
          <ldrswatw>1300</ldrswatw>
          <ldrswato>30</ldrswato>
          <ldrgeoid>National Geodetic Survey (NGS) GEOID12B</ldrgeoid>
        </ldrinfo>
        <ldrinfo>
          <ldrspec>USGS-NGP Base Lidar Specification v1.2</ldrspec>
          <ldrsens>Optech Galaxy (Intermap) Block 15</ldrsens>
          <ldrmaxnr>4</ldrmaxnr>
          <ldrnps>0.57</ldrnps>
          <ldrdens>3.1</ldrdens>
          <ldranps>0.57</ldranps>
          <ldradens>3.1</ldradens>
          <ldrfltht>1600</ldrfltht>
          <ldrfltsp>145</ldrfltsp>
          <ldrscana>34</ldrscana>
          <ldrscanr>66</ldrscanr>
          <ldrpulsr>300</ldrpulsr>
          <ldrpulsd>4</ldrpulsd>
          <ldrpulsw>1.05</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.25</ldrbmdiv>
          <ldrswatw>978</ldrswatw>
          <ldrswato>30</ldrswato>
          <ldrgeoid>National Geodetic Survey (NGS) Geoid12B</ldrgeoid>
        </ldrinfo>
        <ldraccur>
          <ldrchacc>0.614</ldrchacc>
          <rawnva>0.090</rawnva>
          <rawnvan>705</rawnvan>
          <clsnva>0.091</clsnva>
          <clsnvan>705</clsnvan>
          <clsvva>0.117</clsvva>
          <clsvvan>478</clsvvan>
       </ldraccur>
        <lasinfo>
          <lasver>1.4</lasver>
          <lasprf>6</lasprf>
          <laswheld>Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.</laswheld>
          <lasolap>Swath "overage" points were identified in these files using the standard LAS overlap bit.</lasolap>
          <lasintr>16</lasintr>
          <lasclass>
            <clascode>1</clascode>
            <clasitem>Processed, but Unclassified</clasitem>
          </lasclass>
          <lasclass>
            <clascode>2</clascode>
            <clasitem>Bare Earth Ground</clasitem>
          </lasclass>
          <lasclass>
            <clascode>7</clascode>
            <clasitem>Low Noise</clasitem>
          </lasclass>
          <lasclass>
            <clascode>9</clascode>
            <clasitem>Water</clasitem>
          </lasclass>
          <lasclass>
            <clascode>10</clascode>
            <clasitem>Ignored Ground</clasitem>
          </lasclass>
          <lasclass>
            <clascode>17</clascode>
            <clasitem>Bridge Decks</clasitem>
          </lasclass>
          <lasclass>
            <clascode>18</clascode>
            <clasitem>High Noise</clasitem>
          </lasclass>
        </lasinfo>
      </lidar>
      <purpose>To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images, Breaklines and Raster DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 1 meter cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
      <supplinf>USGS Contract No. G16PC00020 CONTRACTOR: Dewberry SUBCONTRACTOR: Leading Edge Geomatics Lidar data were acquired by Leading Edge Geomatics. Axis Lidar data were acquired by Axis. Airborne Imaging Lidar data were acquired by Airborne Imaging. PAR Lidar data were acquired by PAR. Eagle Mapping Lidar data were acquired by Eagle Mapping. Intermap Lidar data were acquired by Intermap. ASI Lidar data were acquired by ASI. All follow-on processing was completed by the prime contractor.
      </supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20180201</begdate>
          <enddate>20181105</enddate>
        </rngdates>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-103.954221</westbc>
        <eastbc>-95.232557</eastbc>
        <northbc>34.470336</northbc>
        <southbc>30.926054</southbc>
      </bounding>
      <lboundng>
      	<leftbc>-518484.964035</leftbc>
      	<rightbc>291448.045126</rightbc>
      	<topbc>3832908.576866</topbc>
      	<bottombc>3456873.389663</bottombc>
      </lboundng>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Model</themekey>
        <themekey>LAS Point Cloud</themekey>
        <themekey>Remote Sensing</themekey>
        <themekey>Elevation Data</themekey>
        <themekey>Lidar</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Texas</placekey>
        <placekey>New Mexico</placekey>
        <placekey>Oklahoma</placekey>
        <placekey>Southeastern New Mexico</placekey>
        <placekey>West Texas</placekey>
        <placekey>Red River region</placekey>
      </place>
    </keywords>
    <accconst>No restrictions apply to these data.</accconst>
    <useconst>None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.</useconst>
  </idinfo>
  <dataqual>
    <logic>Data covers the entire area specified for this project.</logic>
    <complete>These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and data passes Non-Vegetated Vertical Accuracy specifications.</complete>
 <posacc>
      <vertacc>
        <vertaccr>The project specifications require that only Non-Vegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. The required accuracy (ACCz) is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm in the "bare earth" and "urban" land cover classes. The NVA was tested with 705 checkpoints located in bare earth and urban (non-vegetated) areas. These check points were not used in the calibration or post processing of the lidar point cloud data. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. See survey report for additional survey methodologies. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control points. AccuracyZ has been tested to meet 19.6 cm or better Non-Vegetated Vertical Accuracy at 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</vertaccr>
        <qvertpa>
        	<vertaccv>0.090</vertaccv>
        	<vertacce>Tested 0.090 meters NVA at a 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). The NVA of the raw lidar point cloud swath files was calculated against TINs derived from the final calibrated and controlled swath data using 705 independent checkpoints located in Bare Earth and Urban land cover classes.</vertacce>
        </qvertpa>
      </vertacc> 
    </posacc>
    <lineage>
      <srcinfo>
      	<srccite>
      		<citeinfo>
      			<origin>Dewberry Consultants LLC</origin>
      			<pubdate>20180531</pubdate>
      			<title>Ground Control for Texas West Central Lidar  project</title>
      			<geoform>vector digital data and tabular digital data</geoform>
      			<pubinfo>
      				<pubplace>Lanham, Maryland</pubplace>
      				<publish>Dewberry Consultants, LLC, Survey department</publish>
      			</pubinfo>
      			<othercit>None</othercit>
      			<onlink>N/A/</onlink>
      		</citeinfo>
      	</srccite>
      	<srcscale>1640</srcscale>
      	<typesrc>Online</typesrc>
      	<srctime>
      		<timeinfo>
      			<sngdate>
      				<caldate>20180327</caldate>
      			</sngdate>
      		</timeinfo>
      		<srccurr>ground condition</srccurr>
      	</srctime>
      	<srccitea>Texas_West_Central_Ground_Control_Points</srccitea>
      	<srccontr>This data source was used (along with airborne GPS/IMU data) to georeference the lidar point cloud data.</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Precision Aerial Reconnaissance LLC acquired the data for Block 1 using a Leica ALS-70 HP sensor.  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 commercial software to calculate initial boresight adjustment angles based on sample areas selected in 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 how well flight line overlaps match 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 less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.2, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</procdesc>
        <srcused>Texas_West_Central_Ground_Control_Points</srcused>
        <procdate>20181128</procdate>
        <proccont>
           <cntinfo>
             <cntorgp>
               <cntorg>Precision Aerial Reconnaissance LLC</cntorg>
               <cntper>Wesley Palmer</cntper>
             </cntorgp>
             <cntaddr>
               <addrtype>mailing and physical</addrtype>
               <address>3910 Industrial Circle</address>
               <city>Bossier City</city>
               <state>LA</state>
               <postal>71112</postal>
               <country>USA</country>
             </cntaddr>
             <cntvoice> (870)904-1144</cntvoice>
    		     <cntemail>wes@precisionaerialrecon.com</cntemail>
    	       <hours>Monday - Friday 8 a.m. to 4 p.m. (Central Time)</hours>
    		     <cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
    	    </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>Airborne Imaging Inc. acquired the data for Blocks 2 and 3 using a Riegl LMS-Q1560 sensor.  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 commercial software to calculate initial boresight adjustment angles based on sample areas selected in 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 how well flight line overlaps match 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 less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.2, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</procdesc>
        <srcused>Texas_West_Central_Ground_Control_Points</srcused>
        <procdate>20180312</procdate>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Airborne Imaging Inc.</cntorg>
              <cntper>Timothy R Willms</cntper>
            </cntorgp>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>2700-61 Avenue SE</address>
              <city>Calgary</city>
              <state>AB</state>
              <postal>T2C 4V2</postal>
              <country>Canada</country>
            </cntaddr>
            <cntvoice>(403) 215-2960</cntvoice>
            <cntemail>timw@airborneimaginginc.com</cntemail>
            <hours>Monday - Friday 8 a.m. to 4 p.m. (Central Time)</hours>
            <cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>Axis Geospatial, LLC acquired the data for Blocks 4 and 5 using a Riegl VQ-Q1560i sensor.  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 commercial software to calculate initial boresight adjustment angles based on sample areas selected in 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 how well flight line overlaps match 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 less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.2, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</procdesc>
        <srcused>Texas_West_Central_Ground_Control_Points</srcused>
        <procdate>20180312</procdate>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Axis Geospatial, LLC</cntorg>
              <cntper>Justin Lahman</cntper>
            </cntorgp>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>28640 Marys Court STE 200</address>
              <city>Easton</city>
              <state>MD</state>
              <postal>21601</postal>
              <country>USA</country>
            </cntaddr>
            <cntvoice>(410) 822-1441</cntvoice>
            <cntemail>jlahman@axisgeospatial.com</cntemail>
            <hours>Monday - Friday 8 a.m. to 4 p.m. (Central Time)</hours>
            <cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>Eagle Mapping acquired the data for Blocks 6, 7, 8, and 14 using a Riegl LMS-Q1560 sensor.  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 commercial software to calculate initial boresight adjustment angles based on sample areas selected in 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 how well flight line overlaps match 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 less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.2, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</procdesc>
        <srcused>Texas_West_Central_Ground_Control_Points</srcused>
        <procdate>20180312</procdate>
        <proccont>
           <cntinfo>
             <cntorgp>
               <cntorg>Eagle Mapping</cntorg>
               <cntper>Andrew Lewis</cntper>
             </cntorgp>
             <cntaddr>
               <addrtype>mailing and physical</addrtype>
               <address>2071 Kingsway Avenue</address>
               <city>Port Coquitlam</city>
               <state>BC</state>
               <postal>V3C 6N2</postal>
               <country>Canada</country>
             </cntaddr>
             <cntvoice>(877) 942-5551</cntvoice>
    		     <cntemail>alewis@eaglemapping.com</cntemail>
    	       <hours>Monday - Friday 8 a.m. to 4 p.m. (Central Time)</hours>
    		     <cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
    	    </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>Leading Edge Geomatics acquired the data for Blocks 9-13 using a Riegl VQ780i and a Riegl Q1560 sensor.  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 commercial software to calculate initial boresight adjustment angles based on sample areas selected in 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 how well flight line overlaps match 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 less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.2, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</procdesc>
        <srcused>Texas_West_Central_Ground_Control_Points</srcused>
        <procdate>20180304</procdate>
        <proccont>
           <cntinfo>
             <cntorgp>
               <cntorg>Leading Edge Geomatics</cntorg>
               <cntper>Bruce Hogan</cntper>
             </cntorgp>
             <cntaddr>
               <addrtype>mailing and physical</addrtype>
               <address>2398 Route 102, Unit A2</address>
               <city>Lincoln</city>
               <state>NB</state>
               <postal>E3B 7G1</postal>
               <country>Canada</country>
             </cntaddr>
             <cntvoice>(506)446-4403</cntvoice>
    		     <cntemail>b.hogan@legeo.ca</cntemail>
    	       <hours>Monday - Friday 8 a.m. to 4 p.m. (Central Time)</hours>
    		     <cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
    	    </cntinfo>
        </proccont>
        </procstep>
        <procstep>
        <procdesc>Aerial Services Inc. acquired the data for Block 15 using a Leica ALS-70 HP and an Optech Galaxy sensor.  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 commercial software to calculate initial boresight adjustment angles based on sample areas selected in 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 how well flight line overlaps match 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 less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.2, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</procdesc>
        <srcused>Texas_West_Central_Ground_Control_Points</srcused>
        <procdate>20180516</procdate>
        <proccont>
           <cntinfo>
             <cntorgp>
               <cntorg>Aerial Services Inc</cntorg>
               <cntper>Chuck Boyer</cntper>
             </cntorgp>
             <cntaddr>
               <addrtype>mailing and physical</addrtype>
               <address>6315 Chancellor Dr.</address>
               <city>Cedar Falls</city>
               <state>IA</state>
               <postal>50613</postal>
               <country>USA</country>
             </cntaddr>
             <cntvoice>(319) 277-0436</cntvoice>
    		     <cntemail>cboyer@aerialservicesinc.com</cntemail>
    	       <hours>Monday - Friday 8 a.m. to 4 p.m. (Central Time)</hours>
    		     <cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
    	    </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.7 m was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Dewberry proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.</procdesc>
        <procdate>20180515</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Point</direct>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>Universal Transverse Mercator</gridsysn>
          <utm>
            <utmzone>15</utmzone>
            <transmer>
              <sfctrmer>0.9996</sfctrmer>
              <longcm>-93.000000</longcm>
              <latprjo>0.0</latprjo>
              <feast>500000</feast>
              <fnorth>0.0</fnorth>
            </transmer>
          </utm>
        </gridsys>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.01</absres>
            <ordres>0.01</ordres>
          </coordrep>
          <plandu>meters</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>North American Datum of 1983 (2011)</horizdn>
        <ellips>Geodetic Reference System 80</ellips>
        <semiaxis>6378137</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altdatum>North American Vertical Datum of 1988</altdatum>
        <altres>0.01</altres>
        <altunits>meters</altunits>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <metainfo>
    <metd>20190808</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Dewberry</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>1000 N Ashley Drive, Suite 801</address>
          <city>Tampa</city>
          <state>FL</state>
          <postal>33602</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>(813)225-1325</cntvoice>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
  </metainfo>
</metadata>