﻿<?xml version="1.0" encoding="utf-8"?>
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Aero-Graphics, Inc.</origin>
        <pubdate>20231117</pubdate>
        <title>224853_UT_WestEast_7_B22 - West Desert South A WUID300370, Utah 2022 Lidar; Hydro Flattened Bare Earth DEM</title>
        <geoform>raster digital data</geoform>
      </citeinfo>
    </citation>
    <descript>
      <abstract>Product: These are Digital Elevation Model (DEM) data for WUID300370 as part of the required deliverables for the 224853_UT_WestEast_7_B22 - West Desert South A WUID300370, Utah 2022 Lidar project. Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 0.5 meter hydro-flattened Raster DEM.
  Geographic Extent: WUID300370 covering approximately 2,200 square miles. 
  Dataset Description: WUID300370, 224853_UT_WestEast_7_B22 - West Desert South A, Utah 2022 Lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification 2022, Revision A. The data was developed based on a horizontal projection/datum of NAD83 (2011), Universal Transverse Mercator Zone 12N, meters and vertical datum of NAVD88 (GEOID18), meters. Lidar data was delivered as processed Classified LAZ 1.4 files, formatted to 5,785 individual 1000 m x 1000 m tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs and DSMs; all tiled to the same 1000 m x 1000 m schema. 
  Ground Conditions: Lidar was collected in Summer and Fall 2022, 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, the Aero-Graphics Team, established a total of 13 ground control points that were used to calibrate the lidar to known ground locations established throughout the WUID300370 project area. An additional 41 independent accuracy checkpoints, 24 in Bare Earth and Urban landcovers (24 NVA points), 17 in Tall Grass and Brushland/Low Trees categories (17 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.</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 DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 0.5 meter cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
      <supplinf>
  USGS Contract No. G10PC01234 
  CONTRACTOR: Aero-Graphics, Inc. 
  SUBCONTRACTOR: Dewberry. 
  Lidar data were acquired and calibrated by Dewberry. All follow-on processing was completed by Dewberry.
  Raster File Type = GeoTIFF
  Bit Depth/Pixel Type = 32-bit float
  Raster Cell Size = 0.5 Meters
  Interpolation or Resampling Technique = Triangulated Irregular Network (TIN)
  Required Vertical Accuracy = 19.6 cm NVA
      </supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20220624</begdate>
          <enddate>20221031</enddate>
        </rngdates>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-114.073747</westbc>
        <eastbc>-112.815734</eastbc>
        <northbc>39.348061</northbc>
        <southbc>38.754951</southbc>
      </bounding>
      <lboundng>
        <leftbc>235023.639803</leftbc>
        <rightbc>342282.374195</rightbc>
        <topbc>4357000.000000</topbc>
        <bottombc>4294000.000000</bottombc>
      </lboundng>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Model</themekey>
        <themekey>Raster</themekey>
        <themekey>DEM</themekey>
        <themekey>Remote Sensing</themekey>
        <themekey>Elevation Data</themekey>
        <themekey>Lidar</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Utah</placekey>
        <placekey>UT</placekey>
        <placekey>Millard County</placekey>
      </place>
    </keywords>
    <accconst>No restrictions apply to these data.</accconst>
    <useconst>None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.</useconst>
  </idinfo>
  <dataqual>
    <logic>Data covers WUID300370 specified for this project.</logic>
    <complete>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 specifications. The reference dataset encompassing this area passed Non-Vegetated Vertical Accuracy specifications.</complete>
    <posacc>
      <horizpa>
        <horizpar>Only checkpoints photo-identifiable in the intensity imagery can be used to test the horizontal accuracy of the lidar. Photo-identifiable checkpoints in intensity imagery typically include checkpoints located at the ends of paint stripes on concrete or asphalt surfaces or checkpoints located at 90 degree corners of different reflectivity, e.g. a sidewalk corner adjoining a grass surface. The xy coordinates of checkpoints, as defined in the intensity imagery, are compared to surveyed xy coordinates for each photo-identifiable checkpoint. These differences are used to compute the tested horizontal accuracy of the lidar. As not all projects contain photo-identifiable checkpoints, the horizontal accuracy of the lidar cannot always be tested.
  
Lidar vendors calibrate their lidar systems during installation of the system and then again for every project acquired. Typical calibrations include cross flights that capture features from multiple directions that allow adjustments to be performed so that the captured features are consistent between all swaths and cross flights from all directions. This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 64 cm RMSEx/RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 1 meter at a 95% confidence level.</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <procstep>
        <procdesc>Hydro Flattened Raster DEM Process:  Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 0.5 meter hydro-flattened Raster DEM. Using LP360, a TIFF file was created for each tile. Each surface is reviewed using ArcMap to check for any surface anomalies or incorrect elevations found within the surface.</procdesc>
        <procdate>20230715</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Raster</direct>
    <rastinfo>
      <rasttype>Pixel</rasttype>
      <rowcount>2000</rowcount>
      <colcount>2000</colcount>
    </rastinfo>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>Universal Transverse Mercator</gridsysn>
          <utm>
            <utmzone>12</utmzone>
            <transmer>
              <sfctrmer>0.9996</sfctrmer>
              <longcm>-111.000000</longcm>
              <latprjo>0.000000</latprjo>
              <feast>500000</feast>
              <fnorth>0.000000</fnorth>
            </transmer>
          </utm>
        </gridsys>
        <planci>
          <plance>row and column</plance>
          <coordrep>
            <absres>0.500000</absres>
            <ordres>0.500000</ordres>
          </coordrep>
          <plandu>meters</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>North American Datum of 1983 (2011)</horizdn>
        <ellips>Geodetic Reference System 80</ellips>
        <semiaxis>6378137.000000</semiaxis>
        <denflat>298.257222</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altdatum>North American Vertical Datum of 1988, Geoid 18</altdatum>
        <altres>0.01</altres>
        <altunits>meters</altunits>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <metainfo>
    <metd>20231117</metd>
    <metrd>20231117</metrd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Aero-Graphics, Inc.</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>40 West Oakland Avenue</address>
          <city>Salt Lake City</city>
          <state>UT</state>
          <postal>84115</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>(801)487-3273</cntvoice>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <metac>None.</metac>
    <metuc>None.</metuc>
    <metsi>
      <metscs>None.</metscs>
      <metsc>Unclassified.</metsc>
      <metshd>None.</metshd>
    </metsi>
    <metextns>
      <onlink>None.</onlink>
      <metprof>None.</metprof>
    </metextns>
  </metainfo>
</metadata>