<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE metadata SYSTEM "csdgm2.dtd">
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>
          <!--Enter the name of an organization or individual that developed the data set. If the name of editors or compilers are provided, the name must be followed by "(ed.)" or "(comp.)" respectively.


Domain: "Unknown" free text-->
          EarthData International of Maryland, LLC
        </origin>
        <pubdate>
          <!--Enter the date when the data set is published or otherwise made available for release. Not entered by contractor.
Format YYYYMMDD  

Domain: "Unknown" "Unpublished material" free date-->
          20040315
        </pubdate>
        <title>
          <!--Enter the name by which the data file is known. 

Domain: free text-->
          LIDAR Mapping of the Toutle River, WA river basin.  File Name:mounnwfst.txt
        </title>
        <geoform>
          <!--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-->
          Model
        </geoform>
        <othercit>This variably-spaced reflective surface data set is a portion of a project composed of an area delimited by the 500 year flood plain of the Toutle River, WA river basin.  The data set is contained within the USGS quad Mount Saint Helens, WA.</othercit>
      </citeinfo>
    </citation>
    <descript>
      <abstract>
        <!--Enter a brief narrative summary of the data set.

Domain: free text-->
        This variably-spaced reflective surface data set consists of 8,705,044 records of x,y,z values.

The LIDAR system uses a pulsed laser ranging system mounted onboard an aircraft to measure ground elevation.
The laser emits laser beams at high frequency and is directed downward at the earth's surface through a port opening in the bottom of the aircraft's fuselage.  The laser system records the time difference between emission of the laser beam and the reception of the reflected laser signal in the aircraft.
      </abstract>
      <purpose>
        <!--Enter a summary of the intentions with which the data set was developed. 

Domain: free text-->
        The LIDAR collected under this task order has been supplied to the U.S. Geological Survey (USGS) to support photogrammetric and mapping services.

Data collected of these elevation data occurred during leaf off conditions.
      </purpose>
      <supplinf>
        <!--Enter any other descriptive information about the dataset that doesn't fit anywhere else.
-->
        The areas of interest were flown at different altitudes and scanner settings depending on the area of collection.  Lower elevation areas were flown at an altitude of 2133 meters (7000 feet) above mean terrain (AMT).  The airspeed was 140 knots.  The laser pulse rate was 29 kHz.  The field of view was 35 degrees.  The scan rate was 20 Hz.  The average swath width was 1345 meters.  The lidar mode was 3 + 3.  Higher elevation areas were flown at an altitude of 2438 meters (8000 feet) above mean terrain (AMT).  The airspeed was 140 knots.  The laser pulse rate was 29 kHz.  The field of view was 35 degrees.  The scan rate was 18 Hz.  The average swath width was 1537 meters.  The lidar mode was 3 + 3.

File Naming Format:

-qdnm - The first four (4) characters of the filename shall correspond to the first four characters of the quadrangle name.

-qq - Identifies the quarter quad of the original quad where:
 nw - northwest quadrant of quadrangle
 sw - southwest quadrant of quadrangle
 se - southeast quadrant of quadrangle
 ne - northeast quadrant of quadrangle

-typ - Identifies this file contents where:
 brg - removed bridges
 fst - mass points file - First return
 lst - mass points file - Last Return/Bare-Earth
 mta - metadata file
 tin - TIN Files

-.ext - File extension where:
 .txt - Geo-referenced ASCII x,y,z file
 .txt - Metadata file for each ASCII x,y,z file
 .e00 - TIN files
      </supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>
            <!--Enter the year, month, and day  for which the data corresponds to the currentness reference.   Format YYYYMMDD

Domain: "Unknown" free date-->
            20040315
          </caldate>
        </sngdate>
      </timeinfo>
      <current>
        <!--Enter the basis on which the time period of content information is determined.

Domain: "ground condition" "publication date" free text-->
        Publication Date
      </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>
          <!--Enter western-most coordinate of the limit of coverage expressed in longitude (decimal degrees). 

