<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>NV5 Geospatial</origin>
        <pubdate>20230129</pubdate>
        <title>CA_FEMALevee_D23, Work Unit 300456; Classified Point Cloud</title>
        <geoform>LiDAR point cloud</geoform>
      </citeinfo>
    </citation>
    <descript>
      <abstract>
       Product: These lidar data are processed Classified LAS 1.4 files, formatted to 2662 individual 1000 m x 1000 m tiles; used to create intensity images, 3D breaklines, hydro-flattened DEMs, and spatial metadata such as the maximum surface height rasters and swath seperation imagery as necessary.
       Geographic Extent: 1 counties in California, covering approximately 918 total square miles.
       Dataset Description: The CA_FEMALevee_D23, Work Unit 300456 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 Zone 11N, Meter and vertical datum of NAVD88 Geoid 18, Meter. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 2662 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.
       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.</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>
      <supplinf>Contract No. 140G0221D0012, Task Order No. 140G0223F0133; CONTRACTOR: NV5 Geospatial</supplinf>
      <lidar>
        <ldrinfo>
          <ldrspec>USGS-NGP Base Specification 2023 Rev. A</ldrspec>
          <ldrsens>Riegl VQ1560iiS</ldrsens>
          <ldrmaxnr>unlimited</ldrmaxnr>
          <ldrnps>8.0</ldrnps>
          <ldrdens>0.0</ldrdens>
          <ldranps>0.35</ldranps>
          <ldradens>8.16</ldradens>
          <ldrfltht>2532</ldrfltht>
          <ldrfltsp>145</ldrfltsp>
          <ldrscana>29</ldrscana>
          <ldrscanr>204</ldrscanr>
          <ldrpulsr>1534</ldrpulsr>
          <ldrpulsd>3</ldrpulsd>
          <ldrpulsw>0.46</ldrpulsw>
          <ldrwavel>1064</ldrwavel>
          <ldrmpia>1</ldrmpia>
          <ldrbmdiv>0.18</ldrbmdiv>
          <ldrswatw>2807.0</ldrswatw>
          <ldrswato>55</ldrswato>
          <ldrgeoid>Geoid 18</ldrgeoid>
          <ldrcrs>NAD 1983 2011 UTM Zone 11N, Meter</ldrcrs>
        </ldrinfo>
        <ldraccur>
          <ldrchacc>0</ldrchacc>
          <rawnva>0.0</rawnva>
          <rawnvan>0</rawnvan>
        </ldraccur>
        <lasinfo>
          <lasver>1.4</lasver>
          <lasprf>6</lasprf>
          <laswheld>Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.</laswheld>
          <lasolap>Any overage point deemed geometrically reliable will be used within the normal classification schema. Overage points are not specifically flagged with any special bit value.</lasolap>
          <lasintr>16</lasintr>
          <lasclass>
            <clascode>1</clascode>
            <clasitem>Processed, but Unclassified</clasitem>
          </lasclass>
          <lasclass>
            <clascode>2</clascode>
            <clasitem>Bare-Earth Ground</clasitem>
          </lasclass>
          <lasclass>
            <clascode>7</clascode>
            <clasitem>Low Noise</clasitem>
          </lasclass>
          <lasclass>
            <clascode>9</clascode>
            <clasitem>Water</clasitem>
          </lasclass>
          <lasclass>
            <clascode>17</clascode>
            <clasitem>Bridge Decks</clasitem>
          </lasclass>
          <lasclass>
            <clascode>18</clascode>
            <clasitem>High Noise</clasitem>
          </lasclass>
          <lasclass>
            <clascode>20</clascode>
            <clasitem>Ignored Ground</clasitem>
          </lasclass>
          </lasinfo>
      </lidar>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20230530</begdate>
          <enddate>20230615</enddate>
        </rngdates>
      </timeinfo>
      <current>Ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-117.220239897</westbc>
        <eastbc>-115.269071274</eastbc>
        <northbc>35.3369266501</northbc>
        <southbc>34.1963114084</southbc>
      </bounding>
      <lboundng>
        <leftbc>479985.405895</leftbc>
        <rightbc>657331.94643</rightbc>
        <topbc>3910407.98975</topbc>
        <bottombc>3785240.80709</bottombc>
      </lboundng>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Model</themekey>
        <themekey>LAS Point Cloud</themekey>
        <themekey>Remote Sensing</themekey>
        <themekey>Elevation Data</themekey>
        <themekey>Withheld Bit Flag Proof of Performance</themekey>
        <themekey>Swath Separation</themekey>
        <themekey>LiDAR</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>California</placekey>
        <placekey>San Bernardino 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 their limitations. Acknowledgement of the organization providing these data to the public would be appreciated for products derived from these data.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>NV5 Geospatial</cntorg>
          <cntper>Jackie Monge</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>523 Wellington Way</address>
          <city>Lexington</city>
          <state>KY</state>
          <postal>40503</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>859-277-8700</cntvoice>
        <cntfax>859-277-8901</cntfax>
        <cntemail>jackie.monge@nv5.com</cntemail>
        <hours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</hours>
        <cntinst>If unable to reach the contact by telephone, please send an email. You should get a response within 24 hours.</cntinst>
      </cntinfo>
    </ptcontac>
    <native>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
     </native>
  </idinfo>
  <dataqual>
    <logic>Data cover the entire area specified for this project.</logic>
    <complete>These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and the data pass Non-Vegetated Vertical Accuracy specifications.</complete>
    <posacc>
      <horizpa>
  	    <horizpar>This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a ___ (cm) RMSEx / RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- ___ cm 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>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>NV5 Geospatial</origin>
            <pubdate>20230129</pubdate>
            <title>Ground Control for the CA_FEMALevee_D23, Work Unit 300456 Project</title>
            <geoform>Vector digital data and tabular digital data</geoform>
            <pubinfo>
              <pubplace>NV5 Geospatial</pubplace>
              <publish>NV5 Geospatial</publish>
            </pubinfo>
            <othercit>None</othercit>
          </citeinfo>
        </srccite>
        <typesrc>external hard drive</typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>20230907</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>Ground condition</srccurr>
        </srctime>
        <srccitea>CA_FEMALevee_D23_Work_Unit_300456_gnd_ctrl</srccitea>
        <srccontr>This data source was used (along with airborne GPS/IMU data) to georeference the LiDAR point cloud data.</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>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.</procdesc>
        <srcused>CA_FEMALevee_D23_Work_Unit_300456_gnd_ctrl</srcused>
        <procdate>2023</procdate>
      </procstep>
      <procstep>
        <procdesc>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.</procdesc>
        <procdate>2023</procdate>
      </procstep>
      <procstep>
        <procdesc>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.</procdesc>
        <procdate>2023</procdate>
      </procstep>
      <procstep>
        <procdesc>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.</procdesc>
        <procdate>2023</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Point</direct>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>Universal Transverse Mercator</gridsysn>
          <utm>
            <utmzone>11</utmzone>
            <transmer>
              <sfctrmer>0.9996</sfctrmer>
              <longcm>-117</longcm>
              <latprjo>0.0</latprjo>
              <feast>500000</feast>
              <fnorth>0.0</fnorth>
            </transmer>
          </utm>
        </gridsys>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.001</absres>
            <ordres>0.001</ordres>
          </coordrep>
          <plandu>Meter</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>North American Datum of 1983 (2011)</horizdn>
        <ellips>Geodetic Reference System 80</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altdatum>NAVD88 Geoid 18</altdatum>
        <altres>0.001</altres>
        <altunits>Meter</altunits>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <metainfo>
    <metd>20240129</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>NV5 Geospatial</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>523 Wellington Way</address>
          <city>Lexington</city>
          <state>KY</state>
          <postal>40503</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>859-277-8700</cntvoice>
        <cntfax>859-277-8901</cntfax>
        <hours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</hours>
      </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>
