<?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>74802</catalog-item-id>
      <title>2024 USACE FEMA NCMP Phase One 4-Band 8 Bit Imagery: Post Hurricane Milton, FL</title>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49403</parent-catalog-item-id>
      <parent-title>Imagery - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <publication-date>2025-02-04</publication-date>
      <abstract>These files contain 4-band RGBN orthorectified mosaic imagery tiles generated from data collected using a Leica RCD30 digital camera. This full frame medium-format aerial survey camera collected imagery data in tandem with a bathymetric lidar sensor on a single remote sensing platform. Native imagery data is not generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages were used to process the native imagery data into 4-band orthorectified mosaic imagery that can be imported into GIS software for visualization and further analysis. Trajectories were transformed into positional coordinates using the HTDP (Horizontal Time-Dependent Positioning) software to maintain consistency with the NGS (National Geodetic Survey) reference to the North American Datum of 1983 (NAD83) and the North American tectonic plate coordinates realized from the National Adjustment of 2011, or NAD83 (2011). Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to NAD83 (2011) at the 2010.00 epoch. Vertical positions, provided in meters, are referenced to the NAD83 (2011) ellipsoid. The imagery data are in TIF files tiled using 1 km boxes defined by the Military Grid Reference System (MGRS). The file naming convention references the year, effort, area, box number, and data product type. An example file name is, 2024_FEMA_FL_17RLL5013_RGBN.tif, where 2024 is the year of data collection, FEMA is the effort under which data were collected, FL is the area of data collection, 17RLL5013 is the box number and RGBN is the data product type.</abstract>
      <purpose>These data were collected by the USACE in support of FEMA to obtain imagery of conditions along the coast of Florida.</purpose>
      <other-citation-details>Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products.</other-citation-details>
      <supplemental-information>These data depict the heights at the time of the survey and are only accurate for that time. Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products. The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the U.S. Army Corps of Engineers, Mobile District Office, Spatial Data Branch be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The Spatial Data Branch does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or because of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form.</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Data Center Keywords</thesaurus>
         <keyword identifier="7dff3980-7aaa-4db5-a49b-fe778d4935a2">DOD/USARMY/USACE/SAM/MOBILE/OPJ/JALBTCX &gt; Joint Airborne Lidar Bathymetry Technical Center of Expertise, Mobile District, South Atlantic Division, U.S. Army Corps of Engineers, U.S. Army, U.S. Department of Defense</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="0cff6e4b-e42a-4565-89ff-350adf41ed69">EARTH SCIENCE &gt; LAND SURFACE &gt; GEOMORPHIC LANDFORMS/PROCESSES &gt; COASTAL LANDFORMS</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="e26803a0-82ea-40c4-a41a-9e222c9bd09a">EARTH SCIENCE &gt; LAND SURFACE &gt; GEOMORPHIC LANDFORMS/PROCESSES &gt; COASTAL PROCESSES</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="1fbf5df2-ab7c-43fc-9bb2-8eb3f8891f7b">EARTH SCIENCE &gt; OCEANS &gt; COASTAL PROCESSES &gt; COASTAL ELEVATION</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="03f0c0a3-04a7-4ef8-8ec0-3c2266510815">EARTH SCIENCE &gt; SPECTRAL/ENGINEERING &gt; VISIBLE WAVELENGTHS &gt; VISIBLE IMAGERY</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>imageryBaseMapsEarthCover</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>oceans</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Instrument</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Instrument Keywords</thesaurus>
         <keyword identifier="b434201b-4969-4a7e-8749-ba5b7c537c2f">CAMERAS</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>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>GCMD Data Center Keywords v7</thesaurus>
         <keyword>Joint Airborne Lidar Bathymetry Technical Center of Expertise</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>GCMD Data Center Keywords v7</thesaurus>
         <keyword>Mobile District</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>GCMD Data Center Keywords v7</thesaurus>
         <keyword>Spatial Data Branch</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>GCMD Data Center Keywords v7</thesaurus>
         <keyword>United States Army</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>GCMD Data Center Keywords v7</thesaurus>
         <keyword>United States Army Corps of Engineers</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>NOS Data Explorer Topic Category</thesaurus>
         <keyword>Remotely Sensed Imagery/Photography</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX)</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>National Coastal Mapping Program (NCMP)</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Topography</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>U.S. Army Corps of Engineers (USACE)</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Temporal</keyword-type>
         <keyword>2024</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <thesaurus>Geographic Names Information System</thesaurus>
         <keyword>FL</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <thesaurus>Geographic Names Information System</thesaurus>
         <keyword>Florida</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <thesaurus>Geographic Names Information System</thesaurus>
         <keyword>Hurricane Milton</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <thesaurus>Geographic Names Information System</thesaurus>
         <keyword>United States</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>
      <data-presentation-form>Map (digital)</data-presentation-form>
      <distribution-liability>These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures. Any conclusions drawn from the analysis of this information are not the responsibility of JALBTCX, the NOAA Office for Coastal Management, or its partners.</distribution-liability>
      <data-set-credit>Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (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="1367393" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2024-02-12</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="1367395" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2024-02-12</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="1367396" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2024-02-12</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="1367394" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2024-02-12</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="1367412">
         <geographic-areas>
            <geographic-area cc-id="1367414">
               <west-bound>-82.954</west-bound>
               <east-bound>-81.656</east-bound>
               <north-bound>28.267</north-bound>
               <south-bound>25.859</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1367413">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2024-10-29</start-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Projected</crs-type>
               <epsg-code>EPSG:6346</epsg-code>
               <epsg-name>NAD83(2011) / UTM zone 17N</epsg-name>
               <datum-name>NAD83 (National Spatial Reference System 2011)</datum-name>
               <ellipsoid>GRS 1980</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257222101</flattening-ratio>
               <base-crs-name>NAD83(2011)</base-crs-name>
               <projection-name>UTM zone 17N</projection-name>
               <conversion-method>Transverse 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>81° 0' 0" W</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Scale factor at natural origin</parameter-name>
                     <parameter-value>0.9996</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>False easting</parameter-name>
                     <parameter-value>500000</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>E</abbreviation>
                     <units>metre</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Northing</name>
                     <abbreviation>N</abbreviation>
                     <units>metre</units>
                     <orientation>north</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <security-class>Unclassified</security-class>
      <data-access-constraints>None. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.</data-access-constraints>
      <data-use-constraints>These data depict the heights at the time of the survey and are only accurate for that time. Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products. The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the U.S. Army Corps of Engineers, Mobile District Office, Spatial Data Branch be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The Spatial Data Branch does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or because of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="1367397">
         <download-url>https://coast.noaa.gov/dataviewer/#/imagery/search/where:ID=10254</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="1367398">
         <download-url>https://coastalimagery.blob.core.windows.net/digitalcoast/PostMiltonFL_RGBN_2024_10254/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <activity-logs>
      <activity-log cc-id="1367400">
         <activity-date-time>2016-12-09</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="1367399">
         <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="1367401">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="1367402">
         <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>
   <technical-environment>
      <description>Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.1.0.3035</description>
   </technical-environment>
   <data-quality>
      <accuracy>These data are not attributed. | Quantitative Value: N/A | Quantitative Test Explanation: These data are not attributed.</accuracy>
      <horizontal-positional-accuracy>The data positions were obtained using post processed Direct Georeference PPK methods. The horizontal accuracy of the true color imagery operation is 12.2cm at 95% Confidence Level with typical RMSE is 7.1cm. Gross offsets in imagery data may be due to DEM affects or unforseen timing offsets caused by missed or unknown camera trigger times.</horizontal-positional-accuracy>
      <quality-control-procedures>These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.</quality-control-procedures>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1367407">
            <citation-title>JALBTCX</citation-title>
            <contact-type>Position</contact-type>
            <contact-name>Data Production Manager</contact-name>
            <contact-role-type>Originator</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2024-11-16</extent-start-date-time>
            <source-contribution>7225 STENNIS AIRPORT RD STE 100
Kiln, MS 39556

JALBTCX@usace.army.mil
228-252-1131</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1367408">
            <sequence-number>1</sequence-number>
            <description>Leica RCD30 data were converted from raw files created during the data collection to unrectified TIF images using HxMap which is a data processing suite developed by Hexagon. A Smoothed Best Estimate of Trajectory (SBET) solution was resolved from the raw aircraft GNSS-IMU positional data using the NovAtel Inertial Explorer software package. The Exterior Orientation (EO) parameters and camera misalignments for the imagery were then computed using the Leica IPAS CO+ software package where the values were checked against the known current calibration values for this camera installation. A Digital Elevation Model (DEM) was generated from lidar data collected concurrently with the imagery using an adjacent sensor in tandem with the digital camera on a single remote sensing platform. The unrectified TIF files, EO data, DEM file, SimActive Tile Definition File (TDF), and camera calibration file were given as input to the SimActive Correlator3D software package for processing. Using Correlator3D, the data went through Aerial Triangulation (AT), orthorectification, color balancing, and mosaicking. The mosaic data were exported from Correlator3D as TIF files tiled according to 1 km MGRS grid cells. The mosaic image files were compressed using Geospatial Data Abstraction Library (GDAL) tools by applying the LZW lossless compression method. The compressed mosaic image files were finalized using GDAL and the Esri ArcGIS Desktop software package. GDAL was used to calculate statistics and build pyramids, while ArcGIS was used to create metadata for each image tile. The data processing workflow, including software packages, algorithms and parameters are provided in detail, within this metadata as Process Steps.</description>
            <process-date-time>2024-11-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1367409">
            <sequence-number>2</sequence-number>
            <description>These data were collected using the Leica RCD30 digital camera. The camera is owned and operated by Woolpert, Inc. and used in support of the U.S. Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX). The RCD30 is one of Leica's medium-format full frame aerial survey camera specifically designed for mapping applications. The Leica RCD30 can capture high-resolution RGBN (Red Green Blue NIR) imagery with a wide aerial coverage. Aircraft position, velocity, and acceleration information was collected as raw positional data which creates a GNSS-IMU solution for airborne direct georeferencing which precisely measures the position and orientation of the onboard aerial sensors hundreds of times per second and accounts for all motion variables at the exact moment of data capture. All raw data streams from the collected mission, including the raw files from the Leica RCD30 digital camera and the positional data, were then transferred from the field to the office for downloading, duplicating, and processing.</description>
            <process-date-time>2024-11-23T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1367410">
            <sequence-number>3</sequence-number>
            <description>After collection, the navigation data was refined with the NovAtel Inertial Explorer software package. A copy of the raw positional data from the on-board navigation system was used as input for the navigation post-processing. After post-processing, the lever arms and mounting angles were verified to match the values of the current camera installation. Upon satisfactory review, an SBET file was exported from Inertial Explorer using the World Geodetic System 1984 (WGS 84) method where the position data was referenced to the ITRF2014 datum with an epoch targeting the mission date. An ITRF (International Terrestrial Reference Frame) is a realization of the ITRS (International Terrestrial Reference System) which through various scales, rotations, and rates applied to its origin are updated for geodetic use as time goes on by producing new solutions every few years. Over time, the WGS 84 reference coordinate system used by the Global Positioning System (GPS) has had several re-adjustments to keep it in line with ITRF updates. This SBET file was then transformed from the ITRF2014 datum with an epoch corresponding to the mission date to the North American Datum of 1983 (NAD83) and the North American tectonic plate coordinates realized from the National Adjustment of 2011, or NAD83 (2011) at the 2010.00 epoch. The National Geodetic Survey (NGS) has produced several adjustment realizations to NAD83, including NAD83 (2011). While WGS 84 is updated to match ITRF realizations, NAD83 is tied to the North American tectonic plate where its coordinates have been gradually drifting farther from the WGS 84 and ITRF adjustments with the passage of time. Trajectories were transformed into positional coordinates using the HTDP (Horizontal Time-Dependent Positioning) software to maintain consistency with the NGS (National Geodetic Survey) reference to the North American Datum of 1983 (NAD83) and the North American tectonic plate coordinates realized from the National Adjustment of 2011, or NAD83 (2011). Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to NAD83 (2011) at the 2010.00 epoch. Vertical positions, provided in meters, are referenced to the NAD83 (2011) ellipsoid.</description>
            <process-date-time>2024-11-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1367411">
            <sequence-number>4</sequence-number>
            <description>The copy of the raw Leica RCD30 data was converted from raw files created during the data collection to unrectified TIF images using HxMap which was developed by Hexagon. Using HxMap, associated data was extracted from the raw camera data to derive the event file, photo ID file, preliminary Exterior Orientation (EO) file, and installation settings file.