Domain: -180.0 <= West Bounding Coordinate < 180.0-->
          -122.251207
        </westbc>
        <eastbc>
          <!--Enter eastern-most coordinate of the limit of coverage expressed in longitude (decimal degrees).


Domain: -180.0 <= East Bounding Coordinate <= 180.0-->
          -122.188208
        </eastbc>
        <northbc>
          <!--Enter northern-most coordinate of the limit of coverage expressed in latitude (decimal degrees).


Domain: -90.0 <= North Bounding Coordinate <= 90.0;
North Bounding Coordinate >= South Bounding Coordinate-->
          46.249832
        </northbc>
        <southbc>
          <!--Enter southern-most coordinate of the limit of coverage expressed in latitude (decimal degrees).


Domain: -90.0 <= South Bounding Coordinate <= 90.0;
South Bounding Coordinate <= North Bounding Coordinate-->
          46.187832
        </southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>
          <!--Reference a formally registered thesaurus or similar authoritative source for theme keywords. If you didn't use one, enter "none".-->
          EDI Thesaurus
        </themekt>
        <themekey>
          <!--A common-use word or phrase used to describe the subject of the data set. Repeat themekey as many times as needed.

Domain: free text-->
          Light Detection and Ranging (LIDAR)
        </themekey>
        <themekey>
          <!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          Terrain elevation
        </themekey>
        <themekey>
          <!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          Laser
        </themekey>
        <themekey>
          <!--A common-use word or phrase used to describe the subject of the data set.

Domain: free text-->
          Mapping
        </themekey>
        <themekey>Reflective</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-->
          U.S. Department of Commerce, 1995, Countries, dependencies, areas of special sovereignty, and their principal administrative divisions, Federal Information Processing Standard (FIPS) 10-4): Washington, D.C., National Institute of Standards and Technology.
        </placekt>
        <placekey>
          US
          <!--Enter the geographic name of a location covered by a data set.

Domain: free text-->
        </placekey>
      </place>
      <place>
        <placekt>
          <!--Reference to a formally registered thesaurus or a similar authoritative source of place keywords.

Domain: "None" "Geographic Names Information System" free text-->
          U.S. Department of Commerce, 1987, Codes for the Identification of the States, the District of Columbia and the outlying areas of the United States, and associated areas (Federal Information Processing Standard (FIPS) 5-2): Washington, D.C., National Institute of Standards and Technology.
        </placekt>
        <placekey>
          <!--Enter the two-letter designation for the State
-->
          WA
        </placekey>
      </place>
      <place>
        <placekt>None</placekt>
        <placekey>
          <!--Enter the Urban Area name.  


-->
          Toutle River, WA
        </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.

This data was collected to support ASPRS Class I standards for mapping as required to support the requirements of 2' contours.
    </useconst>
    <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-->
      Microsoft Windows 2000 Ver 5.0
ARC GIS ArcInfo 8.2
Lidar Edit (Proprietary)
Lites (Proprietary)
Terrasolid - Terrascan Ver. 3.003
Terrasolid - Terramodeler Ver. 3.003
    </native>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>
        <!--Enter description of the accuracy of the data.

-->
        Raw elevation measurements have been determined to be vertically accurate to within 15cm.
      </attraccr>
    </attracc>
    <logic>
      <!--Enter an explanation of the fidelity of relationships in the data set and tests used.

-->
      Not applicable
    </logic>
    <complete>
      <!--Enter information about omissions, selection criteria, generalization, definitions used, and other rules used to derive the data set.

-->
      Contains only LIDAR derived x,y,z data.
    </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-->
          Horizontal positional accuracy was determined through LH Systems ScanSet proprietary software.
        </horizpar>
        <qhorizpa>
          <horizpav>
            <!--Enter an estimate of the accuracy of the horizontal coordinate measurements in the data set expressed in ground units (meters for this dataset).

Domain: free real
-->
            0.30 cm
          </horizpav>
          <horizpae>
            <!--Enter the identification of the test that yielded the Horizontal Positional Accuracy Value. This dataset has no associated scale that would allow computation from National Map Accuracy Standard. Methods listed in the NSSDA are required.

