<?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>
        <!-- Citation Information - the recommended reference to be used for the data set. -->
        <origin>Merrick-Surdex Joint Venture, LLP</origin>
        <!-- Originator - the name of an organization or individual that developed the data set. Type: text. Domain: "Unknown" free text. -->
        <pubdate>20241029</pubdate>
        <!-- Publication Date - the date when the data set is published or otherwise made available for release. Type: date. Domain: "Unknown" "Unpublished material" free date-->
        <title>Iroquois County, Illinois. 2024</title>
        <!-- Title - the name by which the data set is known. Type: text. Domain: free text. -->
        <geoform>Lidar Point Cloud</geoform>
        <!-- Geospatial Data Presentation Form. Type: text. Domain: "Lidar point cloud" free text. -->
      </citeinfo>
    </citation>
    <descript>
      <abstract>LIDAR-derived binary (.las) files containing classified points of all returns. We have eleven (11) classifications Unclassified (Class 1), Ground (Class 2), Low Vegetation (Class 3), Medium Vegetation (Class 4), High Vegetation (Class 5), Buildings (Class 6), Low Noise(Class 7), Water (Class 9), Bridge Decks(Class 17), High Noise (Class18) and Ignored Ground (Class 20). These files adhere to USGS-NGP Lidar Base Specification 2023 rev. A Quality Level 1 (QL1) standards, eight points or greater per square meter. These files are delivered in tile format (2000x2000ft).</abstract>
      <purpose>This project will support the National Resources Conservation Service (NRCS) high resolution elevation enterprise program,
the Illinois State Geological Survey's Height Modernization Program, and the 3DEP mission.

The Defined Project Area (DPA) is represented by the USGS-provided Esri shapefile IL_10CountyNRCS_D23_DPA, and
encompasses approximately 7,454 square miles, and includes all or portions of Pike, Scott, Bureau, Logan, Christian,
Madison, Livingston, Ford, Kankakee, and Iroquois in the state of Illinois. Said DPA is made up of six (6) non-contiguous
individual boundaries or Areas of Interest (AOIs).

The Block1 area is approximately 3350 square miles and contains 23742 tiles (2000ft by 2000ft).</purpose>
      <supplinf>USGS Task Order 140G0223F0169-IL_10CountyNRCS_D23

Synthetic Points: Optech's Galaxy T2000 raw lidar post-processing software LMS uses a method to fill small voids with synthetic points when the PulseTRAK algorithm drops a point recording. This can happen between the transition of PIA (pulse-in-air) zones.

Time periods have been converted from UTC to Central Standard Time for the metadata.

