﻿<?xml version="1.0" encoding="utf-8"?>
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Aero-Graphics, Inc.</origin>
        <pubdate>2018</pubdate>
        <title Sync="TRUE">t2322_1722.tif</title>
        <geoform Sync="TRUE">raster digital data</geoform>
        <ftname Sync="TRUE">t2322_1722.tif</ftname>
      </citeinfo>
    </citation>
    <descript>
      <abstract>Nez Perce County, Lewis Clark Valley area 0.25, 0.5, and 1 foot ortho images, from Aero-Graphics, Inc., flown on May 28, 2018, May 29, 2018, and June 02, 2018. 1125 tiles cover 895.8 square miles over the area of interest and are available in TIFF and SID formats.

The Lewis Clark Valley project was horizontally referenced to the North American Datum of 1983 (NAD83) 2011, Idaho: State Plane Idaho West Zone (Idaho portions), Washington: State Plane Washington South (Washington portions), and vertically referenced to the North American Vertical Datum of NAVD 1988. Survey Feet have been adusted to ground for the Idaho portions. Units are in U.S. Foot.</abstract>
      <purpose>The flight and images produced under this task order have been supplied to Nez Perce County for use in the development of the geographic information system (GIS) for the county of Nez Perce, Idaho and Lewis Clark Valley area.

Digital orthophotos are aerial images corrected for displacement caused by relief in the Earth's surface, camera/sensor lens distortion and tilting of the sensor at the time of image acquisition.  Additionally, orthophotos are assigned a uniform scale, which allows an end-user the ability to derive accurate measurements from the imagery.  Orthophotos can be used as an accurate record of landscape conditions at the time of the corresponding aerial imagery.  As such, the digital orthophotos are used in a variety of applications, such as environmental monitoring, facility engineering/maintenance, city/county planning, property line review, etc.  The digital orthophoto can be used alone or as a raster base map for corresponding vector line mapping.</purpose>
      <supplinf>Camera: Vexcel UltraCamX (UCX)
Lens Filter: None
Sensor Array: The camera is a sensor array
Focal Length: 100.500mm
Calibration Date: April-17-2014
Exposure Compensation: None</supplinf>
      <langdata Sync="TRUE">en</langdata>
    </descript>
    <timeperd>
      <timeinfo>
        <mdattim>
          <sngdate>
            <caldate>20180528</caldate>
          </sngdate>
          <sngdate>
            <caldate>20180529</caldate>
          </sngdate>
          <sngdate>
            <caldate>20180602</caldate>
          </sngdate>
        </mdattim>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc Sync="TRUE">-116.949522</westbc>
        <eastbc Sync="TRUE">-116.937456</eastbc>
        <northbc Sync="TRUE">46.392768</northbc>
        <southbc Sync="TRUE">46.384419</southbc>
      </bounding>
      <lboundng>
        <leftbc Sync="TRUE">2322000</leftbc>
        <rightbc Sync="TRUE">2325000</rightbc>
        <topbc Sync="TRUE">1725000</topbc>
        <bottombc Sync="TRUE">1722000</bottombc>
      </lboundng>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Digital Ortho Rectified Image</themekey>
        <themekey>Image Map</themekey>
        <themekey>Orthoimage</themekey>
        <themekey>Orthophoto</themekey>
        <themekey>Rectified Image</themekey>
        <themekey>Rectified Photograph</themekey>
        <themekey>SID</themekey>
        <themekey>TIFF</themekey>
      </theme>
      <place>
        <placekt>Geographic Names Information System</placekt>
        <placekey>United States of America</placekey>
        <placekey>Idaho</placekey>
        <placekey>Washington</placekey>
        <placekey>Nez Perce County</placekey>
        <placekey>Culdesac</placekey>
        <placekey>Lapwai</placekey>
        <placekey>Peck</placekey>
      </place>
      <temporal>
        <tempkt>None</tempkt>
        <tempkey>2018</tempkey>
      </temporal>
    </keywords>
    <accconst>None</accconst>
    <useconst>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.</useconst>
    <native>Microsoft Windows Vista Version 6.1 (Build 7601) Service Pack 1; ESRI ArcCatalog 9.3.1.4000</native>
    <natvform Sync="TRUE">Raster Dataset</natvform>
  </idinfo>
  <dataqual>
    <logic>Data cover the entire area specified for this project.</logic>
    <complete>All files are inspected to ensure that the files load in their correct geographic position, all files conform to the project specifications for file standard and content.</complete>
    <posacc>
      <horizpa>
        <horizpar>All products meet or exceed National Map Accuracy standards.</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>All products meet or exceed National Map Accuracy standards.</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <procstep>
        <procdesc>Digital Aerial Photography:  

