<?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>20200810</pubdate>
				<title>Gogebic AOI, Michigan; Hydro Flattened Breaklines</title>
				<geoform>vector data</geoform>
			</citeinfo>
		</citation>
		<descript>
			<abstract>Product: These lidar data are processed Classified LAS 1.4 files, formatted to 1046 individual 2500 ft x 2500 ft tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.
Geographic Extent: Gogebic AOI, Michigan, covering approximately 235 square miles. 
Dataset Description: Gogebic AOI, Michigan 2019 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 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane Coordinate System, international feet and vertical datum of NAVD88 (GEOID12B), international feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 1046 individual 2500 ft x 2500 ft tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 2500 ft x 2500 ft schema. 
Ground Conditions: Lidar was collected in spring 2019, 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 4 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 10 independent accuracy check points, 6 in Open Terrain/Bare-Earth and Urban landcovers (6 NVA points), 4 in Grass, Brush and Trees categories (4 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 2 ft 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>Breakline File Type = GDB
Breakline Elevation Units = International Feet
Downhill Treatment Applied = Monotonic
Type of Hydro Treatment Required = Hydro-flattened
			</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<rngdates>
					<begdate>20190521</begdate>
					<enddate>20200528</enddate>
				</rngdates>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>-90.426006</westbc>
				<eastbc>-89.869963</eastbc>
				<northbc>46.629204</northbc>
				<southbc>46.279124</southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>None</themekt>
				<themekey>Model</themekey>
				<themekey>Breaklines</themekey> 
				<themekey>Elevation Data</themekey>
				<themekey>Lidar</themekey>
			</theme>
			<place>
				<placekt>None</placekt>
				<placekey>Michigan</placekey>
				<placekey>Gogebic AOI</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 the BPA specified for this project. Breaklines were collected in all inland ponds and lakes ~2 acres or greater. These features were flat and level water bodies at a single elevation for each vertex along the bank. The entire water surface edge is at or below the immediate surrounding terrain. Breaklines were collected for all streams and rivers ~100' nominal width or wider. These features are flat and level bank to bank, gradient will follow the surrounding terrain and the water surface will be at or below the surrounding terrain. Streams/river channels will break at culvert locations however not at elevated bridge locations. </logic>
		<complete>All files are inspected to ensure that they conform to the specified file naming conventions, all files load in their correct geographic position, all files conform to the project specifications for file standard and content.</complete>
		<lineage>
			<procstep>
				<procdesc>Hydro Flattening Breakline Processing: Class 2 (ground) lidar points were used to create a bare-earth surface model. The surface model was then used to heads-up digitize 2D breaklines of inland streams and rivers with a 100 foot nominal width and Inland Ponds and Lakes of 2 acres or greater surface area. Elevation values were assigned to all Inland Ponds and Lakes, Inland Pond and Lake Islands, Inland Stream and River Islands, using LP360 functionality. Elevation values were assigned to all Inland streams and rivers using LP360 functionality. All ground (ASPRS Class 2) lidar data inside of the collected inland breaklines were then classified to water (ASPRS Class 9) using LP360 functionality. A buffer of 2 feet was also used around each hydro-flattened feature. These points were moved from ground (ASPRS Class 2) to Ignored Ground (ASPRS Class 20). The breakline files were then translated to ESRI File-Geodatabase format using ESRI conversion tools. Breaklines are reviewed against lidar intensity imagery to verify completeness of capture. All breaklines are then compared to TINs (triangular irregular networks) created from ground only points prior to water classification. The horizontal placement of breaklines is compared to terrain features and the breakline elevations are compared to lidar elevations to ensure all breaklines match the lidar within acceptable tolerances. Some deviation is expected between breakline and lidar elevations due to monotonicity, connectivity, and flattening rules that are enforced on the breaklines. Once completeness, horizontal placement, and vertical variance is reviewed, all breaklines are reviewed for topological consistency and data integrity using a combination of ESRI Data Reviewer tools and proprietary tools.</procdesc>
				<procdate>20200810</procdate>
			</procstep>
		</lineage>
	</dataqual>
	<spdoinfo>
		<direct>Vector</direct>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<gridsys>
					<gridsysn>State Plane Coordinate System 1983</gridsysn>
					<spcs>
						<spcszone>2111</spcszone>
						<transmer>
							<sfctrmer>0.9999</sfctrmer>
							<longcm>-87</longcm>
							<latprjo>44.78333333333333</latprjo>
							<feast>26246719.16</feast>
							<fnorth>0</fnorth>
						</transmer>
					</spcs>
				</gridsys>
				<planci>
					<plance>coordinate pair</plance>
					<coordrep>
						<absres>0.001</absres>
						<ordres>0.001</ordres>
					</coordrep>
					<plandu>feet</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>NAD83_National_Spatial_Reference_System_2011</horizdn>
				<ellips>GRS 1980</ellips>
				<semiaxis>6378137</semiaxis>
				<denflat>298.257222101</denflat>
			</geodetic>
		</horizsys>
		<vertdef>
			<altsys>
				<altdatum>North American Vertical Datum of 1988</altdatum>
				<altres>0.001</altres>
				<altunits>feet</altunits>
				<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
			</altsys>
		</vertdef>
	</spref>
	<metainfo>
		<metd>20200810</metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Sanborn Map Company, Inc.</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical</addrtype>
					<address>1935 Jamboree Drive</address>
					<address>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>
	</metainfo>
</metadata>