<?xml version="1.0" encoding="UTF-8"?>
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>AeroMetric, Inc.</origin>
				<pubdate>
					<!--Use the date that the data was sent to USGS.
Format YYYYMMDD   For example, 20020425 is April 25, 2002

Domain: "Unknown" "Unpublished material" free date-->
          20110912
        </pubdate>
				<title>
					WILLACY COUNTY TEXAS LiDAR TASK ORDER
					</title>
				<geoform>
          remote-sensing image
          <!--Enter the mode in which the geospatial data are represented.

Domain: (the listed domain is partially from pp. 88-91 in Anglo-American Committee on Cataloguing of Cartographic Materials, 1982, Cartographic materials: A manual of interpretation for AACR2: Chicago, American Library Association):

"atlas" "audio" "diagram" "document" "globe" "map" "model" "multimedia
presentation" "profile" "raster digital data" "remote-sensing image" "section" "spreadsheet" "tabular digital data" "vector digital data" "video" "view" free text-->
				</geoform>
        <pubinfo>
        	<pubplace>
        		<!--Enter the name of the city (and state or province, and country, if needed to identify the city) where the data set was published or released.

Domain: free text-->
            Sheboygan, WI
         </pubplace>
           <publish>
            <!--Enter the name of the individual or organization that published the data set.

Domain: free text-->AeroMetric
          </publish>
        </pubinfo>
			</citeinfo>
		</citation>
		<descript>
			<abstract>
				<!--Enter a brief narrative summary of the data set.

Domain: free text-->
This task order is for planning, acquisition, processing, and derivative products of LiDAR data to be collected for a portion of Willacy County, Texas.  LiDAR data, and derivative products produced in compliance with this task order are part of the data to be obtained under the American Recovery and Reinvestment Act (ARRA) of 2009. Contract number G10PC00025. Specifications listed below are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 13.
      </abstract>
			<purpose>
				<!--Enter a summary of the intentions with which the data set was developed.

Domain: free text-->
        USGS has a requirement for LiDAR data over a portion of Willacy County in Texas, covering approximately 501 square miles. Willacy County is to be collected at a nominal pulse spacing (NPS) of 2.0 meters. The Willacy County Texas LiDAR Acquisition project is to provide high accuracy bare-earth processed LiDAR data suitable for the project area. The project consisted of acquisition, post-processing, classification of LiDAR data, and creation of final deliverable products. All areas shall be collected at a nominal pulse spacing (NPS) of 2.0 meters based on UTM14, related to the North American Datum of 1983 (NSRS2007). Vertical accuracy was to achieve a RMSE Z of 12.5 cm (95% confidence level of less than 24.5 cm) or better in the "Open Terrain" land cover category for all areas. Accuracy statement is based on areas of moderate to flat terrain. Diminished accuracies are to be expected in areas in dense vegetation. The accuracy of the LiDAR data as tested met or exceeded the vertical accuracy requirements, however, derived products may be less accurate in areas of dense vegetation due to a lesser number of points defining the bare-earth in such areas.
      </purpose>
		</descript>
		<timeperd>
			<timeinfo>
				<sngdate>
					<caldate>
						<!--Enter the year, month, and day  for which the data corresponds to the currentness reference (for these orthoimage chips, this would be the oldest photo date).

Domain: "Unknown" free date-->
            20110201
          </caldate>
				</sngdate>
			</timeinfo>
			<current>
        ground condition
        <!--Enter the basis on which the time period of content information is determined.

Domain: "ground condition" "publication date" free text-->
			</current>
		</timeperd>
		<status>
			<progress>
				<!--Enter the state of the data set.

Domain: "Complete" "In work" "Planned"-->
        Complete
      </progress>
			<update>
				<!--Enter the frequency with which changes and additions are made to the data
set after the initial data set is completed.

Domain: "Continually" "Daily" "Weekly" "Monthly" "Annually" "Unknown" "As
needed" "Irregular" "None planned" free text-->
        unknown
      </update>
		</status>
		<spdom>
			<bounding>
				<westbc>000.00000000</westbc>
				<eastbc>000.00000000</eastbc>
				<northbc>00.00000000</northbc>
				<southbc>00.00000000</southbc>
			</bounding>
			<lboundng>
				<leftbc>000000.000000</leftbc>
				<rightbc>000000.000000</rightbc>
				<bottombc>000000.000000</bottombc>
				<topbc>000000.000000</topbc>
			</lboundng>
		</spdom>
		<keywords>
			<theme>
				<themekt>
          None
          <!--Reference a formally registered thesaurus or similar authoritative source for theme keywords.-->
				</themekt>
				<themekey>
					<!--A common-use word or phrase used to describe the subject of the data set.
          
