<?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>49791</catalog-item-id>
      <title>2012 MEGIS Topographic Lidar: Statewide Lidar Project Areas 2 and 3 (Mid-Coastal Cleanup), Maine</title>
      <short-name>me2012_megis_midcoastal_m2582_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>2013-10</publication-date>
      <abstract>LiDAR data is a remotely sensed high resolution elevation data collected by an airborne platform. The LiDAR sensor uses a combination of laser range
finding, GPS positioning, and inertial measurement technologies. The LiDAR systems collect data point clouds that are used to produce highly detailed
Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The work order required the LiDAR data to be collected at
a nominal pulse spacing (NPS) of 1.5 meter. The final products include first, last, and at least one intermediate return LAS, full classified LAS and
one (1) meter pixel raster DEMs of the bare-earth surface delivered in Esri 10 ArcGrid format.

Original contact information: 
   Contact Org: State of Maine, Office of Information Technology
   Title: State GIS Manager, Maine Office of GIS
   Phone: (207)215-5530</abstract>
      <purpose>This work order consisted of LiDAR acquisition and processing for The Maine GeoLibrary Board (MEGIS) for three areas of the Maine Statewides Lidar
Project, which is included within the Maine Statewide Orthoimagery Program. This metadata record is for Areas 2 and 3 (also known as Mid-Coastal
Cleanup) only. The work order required new LiDAR to be collected at a nominal post spacing of 1.5-meter during Spring 2012 and processed according the
USGS LiDAR Guidelines and Base Specifications version13. The LiDAR data was collected to meet a vertical accuracy requirement of 12.5 cm (0.41 ft)
RMSE. The LiDAR data was provided in 1,500 meters x 1,500 meters tiles in the UTM19 projection. The 1,500 meters x 1,500 meters LiDAR tile file name
was derived from the southwest corner of each tile. The tiles are named based on the US National Grid. The enhanced lidar data will provide support
multi-use applications, including homeland security, emergency management, economic development, and the business of government.</purpose>
      <notes>10435</notes>
      <supplemental-information>A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2582/supplemental/me2012_megis_midcoastal_footprint.KMZ
The lidar report for this data set may be viewed at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2582/supplemental/me2012_megis_midcoastal_lidarreport.pdf</supplemental-information>
   </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>Theme</keyword-type>
         <keyword>LAZ</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Light Detection and Ranging</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 (ASPRS Class 1,2,7,9,10,12)</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 Woolpert, State of Maine Office of Information Technology,
Maine GeoLibrary Board, NOAA, the Office for Coastal Management or its partners.</distribution-liability>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="677261" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2013-10</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="677263" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2013-10</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="677264" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2013-10</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="677262" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2013-10</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="1134783">
         <geographic-areas>
            <geographic-area cc-id="1134797">
               <west-bound>-70.154996</west-bound>
               <east-bound>-68.873963</east-bound>
               <north-bound>44.77033</north-bound>
               <south-bound>43.983226</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1134784">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-04-18</start-date-time>
            </time-frame>
            <time-frame cc-id="1134785">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-04-19</start-date-time>
            </time-frame>
            <time-frame cc-id="1134786">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-04-20</start-date-time>
            </time-frame>
            <time-frame cc-id="1134787">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-04-25</start-date-time>
            </time-frame>
            <time-frame cc-id="1134788">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-04-26</start-date-time>
            </time-frame>
            <time-frame cc-id="1134789">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-04-28</start-date-time>
            </time-frame>
            <time-frame cc-id="1134790">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-04-29</start-date-time>
            </time-frame>
            <time-frame cc-id="1134791">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-04-30</start-date-time>
            </time-frame>
            <time-frame cc-id="1134792">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-05-03</start-date-time>
            </time-frame>
            <time-frame cc-id="1134793">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-05-04</start-date-time>
            </time-frame>
            <time-frame cc-id="1134794">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-05-06</start-date-time>
            </time-frame>
            <time-frame cc-id="1134795">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-05-07</start-date-time>
            </time-frame>
            <time-frame cc-id="1134796">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-05-12</start-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=2582
;</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. These data depict
the heights at the time of the survey and are only accurate for that time.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="741355">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2582</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="741356">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2582/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="741360">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2582/supplemental/me2012_megis_midcoastal_footprint.KMZ</url>
         <name>Browse Graphic</name>
         <url-type>Browse Graphic</url-type>
         <file-resource-format>kmz</file-resource-format>
         <description>This graphic shows the lidar coverage for Maine Statewide Lidar: Areas 2 and 3 (Androscoggin, Sagadahoc, Kennebec, Lincoln, Waldo, Knox, Somerset,
Penobscot Counties).</description>
      </url>
      <url cc-id="741359">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="741358">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="677298">
         <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="677297">
         <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="718360">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="741357">
         <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>
      <horizontal-positional-accuracy>Horizontal accuracy is at the 95% confidence level using RMSE(r) x 1.9600  as defined by the FGDC Geospatial Positional Accuracy Standards,