Using Leicas IPAS CO+ software package, the SBET file was converted to a solution file format usable by IPAS CO+. This solution file, event file, photo ID file, and valid lever arm misalignment values were used by IPAS CO+ to create and export the finalized Exterior Orientation (EO) values as a text file. Using a custom Python script, this text file was then restructured into a format usable by Correlator3D.

The unrectified TIF imagery was then subjected to image processing using the SimActive Correlator3D software package. The TIF images, concurrent DEM image, EO file, SimActive Tile Definition File (TDF), and camera installation file were used to build a project in Correlator3D. Aerial Triangulation (AT), orthorectification, color balancing, mosaicking, and tiling were done in a preliminary manner and the data was reviewed. The AT report was reviewed to ensure a satisfactory quality assessment and limited projection error. The automatically generated seamlines were manually adjusted to correct unsatisfactory mosaicking patterns. Next, the corrected mosaic data were exported from Correlator3D as TIF files tiled according to 1 km MGRS grid cells.

The mosaic image files were compressed using Geospatial Data Abstraction Library (GDAL) tools by applying the LZW lossless compression method. GDAL was then used to calculate statistics and build pyramids on the compressed mosaic image tiles. The Esri ArcGIS Desktop software package was then used to create metadata for each image tile.</description>
            <process-date-time>2024-11-01T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:74802</guid>
      <metadata-record-created-by pers-id="20138">Erik Hund</metadata-record-created-by>
      <metadata-record-created>2025-01-30T14:10:47</metadata-record-created>
      <metadata-record-last-modified-by pers-id="20138">Erik Hund</metadata-record-last-modified-by>
      <metadata-record-last-modified>2025-02-03T17:10:00</metadata-record-last-modified>
      <record-published>2025-02-03</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>2025-02-03</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2026-02-03</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