Domain: free text-->
          Willacy County
        </themekey>
				<themekey>
					<!--A common-use word or phrase used to describe the subject of the data set.          

Domain: free text-->
          Light Detection and Ranging
        </themekey>
				<themekey>
					<!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          LiDAR
        </themekey>
				<themekey>
					<!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          LAS Point Cloud
        </themekey>
			</theme>
			<place>
				<placekt>
					<!--Reference to a formally registered thesaurus or a similar authoritative source of place keywords.

Domain: "None" "Geographic Names Information System" free text-->
          None
        </placekt>
				<placekey>
          US
          <!--Enter the geographic name of a location covered by a data set.

Domain: free text-->
				</placekey>
				<placekey>
					<!--Enter the geographic name of a location covered by a data set.

Domain: free text-->
          State
        </placekey>
				<placekey>
					<!--Enter the geographic name of a location covered by a data set.

Domain: free text-->
          TX
        </placekey>
			</place>
		</keywords>
		<accconst>
			<!--Enter restrictions and legal prerequisites for accessing the data set. These include any access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the data set.

Domain: "None" free text-->
      None.
    </accconst>
		<useconst>
			<!--Enter restrictions and legal prerequisites for using the data set after access is granted. These include any use constraints applied to assure the protection of privacy or intellectual property, and any special
restrictions or limitations on using the data set.

Domain: "None" free text-->
      None. However, users should be aware that temporal changes may have occurred since this data set was collected and that 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.
      Acknowledgment of the U.S. Geological Survey would be appreciated for products derived from these data.
    </useconst>
    <ptcontac><cntinfo><cntperp><cntper>Patrick Emmett</cntper><cntorg>USGS</cntorg></cntperp><cntpos>NGTOC</cntpos><cntvoice>573-308-3587</cntvoice><cnttdd>unknown</cnttdd><cntfax>573-308-3810</cntfax><cntemail>pemmett@usgs.gov</cntemail><hours>unknown</hours><cntinst>none</cntinst><cntaddr><addrtype>mailing and physical address</addrtype><address>1400 Independence Road</address><city>Rolla</city><state>MO</state><postal>65401</postal><country>USA</country></cntaddr></cntinfo></ptcontac>
		<datacred>
			<!--Recognition of those who contributed to the data set. Contractor may enter company name of primary contractor.

Domain: free text-->
      AeroMetric, Inc.
    </datacred>
        <native>
      <!--Enter a description of the data set in the producer's processing environment, including items such as the name of the hardware and the software (including version) and the computer operating system.

Domain: free text-->
     1. Scanner - Optech ALTM 3100 EA Serial 03SEN145
     2. Processing Programs and versions - Applanix - POSGPS and POSProc, versions 4.4, MMS version 5.2
     3. Program and version - Optech ASDA
     4. Processing Programs and versions - TerraSolid TerraScan (version 011.005), TerraModeler (version 011.001) and TerraMatch (version        011.003), Intergraph MicroStation (version 08.05.02.55), and GeoCue (7.0.34.5).
     5. Viewing Program - GlobalMapper V12.00
        </native>
  </idinfo>
	<dataqual>
		<attracc>
			<attraccr>
				<!--Contractor should enter description of photographic quality control.-->
        The Fundamental Vertical Accuracy (FVA) of the Classified Bare Earth files for the project area achieved an RMSE of 0.088 meters. Forty-five (45) 'open terrain' survey control points were used in this evaluation, with an additional 20 'open terrain' points held in reserve and supplied to the client. Additional survey control points were also supplied to the client with 20 points in the category of 'short grass' and 18 points in the category of 'tall grass'. 
      </attraccr>
		</attracc>
		<logic>None</logic>
		<complete>
			<!--Describe any specific void areas in the dataset.-->
      Complete
    </complete>
		<posacc>
			<horizpa>
				<horizpar>
					<!--An explanation of the accuracy of the horizontal coordinate measurements and a description of the tests used. This must be entered by the contractor to reflect their methods. This is provided only as a sample of the type of information needed. "Tested" can only be used when data testing is performed against independent checkpoints from a source of higher accuracy.