mshr and ssi tiles are not present for two tiles (due to being sliver tiles that are too small for the center pixel to fall inside the DPA for 2ft pixel size). The tiles are: 8570_1487 and 9150_1437</supplinf>
      <lidar>
        <ldrinfo>
          <!-- Lidar Information - contains metadata about the sensor and collection conditions. When multiple instruments are used (e.g. two different instruments in a single plane), please use multiple <ldrinfo> tags to describe each individual instrument. If only one instrument was used, please delete this section. -->
          <ldrspec>USGS-NGP Lidar Base Specification 2023, Revision A</ldrspec>
          <!-- Lidar Base Specification applicable to the point cloud. -->
          <ldrsens>Optech Galaxy T2000 Airborne Laser Terrain Mappers (ALTM) - SNs: 5060411, 5060475, 5060495</ldrsens>
          <!-- Lidar Sensor make and model. -->
          <ldrmaxnr>8</ldrmaxnr>
          <!-- Lidar Maximum Number of Returns per pulse. -->
          <ldrnps>0.35</ldrnps>
          <!-- Lidar Nominal Pulse Spacing, in meters. -->
          <ldrdens>8</ldrdens>
          <!-- Lidar Nominal Pulse Density, in points per square meter. -->
          <ldranps>0.35</ldranps>
          <!-- Lidar Aggregate Nominal Pulse Spacing, in meters. -->
          <ldradens>8</ldradens>
          <!-- Lidar Aggregate Nominal Pulse Density, in points per square meter. -->
          <ldrfltht>1935</ldrfltht>
          <!-- Lidar Flight Height for the collection, in meters. -->
          <ldrfltsp>170</ldrfltsp>
          <!-- Lidar Nominal Flight Speed for the collection, in knots. -->
          <ldrscana>30</ldrscana>
          <!-- Lidar Sensor Scan Angle, total, in degrees. -->
          <ldrscanr>130</ldrscanr>
          <!-- Lidar Scan Frequency of the scanner, in hertz. -->
          <ldrpulsr>1700</ldrpulsr>
          <!-- Lidar Pulse Rate of the scanner, in kilohertz. -->
          <ldrpulsd>3.5</ldrpulsd>
          <!-- Lidar Pulse Duration of the scanner, in nanoseconds. -->
          <ldrpulsw>0.89</ldrpulsw>
          <!-- Lidar Pulse Width of the scanner, in meters. -->
          <ldrwavel>1064</ldrwavel>
          <!-- Lidar Central Wavelength of the sensor laser, in nanometers. -->
          <ldrmpia>1</ldrmpia>
          <!-- Lidar Multiple Pulses In Air, 0 = No; 1 = Yes -->
          <ldrbmdiv>0.23</ldrbmdiv>
          <!-- Lidar Beam Divergence, in Milliradians. -->
          <ldrswatw>1037</ldrswatw>
          <!-- Lidar Swath Width on the ground, in meters. -->
          <ldrswato>20</ldrswato>
          <!-- Lidar Nominal Swath Overlap, as a percentage. -->
          <ldrgeoid>National Geodetic Survey (NGS) Geoid18</ldrgeoid>
          <!-- Geoid used for vertical reference. -->
        </ldrinfo>
        <ldraccur>
          <!-- Lidar Accuracy. Non-vegetated vertical accuracy values for the swath. ALL VALUES ARE REPORTED IN METERS. -->
          <ldrchacc>0</ldrchacc>
          <!-- Lidar Calculated Horizontal Accuracy of the point cloud data. -->
          <rawnva>0.0</rawnva>
          <!-- Raw Nonvegetated Vertical Accuracy of the raw point cloud data. -->
          <rawnvan>0</rawnvan>
          <!-- Raw Nonvegetated Vertical Accuracy Number of checkpoints used to calculate the reported nonvegetated vertical accuracy of the raw point cloud data. -->
          <!-- Classified Non-vegetated Vertical Accuracy. The calculated nonvegetated vertical accuracy of the classified point cloud data (required if available). Type: decimal number. -->
          <!-- Classified Non-vegetated Vertical Accuracy Number of checkpoints. The number of check points used to calculate the reported nonvegetated vertical accuracy of the classified point cloud data. Type: real number. -->
          <!-- Classified Vegetated Vertical Accuracy. The calculated vegetated vertical accuracy of the classified point cloud data (required if available). Type: decimal number. -->
          <!-- Classified Vegetated Vertical Accuracy Number of checkpoints. The number of check points used to calculate the vegetated vertical accuracy of the classified point cloud data. Type: real number. -->
        </ldraccur>
        <lasinfo>
          <!-- LAS Information. Type: compound. -->
          <lasver>1.4</lasver>
          <!-- LAS Version -->
          <lasprf>6</lasprf>
          <!-- LAS Point Record Format. -->
          <laswheld>Withheld (ignore) points were identified in these files using the standard LAS withheld bit.</laswheld>
          <!-- Describe how withheld points are identified. -->
          <lasolap>Swath "overage" points were not identified in these files using the standard LAS overlap bit.</lasolap>
          <!-- Describe how overage points are identified. -->
          <lasintr>12</lasintr>
          <!-- Specify the native radiometric resolution of intensity values, in Bits. -->
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>1</clascode>
            <!-- Classification Code -->
            <clasitem>Unclassified</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>2</clascode>
            <!-- Classification Code -->
            <clasitem>Ground</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>3</clascode>
            <!-- Classification Code -->
            <clasitem>Low Vegetation</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>4</clascode>
            <!-- Classification Code -->
            <clasitem>Medium Vegetation</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>5</clascode>
            <!-- Classification Code -->
            <clasitem>High Vegetation</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>6</clascode>
            <!-- Classification Code -->
            <clasitem>Buildings</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>7</clascode>
            <!-- Classification Code -->
            <clasitem>Low Noise</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>9</clascode>
            <!-- Classification Code -->
            <clasitem>Water</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>17</clascode>
            <!-- Classification Code -->
            <clasitem>Bridge</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>18</clascode>
            <!-- Classification Code -->
            <clasitem>High Noise</clasitem>
            <!-- Classification Item -->
          </lasclass>
          <lasclass>
            <!-- LAS Classification. Type: compound. -->
            <clascode>20</clascode>
            <!-- Classification Code -->
            <clasitem>Ignored Ground</clasitem>
            <!-- Classification Item -->
          </lasclass>
        </lasinfo>
      </lidar>
    </descript>
    <timeperd>
      <timeinfo>
        <!-- -->
        <rngdates>
          <!-- Range of Dates/Times. Type: compound. -->
          <begdate>20231224</begdate>
          <!-- Beginning Date - the first year (and optionally month, or month and day) of the collection. Type: date. Domain: "Unknown" free date. -->
          <enddate>20240329</enddate>
          <!-- Ending Date - the last year (and optionally month, or month and day) for the collection. Type: date. Domain: "Unknown" free date. -->
        </rngdates>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>Unknown</update>
    </status>
    <spdom>
      <!-- Spatial Domain - the geographic areal domain of the data set. Type: compound. -->
      <bounding>
        <!-- Bounding Coordinates - the limits of coverage of a data set expressed by latitude and longitude values in the order western-most, eastern-most, northern-most, and southern-most. Type: compound. -->
        <westbc>-88.9327237564508</westbc>
        <!-- West Bounding Coordinate - western-most coordinate of the limit of coverage expressed in longitude. Type: real. Domain: -180.0 <= West Bounding Coordinate < 180.0 -->
        <eastbc>-87.524401808819</eastbc>
        <!-- East Bounding Coordinate - eastern-most coordinate of the limit of coverage expressed in longitude. Type: real. Domain: -180.0 <= East Bounding Coordinate <= 180.0 -->
        <northbc>41.2989849844873</northbc>
        <!-- North Bounding Coordinate - northern-most coordinate of the limit of coverage expressed in latitude. Type:real. Domain: -90.0 <= North Bounding Coordinate <= 90.0 -->
        <southbc>40.3972013855606</southbc>
        <!-- South Bounding Coordinate - southern-most coordinate of the limit of coverage expressed in latitude. Type: real. Domain: -90.0 <= South Bounding Coordinate <= 90.0 -->
      </bounding>
      <lboundng>
        <leftbc>818512.219419882</leftbc>
        <!-- Left (western-most) Bounding Coordinate for coverage of the dataset expressed in the Coordinate Reference System in which the data are delivered. -->
        <rightbc>1209046.5423523</rightbc>
        <!-- Right (eastern-most) Bounding Coordinate for coverage of the dataset expressed in the Coordinate Reference System in which the data are delivered. -->
        <topbc>1688182.6102178</topbc>
        <!-- Top (northern-most) Bounding Coordinate for coverage of the dataset expressed in the Coordinate Reference System in which the data are delivered. -->
        <bottombc>1358613.33956765</bottombc>
        <!-- Bottom (southern-most) Bounding Coordinate for coverage of the dataset expressed in the Coordinate Reference System in which the data are delivered. -->
      </lboundng>
    </spdom>
    <keywords>
      <theme>
        <!-- Theme - subjects covered by the data set. Type: compound. -->
        <themekt>None</themekt>
        <!-- Theme Keyword Thesaurus. Type: text. Domain: "None" free text. -->
        <themekey>Elevation Data</themekey>
        <themekey>Lidar</themekey>
        <!-- Theme Keyword - common-use word or phrase used to describe the subject of the data set. Type: text. Domain: free text. -->
        <themekey>DSM</themekey>
      </theme>
      <place>
        <!-- Place - geographic locations characterized by the data set. Type: compound. -->
        <placekt>None</placekt>
        <!-- Place Keyword Thesaurus. Type: text. Domain: "None" free text. -->
        <placekey>Illinois</placekey>
        <!-- Place Keyword - the geographic name of a location(s) covered by a data set. Type: text. Domain: free text. -->
      </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 and NRCS would be appreciated for products derived from these data.</useconst>
    <native>Optech LMS 4.x, MARS 2023.x, Windows 10</native>
  </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>
      <horizpa>
        <horizpar>The lidar data set was produced to meet ASPRS "Positional Accuracy Standards for Digital Geospatial Data"
