<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE metadata SYSTEM "http://thor-f5.er.usgs.gov/ngtoc/metadata/fgdc-std-001-1998.dtd">
<metadata>
 <idinfo>
  <citation>
   <citeinfo>
    <origin>Sanborn Map Company, Inc.</origin>
    <pubdate>20240201</pubdate>
    <title>Anne Arundel, MD Lidar; Raw Point Cloud</title>
    <geoform>Lidar point cloud</geoform>
   </citeinfo>
  </citation>
  <descript>
   <abstract>Product: These lidar data are processed LAS 1.4 files, formatted to 36 individual LAS files.
   	Geographic Extent: Anne Arundel county, Maryland; covering approximately 459 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.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification.
   	The data was developed based on a horizontal projection/datum of NAD83 HARN, Maryland Feet, and vertical datum of NAVD88 (GEOID12B) Feet. Lidar data was delivered as flightline-extent unclassified LAS swaths and as processed Classified LAS 1.4 files, formatted to 619 individual tiles as tiled bare-earth DEMs; tiled to the 4000 ft x 6000 ft schema.
   	Ground Conditions: Lidar was collected in March 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 50 independent accuracy check points, 30 in Bare Earth and Urban landcovers (30 NVA points), 20 in Tall Grass and Brushland/Low Trees categories (20 VVA points). These were used to assess the vertical accuracy of 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 ft cell size.
    These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
   <supplinf>Sanborn Map Company, Inc. </supplinf>
   <lidar>
    <ldrinfo>
     <ldrspec>U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification</ldrspec>
     <ldrsens>Leica TerrainMapper</ldrsens>
     <ldrmaxnr>15</ldrmaxnr>
     <ldrnps>0.34</ldrnps>
     <ldrdens>8.8</ldrdens>
     <ldranps>0.29</ldranps>
     <ldradens>12.1</ldradens>
     <ldrfltht>2000</ldrfltht>
     <ldrfltsp>150</ldrfltsp>
     <ldrscana>40</ldrscana>
     <ldrscanr>150</ldrscanr>
     <ldrpulsr>1800</ldrpulsr>
     <ldrpulsd>4</ldrpulsd>
     <ldrpulsw>0.47</ldrpulsw>
     <ldrwavel>1064</ldrwavel>
     <ldrmpia>1</ldrmpia>
     <ldrbmdiv>0.25</ldrbmdiv>
     <ldrswatw>1456</ldrswatw>
     <ldrswato>20</ldrswato>
     <ldrgeoid>National Geodetic Survey (NGS) Geoid12B</ldrgeoid>
    </ldrinfo>
    <ldraccur>
     <ldrchacc>0.5</ldrchacc>
     <rawnva>0</rawnva>
     <rawnvan>0</rawnvan>
    </ldraccur>
    <lasinfo>
     <lasver>1.4</lasver>
     <lasprf>6</lasprf>
     <laswheld>Withheld (ignore) points were not 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>11</lasintr>
     <lasclass>
      <clascode>0</clascode>
      <clasitem>Created, never classified</clasitem>
     </lasclass>
    </lasinfo>
   </lidar>
  </descript>
  <timeperd>
   <timeinfo>
    <rngdates>
     <begdate>20230316</begdate>
     <enddate>20230319</enddate>
    </rngdates>
   </timeinfo>
   <current>ground condition</current>
  </timeperd>
  <status>
   <progress>Complete</progress>
   <update>None planned</update>
  </status>
  <spdom>
   <bounding>
    <westbc>-76.84152377</westbc>
    <eastbc>-76.39126807</eastbc>
    <northbc>39.23869669</northbc>
    <southbc>38.71116818</southbc>
   </bounding>
   <lboundng>
   	<leftbc>1357552.87</leftbc>
   	<rightbc>1484753.39</rightbc>
   	<topbc>572560.41</topbc>
   	<bottombc>380962.83</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>Maryland</placekey>
    <placekey>Anne Arundel 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; GeoCue; Windows</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>
   <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 = 5.67 cm, equating to +/- 11.03 cm at 95% confidence level.</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>20231166_Anne_Arundel_MD_Survey</srcused>
    <procdate>2023</procdate>
   </procstep>
   <procstep>
    <procdesc>Data was tested at 0.29 meter aggregate nominal pulse spacing and at 12.1 aggregate points per meter. The aggregate nominal pulse spacing was tested on classified tiled LAS using geometrically reliable first-return points. ANPS was tested using Delaunay Triangulation that produced average point spacing between all nearest neighbors.</procdesc>
    <procdate>2023</procdate>
   </procstep>
  </lineage>
 </dataqual>
 <spdoinfo>
  <direct>Point</direct>
   <ptvctinf>
  	<sdtsterm>
  		<sdtstype>Point</sdtstype>
  		<ptvctcnt>17,701,312,790</ptvctcnt>
  	</sdtsterm>
  </ptvctinf>
 </spdoinfo>
 <spref>
  <horizsys>
   <planar>
    <mapproj>
     <mapprojn>NAD 1983 HARN StatePlane Maryland FIPS 1900 Feet</mapprojn>
     <lambertc>
      <stdparll>38.3</stdparll>
      <stdparll>39.45</stdparll>
      <longcm>-77.0</longcm>
      <latprjo>37.66666666666666</latprjo>
      <feast>1312333.333333333</feast>
      <fnorth>0.0</fnorth>
     </lambertc>
    </mapproj>
    <planci>
     <plance>coordinate pair</plance>
     <coordrep>
      <absres>0.001</absres>
      <ordres>0.001</ordres>
     </coordrep>
     <plandu>feet</plandu>
    </planci>
   </planar>
   <geodetic>
    <horizdn>North American 1983 HARN</horizdn>
    <ellips>GRS 1980</ellips>
    <semiaxis>6378137.0</semiaxis>
    <denflat>298.257222101</denflat>
   </geodetic>
  </horizsys>
  <vertdef>
   <altsys>
    <altdatum>North American Vertical Datum of 1988, Geoid12B</altdatum>
    <altres>0.001</altres>
    <altunits>feet</altunits>
    <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
   </altsys>
  </vertdef>
 </spref>
 <metainfo>
  <metd>20240201</metd>
  <metrd>20240201</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>