Domain: free text
-->
            LIDAR elevation points are estimated to be horizontally accurate to 0.30 cm.   Horizontal positional accuracy was determined through LH Systems ScanSet proprietary software.
          </horizpae>
        </qhorizpa>
      </horizpa>
      <vertacc>
        <vertaccr>
          <!--Describe the vertical accuracy of the dataset, encompassing both random and systematic errors introduced during production of the data. 
-->
          The data set was evaluated against GPS collected control points which resulted in an vertical RMSE of 0.053 meters.
        </vertaccr>
        <qvertpa>
          <vertaccv>
            <!--Enter an estimate of the accuracy of the vertical coordinate measurements in the data set expressed in (ground) meters.

Domain: free real-->
            15cm - 30cm
          </vertaccv>
          <vertacce>
            <!--Enter the identification of the test that yielded the Vertical Positional
Accuracy Value.

Domain: free text-->
            The ALS 40 LIDAR sensor vertical accuracy is stated as being between 15cm and 30cm.  Based on project acquisition parameters results of less than 15cm are common with this sensor.
          </vertacce>
        </qvertpa>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <!--Document the source used for the data. Repeat this section for each source.-->
        <srccite>
          <citeinfo>
            <origin>EarthData International of Maryland, LLC</origin>
            <pubdate>20040315</pubdate>
            <title>LIDAR data</title>
          </citeinfo>
        </srccite>
        <typesrc>
          <!--Enter the medium of the source dataset.

Examples: paper, stable-base material, CD-ROM, disc, cartridge tape
-->
          CD-ROM
        </typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>
                <!--Enter the date to which this source is current.
Format YYYYMMDD-->
                20040315
              </caldate>
            </sngdate>
          </timeinfo>
          <srccurr>
            <!--Enter the basis on which the time period of content information is determined.

Domain: "ground condition" "publication date" free text-->
            Publication date
          </srccurr>
        </srctime>
        <srccitea>
          <!--Enter the abbreviation by which the source is referenced in the Process Description.-->
          LIDAR
        </srccitea>
        <srccontr>
          <!--Brief statement identifying the information contributed by the source to the data set-->
          Source data
        </srccontr>
      </srcinfo>
      <procstep>
        <procdesc>
          <!--Describe the process used to create the dataset. Be sure to include how all sources were used.-->
          EarthData has developed a unique method for processing LIDAR data to either reflective or bare-earth surfaces.  The algorithms for filtering data were utilized within EarthData's proprietary software and commercial software written by TerraSolid.  This software suite of tools provides efficient processing for small to large-scale projects and has been incorporated into ISO 9001 compliant production work flows.  The following is a step-by-step breakdown of the process utilized to produce variably-spaced reflective surface data sets.
1.  Processing of the LIDAR data begins with refinement of the initial boresight alignment parameters provided by EarthData Aviation in the LITES configuration file delivered with the raw data. The technician also verifies that there are no voids, and that the data covers the entire project area. Calibration is accomplished using the tri-directional flight lines over the project airport, which is generally flat and free of major obstructions, trees or brush. Two overlapping bi-directional lines are flown along the length of the runway, and the cross flight line is perpendicular to both. All three lines are examined to ensure that they agree, within expected system tolerances, in the overlapping areas. The technician will review flight lines and locate the areas that contained systematic errors or distortions that were introduced by the LIDAR sensor.
2.   Systematic distortions highlighted in step 1 were removed and the data was re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from on type of land cover to another.
3.  All flight lines are processed with the refined calibration parameters obtained thru steps 1 and 2.  All flight line are examined to ensure that they agree, within expected system tolerances, in the overlapping areas (side lap).
3a. R1 (first return) points are extracted from the point cloud and are used for Reflective surface classification.
4.  The LIDAR data for each flight line was trimmed in batch for the removal of the overlap areas between flight lines.  The data was checked against a control network to ensure that vertical requirements were maintained. Conversion to the client-specified datum and projections were then completed.  The LIDAR flight line data sets were then segmented into adjoining tiles for batch processing and data management.
5.  The data was then edited for Blunder removal.  
6.  The data was processed interactively by the operator using LIDAR editing tools. During this final phase the operator generated a TIN based on a desired thematic layers to evaluate the automated classification performed in step 5. This allowed the operator to quickly re-classify points from one layer to another and recreate the TIN surface to see the effects of edits.  The use of geo-referenced images were toggled on or off to aid the operator in identifying problem areas. The data was also examined with an automated profiling tool to aid the operator in the reclassification.
7.  The data was separated into (1) variably-spaced Reflective surface in ASCII x-y-z comma delimited files and (2) ESRI Arc/Info TIN format.  The files were written to PC readable CD-ROM.
        </procdesc>
        <procdate>
          <!--The date that the dataset was produced; format  yyyymmdd-->
          20040315
        </procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>
      <!--The system of objects used to represent space in the dataset. 

