<?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>58730</catalog-item-id>
      <title>2015 FEMA Lidar: Michigan Part 3 (Baraga, Marquette Counties)</title>
      <short-name>mi2015_bar_marq_m9009_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>2015</publication-date>
      <abstract>This metadata record describes the Classified Point Cloud (LAS) for the 2015 Michigan LiDAR project covering approximately 1069 square miles in Baraga County and approximately 3425 square miles in Marquette County. 

The NOAA Office for Coastal Management (OCM) downloaded 2 data sets from this USGS site:
ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/

The data sets downloaded were:
USGS_LPC_MI_Baraga_2015_LAS_2018/ Number of files: 4381
USGS_LPC_MI_Marquette_2015_LAS_2018/ Number of files: 8705
These files were processed to the Data Access Viewer (DAV) and https. The total number of files downloaded and processed was 13,086.

Hydro breaklines are also available. These data are available for download at the link provided in the URL section of this metadata record. Please note that these products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM.</abstract>
      <purpose>To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling. LAS data products are suitable for 1 foot contour generation.  USGS LiDAR Base Specification 1.0, QL2. 24.5 cm FVA.</purpose>
      <supplemental-information>Project collection parameters: 
Projection, Datums and Units.  Projection - State Plane Michigan North.  Horizontal datum - North American Datum of 1983 (NAD83 (2011)).  Vertical datum - North American Vertical Datum of 1988 (NAVD88) using the latest geoid (Geoid12a) for converting ellipsoidal heights to orthometric heights.  Units - intl feet
   The following are the USGS lidar fields in JSON:
              {
                

    "ldrinfo" : {
              

    "ldrspec" : "USGS Base Specification 1.0, QL2 meeting 24.5cm FVA",

    "ldrsens" : "Leica ALS70",

    "ldrmaxnr" : "4",

    "ldrnps" : "0.65",

    "ldrdens" : "1.67",

    "ldradens" : "2.2",

    "ldranps" : "0.71",

    "ldrfltht" : "2250",

    "ldrfltsp" : "135",

    "ldrscana" : "32",

    "ldrscanr" : "64",

    "ldrpulsr" : "167",

    "ldrpulsd" : "10",

    "ldrpulsw" : "3",

    "ldrwavel" : "1064",

    "ldrmpia" : "1",

    "ldrbmdiv" : "0.3",

    "ldrswatw" : "1222",

    "ldrswato" : "30",

    "ldrcrs" : "NAD_1983_2011_State_Plane_Michigan_North_2111_Ft_Intl",

    "ldrgeoid" : "NGS Geoid12a"
  },

    "ldraccur" : {
              

    "ldrchacc" : "1.0",

    "rawfva" : "0.169",

    "clsfva" : "0.175",

    "clscva" : "0.271",

    "clssvas" : {
              

    "svalctyp" : "LowVeg",

    "svavalue" : "0.242"
  },

    "clssvas" : {
              

    "svalctyp" : "MedVeg",

    "svavalue" : "0.329"
  },

    "clssvas" : {
              

    "svalctyp" : "HighVeg",

    "svavalue" : "0.263"
  }
  },

    "lasinfo" : {
              

    "lasver" : "1.2",

    "lasprf" : "1",

    "laswheld" : "Withheld (ignore) points were identified in these files using class 10.",

    "lasolap" : "Swath "overage" points were identified in these files by classifying to class 11.",

    "lasintr" : "10",

    "lasclass" : {
              

    "clascode" : "1",

    "clasitem" : "Unclassified"
  },

    "lasclass" : {
              

    "clascode" : "2",

    "clasitem" : "Bare-earth"
  },

    "lasclass" : {
              

    "clascode" : "7",

    "clasitem" : "All noise"
  },

    "lasclass" : {
              

    "clascode" : "9",

    "clasitem" : "Water"
  },

    "lasclass" : {
              

    "clascode" : "10",

    "clasitem" : "Ignored Ground (Breakline Proximity)"
  },

    "lasclass" : {
              

    "clascode" : "11",

    "clasitem" : "Withheld (overlap)"
  },

    "lasclass" : {
              

    "clascode" : "17",

    "clasitem" : "Bridges (most bridges are in class 1)"
  }
  }}</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="5561d10d-5224-4e09-9d68-caffd6bc3d74">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; MICHIGAN</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>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>ALS70</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Bare Earth</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Contour</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Digital Elevation Model (DEM)</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Digital Surface Model (DSM)</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Digital Terrain Model (DTM)</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>First Return</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Grid</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>IMG</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Intensity return</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>LAS</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>LiDAR</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Overlap points</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Unclassified points</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>Water points</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>ground points</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>mapping</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>MI</thesaurus>
         <keyword>point cloud</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>beach</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>erosion</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <keyword>Continent &gt; North America &gt; United States Of America &gt; Michigan &gt; Baraga County</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <keyword>Continent &gt; North America &gt; United States Of America &gt; Michigan &gt; Marquette County</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>Unknown</maintenance-frequency>
      <data-presentation-form>Model (digital)</data-presentation-form>
      <entity-attribute-detail-citation>USGS Base Specification 1.0, QL2 meeting 24.5cm FVA</entity-attribute-detail-citation>
      <distribution-liability>The State of Michigan Geographic Information Systems digital data have been tested and their documentation carefully reviewed.  However, the State of Michigan and its representatives make no warranty or representation, either expressed or implied, with respect to the digital data and their documentation, their quality, performance, merchantability, or fitness for a particular purpose.  The digital data are distributed on "as is" basis, and the user assumes all risk to their quality, the results obtained from their use, and the performance of the data.  In no event will the State of Michigan or its representatives be liable for any direct, indirect, special, incidental or consequential damages resulting from and defect in the State of Michigan or in their documentation.  This disclaimer of warranty is exclusive and in lieu of all others, oral or written, express or implied.  No agent or employee is authorized to make any modification, extension, or addition to this warranty.