Domain: free text-->
          All Area data products were acquired at or below 2500 meters above mean terrain (AMT) and have a horizontal accuracy of 0.45 meters (per manufacturers system specifications), with a nominal point spacing of 1.5 meters.  
          </horizpar>
			</horizpa>
			<vertacc>
				<vertaccr>The Fundamental Vertical Accuracy (FVA) of the Classified Bare Earth for all Areas achieved is 0.172 meters at a 95% confidence level in the "Open Terrain" land cover category. Forty-five (45) survey control points were used in this evaluation.
        </vertaccr>
			</vertacc>
		</posacc>
		<lineage>
			<procstep>
				<procdesc>
					<!--Describe the process used to create the dataset.-->
          The LiDAR data was captured using AeroMetric's twin-engine Cessna 310, fixed wing aircraft equipped with a LiDAR system.  The LiDAR system includes a differential GPS unit and inertial measurement system to provide superior positional accuracy.

Acquisition parameters:  
1. Flight Height - 2500 meters above mean terrain
2. Swath Width - 34 degrees
3. Sidelap - 30%
4. Nominal Post Spacing - 1.5 meters

GPS and IMU processing parameters:  
1. Maximum baseline length - Not greater than 40 kilometers.
2. Number of base stations during LiDAR collection - A minimum of 1.  
3. Maximum positional RMS of trajectory during LiDAR collection - 0.05 meters  
4. IMU processing monitored for consistency and smoothness - Yes.

Point Cloud Processing:  
1. Horizontal Datum - NAD83(NSRS2007)  
2. Horizontal Coordinates - Universal Transverse Mercator, Zone 14, in meters.
3. Vertical Datum - NAVD88  
4. Geoid Model used to reduce satellite derived elevations to orthometric heights - NGS Geoid09.

LiDAR Processing:  
1. Point Cloud data is imported via TerraScan in a Microstation V8 (V) CAD environment on a specified 1500 meter by 1500 meter tiling scheme.
2. Analyze the data for overall completeness and consistency.  This is to ensure that there are no voids or anomolies in the data collection.  
3. Inspect for calibration errors in the dataset using the TerraMatch software.  This is accomplished by sampling the data collected across all flight lines and classify the individual lines to ground.  The software will use the ground-classified points by flightline to compute corrections (Heading, Pitch, Roll, and Scale).  
4. Orientation corrections (i.e. Calibration corrections) are applied (if needed) to the entire dataset.  
5. Automatic ground classification is performed using algorithms with customized parameters to best fit the project area. Several areas of varying relief and planimetric features were inspected to verify the final ground surface.  
6. AeroMetric, Inc. provided Quality Assurance and Quality Control (QA/QC) data for this project.  AeroMetric captured QA/QC points in 'open terrain' land cover category that were used to test the accuracy of the LiDAR ground surface.  TerraScan's Output Control Report (OCR) was used to compare the QA/QC data to the LiDAR data. This routine searches the LiDAR dataset by X and Y coordinate, finds the closest LiDAR point and compares the vertical (Z) values to the known data collected in the field.  Based on the QA/QC data, a bias adjustment was determined, and the results were applied (if necessary) to the LiDAR data.  A final OCR was performed with a resulting RMSE of 0.088 meters for the project.  
7. Each tile is reviewed for accuracy and consistency of the macro ground classification. 
8. Once the automatic processing and the testing of LiDAR is complete, AeroMetric meticulously reviews the generated bare-earth surface data to ensure that proper classification was achieved as part of a Quality Control process. 
9. Final deliverables are generated and output to a client specified 1500 meters by 1500 meters tiling scheme.
        </procdesc>
				<procdate>
					<!--The date (year and month or year, month, and day) that the LiDAR data was produced; format  yyyymm, or yyyymmdd-->
          20110909
        </procdate>
			</procstep>
		</lineage>
		<cloud>Unknown</cloud>
	</dataqual>
	<spdoinfo>
		<direct>Point</direct>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>Universal Transverse Mercator</gridsysn>
					<utm>
						<utmzone>
							<!--Enter the  identifier for the UTM zone.
Type: integer

Domain: 
1 <= UTM Zone Number <= 60 for the northern hemisphere;
-60 <= UTM Zone Number <= -1 for the southern hemisphere-->
              14
            </utmzone>
						<transmer>
							<sfctrmer>
								<!--Enter a multiplier for reducing a distance obtained from a map by computation or scaling to the actual distance along the central meridian.

