<?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>78379</catalog-item-id>
      <title>2020 USGS Lidar DEM: Goodhue County, MN</title>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49401</parent-catalog-item-id>
      <parent-title>Lidar - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <creation-date>2020</creation-date>
      <publication-date>2023</publication-date>
      <abstract>Project Description for the Original Data:
The Goodhue County lidar project area covers approximately 941 square miles which includes a 100 meter buffer around the county boundary. The airborne lidar data was acquired at an aggregate nominal point density (ANPD) of 30 points per square meter. Project specifications are based on Goodhue County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83(HARN) Adj MN Goodhue Co (ftUS), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using a Riegl VQ 1560i sensor with serial number 4040 from April 08, 2020 to May 03, 2020 in 13 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels.

This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the GeoTIFF files hosted by USGS on Amazon Web Services.</abstract>
      <purpose>This data, along with its derivatives, is the result of a countywide elevation mapping with cooperative partnerships from Goodhue County, Minnesota DOA, and the USGS 3DEP program. This data was produced from lidar data collected in May 2020, which was processed and delivered in 2021.</purpose>
      <supplemental-information>Raster File Type = TIFF Bit Depth/Pixel Type = 32-bit float Raster Cell Size = 1 foot Interpolation or Resampling Technique = Triangulated Irregular Network Required Vertical Accuracy = 9.8 cm NVA</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="e9f67a66-e9fc-435c-b720-ae32a2c3d8f5">EARTH SCIENCE</keyword>
      </keyword>
      <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 version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="395372ad-2883-4b6a-a481-6383a310ca47">EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION &gt; DIGITAL ELEVATION/TERRAIN MODEL (DEM)</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="2e2d65b6-d3de-4921-877c-2d3a4e447978">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; MINNESOTA</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="90761f8d-6abe-499c-b711-acec394daa59">VERTICAL LOCATION &gt; LAND SURFACE</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Instrument</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Instrument Keywords</thesaurus>
         <keyword identifier="7166c458-f935-4bd9-a322-d92830cf0c33">LIDAR &gt; Light Detection and Ranging</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Platform</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Platform Keywords</thesaurus>
         <keyword identifier="8b7834c1-2c66-414e-a655-2298e7dcc479">Airplane &gt; Airplane</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office for Coastal Management</organization>
      <city>Charleston</city>
      <state-province>SC</state-province>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <data-set-type>Elevation</data-set-type>
      <maintenance-frequency>None Planned</maintenance-frequency>
      <data-presentation-form>Model (digital)</data-presentation-form>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Ayres Associates, USGS</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1450582" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2025</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="1450581" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2025</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="1450585" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2023</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>U.S. Geological Survey</contact-name>
         <contact-address>12201 Sunrise Valley Drive </contact-address>
         <contact-address-city>Reston</contact-address-city>
         <contact-address-state>VA</contact-address-state>
         <contact-address-zip>20191</contact-address-zip>
         <contact-address-country>USA</contact-address-country>
         <contact-url>https://usgs.gov</contact-url>
         <contact-url-name>USGS Home</contact-url-name>
         <contact-url-description>Home page for USGS</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1450583" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2025</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="1450584" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2025</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="1450607">
         <geographic-areas>
            <geographic-area cc-id="1450609">
               <west-bound>-93.097105</west-bound>
               <east-bound>-92.220453</east-bound>
               <north-bound>44.721758</north-bound>
               <south-bound>44.165595</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1450608">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2020-04-08</start-date-time>
               <end-date-time>2020-05-03</end-date-time>
               <description>Dates of collection for Goodhue County</description>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <grid>Yes</grid>
            <vector>No</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>Vertical</crs-type>
               <epsg-code>EPSG:6360</epsg-code>
               <epsg-name>NAVD88 height (ftUS)</epsg-name>
               <datum-name>North American Vertical Datum 1988</datum-name>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Gravity-related height</name>
                     <abbreviation>H</abbreviation>
                     <units>US survey foot</units>
                     <orientation>up</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <data-license-type>Custom</data-license-type>
      <security-class>Unclassified</security-class>
      <data-access-procedure>Data is available online for bulk and custom downloads.</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <data-use-constraints>Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="1450586">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=13709/details/13709</download-url>
         <distributor cc-id="1450581">
            <from-date>2025</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, map projection, file format, etc. A new metadata will be produced to reflect your request using this record as a base.</description>
         <distribution-format>Not Applicable</distribution-format>
         <compression>Zip</compression>
      </distribution>
      <distribution cc-id="1450587">
         <download-url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/MN_GoodhueCounty_2020_A20/MN_GoodhueCo_1_2020/TIFF/</download-url>
         <distributor cc-id="1450585">
            <from-date>2023</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>U.S. Geological Survey</contact-name>
         </distributor>
         <file-name>Bulk Download</file-name>
         <description>Bulk download of data files in the original projection/datum of NAD83(HARN) Adj MN Goodhue Co (ftUS), and vertical datum of NAVD88 - Geoid12B (Feet).</description>
         <distribution-format>GeoTIFF</distribution-format>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="1450591">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/MN_GoodhueCounty_2020_A20/MN_GoodhueCo_1_2020/reports/Processing%20Report%20Goodhue%20County%203DEP%20Lidar_Ayres.pdf</url>
         <name>Lidar Processing Report</name>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Ayres lidar processing report.</description>
      </url>
      <url cc-id="1450588">
         <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="1450592">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/MN_GoodhueCounty_2020_A20/MN_GoodhueCo_1_2020/reports/Collection%20Report%20Goodhue%20County%203DEP%20Lidar_Ayres.pdf</url>
         <name>Lidar Collection Report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the Ayres lidar collection report.</description>
      </url>
      <url cc-id="1450593">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/MN_GoodhueCounty_2020_A20/USGS_MN_GoodhueCounty_2020_A20_ProjectReport.pdf</url>
         <name>USGS Project Report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the USGS Project Report that provides information about the project, vertical accuracy results, and the point classes and sensors used.</description>
      </url>
      <url cc-id="1450594">
         <url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/metadata/MN_GoodhueCounty_2020_A20/MN_GoodhueCo_1_2020/</url>
         <name>USGS Additional Info</name>
         <url-type>Online Resource</url-type>
         <description>Link to the reports, breaklines, metadata, and spatial metadata.</description>
      </url>
      <url cc-id="1450589">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MN_GoodhueCo_1_2020/ept.json</url>
         <name>USGS Entwine Point Tile (EPT)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1450590">
         <url>https://usgs.entwine.io/data/view.html?r=https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MN_GoodhueCo_1_2020/ept.json</url>
         <name>USGS 3D View</name>
         <url-type>Online Resource</url-type>
         <description>Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer.</description>
      </url>
   </urls>
   <technical-environment>
      <description>Terrasolid</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>Not provided</horizontal-positional-accuracy>
      <vertical-positional-accuracy>This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.