Aero-Graphics collected imagery on May 28, 2018, May 29, 2018, and June 02, 2018 using a UltraCamX direct digital sensor.  A 0.25 inch pixel size resulted in a 1:9726 scale, the 0.5 inch pixel size resulted in a 1:20841 scale, and the 1 foot pixel size resulted in a scale of 1:41681.  Nominal overlap was 60% forward and 30% side.  The UltraCamX has a 7.2 micron pixel size, a focal length of 100.5 millimeters, and collects red, green, blue, near-infrared, and panchromatic image bands simultaneously.  The UltraCamX is equipped with forward motion compensation, high resolution optics, airborne GPS capability, an ApplAnix inertial measurement unit and is also equipped with a computer controlled GPS guidance system.  Based upon the CCD array configuration present in the digital sensor, imagery for each exposure is 14,430 pixels in the cross-track dimension.</procdesc>
      </procstep>
      <procdate>2018</procdate>
      <procstep>
        <procdesc>Aerial Mission Project Planning and Execution:  

The project boundary was uploaded into TrackAir flight planning software where the software generated each flight line and tabulated the number of exposures based upon project specific criteria such as desired photo scale or ground sample distance and percent of forward and side lap.  Ground elevation values for each flight line were determined and applied in TrackAir's DEM "SnapPlan" module planning software.  

Sites for base stations (IGS, CORS and/or Project Specific-Airport Base) were determined by the level of GPS/IMU data accuracy that was needed and total area to be covered by the aircraft during that day.  

To support the airborne GPS flight, Aero-Graphics' flight crew utilized operational CORS/IGS stations and a manually-set GPS base in the vicinity of the project site for use in post-processing photo center coordinates, accurate to within 5 m.  Following the flight, Aero-Graphics downloaded the imagery and GPS/IMU data and performed GPS/IMU data post processes.  

A ground verification of all aviation equipment and camera systems was performed to ensure all equipment is working prior to take off.  The project file was loaded from the portable media device to TrackAir's SnapShot flight management software (FMS).  Calibration of all systems (FMS/GPS/IMU) was performed during a 5 minute initialization period prior to takeoff.  

Before flight execution, the camera operator opened the project file in TrackAir's SnapShot and the flight management system provided guidance information to the first flight line.  Images were reviewed as they are collected to assure they meet target project tolerances.  Corrections for airplane roll, pitch, drift, and forward motion were performed automatically by a gyro stabilized mount controlled by the IMU and flight management system.  All systems were constantly monitored during flight execution.  

Once the flight mission was complete, the camera operator reviewed the recorded flight acquisition data enroute to the base of operation.  System shutdown procedures were performed prior to landing and/or leaving the project area.  All data storage mediums and flight logs were then removed from the aircraft and returned to the office for processing.  All digital imagery was downloaded and processed using Microsoft's UltraMap software.</procdesc>
      </procstep>
      <procdate>2018</procdate>
      <procstep>
        <procdesc>Image Download Management:  