Domain: point, vector, or raster-->
      point
    </direct>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>
            Universal Transverse Mercator
            <!--Enter name of the grid coordinate system.

Domain: "Universal Transverse Mercator" "Universal Polar Stereographic" "State Plane Coordinate System 1927" "State Plane Coordinate System 1983" "ARC Coordinate System"
"other grid system" -->
          </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-->
              10
            </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-->
                -123.000000
              </longcm>
              <latprjo>
                <!--Enter latitude chosen as the origin of rectangular coordinates for a map projection.

Domain: -90.0 <= Latitude of Projection Origin <= 90.0-->
                +00.000000
              </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.0
              </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-->
              5 meters
            </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-->
              5 meters
            </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
        </horizdn>
        <ellips>
          <!--Enter identification given to established representations of the Earth's shape.

Domain: "Clarke 1866" "Geodetic Reference System 80" free text-->
          Geodetic Reference System 80
        </ellips>
        <semiaxis>
          <!--Enter radius of the equatorial axis of the ellipsoid.

Domain: Semi-major Axis > 0.0-->
          6,378,137
        </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.2572221010
        </denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altdatum>
          <!--Enter the identification given to the surface taken as the surface of reference from which altitudes are measured.

Domain: "National Geodetic Vertical Datum of 1929" "North American Vertical
Datum of 1988" free text-->
          North American vertical Datum of 1988
        </altdatum>
        <altres>
          <!--Enter the minimum distance possible between two adjacent altitude values, expressed in Altitude Distance Units of measure.

Domain: Altitude Resolution > 0.0-->
          0.15
        </altres>
        <altunits>
          <!--Enter units in which altitudes are recorded.

Domain: "meters" "feet" free text-->
          Meters
        </altunits>
        <altenc>
          <!--Enter the means used to encode the altitudes.

Domain: "Explicit elevation coordinate included with horizontal coordinates"
"Implicit coordinate" "Attribute values"-->
          Explicit elevation
        </altenc>
      </altsys>
    </vertdef>
  </spref>
  <metainfo>
    <metd>
      <!--Enter the date that the metadata were created or last updated. Format YYYYMMDD

Domain: free date-->
      20040315
    </metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>
            <!--Enter the name of the organization to which the contact type applies.

Domain: free text-->
            EarthData International of Maryland, LLC
          </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-->
            7320 Executive Way
          </address>
          <city>
            <!--Enter name of the city where the contractor is located.-->
            Frederick
          </city>
          <state>
            <!--Enter the name of the State in which the contractor is located.-->
            MD
          </state>
          <postal>
            <!--Enter the zip code for the address above.-->
            21704
          </postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>
          <!--Enter the telephone number for the POC for this dataset.-->
          301-948-8550
        </cntvoice>
        <Facsimile>
          <!--Enter the Facsimile number if one is available.-->
          301-963-2064
        </Facsimile>
        <cntemail>
          <!--Enter the e-mail address for the contact group or persons.-->
          metadata@earthdata.com
        </cntemail>
      </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>

