<?xml version="1.0" encoding="UTF-8"?>
<inport-metadata xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 version="1.11"
                 source="https://www.fisheries.noaa.gov">
   <item-identification>
      <catalog-item-id>72702</catalog-item-id>
      <title>2014 ILHMP Lidar: Madison County, IL</title>
      <short-name>il2014_madison_m10124_metadata</short-name>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49401</parent-catalog-item-id>
      <parent-title>Lidar - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <creation-date>2014</creation-date>
      <publication-date>2014-06-27</publication-date>
      <abstract>This dataset is LiDAR point cloud data and derivative models of Madison County, Illinois.  Madison County is approximately 904 square miles in south western Illinois bordering the Mississippi River.  Data was collected at a nominal pulse spacing (NPS) of 0.7 meter.  

Data acquisition, processing and assessment is compliant with procedures and methods stated in U.S. Geological Survey National Geospatial Program LiDAR Base Specification Version 1.0 and Federal Emergency Management Agency Procedure Memorandum 61.

This dataset consists of LiDAR LAS swath files and tiled LAS files. Tiled LAS files contain LiDAR point information which has been calibrated, controlled, and classified. Tiled LAS and derived data models are named according to the coordinates at the south west corner of the tile.
Quantum Spatial Project No: 1140309

This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.

</abstract>
      <purpose>LiDAR data collection is used to produce high accuracy surface models of Madison County, Illinois in accordance with project requirements.  

The LiDAR point cloud data is used to create surface models as requested; classified LiDAR LAS files, Hydro-flattened bare-earth Digital Elevation Models (DEM), shapefiles of breaklines representative of surface hydro features and a ESRI geodatabase of all deliverables.</purpose>
      <supplemental-information>None.
            
   The following are the USGS lidar fields in JSON:
              {
                

    "ldrinfo" : {
              

    "ldrspec" : "USGS NGP Base Specification v1",

    "ldrsens" : "Leica ALS70 Serial Number 7220",

    "ldrmaxnr" : "4returns per pulse",

    "ldrnps" : "0.67 meters",

    "ldrdens" : "2.21 points per meter squared",

    "ldrfltht" : "1970 - 2100 meters",

    "ldrfltsp" : "150 knots",

    "ldrscana" : "40.0 degrees",

    "ldrscanr" : "39.1 Hz",

    "ldrpulsr" : "261000 Hz",

    "ldrpulsd" : "4 nanoseconds",

    "ldrpulsw" : "0.48 meters, 1/e^2",

    "ldrwavel" : "1064 nanometers",

    "ldrmpia" : "1 [enabled]",

    "ldrbmdiv" : "0.15 milliradians",

    "ldrswatw" : "1528.67 meters",

    "ldrswato" : "15.24%",

    "ldrcrs" : "NAD_1983_2011_StatePlane_Illinois_West_FIPS_1202_Ft_US",

    "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12A"
  },

    "ldraccur" : {
              

    "ldrchacc" : " 0.33 feet",

    "rawfva" : "0.517 feet",

    "clscva" : "0.587 feet",

    "clssvas" : {
              

    "svalctyp" : "Open Terrain survey points compared to DEM. 95th percentile",

    "svavalue" : "0.587 feet"
  },

    "clssvas" : {
              

    "svalctyp" : "Urban survey points compared to DEM. 95th percentile",

    "svavalue" : "0.276 feet"
  },

    "clssvas" : {
              

    "svalctyp" : "Tall Grass survey points compared to DEM. 95th percentile",

    "svavalue" : "0.487 feet"
  },

    "clssvas" : {
              

    "svalctyp" : "Brush survey points compared to DEM. 95th percentile",

    "svavalue" : "0.696 feet"
  },

    "clssvas" : {
              

    "svalctyp" : "Forest survey points compared to DEM. 95th percentile",

    "svavalue" : "0.321 feet"
  }
  },

    "lasinfo" : {
              

    "lasver" : "1.2",

    "lasprf" : "1",

    "laswheld" : "Withheld (ignore) points were identified in these files using the standard LAS Withheld bit
                    ",

    "lasolap" : "There are not Overlap class points in this data.
                    ",

    "lasintr" : "8-bit",

    "lasclass" : {
              

    "clascode" : "1",

    "clasitem" : "Undetermined/Unclassified"
  },

    "lasclass" : {
              

    "clascode" : "2",

    "clasitem" : "Bare-earth"
  },

    "lasclass" : {
              

    "clascode" : "3",

    "clasitem" : "Low Vegetation"
  },

    "lasclass" : {
              

    "clascode" : "4",

    "clasitem" : "Medium Vegetation"
  },

    "lasclass" : {
              

    "clascode" : "5",

    "clasitem" : "High Vegetation"
  },

    "lasclass" : {
              

    "clascode" : "6",

    "clasitem" : "Building"
  },

    "lasclass" : {
              

    "clascode" : "7",

    "clasitem" : "All noise"
  },

    "lasclass" : {
              

    "clascode" : "8",

    "clasitem" : "Model Key"
  },

    "lasclass" : {
              

    "clascode" : "9",

    "clasitem" : "Water"
  },

    "lasclass" : {
              

    "clascode" : "10",

    "clasitem" : "Ignored ground"
  }
  }}</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="74ed1690-968e-444c-8a31-7b8344a2aad3">EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="753f915c-70d4-49e1-9bd5-83e75f461e30">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="06b1e163-667a-4d13-b638-5273e7a65dad">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; ILLINOIS</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="90761f8d-6abe-499c-b711-acec394daa59">VERTICAL LOCATION &gt; LAND SURFACE</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Instrument</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Instrument Keywords</thesaurus>
         <keyword identifier="7166c458-f935-4bd9-a322-d92830cf0c33">LIDAR &gt; Light Detection and Ranging</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Platform</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Platform Keywords</thesaurus>
         <keyword identifier="8b7834c1-2c66-414e-a655-2298e7dcc479">Airplane &gt; Airplane</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office for Coastal Management</organization>
      <city>Charleston</city>
      <state-province>SC</state-province>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <data-set-type>Elevation</data-set-type>
      <maintenance-frequency>None Planned</maintenance-frequency>
      <data-presentation-form>Model (digital)</data-presentation-form>
      <distribution-liability>In no event shall the creators, custodians, or distributors of these data be liable for any damages arising out of its use, or from the inability of the customer to use these data for their intended application.
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners.
        
