<?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>50058</catalog-item-id>
      <title>2006 USACE Topobathy Lidar: Lake Michigan (IN), Lake Erie (OH,PA), Lake Huron (MI)</title>
      <short-name>usace2006_gl_m40_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>
      <publication-date>2007-03-22</publication-date>
      <abstract>The U.S. Army Corps of Engineers collects and maintains LiDAR data including orthophotos in coastal areas of the United States and its territories. The Corps acquires this data in the course of performing its mission of Flood Control, Navigation, Environmental Engineering, and support for the Army and others. These data were collected along the Indiana, Michigan, Ohio and Pennsylvania coasts of the Great Lakes using the CHARTS (Compact Hydrographic Airborne Rapid Total Survey) system and industry based coastal mapping and charting systems.
Original contact information: 
   Contact Org: NOAA Office for Coastal Management
   Phone: 843-740-1202
   Email: coastal.info@noaa.gov</abstract>
      <purpose>The purpose of this survey was to collect topographic and hydrographic elevations to obtain the existing conditions
of the beach and near shore in support of the Joint Airborne LiDAR Bathymetric Technical Center of Expertise National
Coastal Mapping Program. However, depths were not attained in many areas due to water clarity.</purpose>
      <notes>10702</notes>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Temporal</keyword-type>
         <keyword>June 2006</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Temporal</keyword-type>
         <keyword>September 2006</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>
      <maintenance-frequency>As Needed</maintenance-frequency>
      <entity-attribute-overview>Lidar points in LAZ format Classed as 1,2,11</entity-attribute-overview>
      <entity-attribute-detail-citation>none</entity-attribute-detail-citation>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of the US Army Corp of Engineers,
the Joint Airborne Lidar Bathymetry Center of Expertise(JALBTCX), NOAA, the Office for Coastal Management or it's partners.</distribution-liability>
      <data-set-credit>Acknowledgment of JALBTCX would be appreciated in any publications or derived products.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="688728" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2007-03-22</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="688730" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2007-03-22</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="688731" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2007-03-22</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="688729" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2007-03-22</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="1135969">
         <geographic-areas>
            <geographic-area cc-id="1135971">
               <west-bound>-87.2</west-bound>
               <east-bound>-79.98</east-bound>
               <north-bound>44.08</north-bound>
               <south-bound>41.37</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1135970">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2006-06-14</start-date-time>
               <end-date-time>2006-09-26</end-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
      </spatial-representation>
   </spatial-information>
   <access-information>
      <security-class>Unclassified</security-class>
      <data-access-procedure>This data can be obtained on-line at the following URL:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=40;</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
it's limitations.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="742832">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=40</download-url>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, product type, map projection, file format, datum, etc.</description>
      </distribution>
      <distribution cc-id="742833">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/40/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="742836">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="742835">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="688754">
         <activity-date-time>2016-05-23</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="688753">
         <activity-date-time>2017-11-14</activity-date-time>
         <description>Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.</description>
      </activity-log>
      <activity-log cc-id="718662">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="742834">
         <activity-date-time>2018-03-13</activity-date-time>
         <description>Partial upload to move data access links to Distribution Info.</description>
      </activity-log>
   </activity-logs>
   <data-quality>
      <accuracy>N/A</accuracy>
      <horizontal-positional-accuracy>The data has been collected and compiled to meet the +/- 3 m (2 sigma) accuracy specification.; Quantitative Value: 3.0 meters, Test that produced the value: Compiled to meet</horizontal-positional-accuracy>
      <vertical-positional-accuracy>The data has been collected and compiled to meet the +/- 30 cm (2 sigma) accuracy specification.; Quantitative Value: 0.3 meters, Test that produced the value: Compiled to meet</vertical-positional-accuracy>
      <completeness-report>See Process Step</completeness-report>
      <conceptual-consistency>N/A</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1135963">
            <citation-title>2006 USACE National Coastal Mapping Program, Great Lakes Topo/Bathy LiDAR</citation-title>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2006-09-25</extent-start-date-time>
            <source-contribution>Fugro Pelagos, Inc. | Type of Source Media: Electronic Mail System</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1135964">
            <sequence-number>1</sequence-number>
            <description>Acquisition - Data were acquired using a SHOALS-1000T. Sensor orientation was measured using a POS AV 410, while
images were acquired at 1Hz using a Duncantech DT4000 digital camera. Prior to survey PDOP was checked and missions
planned to avoid PDOP greater than 3.5. During survey the plane was always within 30km of a GPS ground control point,
to provide a good quality position solution. Final positions were determined using a post-processed inertially aided
Kinematic GPS (KGPS) solution. GPS ground control data were acquired at 1Hz.

Data received by the airborne system were continually monitored for data quality during acquisition operations. Display
windows showed coverage and information about the system status. In addition, center waveforms at 5Hz were shown. All
of this information allowed the airborne operator to assess the quality of data being collected.

The data were collected and processed in geographic coordinates and ellipsoid heights.  The positions are
relative to NAD83 in decimal degrees of longitude and latitude.  The heights were converted from ellipsoid
to geoid heights (NAVD88) using the Geoid03 model with the results in meters.

Data were processed in the field to verify coverage and data quality.</description>
         </lineage-process-step>
         <lineage-process-step cc-id="1135965">
            <sequence-number>2</sequence-number>
            <description>Processing - Data were processed using the SHOALS Ground Control System (GCS). The GCS includes links to Applanix POSPac
software for GPS and inertial processing, and IVS Fledermaus software for data visualization, 3D editing and tie-line
analysis. Data were processed in NAD83 horizontal and vertical datum. Data were later converted to the NAVD88 vertical
datum using the GEOID03 model. The date and time of each point are also MM:SS.SSSSSS.

Fugro in-house utilities were used to extract XYZ data from the native LiDAR files and split the data in to pre-defined
boxes, each covering approximately 5km of shoreline. ASCII files include: Longitude, Latitude, Elevation, Date, Time,
and Intensity.</description>
         </lineage-process-step>
         <lineage-process-step cc-id="1135966">
            <sequence-number>3</sequence-number>
            <description>Files converted to LDART LAS format (geographic coords, ellipsoid heights,using GEOID03),
sorted by latitude and filtered to eliminate outliers.</description>
            <process-date-time>2007-06-15T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1135967">
            <sequence-number>4</sequence-number>
            <description>Times had originally been stored as POSIX seconds when converted to LAS. This was switched to adjusted GPS time (GPS seconds - 1e9) to conform to the LAS 1.2 standard.</description>
            <process-date-time>2014-01-09T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1135968">
            <sequence-number>5</sequence-number>
            <description>NOAA OCM received the data in LAS v1.2 format. For data storage and Digital Coast provisioning purposes, the data were processed as follows:
1. Heights were converted Ellipsoid heights, horizontal coordinates were converted to geographic coordinates. 
2. lastools's Lasground processed the all unclassifed points to have ground classified points as well. 
3. LAS files were converted to LAZ and sorted.</description>
            <process-date-time>2013-07-01T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:50058</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:24:02</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2022-08-09T17:11:37</metadata-record-last-modified>
      <record-published>2022-03-16</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>2022-03-16</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2023-03-16</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