USGS Determined DEM Vertical Accuracy:

Tested NVA RMSEz = 2.59 cm

Tested 95th percentile value for VVA is : 13.62 cm

For more information see the USGS project report and the lidar report. The links to these reports are provided in the URL section of this metadata record.</vertical-positional-accuracy>
      <completeness-report>Datasets contain complete coverage of tiles. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. There are no void areas or missing data. The raw point cloud is of good quality and data passes Non-Vegetated Vertical Accuracy specifications.</completeness-report>
      <conceptual-consistency>Data covers the entire area specified for this project.</conceptual-consistency>
   </data-quality>
   <data-management>
      <resources-identified>Yes</resources-identified>
      <resources-budget-percentage>Unknown</resources-budget-percentage>
      <data-access-directive-compliant>Yes</data-access-directive-compliant>
      <archive-location>NCEI-NC</archive-location>
      <data-protection-plan>Data is backed up to cloud storage.</data-protection-plan>
   </data-management>
   <lineage>
      <lineage-statement>The NOAA Office for Coastal Management (OCM) ingested references to the USGS GeoTIFF files that are hosted on Amazon Web Services (AWS), into the Digital Coast Data Access Viewer (DAV). The DAV accesses the raster data as it resides on AWS.</lineage-statement>
      <lineage-sources>
         <lineage-source cc-id="1450602">
            <citation-title>USGS AWS GeoTIFF Files - MN_GoodhueCo_1_2020</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/MN_GoodhueCounty_2020_A20/MN_GoodhueCo_1_2020/TIFF/</citation-url>
            <citation-url-name>USGS AWS GeoTIFF Files for MN_GoodhueCo_1_2020</citation-url-name>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1450603">
            <sequence-number>1</sequence-number>
            <description>The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used RIEGL RiPROCESS software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 9.8 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 2.1, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</description>
            <process-date-time>2020-06-23T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1450604">
            <sequence-number>2</sequence-number>
            <description>LAS Point Cloud Classification:
LiDAR data processing for the point cloud deliverable consists of classifying the LiDAR using a combination of automated classification and manual edit/reclassification processes. On most projects the automated classification routines will correctly classify 90-95 percent of the LiDAR points. The remaining 5-10 percent of the bare earth ground class must undergo manual edit and reclassification.
Because the classified points serve as the foundation for the Terrain, DEM and breakline products, it is necessary for the QA/QC supervisor to review the completed point cloud deliverables prior to the production of any additional products.
The following workflow steps are followed for automated LiDAR classification:
1.	Lead technicians review the group of LiDAR tiles to determine which automated classification routines will achieve the best results. Factors such as vegetation density, cultural features, and terrain can affect the accuracy of the automated classification.  The lead technicians have the ability to edit or tailor specific routines in order to accommodate the factors mentioned above, and achieve the best results and address errors.
2.	Distributive processing is used to maximize the available hardware resources and speed up the automated processing as this is a resource-intensive process.
3.	Once the results of the automated classification have been reviewed and passed consistent checks, the supervisor then approves the data tiles for manual classification.
The following workflow steps are followed for manual edits of the LiDAR bare earth ground classification:
1.	LiDAR technicians review each tile for errors made by the automated routines and correctly address errors any points that are in the wrong classification. By methodically panning through each tile, the technicians view the LiDAR points in profile, with a TIN surface, and as a point cloud.
2.	Any ancillary data available, such as Google Earth, is used to identify any features that may not be identifiable as points so that the technician can make the determination to which classification the feature belongs.
The QA/QC processes for the LiDAR processing phase consist of:
1.	The lead technician reviews all automated classification results and adjust the macros as necessary to achieve the optimal efficiency. This is an iterative process, and the technician may need to make several adjustments to the macros, depending upon the complexity of the features in the area being processed.
	During the manual editing process, the LiDAR technicians use a system of QA, whereby they check each other’s edits. This results in several benefits to the process:
	There is a greater chance of catching minor blunders
	It increases communication between technicians on technique and appearance
	Solutions to problems are communicated efficiently
	To ensure consistency across the project area, the supervisor reviews the data once the manual editing is complete.
