<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Watershed Sciences, Inc.</origin>
				<pubdate>2006</pubdate>
				<title>001.tif</title>
				<geoform>remote-sensing image</geoform>
				<onlink>\\WINXP\F$\sandy\Deliverables\Rasters\intensity_images\001.tif</onlink>
			</citeinfo>
		</citation>
		<descript>
			<abstract>The dataset encompasses the Sandy River from its mouth to just above Marmot Dam.  

Each intensity image depicts, at a 3-foot resolution, intensity values of the LiDAR laser returns.    

Watershed Sciences, Inc. collected the LiDAR and created this data set for Portland General Electric.</abstract>
			<purpose>Provide intensity images.</purpose>
			<supplinf>This data is assembled into processing bins.  This dataset is in the Oregon State Plane North Coordinate System, FIPS 3601, with units in the NAD83/NAVD88 datum.  Reference http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&amp;d=25687  for an explanation concerning the coordinate system displayed in the Spatial Metadata Section.</supplinf>
		</descript>
		<timeperd>
			<timeinfo>
				<sngdate>
					<caldate>REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.</caldate>
				</sngdate>
			</timeinfo>
			<current>ground condition</current>
		</timeperd>
		<status>
			<progress>Complete</progress>
			<update>None planned</update>
		</status>
		<spdom>
			<bounding>
				<westbc>
-122.425775</westbc>
				<eastbc>
-122.402291</eastbc>
				<northbc>
45.574485</northbc>
				<southbc>
45.570584</southbc>
			</bounding>
		</spdom>
		<keywords>
			<theme>
				<themekt>REQUIRED: Reference to a formally registered thesaurus or a similar authoritative source of theme keywords.</themekt>
				<themekey>LiDAR</themekey>
				<themekey>Light Detection and Ranging</themekey>
				<themekey>Intensity</themekey>
				<themekey>topography</themekey>
				<themekey>high-resolution</themekey>
				<themekey>intensity image</themekey>
				<themekey>intensity</themekey>
			</theme>
			<place>
				<placekey>Oregon</placekey>
				<placekey>Sandy River</placekey>
				<placekey>Pacific Northwest</placekey>
				<placekey>Troutdale</placekey>
				<placekey>Marmot Dam</placekey>
				<placekey>Cascades</placekey>
			</place>
		</keywords>
		<accconst>None.</accconst>
		<useconst>REQUIRED: Restrictions and legal prerequisites for using the data set after access is granted.</useconst>
		<ptcontac>
			<cntinfo>
				<cntorgp>
					<cntorg>Watershed Sciences, Inc.</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>215 SE 9th  Suite 106</address>
					<city>Portland</city>
					<state>OR</state>
					<postal>97214</postal>
					<country>USA</country>
				</cntaddr>
				<cntemail>watershedsciences.com</cntemail>
			</cntinfo>
		</ptcontac>
		<native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722</native>
	</idinfo>
	<dataqual>
		<logic>LiDAR flight lines have been examined to ensure that there was at least 50% sidelap, there are no gaps between flightlines, and overlapping flightlines have consistent elevation values.

Shaded relief images have been visually inspected for data errors such as pits, border artifacts, gaps, and shifting.  The data was examined at a 1:3500 scale.</logic>
		<complete>LiDAR data has been collected and processed for all areas within the project study area.</complete>
		<posacc>
			<horizpa>
				<qhorizpa>
					<horizpav>1/3000th AGL</horizpav>
					<horizpae>See LiDAR data report.</horizpae>
				</qhorizpa>
			</horizpa>
			<vertacc>
			</vertacc>
		</posacc>
		<lineage>
			<procstep>
				<procdesc>Acquisition.

The LiDAR data was collected on October 22, 2006.  This was a leaf-on condition.  A Leica ALS50 LiDAR system was mounted in a fixed-wing aircraft and flown 1100 meters above ground level (AGL).  A pulse rate  (PR) of 93 kHz with at least 100% overlap (minimum 50% side-lap) was used.  Greater than 4 points per square meter and near nadir scan angles were used to increase penetration of vegetation to ground surfaces.  Ground level GPS and aircraft IMU were collected during the flight.</procdesc>
			</procstep>
			<procstep>
				<procdesc>LiDAR Data Processing.

1. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points.
2. Laser point return coordinates were computed using ALS Post Processing software and IPAS based on independent data from the LiDAR system, IMU, and aircraft.
3. The raw LiDAR file was assembled into flight lines per return with each point having an associated x, y, and z coordinate.
4. Visual inspection of swath to swath laser point consistencies within the study area were used to perform manual refinements of system alignment.
5. Custom algorithms were designed to evaluate points between adjacent flight lines.  Automated system alignment was computed based upon randomly selected swath to swath accuracy measurements that consider elevation, slope, and intensities.  Specifically, refinement in the combination of system pitch, roll and yaw offset parameters optimize internal consistency.
6. Noise (e.g., pits and birds) was filtered using ALS postprocessing software,  based on known elevation ranges and included the removal of any cycle slips.
7. Using TerraScan and Microstation, ground classifications utilized custom settings appropriate to the study area.
8. The corrected and filtered return points were compared to the RTK ground survey points collected to verify the vertical and horizontal accuracies.
9.  Points were broken into processing bins and output areas and output per 5000 sq ft  as GeoTiffs, colored (0-255) by intensity values.</procdesc>
			</procstep>
			<procstep>
				<procdesc>Metadata imported.</procdesc>
				<srcused>C:\wills_templates\metadata_templates\sandy\intensity_metadata.xml</srcused>
			</procstep>
			<procstep>
				<procdesc>Metadata imported.</procdesc>
				<srcused>C:\wills_templates\metadata_templates\sandy\intensity_metadata.xml</srcused>
			</procstep>
			<procstep><procdesc Sync="TRUE">Metadata imported.</procdesc><srcused Sync="TRUE">C:\wills_templates\metadata_templates\sandy\intensity_metadata.xml</srcused><date Sync="TRUE">20061128</date><time Sync="TRUE">13525600</time></procstep></lineage>
	</dataqual>
	<spdoinfo>
		<direct>Raster</direct>
		<rastinfo>
			<rasttype>Pixel</rasttype>
			<rowcount>427</rowcount>
			<colcount>1995</colcount>
			<vrtcount>1</vrtcount>
		</rastinfo>
	</spdoinfo>
	<spref>
		<horizsys>
			<planar>
				<mapproj>
					<mapprojn>Lambert Conformal Conic</mapprojn>
					<lambertc>
						<stdparll>44.333333</stdparll>
						<stdparll>46.000000</stdparll>
						<longcm>-120.500000</longcm>
						<latprjo>43.666667</latprjo>
						<feast>8202099.737533</feast>
						<fnorth>0.000000</fnorth>
					</lambertc>
				</mapproj>
				<planci>
					<plance>row and column</plance>
					<coordrep>
						<absres>3.000000</absres>
						<ordres>3.000000</ordres>
					</coordrep>
					<plandu>international feet</plandu>
				</planci>
			</planar>
			<geodetic>
				<horizdn>North American Datum of 1983</horizdn>
				<ellips>Geodetic Reference System 80</ellips>
				<semiaxis>6378137.000000</semiaxis>
				<denflat>298.257222</denflat>
			</geodetic>
		</horizsys>
	</spref>
	<eainfo>
		<detailed>
			<enttyp>
				<enttypl>
Band_1</enttypl>
			</enttyp>
			<attr>
				<attrlabl>ObjectID</attrlabl>
				<attrdef>Internal feature number.</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<udom>Sequential unique whole numbers that are automatically generated.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>Value</attrlabl>
			</attr>
			<attr>
				<attrlabl>Count</attrlabl>
			</attr>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>
Band_2</enttypl>
			</enttyp>
			<attr>
				<attrlabl>ObjectID</attrlabl>
				<attrdef>Internal feature number.</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<udom>Sequential unique whole numbers that are automatically generated.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>Value</attrlabl>
			</attr>
			<attr>
				<attrlabl>Count</attrlabl>
			</attr>
		</detailed>
		<detailed>
			<enttyp>
				<enttypl>
Band_3</enttypl>
			</enttyp>
			<attr>
				<attrlabl>ObjectID</attrlabl>
				<attrdef>Internal feature number.</attrdef>
				<attrdefs>ESRI</attrdefs>
				<attrdomv>
					<udom>Sequential unique whole numbers that are automatically generated.</udom>
				</attrdomv>
			</attr>
			<attr>
				<attrlabl>Value</attrlabl>
			</attr>
			<attr>
				<attrlabl>Count</attrlabl>
			</attr>
		</detailed>
	</eainfo>
	<distinfo>
		<distrib>
			<cntinfo>
				<cntorgp>
					<cntorg>Watershed Sciences, Inc</cntorg>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>215 SE 9th  Suite 106</address>
					<city>Portland</city>
					<state>OR</state>
					<postal>97214</postal>
					<country>USA</country>
				</cntaddr>
				<cntemail>watershedsciences.com</cntemail>
			</cntinfo>
		</distrib>
		<resdesc>Downloadable Data</resdesc>
		<stdorder>
			<digform>
				<digtinfo>
					<transize>0.000</transize>
				</digtinfo>
			</digform>
		</stdorder>
	</distinfo>
	<metainfo>
		<metd>20061128</metd>
		<metc>
			<cntinfo>
				<cntorgp>
					<cntorg>Watershed Sciences, Inc.</cntorg>
					<cntper>REQUIRED: The person responsible for the metadata information.</cntper>
				</cntorgp>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
					<address>215 SE 9th  Suite 106</address>
					<city>Portland</city>
					<state>OR</state>
					<postal>97214</postal>
					<country>USA</country>
				</cntaddr>
				<cntvoice>REQUIRED: The telephone number by which individuals can speak to the organization or individual.</cntvoice>
				<cntemail>watershedsciences.com</cntemail>
			</cntinfo>
		</metc>
		<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
		<metstdv>FGDC-STD-001-1998</metstdv>
		<mettc>local time</mettc>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
		<metextns>
			<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
			<metprof>ESRI Metadata Profile</metprof>
		</metextns>
	</metainfo>
	<Esri><MetaID>{A4B2F9A8-8618-4292-B2C5-7F3DDB98FCC7}</MetaID><CreaDate>20061128</CreaDate><CreaTime>13525600</CreaTime><SyncOnce>TRUE</SyncOnce></Esri></metadata>