Post flight, the imagery was downloaded from the camera hard drives (primary and backup) to Aero-Graphics' fiber-channel based Storage Area Network (SAN).  Once downloaded, the image data was converted to Level 1 imagery.  Using Microsoft UltraMap software, Level 1 imagery was stitched together (9 panchromatic and 4 color) and processed to Level 2.  Level 2 imagery consisted of pan-sharpened, high-resolution 4 band (RGB-IR) and Panchromatic TIFF images.  Shortly thereafter, Level 2 image data was loaded into OPC software for Level 3 processing.  Level 3 processing consists of taking the Level 2 images and performing radiometric adjustments on the various images across the project; such as, correct color balance, gamma adjustments, and dodging to achieve a uniform balance across all images.  

Following advanced radiometric adjustments, processed images were copied to a custom designed Storage Area Network (SAN), which is connected by high-speed fiber optics to desktop processing clients.</procdesc>
      </procstep>
      <procdate>2018</procdate>
      <procstep>
        <procdesc>GPS/IMU Processing and AT Processing:  

Raw GPS/IMU data was processed through Applanix POSPac MMS.  This refined/corrected the air point coordinates (XYZ) and angles (Omega, Phi, Kappa, or roll, pitch, and yaw of the plane) based on correction data obtained from a combination of Local, CORS and Aero-Graphics set base station.  

Additional GPS/IMU Processing Q/C procedures: 
Examined result plots (smoothed best estimate of trajectory) to ensure correct resemblance of planned flight path (seems obvious, but is a very simple and fast way to assure a correctly flown project).  
Examined result plots to ensure a sufficient number of satellites during the flight  
Examined result plots to ensure a good satellite geometry, spread, and PDOP  

Inpho Match-AT software was utilized to perform fully analytical digital aero-triangulation.  Automatic tie points and GPS/ IMU data were read and measured to extend full control for each stereo model.  

Aerotriangulation blocks were defined primarily by order of acquisition and consisted of 96 imagery strips.  Image tie points providing the observations for the least squares bundle adjustment were selected from the images using an autocorrelation algorithm.  Photogrammetric control points consisted of photo identifiable features collected using GPS field survey techniques.  These control points were loaded into the AT software and measured in the acquired image strips.  A least squares bundle adjustment of image tie points, control points and the ABGPS was performed to develop a refined aerotriangulation solution for each block using Inpho Match-AT software.  

Once the AT solution was complete, Inpho DTMaster was used to check every model in stereo.  QC/QA procedures were implemented to sure that all parallax was cleared and that all tie points were on the ground with no points floating or digging.  Auto-tie-point generation, depending on the terrain, is somewhat notorious for putting some points on water, trees, or just floating above or digging into the ground.</procdesc>
      </procstep>
      <procdate>2018</procdate>
      <procstep>
        <procdesc>Ortho Photo Generation:

Ortho workflow began by importing the AT solution output from Inpho Match AT software into Inpho MatchT surface generation software. This software determined where corresponding pixels were in overlapping raw photos and created points on the bare earth surface inside the area of interest.  MatchT created a dense point cloud over the area of interest.  

Once the point surfaces were created, they were then imported into DTMaster for stereo analysis.  By viewing the point surface in 3D, any areas of the surface that did not fall on the earth's surface were located and corrected.  

In the OrthoMaster software, raw images were run against the corrected surface to create an ortho rectified image from each raw photo.  This took out any distortion in the photo and brought everything to scale.  

After the raw individual orthos were finished, each photo was reviewed for anomalies.  The image files were then mosaicked into tiles in TIFF and SID formats.  Color correction of adjacent images was completed using OrthoVista software.  

Once imagery had been inspected and passed all quality control procedures (seam line, radiometry, and spatial analyses), the files were then written to hard drive for delivery.  As a final step, the hard drive was installed on an isolated computer and the drive contents tested for accessibility and completeness.   