</distribution-liability>
      <data-set-credit>Quantum Spatial, Inc., ILHMP (Illinois Height Modernization Program)</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1335360" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2024</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1335359" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2024</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1335381" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2014</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>U.S. Geological Survey</contact-name>
         <contact-address>12201 Sunrise Valley Drive </contact-address>
         <contact-address-city>Reston</contact-address-city>
         <contact-address-state>VA</contact-address-state>
         <contact-address-zip>20191</contact-address-zip>
         <contact-address-country>USA</contact-address-country>
         <contact-url>https://usgs.gov</contact-url>
         <contact-url-name>USGS Home</contact-url-name>
         <contact-url-description>Home page for USGS</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1335361" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2024</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1335362" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2024</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
   </support-roles>
   <extents>
      <currentness-reference>Ground Condition</currentness-reference>
      <extent cc-id="1335363">
         <geographic-areas>
            <geographic-area cc-id="1335382">
               <west-bound>-90.3</west-bound>
               <east-bound>-89.56</east-bound>
               <north-bound>39.02</north-bound>
               <south-bound>38.62</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1335364">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2014-03-23</start-date-time>
            </time-frame>
            <time-frame cc-id="1335383">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2014-03-26</start-date-time>
            </time-frame>
            <time-frame cc-id="1335384">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2014-03-30</start-date-time>
            </time-frame>
            <time-frame cc-id="1335385">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2014-03-31</start-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <grid>No</grid>
            <vector>Yes</vector>
            <text-table>No</text-table>
            <tin>No</tin>
            <stereo-model>No</stereo-model>
            <video>No</video>
         </representations-used>
         <vector-representations>
            <vector-representation cc-id="1335354">
               <point-object>
                  <present>Yes</present>
                  <count>12645182002</count>
               </point-object>
            </vector-representation>
         </vector-representations>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Projected</crs-type>
               <epsg-code>EPSG:3857</epsg-code>
               <epsg-name>WGS 84 / Pseudo-Mercator</epsg-name>
               <datum-name>World Geodetic System 1984</datum-name>
               <ellipsoid>WGS 84</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257223563</flattening-ratio>
               <base-crs-name>WGS 84</base-crs-name>
               <projection-name>Popular Visualisation Pseudo-Mercator</projection-name>
               <conversion-method>Popular Visualisation Pseudo Mercator</conversion-method>
               <parameters>
                  <parameter>
                     <parameter-name>Latitude of natural origin</parameter-name>
                     <parameter-value>0° 0' 0" N</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Longitude of natural origin</parameter-name>
                     <parameter-value>0° 0' 0" E</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>False easting</parameter-name>
                     <parameter-value>0</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
                  <parameter>
                     <parameter-name>False northing</parameter-name>
                     <parameter-value>0</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
               </parameters>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Easting</name>
                     <abbreviation>X</abbreviation>
                     <units>metre</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Northing</name>
                     <abbreviation>Y</abbreviation>
                     <units>metre</units>
                     <orientation>north</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Vertical</crs-type>
               <epsg-code>EPSG:5703</epsg-code>
               <epsg-name>NAVD88 height</epsg-name>
               <datum-name>North American Vertical Datum 1988</datum-name>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Gravity-related height</name>
                     <abbreviation>H</abbreviation>
                     <units>metre</units>
                     <orientation>up</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <data-license-type>Custom</data-license-type>
      <security-class>Unclassified</security-class>
      <data-access-procedure>Data is available online for bulk and custom downloads.</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <data-use-constraints>Users should be aware that temporal changes may have occurred since this data set was collected and 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.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="1335365">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10124/details/10124</download-url>
         <distributor cc-id="1335359">
            <from-date>2024</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options.</description>
         <distribution-format>Not Applicable</distribution-format>
         <compression>Zip</compression>
      </distribution>
      <distribution cc-id="1335366">
         <download-url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/IL_5_County_2014_15/IL_MadisonCo_2014/LAZ/</download-url>
         <distributor cc-id="1335381">
            <from-date>2014</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>U.S. Geological Survey</contact-name>
         </distributor>
         <file-name>Bulk Download</file-name>
         <description>Bulk download of data files in LAZ format, IL State Plane West NAD83, US survey feet coordinates and in NAVD88 (Geoid12A) elevations in feet.</description>
         <distribution-format>LAS/LAZ - LASer</distribution-format>
         <compression>LAZ</compression>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="1335357">
         <url>https://coast.noaa.gov/dataviewer/</url>
         <name>NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>HTML</file-resource-format>
         <description>The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.</description>
      </url>
      <url cc-id="1335391">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/IL_5_County_2014_15/IL_MadisonCo_2014/</url>
         <name>USGS Additional Info</name>
         <url-type>Online Resource</url-type>
         <description>Link to the reports, breaklines, metadata, and spatial metadata.</description>
      </url>
      <url cc-id="1335390">
         <url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/IL_5_County_2014_15/IL_MadisonCo_2014/reports/2014_Madison_County_2ppsm_LiDAR_Report.pdf</url>
         <name>Lidar Report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the lidar report.</description>
      </url>
      <url cc-id="1335388">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_IL_MadisonCo_2014_LAS_2016/ept.json</url>
         <name>USGS Entwine Point Tile (EPT)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1335389">
         <url>https://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_IL_MadisonCo_2014_LAS_2016%22</url>
         <name>USGS 3D View</name>
         <url-type>Online Resource</url-type>
         <description>Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer.</description>
      </url>
   </urls>
   <technical-environment>
      <description>ALS Post Processor 2.75 Build#25; GeoCue Version 13.1.45.1; Windows 7 Operating System</description>
   </technical-environment>
   <data-quality>
      <vertical-positional-accuracy>Vertical accuracy assessment is conducted by comparing ground survey check point z values to processed LiDAR data z values by horizontal proximity. Differences in z values are calculated to express an RMSEz value. As documented in the Task Order, to meet USGS QL2 requirements, collected data was to achieve an RMSE of 9.25cm (0.30 ft) in the open terrain land cover category based on a Triangulated Integrated Network (TIN) of the LiDAR points and from values of the Digital Elevation Models (DEM) derived from LiDAR data. Quantum Spatial achieved a fundamental vertical accuracy (FVA) of 15.85 cm at a 95% confidence level with an RMSE of 7.93 cm utilizing twenty (20) open terrain ground survey check points .</vertical-positional-accuracy>
      <completeness-report>These data files include all data points collected.