Domain: Scale Factor at Central Meridian > 0.0-->
                0.9996
              </sfctrmer>
							<longcm>
								<!--Enter the line of longitude at the center of a map projection generally used as the basis for constructing the projection.
Type: real
Domain: -180.0 <= Longitude of Central Meridian < 180.0-->
                -90
              </longcm>
							<latprjo>
								<!--Enter latitude chosen as the origin of rectangular coordinates for a map projection.

Domain: -90.0 <= Latitude of Projection Origin <= 90.0-->
                0
              </latprjo>
							<feast>
								<!--Enter the value added to all "x" values in the rectangular coordinates for a map projection. This value frequently is assigned to eliminate negative numbers. Expressed in the unit of measure identified in Planar Coordinate Units.

Domain: free real-->
                500000
              </feast>
							<fnorth>
								<!--Enter the value added to all "y" values in the rectangular coordinates for a map projection. This value frequently is assigned to eliminate negative numbers. Expressed in the unit of measure identified in Planar Coordinate Units.

Domain: free real-->
                0
              </fnorth>
						</transmer>
					</utm>
				</gridsys>
				<planci>
					<plance>
						<!--Enter the means used to represent horizontal positions.

Domain: "coordinate pair" "distance and bearing" "row and column"-->
            coordinate pair
          </plance>
					<coordrep>
						<absres>
							<!--Enter the (nominal) minimum distance between the "x" or column values of two adjacent points, expressed in Planar Distance Units of measure.

Domain: Abscissa Resolution > 0.0-->
              0.01
            </absres>
						<ordres>
							<!--Enter the (nominal) minimum distance between the "y" or row values of two adjacent points, expressed in Planar Distance Units of measure.

Domain: Ordinate Resolution > 0.0-->
              0.01
            </ordres>
					</coordrep>
					<plandu>
						<!--Enter units of measure used for distances.

Domain: "meters" "international feet" "survey feet" free text-->
            meters
          </plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>
					<!--Enter the identification given to the reference system used for defining the coordinates of points.

Domain: "North American Datum of 1927" "North American Datum of 1983" free text-->
          North American Datum of 1983 (NSRS 2007)
        </horizdn>
				<ellips>
          Geodetic Reference System 80
          <!--Enter identification given to established representations of the Earth's shape.

Domain: "Clarke 1866" "Geodetic Reference System 80" free text-->
				</ellips>
				<semiaxis>
					<!--Enter radius of the equatorial axis of the ellipsoid.

Domain: Semi-major Axis > 0.0-->
          6378137.000000
        </semiaxis>
				<denflat>
					<!--Enter the denominator of the ratio of the difference between the equatorial and polar radii of the ellipsoid when the numerator is set to 1.

Domain: Denominator of Flattening > 0.0-->
          298.25722210088
        </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>
  <refSysInfo>
	  <RefSystem>
		 <refSysID>
  			<identCode>NAD_1983_UTM_Zone_14N</identCode> 
  		</refSysID>
  	</RefSystem>
  </refSysInfo>
	<distinfo>
		<resdesc>		The data are being provided on an 'as is' basis. The USGS specifically 
								disclaims any warranty, expressed or implied, including, but not limited 
								to, the implied warranties or merchantability and fitness for a particular 
								use. The entire risk as to quality and performance is with the user. 
								In no event will the USGS or its staff be liable for any direct, indirect,
								incidental, special, consequential, or other damages, including loss of profit,
								arising out of the use of these data even if the USGS has been advised of the
								possibility of such damages. All data are intended for resource management use.
		</resdesc>
		<distliab>	Translation of files to formats other than those described here is the sole responsibility 
			        	of individuals downloading the data. Although these data have been processed successfully 
			        	on a computer system at the USGS, no warranty expressed or implied is made by the USGS 
			        	regarding the use of the data on any other system, nor does the act of distribution 
			        	constitute any such warranty. Data may have been compiled from various outside sources.  
			        	Spatial information may not meet National Map Accuracy Standards.  This information may 
			        	be updated without notification. The USGS shall not be liable for any activity involving 
			        	these data, installation, fitness of the data for a particular purpose, its use, or 
			        	analyses results.
		</distliab>
		<stdorder>
			<fees>None</fees>
			<turnarnd>Varies</turnarnd>
			<nondig>ASCII or LAS</nondig>
			<ordering>None.  Downloadable data only.</ordering>
		</stdorder>
		<custom>None</custom>
		<distrib>
			<cntinfo>
				<cntorgp>
  				<cntorg>U.S. Geological Survey</cntorg> 
					<cntper>EROS Customer Services</cntper>
  			</cntorgp>
				<cntaddr>
	  			<addrtype>Mailing and physical address</addrtype> 
  				<address>Customer Services</address> 
  				<address>U.S. Geological Survey</address> 
  				<address>EROS Data Center</address> 
  				<address>47914 252nd Street</address> 
  				<city>Sioux Falls</city> 
  				<state>SD</state> 
  				<postal>57198-0001</postal> 
  				<country>US</country> 
  			</cntaddr>
  			<cntvoice>1-800-252-4547</cntvoice> 
  			<cnttdd>1-605-594-6933</cnttdd> 
  			<cntfax>1-605-594-6589</cntfax> 
  			<cntemail>custserv@usgs.gov</cntemail> 
  			<hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours> 
  			<cntinst>	The above is the contact information for EROS Data Center in 
									Sioux Falls, SD. this is the digital data storage and distribution 
									center for the USGS. For best service, identify your question 
									as related to "CLICK Lidar Data".
  			</cntinst> 
  		</cntinfo>
		</distrib>
	</distinfo>

	
	<metainfo>
		<metd>
			<!--Enter the date that the metadata were created or last updated.

