<?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>74267</catalog-item-id>
      <title>2023 FEMA Lidar DEM: California Levees</title>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49404</parent-catalog-item-id>
      <parent-title>DEMs - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <creation-date>2023</creation-date>
      <publication-date>2024</publication-date>
      <abstract>Original Product: These are Digital Elevation Model (DEM) data for California as part of the required deliverables for the CA_FEMALevee_D23 project. Class 2 (ground) LiDAR points in conjunction with the hydro breaklines were used to create a 0.5 meter hydro-flattened Raster DEM. 

Original Geographic Extent: 3 counties in California, covering approximately 485 square miles in Sacramento and San Joaquin Counties and 918 square miles in San Bernardino County.

Original Dataset Description: The CA_FEMALevee_D23 project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 8.0 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, 2023 Rev. A. The data were developed based on a horizontal projection/datum of NAD 1983 2011 UTM Zones 10N and 11N, Meters and vertical datum of NAVD88 Geoid 18, Meter. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to individual 1000 m x 1000 m tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 1000 m x 1000 m schema. Continuous breaklines were produced in Esri file geodatabase format.

Original Dataset Ground Conditions: LiDAR was collected in summer 2023, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications and meet ASPRS vertical accuracy guidelines, NV5 Geospatial utilized a total of 28 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 68 independent accuracy checkpoints, 38 in Bare Earth and Urban landcovers (38 NVA points), 30 in Tall Weeds categories (30 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.

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 USGS GeoTIFF files hosted by USGS on Amazon Web Services.</abstract>
      <purpose>To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create intensity images, breaklines and raster DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 0.5 meter cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
      <supplemental-information>Raster File Type = GeoTIFF; Bit Depth/Pixel Type = 32-bit float; Raster Cell Size = 0.5 meter; Interpolation or Resampling Technique = Triangulated Irregular Network (TIN), Linear Interpolation, Proprietary; Required Vertical Accuracy = 0.196</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 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>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="fc4f2acd-ace7-452b-a540-4162f9e9ddb0">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; CALIFORNIA</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> Acknowledgement of FEMA and USGS would be appreciated for products derived from these data.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1362573" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2024</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="1362572" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2024</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="1362576" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2024</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="1362574" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2024</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="1362575" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2024</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="1362601">
         <geographic-areas>
            <geographic-area cc-id="1362606">
               <west-bound>-117.23</west-bound>
               <east-bound>-115.27</east-bound>
               <north-bound>35.35</north-bound>
               <south-bound>34.2</south-bound>
               <description>CA_FEMALevee_2 (Work Unit 300456) in San Bernardino County</description>
            </geographic-area>
            <geographic-area cc-id="1362607">
               <west-bound>-121.493627841</west-bound>
               <east-bound>-121.074760591</east-bound>
               <north-bound>38.6219502332</north-bound>
               <south-bound>38.0012606183</south-bound>
               <description>CA_FEMALevee_1 (Work Unit 300455) in Sacramento and San Joaquin Counties</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1362605">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2023-05-25</start-date-time>
               <end-date-time>2023-05-26</end-date-time>
               <description>Dates of collection for CA_FEMALevee_1 (Work Unit 300455) in Sacramento and San Joaquin Counties</description>
            </time-frame>
            <time-frame cc-id="1362602">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2023-05-30</start-date-time>
               <end-date-time>2023-05-31</end-date-time>
               <description>Dates of collection for CA_FEMALevee_2 (Work Unit 300456) in San Bernardino County</description>
            </time-frame>
            <time-frame cc-id="1362603">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2023-06-01</start-date-time>
               <end-date-time>2023-06-02</end-date-time>
               <description>Dates of collection for CA_FEMALevee_2 (Work Unit 300456) in San Bernardino County</description>
            </time-frame>
            <time-frame cc-id="1362604">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2023-06-15</start-date-time>
               <description>Date of collection for CA_FEMALevee_2 (Work Unit 300456) in San Bernardino 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:5703</epsg-code>
               <epsg-name>NAVD88 height</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>metre</units>
                     <orientation>up</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Projected</crs-type>
               <epsg-code>EPSG:6339</epsg-code>
               <epsg-name>NAD83(2011) / UTM zone 10N</epsg-name>
               <datum-name>NAD83 (National Spatial Reference System 2011)</datum-name>
               <ellipsoid>GRS 1980</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257222101</flattening-ratio>
               <base-crs-name>NAD83(2011)</base-crs-name>
               <projection-name>UTM zone 10N</projection-name>
               <conversion-method>Transverse Mercator</conversion-method>
               <parameters>
                  <parameter>
                     <parameter-name>Latitude of natural origin</parameter-name>
                     <parameter-value>0° 0' 0" N</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Longitude of natural origin</parameter-name>
                     <parameter-value>123° 0' 0" W</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Scale factor at natural origin</parameter-name>
                     <parameter-value>0.9996</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>False easting</parameter-name>
                     <parameter-value>500000</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
                  <parameter>
                     <parameter-name>False northing</parameter-name>
                     <parameter-value>0</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
               </parameters>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Easting</name>
                     <abbreviation>E</abbreviation>
                     <units>metre</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Northing</name>
                     <abbreviation>N</abbreviation>
                     <units>metre</units>
                     <orientation>north</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Projected</crs-type>
               <epsg-code>EPSG:6340</epsg-code>
               <epsg-name>NAD83(2011) / UTM zone 11N</epsg-name>
               <datum-name>NAD83 (National Spatial Reference System 2011)</datum-name>
               <ellipsoid>GRS 1980</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257222101</flattening-ratio>
               <base-crs-name>NAD83(2011)</base-crs-name>
               <projection-name>UTM zone 11N</projection-name>
               <conversion-method>Transverse Mercator</conversion-method>
               <parameters>
                  <parameter>
                     <parameter-name>Latitude of natural origin</parameter-name>
                     <parameter-value>0° 0' 0" N</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Longitude of natural origin</parameter-name>
                     <parameter-value>117° 0' 0" W</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Scale factor at natural origin</parameter-name>
                     <parameter-value>0.9996</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>False easting</parameter-name>
                     <parameter-value>500000</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
                  <parameter>
                     <parameter-name>False northing</parameter-name>
                     <parameter-value>0</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
               </parameters>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Easting</name>
                     <abbreviation>E</abbreviation>
                     <units>metre</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Northing</name>
                     <abbreviation>N</abbreviation>
                     <units>metre</units>
                     <orientation>north</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <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="1362577">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10241/details/10241</download-url>
         <distributor cc-id="1362572">
            <from-date>2024</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="1362578">
         <download-url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/OPR/Projects/CA_FEMALevee_D23/</download-url>
         <distributor cc-id="1362576">
            <from-date>2024</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 GeoTIFF format, UTM Zones 10N and 11N NAD83(2011), meters coordinates and elevations in NAVD88 (Geoid18) meters.</description>
         <distribution-format>GeoTIFF</distribution-format>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="1362586">
         <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="1362581">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/CA_FEMALevee_D23/CA_FEMALevee_1_D23/reports/CA_FEMALevee_D23_UTM10.pdf</url>
         <name>Lidar Report - CA_FEMALevee_1 (Sacramento and San Joaquin Counties)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the lidar report for CA_FEMALevee_1 ( Sacramento and San Joaquin Counties)</description>
      </url>
      <url cc-id="1362582">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/CA_FEMALevee_D23/CA_FEMALevee_2_D23/reports/CA_FEMALevee_2_D23.pdf</url>
         <name>Lidar Report - CA_FEMALevee_2 (San Bernardino County)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the lidar report for CA_FEMALevee_2 ( San Bernardino County)</description>
      </url>
      <url cc-id="1362580">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/CA_FEMALevee_D23/USGS_CA_FEMALevee_D23_Project_Report.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="1362583">
         <url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/metadata/CA_FEMALevee_D23/</url>
         <name>USGS Additional Info</name>
         <url-type>Online Resource</url-type>
         <description>Link to the reports, breaklines, metadata, and spatial metadata.</description>
      </url>
   </urls>
   <technical-environment>
      <description>MicroStation Connect; TerraScan Version 21.016; STRIPALIGN 2.21 ; TerraModeler Version 21.008; GeoCue Version 2020.1.22.1; Esri ArcGIS 10.6; Global Mapper 19/20; RiProcess 1.8.6; Windows 10 Operating System
      \\point_cloud\tilecls\*.las</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>CA_FEMALevee_1 (Sacramento, San Joaquin Counties):
Lidar horizontal accuracy is a function of Global Navigation Satellite System (GNSS) derived positional error, flying altitude, and INS derived attitude error. The obtained RMSEr value is multiplied by a conversion factor of 1.7308 to yield the horizontal component of the National Standards for Spatial Data Accuracy (NSSDA) reporting standard where a theoretical point will fall within the obtained radius 95% of the time. Based on a flying altitude of 2500 meters, an IMU error of 0.002 decimal degrees, and a GNSS positional error of 0.015 meters, this project was compiled to meet 0.27 meter horizontal accuracy at the 95% confidence level (or 15 cm RMSEr). 

CA_FEMALevee_2 (San Bernardino County):
Lidar horizontal accuracy is a function of Global Navigation Satellite System (GNSS) derived positional error, f lying altitude, and INS derived attitude error. The obtained RMSEr value is multiplied by a conversion factor of 1.7308 to yield the horizontal component of the National Standards for Spatial Data Accuracy (NSSDA) reporting standard where a theoretical point will fall within the obtained radius 95% of the time. Based on a f lying altitude of 2532 meters, an IMU error of 0.002 decimal degrees, and a GNSS positional error of 0.019 meters, this project was compiled to meet 0.27 meter horizontal accuracy at the 95% confidence level (or 16 cm RMSEr).</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 DEM Determined Vertical Accuracy:

Non-Vegetated Vertical Accuracy (NVA) = 3.62 cm RMSE

Vegetated Vertical Accuracy (VVA) = 22.99 cm at the 95th Percentile</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 pass Non-Vegetated Vertical Accuracy specifications.</completeness-report>
      <conceptual-consistency>Data cover 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="1362593">
            <citation-title>USGS GeoTIFF Files - CA_FEMALevee_1 (Sacramento, San Joaquin Counties)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/OPR/Projects/CA_FEMALevee_D23/CA_FEMALevee_1_D23/TIFF/</citation-url>
            <citation-url-name>USGS GeoTIFF files for CA_FEMALevee_1 (Sacramento, San Joaquin Counties)</citation-url-name>
         </lineage-source>
         <lineage-source cc-id="1362594">
            <citation-title>USGS GeoTIFF Files - CA_FEMALevee_2 (San Bernardino County)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/OPR/Projects/CA_FEMALevee_D23/CA_FEMALevee_2_D23/TIFF/</citation-url>
            <citation-url-name>USGS GeoTIFF files for CA_FEMALevees_2 (San Bernardino County)</citation-url-name>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1362595">
            <sequence-number>1</sequence-number>
            <description>Raw Data and Boresight Processing: 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 NV5 Geospatial proprietary and commercial 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 technicians then analyzed the results and made any necessary additional adjustment until it was 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 matched 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 checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met.</description>
            <process-date-time>2023-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1362596">
            <sequence-number>2</sequence-number>
            <description>LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.5 feet was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper us used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.</description>
            <process-date-time>2023-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1362597">
            <sequence-number>3</sequence-number>
            <description>Maximum Surface Height Rasters were produced as ancillary data from the classified lidar point cloud in order to evaluate the withheld bit flag proof of performance for points that cannot be reasonably interpreted as valid surface returns. These were produced using all returns, withheld flagged points excluded, and using the highest elevation point value from each pixel. These rasters are 32-bit, floating point format and delivered as GeoTIFF files per tile. MSHR are generated from the point cloud data and will not be altered after creation nor will there be further maintenance on this product.</description>
            <process-date-time>2023-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1362598">
            <sequence-number>4</sequence-number>
            <description>Swath Separation Imagery was produced for the entire project area. Swath separation images use color-coding to illustrate differences in elevation (z-) values where swaths overlap. The color-coded images are semi-transparent and overlay the lidar intensity image. They are ancillary data used as visual aids to more easily identify regions within point cloud datasets that may have suspect interswath alignment or other geometric issues. Imagery was created using last returns with all classification and bit flags, except for noise and withheld bit flag are included. SSI are generated from the point cloud data and will not be altered after creation nor will there be further maintenance on this product.</description>
            <process-date-time>2023-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1362599">
            <sequence-number>5</sequence-number>
            <description>Hydro-Flattened Raster DEM Processing: Class 2 (Ground) LiDAR points in conjunction with the hydro-breaklines were used to create a 0.5 meter hydro-flattened raster DEM. Using automated scripting routines in proprietary software, GeoTIFF files were created for each tile. Each surface was reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface.</description>
            <process-date-time>2023-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1362600">
            <sequence-number>6</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://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/OPR/Projects/CA_FEMALevee_D23/CA_FEMALevee_1_D23/TIFF/
https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/OPR/Projects/CA_FEMALevee_D23/CA_FEMALevee_2_D23/TIFF/</description>
            <process-date-time>2024-12-27T00: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>74205</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2023 FEMA Lidar: California Levees</title>
         <relationship-type>Cross Reference</relationship-type>
      </related-item>
   </related-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:74267</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2024-12-27T20:09:06</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>2024-12-27</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>2024-12-20</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2025-12-20</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