No points have been removed or excluded.
The raw point cloud is of good quality and data passes Fundamental Vertical Accuracy specifications.</completeness-report>
      <conceptual-consistency>Data cover the entire area specified for this project.</conceptual-consistency>
   </data-quality>
   <data-management>
      <resources-identified>Yes</resources-identified>
      <resources-budget-percentage>Unknown</resources-budget-percentage>
      <data-access-directive-compliant>Yes</data-access-directive-compliant>
      <archive-location>NCEI-NC</archive-location>
      <data-protection-plan>Data is backed up to cloud storage.</data-protection-plan>
   </data-management>
   <lineage>
      <lineage-statement>The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tile (EPT) hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.</lineage-statement>
      <lineage-sources>
         <lineage-source cc-id="1335392">
            <citation-title>USGS AWS Entwine Point Tile (EPT)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_IL_MadisonCo_2014_LAS_2016/ept.json</citation-url>
            <citation-url-name>Entwine Point Tile (EPT)</citation-url-name>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1335346">
            <sequence-number>1</sequence-number>
            <description>Ground based survey points are collected to be compared as check points with airborne data points. Measurements are recorded by Quantum Spatial for use in establishment of the LiDAR point set to ground elevations (indexing). Additional ground survey points are made in representative ground cover categories to provide for vertical accuracy assessment of LiDAR data or derivative models.</description>
            <process-date-time>2014-06-22T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1335347">
            <sequence-number>2</sequence-number>
            <description>Airborne LiDAR collection survey is conducted using fixed wing aircraft equipped with a LiDAR scanning system following specifications of the flight plan.  Acquisition flights are planned to assure full coverage of the project area in consideration of local surface terrains. Flight plan is accessed by the aircraft navigation system to achieve predetermined flight specifications. The LiDAR sensor is calibrated prior to each mission. GPS and IMU data are collected during LiDAR acquisition to aid in LiDAR swath calibration.</description>
            <process-date-time>2014-04-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1335348">
            <sequence-number>3</sequence-number>
            <description>Airborne GPS and IMU data are merged to develop a Single Best Estimate Trajectory for each swath. LiDAR data are calibrated using previous best parameters for this instrument and aircraft. Relative calibration is evaluated using plane-matching analysis and parameter corrections are derived. This is repeated iteratively until residual errors between overlapping swaths, across all project lifts, is reduced to acceptable levels. Data are block adjusted to surveyed control points. 

       Raw FVA is checked using surveyed ground checkpoints. Swath overage points are identified and tagged within each swath. Overage points may be classed as Overlap (12) or classed to Non-ground (1).</description>
            <process-date-time>2014-05-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1335349">
            <sequence-number>4</sequence-number>
            <description>Points in the calibrated swaths are classified using analysis routines and proprietary software. The routines analyze information on all points to establish appropriate Class designations. 

       Classified LiDAR is inspected on a per tile basis for local classification, manual editing, and peer-based QC checks. The bare earth surface is manually reviewed to ensure correct classification of Class 2 (Ground) points.  After the bare-earth surface is finalized, it is used to guide hydro-breaklines generation through heads-up digitization.

				All data was manually reviewed and any remaining artifacts removed using controls and tools in TerraScan and TerraModeler.  Global Mapper is used as a final check of the bare earth dataset.  GeoCue  creates the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth.

				All classification tags are stored in the original swath files.

				Classifications follow ASPRS guidelines: Non-ground (Class 1), Ground (Class 2), Low Vegetation (Class 3). Medium Vegetation (Class 4), High Vegetation (Class 5), Buildings (Class 6),Noise/Low Points (Class 7), Model Key Point (Class 8) Water (Class 9), Ignored Ground/Breakline proximity (Class 10)

				After completion of classification and final QC approval, the FVA, SVAs, and CVA for the project are calculated. Vertical accuracy is determined by comparison of elevation of the ground survey check points to elevations of DEMs derived from the LiDAR Ground points. Differences are calculated to establish a RSME, FVA, CVA and SVA.</description>
            <process-date-time>2014-06-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1335350">
            <sequence-number>5</sequence-number>
            <description>Ground (class 2) LiDAR is used to create a bare earth surface model.  The surface model is then used to heads-up digitize 2D breaklines of rivers  of specific width and lakes of specific size. Breaklines delineate the margin where surface water and ground meet.
				Elevation values are assigned to lakes in accordance with ground data where the water and ground surfaces meet. Elevation values are assigned to rivers of adequate width and are created to depict the flow of the drainage; following the change in ground elevation at the edge of the drainage.
				All ground (Class 2) LiDAR data inside of the collected inland breaklines are classified to water (Class 9) using TerraScan macro functionality.  A buffer of 1 meter is  maintained along breaklines of each hydro flattened feature.  Points within this one meter buffer are classed  from ground (Class 2) to Ignored Ground (Class 10).

				The breakline files are then translated to ESRI Shapefile format using ESRI conversion tools.</description>
            <process-date-time>2014-06-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1335351">
            <sequence-number>6</sequence-number>
            <description>Ground (Class 2) points in conjunction with the hydro breaklines are used to generate DEM files in ASCII format on a per tile basis with hydro Breaklines in place to delineate surface water and with neighboring tile data available to minimize seams between tiles. The DEM are converted to ESRI Grid format. Resulting DEM are reviewed in ArcMap for adherence, completeness and any anomalies or inconsistencies.</description>
            <process-date-time>2014-06-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1335352">
            <sequence-number>7</sequence-number>
            <description>On a per tile basis, data files and Triangulated Integrated Network (TIN) files are generated by processing finalized Ground (class 2) LiDAR points with hydro breaklines delineating surface water through a Geopak macro. Subsequent files are reviewed for adherence and completeness to the data and tile layout used during the creation process.</description>
            <process-date-time>2014-06-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1335393">
            <sequence-number>8</sequence-number>
            <description>Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and the vertical units were converted to meters (NAVD88 GEOID12A).</description>
            <process-contact>
               <contact-type>Organization</contact-type>
               <contact-name>U.S. Geological Survey</contact-name>
               <contact-address>12201 Sunrise Valley Drive </contact-address>
               <contact-address-city>Reston</contact-address-city>
               <contact-address-state>VA</contact-address-state>
               <contact-address-zip>20191</contact-address-zip>
               <contact-address-country>USA</contact-address-country>
               <contact-url>https://usgs.gov</contact-url>
               <contact-url-name>USGS Home</contact-url-name>
               <contact-url-description>Home page for USGS</contact-url-description>
               <contact-url-function>Online Resource</contact-url-function>
            </process-contact>
         </lineage-process-step>
         <lineage-process-step cc-id="1335394">
            <sequence-number>9</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) that was ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container.