Domain: free date-->
      20110912
    </metd>
		<metc>
			<cntinfo>
				<cntorgp>
  				<cntorg>U.S. Geological Survey</cntorg> 
  			</cntorgp>
				<cntaddr>
  				<addrtype>Mailing and physical address</addrtype> 
  				<address>Customer Services</address> 
  				<address>U.S. Geological Survey</address> 
  				<address>EROS Data Center</address> 
  				<address>47914 252nd Street</address> 
  				<city>Sioux Falls</city> 
  				<state>SD</state> 
  				<postal>57198-0001</postal> 
  				<country>US</country> 
  			</cntaddr>
  			<cntvoice>1-800-252-4547</cntvoice> 
  			<cnttdd>1-605-594-6933</cnttdd> 
  			<cntfax>1-605-594-6589</cntfax> 
  			<cntemail>custserv@usgs.gov</cntemail> 
  			<hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours> 
  			<cntinst>	The above is the contact information for EROS Data Center in 
									Sioux Falls, SD. this is the digital data storage and distribution 
									center for the USGS. To improve service, identify your question 
									as related to "CLICK Lidar Data".
  			</cntinst> 
  		</cntinfo>
		</metc>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>
						<!--Enter the name of the organization to which the contact type applies.

Domain: free text-->
            AeroMetric, Inc.
          </cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>
						<!--Enter the information provided by the address.

Domain: "mailing" "physical" "mailing and physical", free text-->
            Mailing and physical address
          </addrtype>
					<address>
						<!--Enter an address line for the address. Enter contractor's mailing address here.

Domain: free text-->
            4020 Technology Parkway
          </address>
					<city>
						<!--Enter name of the city where the contractor is located.-->
            Sheboygan
          </city>
					<state>
						<!--Enter the name of the State in which the contractor is located.-->
            WI
          </state>
					<postal>
						<!--Enter the zip code for the address above.-->
            53083-6049
          </postal>
					<country>US</country>
				</cntaddr>
				<cntvoice>
					<!--Enter the telephone number for the POC for this dataset.-->
          1-920-457-3631
        </cntvoice>
				<cntfax>1-920-457-0410</cntfax>
				<cntemail>
					<!--Enter the e-mail address for the contact group or persons.-->
          rmerry@aerometric.com
        </cntemail>
				<hours>Monday through Friday 8:00 AM to 5:00 PM (Central Time)</hours>
			</cntinfo>
		</metc>
		<metstdn>
      FGDC Content Standard for Digital Geospatial Metadata
      <!--Enter the name of the metadata standard used to document the data set.

Domain: "FGDC Content Standard for Digital Geospatial Metadata" free text-->
		</metstdn>
		<metstdv>
      FGDC-STD-001-1998
      <!--Enter identification of the version of the metadata standard used to document the data set.

Domain: free text-->
		</metstdv>
	</metainfo>
</metadata>