Any conclusions drawn from the analysis of this information are not the responsibility of Sanborn, the State of Michigan, FEMA, USGS, NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>State of Michigan (SOM)</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="895929" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2020</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="895930" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2020</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="895931" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2020</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="895932" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2020</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="1143639">
         <geographic-areas>
            <geographic-area cc-id="1143642">
               <west-bound>-88.676764</west-bound>
               <east-bound>-87.105517</east-bound>
               <north-bound>46.9627</north-bound>
               <south-bound>45.981403</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1143640">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2015-05-21</start-date-time>
               <end-date-time>2016-05-17</end-date-time>
               <description>Marquette County</description>
            </time-frame>
            <time-frame cc-id="1143641">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2015-10-25</start-date-time>
               <end-date-time>2015-11-15</end-date-time>
               <description>Baraga County</description>
            </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>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Geographic 3D</crs-type>
               <epsg-code>EPSG:6319</epsg-code>
               <epsg-name>NAD83(2011)</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>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Geodetic Latitude</name>
                     <abbreviation>Lat</abbreviation>
                     <units>degree</units>
                     <orientation>north</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Geodetic Longitude</name>
                     <abbreviation>Lon</abbreviation>
                     <units>degree</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>3</order>
                     <name>Elipsoidal height</name>
                     <abbreviation>h</abbreviation>
                     <units>metre</units>
                     <orientation>up</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <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="895936">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9009</download-url>
         <distributor cc-id="895930">
            <from-date>2020</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>
         <!--Note: file-type is deprecated-->
         <file-type>Zip</file-type>
         <compression>Zip</compression>
      </distribution>
      <distribution cc-id="895937">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9009/index.html</download-url>
         <distributor cc-id="895930">
            <from-date>2020</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>Bulk Download</file-name>
         <description>Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum.</description>
         <!--Note: file-type is deprecated-->
         <file-type>LAZ</file-type>
         <distribution-format>LAS/LAZ - LASer</distribution-format>
         <compression>Zip</compression>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="895927">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9009/supplemental/mi2015_part3_m9009.kmz</url>
         <name>Browse graphic</name>
         <url-type>Browse Graphic</url-type>
         <file-resource-format>KML</file-resource-format>
         <description>This graphic displays the footprint for this lidar data set.</description>
      </url>
      <url cc-id="895926">
         <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="895990">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9009/breaklines/index.html</url>
         <name>Breaklines</name>
         <url-type>Online Resource</url-type>
         <description>Link to the dataset breaklines.</description>
      </url>
      <url cc-id="895989">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9009/supplemental/Final_Report_Michigan_LiDAR_2015.docx</url>
         <name>Dataset report</name>
         <url-type>Online Resource</url-type>
         <description>Link to the dataset report.</description>
      </url>
   </urls>
   <technical-environment>
      <description>Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>Horizontal positional accuracy for Area 1 LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture.  The standard system results for horizontal accuracy meet or exceed the project specified 1.0 meter RMSE. For Area 1, this value is computed by comparing ground control to a DEM derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>For the DEM data derived from the classified point cloud, the FVA, SVA, and CVA were computed. The vertical accuracy was tested with independent survey check points located in various terrain types within Area 1. These check points were not used in the calibration or post processing of the lidar point cloud data. The survey check points were distributed throughout the block area. Specifications for this project require that the FVA be 24.5 cm or better @ 95 percent confidence level.