Part 3: NSSDA
; Quantitative Value: 0.250 meters, Test that produced the value: LiDAR system calibration is available in the project report.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Lidar Data Tested 0.13 meters at 95% confidence level.
The data collected under this Task Order meets the National Standard for Spatial Database Accuracy (NSSDA) accuracy standards. The NSSDA standards
specify that vertical accuracy be reported at the 95 percent confidence level for data tested by an independent source of higher accuracy.
(http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/index_html)
; Quantitative Value: 0.13 meters, Test that produced the value: The LiDAR collected for this task order was tested to meet a vertical accuracy of 0.066 m Root Mean Squared (RMSE).</vertical-positional-accuracy>
      <completeness-report>The LiDAR data is visually inspected by Woolpert, Inc. for completeness to ensure that are no gaps between flight lines</completeness-report>
      <conceptual-consistency>All formatted data are validated using commercial GIS software to ensure proper formatting and loading prior to delivery.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-process-steps>
         <lineage-process-step cc-id="1134777">
            <sequence-number>1</sequence-number>
            <description>Using a combination of Leica ALS60 and Optech Gemini LiDAR systems, 307 flight lines of high density data, at a nominal pulse spacing (NPS) of 1.5
meter, were collected over Maine (approximately 2327 square miles). Multiple returns were recorded for each laser pulse along with an intensity
value for each return. A total of twenty-one (21) missions were flown April 18, 2012  May 12, 2012. Two airborne global positioning system (GPS)
base stations were used in support of the LiDAR data acquisition. 34 ground control points were surveyed through static methods.  The geoid used to
reduce satellite derived elevations to orthometric heights was Geoid09. The horizontal datum used for this survey is North American Datum 1983
(NSRS2007), UTM19, and expressed in meters. The vertical datum used for this survey is North American Vertical Datum 1988 (NAVD88), and expressed
in meters. Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of
trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. System
Parameters: - LIDAR data was collected using Leicas ALS60 and Optechs Gemini LiDAR Systems in Multi-Pulse mode. The ALS60 and Gemini LiDAR Systems
collect up to four returns (echo) per pulse, recording attributes such as time stamp and intensity data, for the first three returns. If a fourth
return was captured, the system does not record an associated intensity value. The aerial LiDAR was collected at the following sensor specifications:
Nominal Post Spacing: 4.92 ft / 1.5 m, AGL (Above Ground Level) average flying height: 7,800 ft / 2,377 m (Leica ALS60), 6,800 ft / 2,072 m
(Optech Gemini), MSL (Mean Sea Level) average flying height: Varies by terrain, Average Ground Speed: 150 knots / 172 mph, Field of View (full):
40 degrees, Pulse Rate: 99  kHz (Leica ALS60), 100 kHz (Optech Gemini), Scan Rate: 38 Hz (Leica ALS60), 32 Hz (Optech Gemini), Side Lap (Minimum): 25%.</description>
            <process-date-time>2012-04-18T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134778">
            <sequence-number>2</sequence-number>
            <description>The Leica ALS60 and Optech Gemini LiDAR system calibration and performance is verified on a periodic basis using Woolpert's calibration range. The
calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using
conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position
of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data
against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment
angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw LiDAR
data is reduced using the refined misalignment angles.</description>
            <process-date-time>2012-04-18T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134779">
            <sequence-number>3</sequence-number>
            <description>Once the data acquisition and GPS processing phases are complete, the LiDAR data was processed immediately to verify the coverage had no voids. The
GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the
solution was verified to be consistent with the accuracy requirements of the project.</description>
            <process-date-time>2012-05-14T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134780">
            <sequence-number>4</sequence-number>
            <description>The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines
were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The point cloud underwent a
classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" LiDAR returns. This
process determined bare-earth points (Class 2), noise (Class 7), water (Class 9) ignored ground (Class 10), unclassified data (Class 1), overlap
points (Class 11). The bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that artifacts have been removed from the
bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset.</description>
            <process-date-time>2012-05-14T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134781">
            <sequence-number>5</sequence-number>
            <description>Breaklines defining lakes, greater than two acres, and double-line streams, wider than 100 feet (30.5 meters), were compiled using digital
photogrammetric techniques as part of the hydrographic flattening process and provided as ESRI Polyline Z and Polygon Z shape files. Breaklines
defining water bodies and streams were compiled for this task order. The breaklines were used to perform the hydrologic flattening of water bodies,
and gradient hydrologic flattening of double line streams. Lakes, reservoirs and ponds, at a nominal minimum size of two (2) acres or greater, were
compiled as closed polygons. The closed water bodies were collected at a constant elevation. Rivers and streams, at a nominal minimum width of 100
feet (30.5 meters), were compiled in the direction of flow with both sides of the stream maintaining an equal gradient elevation. The hydrologic
flattening of the LiDAR data was performed for inclusion in the National Elevation Dataset (NED).</description>
            <process-date-time>2012-06-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1134782">
            <sequence-number>6</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received topographic files in .LAS V1.2 format. The files contained lidar elevation measurements, intensity
values, scan angle values, return information, and adjusted standard GPS time. The data were received in UTM Zone 19N, NAD83 coordinates and were
vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were meters. OCM performed the following processing for
data storage and Digital Coast provisioning purposes:
1. Points in Class 11 (Overlap) were changed to Class 12 (Overlap).
2. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09.
3. The topographic las files were converted from a Projected Coordinate System (UTM Zone 19N) to a Geographic Coordinate System (NAD83).
4. The topographic las files' horizontal units were converted from meters to decimal degrees.</description>
            <process-date-time>2013-10-01T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49791</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:22:19</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:36</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>