For this phase of a project, the following specifications are checked against:
•	Point cloud – all points must be classified according to the USGS classification standard for LAS. The all-return point cloud must be delivered in fully-compliant LAS version 1.4.
•	LAS files will use the Spatial Reference Framework according to project specification and all files shall be projected and defined.
•	General Point classifications:
	Class 1. Processed, but unclassified
	Class 2. Bare Earth
	Class 5. High Vegetation  
	Class 6. Building
	Class 7. Noise 
	Class 9. Water
	Class 17. Bridge Decks
	Class 18. High Noise
	Class 20. Ignored ground (Breakline proximity)
	Class 22. Temporaral Exclusion
•	Outliers, noise, blunders, duplicates, geometrically unreliable points near the extreme edge of the swath, and other points deemed unusable are to be identified using the "Withheld" flag. This applies primarily to points which are identified during pre-processing or </description>
            <process-date-time>2020-06-23T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1450605">
            <sequence-number>3</sequence-number>
            <description>LiDAR processing utilizes several software packages, including GeoCue and the TerraSolid suite of processing components. The GeoCue software is a database management system for housing the LiDAR dataset (usually multiple gigabytes in size). GeoCue incorporates a thorough checklist of processing steps and quality assurance/quality control (QA/QC) procedures that assist in the LiDAR workflow. The TerraSolid software suite is used to automate the initial classification of the LiDAR point cloud based on a set of predetermined parameters. Lidar technicians refer to ground cover research (natural and cultural features) within the project area and determine algorithms most suitable for the initial automated LiDAR classification. (Some algorithms/filters recognize the ground in forests well, while others have greater capability in urban areas). During this process each point is given an initial classification (e.g., as ground, vegetation, or noise) based on the point's coordinates and the relation to its neighbors. Classifications to be assigned include all those outlined by ASPRS standards. The initial classifications produce a coarse and inexact dataset, but offer an adequate starting point for the subsequent manual classification procedure. During this step, "overlap" points are automatically classified (those originating from neighboring flightlines) using information gathered from the ABGPS and IMU data. Any duplicate points existing from adjacent flightlines are removed during this process. Hydrographic breaklines are collected using LiDARgrammetry to ensure hydroflattened water surfaces. This process involves manipulating the LiDAR data's intensity information to create a metrically sound stereo environment. From this generated "imagery", breaklines are photogrammetrically compiled. Breakline polygons are created to represent open water bodies. The LiDAR points that fall within these areas are classified as "water." All hydrographic breaklines include a 3.125 foot buffer, with the Class 2 (bare earth) points being re-classified as Class 20 (ignored ground). TerraSolid is further used for the subsequent manual classification of the LiDAR points allowing technicians to view the point cloud in a number of ways to ensure accuracy and consistency of points and uniformity of point coverage. The TIN was processed to create a GRID or digital elevation model (DEM) with 2 foot pixels.</description>
            <process-date-time>2020-06-23T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1450606">
            <sequence-number>4</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) created references to the USGS GeoTIFF files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the raster data as it resides on Amazon Web Services (AWS).

These are the GeoTIFF files that are being accessed:
https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/MN_GoodhueCounty_2020_A20/MN_GoodhueCo_1_2020/TIFF/</description>
            <process-date-time>2025-10-08T00: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>
   <related-items>
      <related-item>
         <catalog-item-id>72333</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2020 USGS Lidar: Goodhue County, MN</title>
         <relationship-type>Cross Reference</relationship-type>
      </related-item>
   </related-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:78379</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2025-10-07T19:04:48</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>2025-11-20</record-published>
      <owner-organization>OCM Partners</owner-organization>
      <owner-organization-acronym>OCMP</owner-organization-acronym>
      <owner-organization-address/>
      <owner-organization-address-city/>
      <owner-organization-address-state/>
      <owner-organization-address-zip/>
      <owner-organization-address-country/>
      <owner-organization-phone/>
      <owner-organization-url/>
      <owner-organization-business-hours/>
      <owner-organization-group-id>1002</owner-organization-group-id>
      <publication-status>Public</publication-status>
      <limited-metadata-available>No</limited-metadata-available>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2024-03-20</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2025-03-20</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