The FVA was tested using 25 independent survey check points located in flat terrain types within Area 1. The 25 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.087 m. AccuracyZ has been tested to meet 12.5 cm Fundamental Vertical Accuracy at 95 Percent confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. 

The CVA was tested using 97 independent survey check points located in various terrain types within Area 1. The 97 independent check points contained all FVA and SVA class points and were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.140m, or 0.271m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. 

The SVA for the Low Veg class was tested using 25 independent survey check points located in low vegetation terrain types within Area 1. The 25 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.132m, or 0.242m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.

The SVA for the Medium Veg class was tested using 23 independent survey check points located in medium vegetation terrain types within Area 1. The 23 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.199m, or 0.329m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. 

The SVA for the High Veg class was tested using 23 independent survey check points located in high vegetation terrain types within Area 1.The 23 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.126m, or 0.263m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.</vertical-positional-accuracy>
      <completeness-report>LiDAR data is collected for the project area.  Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums.  The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes.  Anomalous laser returns that occur infrequently are removed entirely from the data set.  Once clean bare earth points are established, DEMs are created using bare earth points and hydro features. The DEM surface is then compared to the survey checkpoints. These accuracies must pass the Fundamental Vertical Accuracy, Supplemental Vertical Accuracy, and Consolidated Vertical Accuracy specifications.</completeness-report>
      <conceptual-consistency>LiDAR data is collected within the project area and processed. After the DEMs were created, the dataset was verified against control.  Control was collected in 5 areas.  Area 1 includes Baraga and Marquette.  Accuracy results are reported for Area 1.</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-CO</archive-location>
      <data-protection-plan>Data is backed up to tape and to cloud storage.</data-protection-plan>
   </data-management>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1143625">
            <citation-title>Classified lidar</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>Sanborn Map Company Inc.</contact-name>
            <contact-role-type>Originator</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2015</extent-start-date-time>
            <scale-denominator>1200</scale-denominator>
            <source-contribution>The classified lidar point cloud is used to derive various data products such as, but not limited to, bare earth gridded DEM, triangulated irregular networks (TIN), contours, digital surface models (DSM).  The output format is fully compliant LAS v1.2 or v1.3, Point Record Format 1</source-contribution>
         </lineage-source>
         <lineage-source cc-id="1143626">
            <citation-title>Ground control</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>Sanborn Map Company Inc.</contact-name>
            <contact-role-type>Originator</contact-role-type>
            <publish-date>2010-01-01</publish-date>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2015</extent-start-date-time>
            <source-contribution>Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy.  Predefined points (NGS when available) within the project area are targeted.</source-contribution>
         </lineage-source>
         <lineage-source cc-id="1143627">
            <citation-title>LiDAR Data</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>Sanborn Map Company Inc.</contact-name>
            <contact-role-type>Originator</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2015</extent-start-date-time>
            <source-contribution>Aerial LiDAR and GPS/IMU data are recorded for the defined project area at an altitude, flight speed, scanner swath width and scanner pulse frequency to achieve the design goals of the project.</source-contribution>
         </lineage-source>
         <lineage-source cc-id="1143628">
            <citation-title>Post processed GPS/INS</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>Sanborn Map Company Inc.</contact-name>
            <contact-role-type>Originator</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2015</extent-start-date-time>
            <scale-denominator>1200</scale-denominator>
            <source-contribution>Post processed GPS/INS is applied to the lidar point data to georeference each point in the project coordinate system</source-contribution>
         </lineage-source>
         <lineage-source cc-id="1143629">
            <citation-title>Post processed lidar</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>Sanborn Map Company Inc.</contact-name>
            <contact-role-type>Originator</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2015</extent-start-date-time>
            <scale-denominator>1200</scale-denominator>
            <source-contribution>The post processed lidar data has been projected and oriented in the specified coordinate system as an un-classified point cloud.</source-contribution>
         </lineage-source>
         <lineage-source cc-id="1143630">
            <citation-title>Tile Definition</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>State of Michigan</contact-name>
            <contact-role-type>Originator</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2015</extent-start-date-time>
            <scale-denominator>1200</scale-denominator>
            <source-contribution>The tile definition defines discreet non-overlapping rectangular areas used as cut lines to break up the large classified lidar dataset into smaller, more manageable data tiles.  Each tile is 2500ft by 2500ft in dimension.</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1143631">
            <sequence-number>1</sequence-number>
            <description>At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets.</description>
            <process-date-time>2015-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143632">
            <sequence-number>2</sequence-number>
            <description>New LiDAR data is captured for the project area using a Leica ALS70 LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane.</description>
            <process-date-time>2015-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143633">
            <sequence-number>3</sequence-number>
            <description>The airborne GPS data is post-processed in Inertial Explorer software and LEICA CloudPro software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey.</description>
            <process-date-time>2015-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143634">
            <sequence-number>4</sequence-number>
            <description>The post processed GPS/INS solution is applied to the raw lidar data to orient and project the data points into the project area reference system as an unclassified point cloud.</description>
            <process-date-time>2015-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143635">
            <sequence-number>5</sequence-number>
            <description>The georeferenced lidar data is then classified and edited in Terrasolid Terrascan software.  Data is classified to produce:  Class 1:  unclassified,  Class 2:  ground,  Class 7:  low point,  Class 9: water, Class 10: ignored ground, Class 11:  withheld.</description>
            <process-date-time>2015-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143636">
            <sequence-number>6</sequence-number>
            <description>The classified lidar data is exported as 2500 X 2500 foot tiles in the LAS format with any or all classes required to produce derivative products.</description>
            <process-date-time>2015-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143637">
            <sequence-number>7</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) downloaded 2 data sets from this USGS site:
ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/

The data sets downloaded were:
USGS_LPC_MI_Baraga_2015_LAS_2018/ Number of files: 4381
USGS_LPC_MI_Marquette_2015_LAS_2018/ Number of files: 8705
These files were processed to the Data Access Viewer (DAV) and https. The total number of files downloaded and processed was 13,086.

The data were in Michigan State Plane North (NAD83 2011), international feet coordinates and NAVD88 (Geoid12A) elevations in feet (Marquette County only, Baraga County data was in meters). The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 10 - Ignored Ground, 11 - Withheld. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 10, 11.

OCM performed the following processing on the data for Digital Coast storage and provisioning purposes:

1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges.

2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 12A model, to convert from Michigan State Plane North (NAD83 2011), international feet coordinates to geographic coordinates, to convert from vertical units of feet to meters (for Marquette County only, Baraga County data was in meters), to assign the geokeys, to sort the data by gps time and zip the data to database and to http.</description>
            <process-date-time>2020-02-04T00: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:58730</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2020-01-30T15:05:18</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>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>
      <best-available-metadata>No</best-available-metadata>
      <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>