(2014) for a 20 (cm) RMSEx / RMSEy Horizontal Accuracy Class which equates to Positional Horizontal
Accuracy = +/- 43 cm at a 95% confidence level.</horizpar>
      </horizpa>
      <vertacc>
        <!-- Vertical Positional Accuracy - an estimate of accuracy of the vertical positions in the data set. Type: compound. -->
        <vertaccr>This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.</vertaccr>
        <!-- Vertical Positional Accuracy Report - an explanation of the accuracy of the vertical coordinate measurements and a description of the tests used. Type: text. Domain: free text. -->
      </vertacc>
    </posacc>
    <lineage>
      <procstep>
        <!-- Process Step - information about a single processing step. Type: compound.  Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text Process Date - the date when the processing step was completed. Date must be formatted YYYYMMDD. Type: text. Domain: "Unknown" "Not complete" free date. -->
        <procdesc>Lidar data was collected using Optech Galaxy T2000 sensor.  The raw data was verified in MARS software for complete coverage of the project area, and boresighted to align the flightlines.  Raw data files were parsed into manageable client-specific tiles.  These tiles were then processed through automated filtering that separates the data into different classification groups: unclassified points, ground points, low noise, water, bridge decks,  high noise and ignore ground.  The data was next taken into MARS to reclassify the erroneous points that may remain in the lidar point cloud after auto filter. Eight points per square meter (QL1).</procdesc>
        <procdate>20241029</procdate>
      </procstep>
      <procstep>
        <!-- Process Step - information about a single processing step. Type: compound.  Process Description - an explanation of the the processing step and parameters used. Include Flight, Imagery development, Analysis. Type: text. Domain: free text Process Date - the date when the processing step was completed. Date must be formatted YYYYMMDD. Type: text. Domain: "Unknown" "Not complete" free date. -->
        <procdesc>LiDAR swath data was measured to have an aggregate of 0.199 meter nominal pulse spacing and 25.317 pulses per meter. The method used was counting first return points within the each swath then dividing by the area of the extent of the corresponding swath to get density.  NPS was mathematically derived from this density number.  This was performed on each swath then averaged to generate the two numbers above.  This USGS method does not consider swath sidelap in these calculations.</procdesc>
        <procdate>20241029</procdate>
      </procstep>
      <procstep>
        <!-- Process Step - information about a single processing step. Type: compound. -->
        <procdesc>The Maximum Surface Height Rasters (MSHR) are created from all lidar return points minus witheld points to a two-foot (2.0ft) cell size, 32-bit floating point raster images using MARS software. The MSHR are exported to the project tiling scheme (2000x2000ft) Projection information is applied that reflects the project Coordinate Reference System (CRS).</procdesc>
        <!-- Process Description - description of the method and parameters used to generate maximum surface height rasters from the classified point cloud. Type: text. Domain: free text-->
        <procdate>20241029</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD Type: text. Domain: "Unknown" "Not complete" free date. -->
      </procstep>
      <procstep>
        <!-- Process Step - information about a single processing step. Type: compound. -->
        <procdesc>Swath Separation Imagery was produced for the entire project area. Swath separation images use color-coding to illustrate differences in elevation (z) values where swaths overlap. The color-coded images are semi-transparent and overlay the lidar intensity image. They are ancillary data used as visual aids to more easily identify regions within point cloud datasets that may have suspect interswath alignment or other geometric issues. Imagery was created using last returns with all classification and bit flags, except for noise and withheld bit flag are included. Images are derived from a TIN and have a 50% transparent RGB layer over lidar intensity. These files were produced as GeoTIFF tiles using a cell size of two-foot (2.0ft).</procdesc>
        <!-- Process Description - description of the method and parameters used to generate swath separation imagery from the classified point cloud. Type: text. Domain: free text-->
        <procdate>20241029</procdate>
        <!-- Process Date - the date when the processing step was completed. The field MUST be formatted YYYYMMDD Type: text. Domain: "Unknown" "Not complete" free date. -->
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Point</direct>
    <ptvctinf>
      <!-- Point and Vector Object Information - the types and numbers of vector or nongridded point spatial objects in the data set. Type: Compound. -->
      <sdtsterm>
        <!-- SDTS Terms Description - point and vector object information using the terminology and concepts from "Spatial Data Concepts," which is Chapter 2 of Part 1 in Department of Commerce, 1992, Spatial Data Transfer Standard (SDTS) (Federal Information Processing Standard 173): Washington, Department of Commerce, National Institute of Standards and Technology. (Note that this reference to the SDTS is used ONLY to provide a set of terminology for the point and vector objects.). Type: Compound. -->
        <sdtstype>Point</sdtstype>
        <!-- SDTS Point and Vector Object Type - name of point and vector spatial objects used to locate zero-, one-, and two-dimensional spatial locations in the data set. Domain: (The domain is from "Spatial Data Concepts," which is Chapter 2 of Part 1 in Department of Commerce, 1992, Spatial Data Transfer Standard (SDTS) (Federal Information Processing Standard 173): Washington, Department of Commerce, National Institute of Standards and Technology): "Point" "Entity point" "Label point" "Area point" "Node, planar graph" "Node, network" "String" "Link" "Complete chain" "Area chain" "Network chain, planar graph" "Network chain, nonplanar graph" "Circular arc, three point center" "Elliptical arc" "Uniform B-spline" "Piecewise Bezier" "Ring with mixed composition" "Ring composed of strings" "Ring composed of chains" "Ring composed of arcs" "G-polygon" "GT-polygon composed of rings" "GT-polygon composed of chains" "Universe polygon composed of rings" "Universe polygon composed of chains" "Void polygon composed of rings" "Void polygon composed of chains"-->
        <ptvctcnt>226,824,140,074</ptvctcnt>
        <!-- Point and Vector Object Count - the total number of the point or vector object type occurring in the data set. Type: integer. Domain: Point and Vector Object Count > 0 -->
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <mapproj>
          <mapprojn>NAD 1983 2011 StatePlane Illinois East FIPS 1201 Ft US</mapprojn>
          <transmer>
            <sfctrmer>0.999975</sfctrmer>
            <longcm>-88.33333333333333</longcm>
            <latprjo>36.66666666666666</latprjo>
            <feast>984250.0</feast>
            <fnorth>0.0</fnorth>
          </transmer>
        </mapproj>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.001</absres>
            <ordres>0.001</ordres>
          </coordrep>
          <plandu>foot_us</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>D NAD 1983 2011</horizdn>
        <ellips>GRS 1980</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altdatum>North American Vertical Datum of 1988 Geoid2018</altdatum>
        <altres>0.001</altres>
        <altunits>foot_us</altunits>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <metainfo>
    <metd>20241029</metd>
    <metc>
      <cntinfo>
        <!-- Contact Information - Identity of, and means to communicate with, person(s) and organization(s) associated with the data set.Type: compound. -->
        <cntorgp>
          <!-- Contact Organization Primary - the organization, and the member of the organization, associated with the data set. Type: compound. -->
          <cntorg>Merrick-Surdex Joint Venture, LLP</cntorg>
          <!-- Contact Organization - the name of the organization. Type: text. Domain: free text. -->
        </cntorgp>
        <cntaddr>
          <!-- Contact Address - the address for the organization or individual. Type: compound. -->
          <addrtype>mailing and physical address</addrtype>
          <!-- Address Type. Type: text. Domain: "mailing" "physical" "mailing and physical", free text. -->
          <address>5970 Greenwood Plaza Blvd</address>
          <!-- Address - an address line for the address. Type: text. Domain: free text. -->
          <city>Greenwood Village</city>
          <!-- City - the city of the address. Type: text. Domain: free text. -->
          <state>CO</state>
          <!-- State or Province - the state or province of the address. Type: text. Domain: free text. -->
          <postal>80111</postal>
          <!-- Postal Code - the ZIP or other postal code of the address. Type: text. Domain: free text. -->
          <country>USA</country>
          <!-- Country - the country of the address. Type: text. Domain: free text. -->
        </cntaddr>
        <cntvoice>303-353-3903</cntvoice>
        <!-- Contact Voice Telephone - the telephone number by which individuals can speak to the organization or individual. Type: text. Domain: free text. -->
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
  </metainfo>
</metadata>

