<?xml-stylesheet type="text/xsl" href="fgdc_classic.xsl"?>

<metadata>
 <idinfo>
  <citation>
   <citeinfo>
    <origin>Sanborn Map Company, Inc.</origin>
    <pubdate>20240109</pubdate>
    <title>NY_Hudson_1_D22; 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 4025 individual 1500 m x 1500 m tiles clipped to the DPA; used to create intensity images, 3D breaklines, hydro-flattened DEMs, and all-return MSHRs as necessary.
   	Geographic Extent: Columbia, Jefferson, Lewis, Rensselaer, Saratoga, Warren, and Washington Counties New York, covering approximately 3279 square miles. Dataset Description: The 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.7 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), UTM Zone 18N, Meters and vertical datum of NAVD88 (GEOID18), Meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 4025 individual 1500 m x 1500 m tiles clipped to the DPA, as tiled intensity images, as tiled bare-earth DEMs, as tiled all-return MSHRs; all tiled to the same 1500 m x 1500 m schema.
   	Ground Conditions: Lidar was collected in fall 2022 and spring 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, Sanborn Map Company, Inc., established a total of 41 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area.
   	An additional 139 independent accuracy check points, 96 in Bare Earth and Urban landcovers (96 NVA points), 43 in Tall Grass and Brushland/Low Trees categories (43 VVA points), were used to assess the vertical accuracy of the data. These check points 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 1 m cell size.
    These lidar point cloud data were used to create intensity images, 3D breaklines, hydro-flattened DEMs, and all-return MSHRs as necessary.</purpose>
   <supplinf>CONTRACTOR: Sanborn Map Company, Inc.</supplinf>
   <lidar>
    <ldrinfo>
     <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification 2022, Revision A</ldrspec>
     <ldrsens>Leica TerrainMapper</ldrsens>
     <ldrmaxnr>1</ldrmaxnr>
     <ldrnps>0.66</ldrnps>
     <ldrdens>2.23</ldrdens>
     <ldranps>0.52</ldranps>
     <ldradens>3.6</ldradens>
     <ldrfltht>3350</ldrfltht>
     <ldrfltsp>160</ldrfltsp>
     <ldrscana>15</ldrscana>
     <ldrscanr>86.9</ldrscanr>
     <ldrpulsr>730</ldrpulsr>
     <ldrpulsd>4</ldrpulsd>
     <ldrpulsw>0.78</ldrpulsw>
     <ldrwavel>1064</ldrwavel>
     <ldrmpia>1</ldrmpia>
     <ldrbmdiv>0.25</ldrbmdiv>
     <ldrswatw>2439</ldrswatw>
     <ldrswato>20</ldrswato>
     <ldrgeoid>National Geodetic Survey (NGS) Geoid18</ldrgeoid>
    </ldrinfo>
    <ldrinfo>
     <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification 2022, Revision A</ldrspec>
     <ldrsens>Riegl VQ-1560 II</ldrsens>
     <ldrmaxnr>1</ldrmaxnr>
     <ldrnps>0.67</ldrnps>
     <ldrdens>2.2</ldrdens>
     <ldranps>0.52</ldranps>
     <ldradens>3.6</ldradens>
     <ldrfltht>2190</ldrfltht>
     <ldrfltsp>170</ldrfltsp>
     <ldrscana>58.52</ldrscana>
     <ldrscanr>178</ldrscanr>
     <ldrpulsr>856</ldrpulsr>
     <ldrpulsd>4</ldrpulsd>
     <ldrpulsw>0.41</ldrpulsw>
     <ldrwavel>1064</ldrwavel>
     <ldrmpia>1</ldrmpia>
     <ldrbmdiv>0.25</ldrbmdiv>
     <ldrswatw>2453</ldrswatw>
     <ldrswato>20</ldrswato>
     <ldrgeoid>National Geodetic Survey (NGS) Geoid18</ldrgeoid>
    </ldrinfo>
    <ldraccur>
     <ldrchacc>0</ldrchacc>
     <rawnva>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>Swath "overage" points were not identified in these files using the standard LAS overlap bit.</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>20221108</begdate>
     <enddate>20230415</enddate>
    </rngdates>
   </timeinfo>
   <current>ground condition</current>
  </timeperd>
  <status>
   <progress>Complete</progress>
   <update>None planned</update>
  </status>
  <spdom>
   <bounding>
    <westbc>-76.08359028</westbc>
    <eastbc>-73.21516608</eastbc>
    <northbc>44.26170203</northbc>
    <southbc>41.97111802</southbc>
   </bounding>
   <lboundng>
   	<leftbc>4901000.000</leftbc>
   	<rightbc>4648000.000</rightbc>
   	<topbc>413500.000</topbc>
   	<bottombc>642500.000</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>Lidar</themekey>
   </theme>
   <place>
    <placekt>None</placekt>
    <placekey>New York</placekey>
    <placekey>Columbia County</placekey>
    <placekey>Jefferson County</placekey>
    <placekey>Lewis County</placekey>
    <placekey>Rensselaer County</placekey>
    <placekey>Saratoga County</placekey>
    <placekey>Warren County</placekey>
    <placekey>Washington 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>
  <native>Leica HexMap; Riegl RiProcess; GeoCue; Windows 10</native>
 </idinfo>
 <dataqual>
  <logic>Data covers the DPA 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 data passes Non-Vegetated Vertical Accuracy specifications.</complete>
 <posacc>
  <horizpa>
	<horizpar>This dataset 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 Accuract = +/- __cm at a 95% confidence level.</horizpar>
   </horizpa>
   <vertacc>
    <vertaccr>This data set was tested to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10cm RMSEz Vertical Accuracy Class.
    Actual NVA accuracy was found to be RMSEz = __cm, equating to +/- __cm at 95% confidence level. Actual VVA accuracy was found to be +/- __cm at the 95th percentile.</vertaccr>
   </vertacc> 
  </posacc>
  <lineage>
   <procstep>
    <procdesc>The boresight was completed prior to project execution. The following steps describe the Raw Data Processing process:
    1) Technicians processed the raw data to LAS format flight lines using the final GNSS/IMU solution. This LAS data set was used as source data for lidar matching.
    2) 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.
    3) Once all lifts were completed with lidar matching, 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 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths).
    4) The technicians ran a final vertical accuracy check of the flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification, and breaklines were collected for water features. Bare-earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</procdesc>
    <srcused>2467_USGS_NY_Hudson_Lidar_ControlSurvey</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 Class 2 (Ground) lidar data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Class 9 (Water) using LP360 functionality.
    A buffer of 1 m was also used around each hydro-flattened feature to classify these Class 2 (Ground) points to Class 20 (Ignored Ground). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the Class 2 (Ground) points were reclassified to the correct classification after the automated classification was completed. 
	All data was manually reviewed and any remaining artifacts removed using functionality provided by LP360, TerraScan and TerraModeler.
    Global Mapper was used as a final check of the bare-earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files. Sanborn Map Company, Inc. 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>Data was tested at 0.52 meter aggregate nominal pulse spacing and at 3.6 aggregate points per meter. The aggregate nominal pulse spacing was tested on classified tiled LAS using geometrically reliable first-return points without overlap. ANPS was tested using Delaunay Triangulation that produced average point spacing between all nearest neighbors.</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. Cell size of the MSHR is 1 m 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. Images are derived from a TIN and have a 50% transparent RGB layer over lidar intensity. Color intervals are as follows for QL2 data: 0-8cm, green; 8-16cm, yellow; >16cm, red. These files were produced as GeoTIFF tiles using a cell size of 2 m. 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>
   <procstep>
    <procdesc>Supplemental Project Information</procdesc>
    <srcused>lidar_gnd_ctrl</srcused>
    <procdate>2023</procdate>
   </procstep>
  </lineage>
 </dataqual>
 <spdoinfo>
  <direct>Point</direct>
   <ptvctinf>
  	<sdtsterm>
  		<sdtstype>Point</sdtstype>
  		<ptvctcnt>47,789,796,401</ptvctcnt>
  	</sdtsterm>
  </ptvctinf>
 </spdoinfo>
 <spref>
  <horizsys>
   <planar>
    <mapproj>
     <mapprojn>NAD 1983 2011 UTM Zone 18N</mapprojn>
     <transmer>
      <sfctrmer>0.9996</sfctrmer>
      <longcm>-75.0</longcm>
      <latprjo>0.0</latprjo>
      <feast>500000.0</feast>
      <fnorth>0.0</fnorth>
     </transmer>
    </mapproj>
    <planci>
     <plance>coordinate pair</plance>
     <coordrep>
      <absres>0.001</absres>
      <ordres>0.001</ordres>
     </coordrep>
     <plandu>meter</plandu>
    </planci>
   </planar>
   <geodetic>
    <horizdn>NAD 1983 2011</horizdn>
    <ellips>GRS 1980</ellips>
    <semiaxis>6378137.0</semiaxis>
    <denflat>298.257222101</denflat>
   </geodetic>
  </horizsys>
  <vertdef>
   <altsys>
    <altdatum>North American Vertical Datum of 1988, Geoid 18</altdatum>
    <altres>0.001</altres>
    <altunits>meter</altunits>
    <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
   </altsys>
  </vertdef>
 </spref>
 <metainfo>
  <metd>20240109</metd>
  <metrd>20240109</metrd>
  <metc>
   <cntinfo>
    <cntorgp>
     <cntorg>Sanborn Map Company, Inc.</cntorg>
    </cntorgp>
    <cntaddr>
     <addrtype>mailing and physical</addrtype>
     <address>1935 Jamboree Drive, Suite 100</address>
     <city>Colorado Springs</city>
     <state>CO</state>
     <postal>80920</postal>
     <country>USA</country>
    </cntaddr>
    <cntvoice>(866)726-2676</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>