This is the AWS URL being accessed:
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_IL_MadisonCo_2014_LAS_2016/ept.json</description>
            <process-date-time>2024-05-30T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Organization</contact-type>
               <contact-name>Office for Coastal Management</contact-name>
               <contact-noaa-acronym>OCM</contact-noaa-acronym>
               <contact-ror>https://ror.org/05v14bq57</contact-ror>
               <contact-address>2234 South Hobson Avenue</contact-address>
               <contact-address-city>Charleston</contact-address-city>
               <contact-address-state>SC</contact-address-state>
               <contact-address-zip>29405-2413</contact-address-zip>
               <contact-url>https://www.coast.noaa.gov/</contact-url>
            </process-contact>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:72702</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2024-05-30T20:31:11</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2026-03-04T19:17:17</metadata-record-last-modified>
      <record-published>2024-05-30</record-published>
      <owner-organization>OCM Partners</owner-organization>
      <owner-organization-acronym>OCMP</owner-organization-acronym>
      <owner-organization-address/>
      <owner-organization-address-city/>
      <owner-organization-address-state/>
      <owner-organization-address-zip/>
      <owner-organization-address-country/>
      <owner-organization-phone/>
      <owner-organization-url/>
      <owner-organization-business-hours/>
      <owner-organization-group-id>1002</owner-organization-group-id>
      <publication-status>Public</publication-status>
      <limited-metadata-available>No</limited-metadata-available>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2024-05-30</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2025-05-30</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