1125 tiles cover 895.8 square miles and were delivered in TIFF and SID formats.  Overall SID mosaics and tile indexes have also been included in SID and PDF file format.</procdesc>
        <procdate>2018</procdate>
      </procstep>
    </lineage>
    <cloud>0</cloud>
  </dataqual>
  <spdoinfo>
    <direct>Raster</direct>
    <rastinfo>
      <rasttype Sync="TRUE">Pixel</rasttype>
      <rowcount Sync="TRUE">12000</rowcount>
      <colcount Sync="TRUE">12000</colcount>
      <vrtcount Sync="TRUE">1</vrtcount>
      <rastxsz Sync="TRUE">0.250000</rastxsz>
      <rastysz Sync="TRUE">0.250000</rastysz>
      <rastbpp Sync="TRUE">8</rastbpp>
      <rastorig Sync="TRUE">Upper Left</rastorig>
      <rastcmap Sync="TRUE">FALSE</rastcmap>
      <rastcomp Sync="TRUE">None</rastcomp>
      <rastband Sync="TRUE">3</rastband>b
      <rastdtyp Sync="TRUE">pixel codes</rastdtyp>
      <rastplyr Sync="TRUE">FALSE</rastplyr>
      <rastifor Sync="TRUE">TIFF</rastifor>
    </rastinfo>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <planci>
          <plance Sync="TRUE">row and column</plance>
          <coordrep>
            <absres Sync="TRUE">0.250000</absres>
            <ordres Sync="TRUE">0.250000</ordres>
          </coordrep>
          <plandu Sync="TRUE">survey feet</plandu>
        </planci>
        <mapproj>
          <mapprojn Sync="TRUE">Lambert Conformal Conic</mapprojn>
          <lambertc>
            <stdparll Sync="TRUE">38.450000</stdparll>
            <stdparll Sync="TRUE">39.750000</stdparll>
            <longcm Sync="TRUE">-105.500000</longcm>
            <latprjo Sync="TRUE">37.833333</latprjo>
            <feast Sync="TRUE">3000000.000316</feast>
            <fnorth Sync="TRUE">999999.999996</fnorth>
          </lambertc>
        </mapproj>
      </planar>
      <geodetic>
        <horizdn Sync="TRUE">North American Datum of 1983</horizdn>
        <ellips Sync="TRUE">Geodetic Reference System 80</ellips>
        <semiaxis Sync="TRUE">6378137.000000</semiaxis>
        <denflat Sync="TRUE">298.257222</denflat>
      </geodetic>
      <cordsysn>
        <geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
        <projcsn Sync="TRUE">NAD_1983_StatePlane_Idaho_West_Feet</projcsn>
      </cordsysn>
    </horizsys>
  </spref>
  <eainfo>
    <overview>
      <eaover>Black and white orthoimagery is organized in an 8-bit gray-scale value between 0-255.  Zero represents black, while 255 represents white.  All values between zero and 255 represent a shade of gray varying from black to white.  Natural color orthoimagery is organized in three color bands or channels which represent the red, green, and blue portions of the spectrum.  Each image pixel is assigned a triplet of numeric values, one for each color band.  Numeric values range from 0 to 255.  Areas where data is incomplete due to lack of full image coverage are represented with the numeric value of 255.</eaover>
      <eadetcit>U.S. Department of the Interior, U.S. Geological Survey, 1996, Standards for Digital Orthophotos: Reston, VA.</eadetcit>
    </overview>
  </eainfo>
  <metainfo>
    <metd>20180913</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Aero-Graphics, Inc.</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical address</addrtype>
          <address>40 West Oakland Avenue</address>
          <city>Salt Lake City</city>
          <state>Utah</state>
          <postal>84115-3007</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>(801) 487-3273</cntvoice>
        <cntfax>(801) 487-3313</cntfax>
        <cntemail>agi@aero-graphics.com</cntemail>
        <hours>8 AM - 5 PM Mon. - Fri.</hours>
      </cntinfo>
    </metc>
    <metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn>
    <metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv>
    <mettc Sync="TRUE">local time</mettc>
  </metainfo>
</metadata>