<?xml version="1.0" encoding="UTF-8"?>
<metadata xml:lang="en">
	<idinfo>
		<citation>
			<citeinfo>
				<origin>Oregon Department of Geology and Mineral Industries</origin>
				<pubdate>Unknown</pubdate>
				<othercit>Public domain.</othercit>
				<ftname Sync="TRUE">SLIDOv1</ftname><pubtime>Unknown</pubtime><geoform Sync="TRUE">vector digital data</geoform><serinfo><sername>Statewide Landslide Information Database of Oregon (SLIDO) Release 1</sername><issue>SLIDO Release 1</issue></serinfo><pubinfo><pubplace>Portland, Oregon</pubplace><publish>Oregon Department of Geology and Mineral Industries</publish></pubinfo><lworkcit><citeinfo><serinfo><sername>REQUIRED - wite out series name: Open-File Report, etc.</sername><issue>REQUIRED - use IMS, OFR, GMS, etc.</issue></serinfo><pubinfo><pubplace>Portland, Oregon</pubplace><publish>Oregon Department of Geology and Mineral Industries</publish></pubinfo></citeinfo></lworkcit><title Sync="TRUE">SLIDOv1</title><onlink Sync="TRUE">\\rocks\staff-public\Publications\NEW publications\FINAL COPY\SLIDO-1\for CD\GIS Files\SLIDOv1.shp</onlink></citeinfo>
		</citation>
		<descript>
			<abstract>One of the primary chronic and most devastating geologic hazards in Oregon is landslides.  Average annual repair costs for landslides in Oregon exceed $10 million and severe winter storm losses can exceed $100 million (Wang and others, 2002). As population growth continues to expand and development into increased landslide susceptible terrain occurs, greater losses are likely to result (Figure 1).   In order to begin reducing losses from landslides, large-scale endeavors are necessary at all community levels from state government to individual family homes.  One successful way to reduce losses from landslides is through pre-disaster mitigation, which can be performed at many scales from statewide to local.  To begin pre-disaster mitigation of landslides, the landslide hazard must be located (Figure 1).  Once the hazard is located the population and infrastructure vulnerable to the hazards can be identified and the risk mitigated.  

In order to improve our understanding of the landslide hazard in Oregon and to create a statewide base level of landslide data, this database of mapped landslides, the Statewide Landslide Information Database of Oregon (SLIDO) was created.  The four main objectives of this study were 1) identify previously mapped landslide deposits statewide, 2) improve the understanding of landslide hazards throughout Oregon, 3) improve the abilities of communities to begin effective landslide management and risk reduction activities, and 4) recommend future improvements and updates to the database.
The resulting database includes more than 15,000 landslide and landslide related features (polygons) extracted from 257 published and non-published studies.  The original studies vary widely in scale, scope and focus which is reflected in a wide range in the accuracy, detail and completeness with which landslides are mapped. </abstract>
			<purpose>In order to improve our understanding of the landslide hazard in Oregon and to create a statewide base level of landslide data, this database of mapped landslides, the Statewide Landslide Information Database of Oregon (SLIDO) was created.  The four main objectives of this study were 1) identify previously mapped landslide deposits statewide, 2) improve the understanding of landslide hazards throughout Oregon, 3) improve the abilities of communities to begin effective landslide management and risk reduction activities, and 4) recommend future improvements and updates to the database.</purpose>
			<langdata Sync="TRUE">en</langdata><supplinf>The resulting database includes more than 15,000 landslide and landslide related features (polygons) extracted from 257 published and non-published studies.  The original studies vary widely in scale, scope and focus which is reflected in a wide range in the accuracy, detail and completeness with which landslides are mapped.
SLIDO was created through the compilation of the best data available. Several limitations are worth noting, and underscore that any hazard map is generally useful for regional applications but should not be used as an alternative to site-specific studies in critical areas. 
1. Although it every effort was made to ensure that digitization and database entry were accurate and complete, no effort was made to verify the original data on which the compilation is based. Geologic data in the less populated eastern portions of the state were particularly limited in terms of scale, for example the 1:500,000 scale geologic map of the state was used in some locations.
2. As previously discussed, the developed database is from original sources that vary in scale, original purpose of mapping, available tools at the time of mapping, and background and interpretation by original mapper.  These factors all affect the level of detail and accuracy of the landslides.
4.  We neither collected, nor analyzed any new data to create this map. Therefore, this database is a snapshot view of the current data.
Results of a recent study by DOGAMI and USGS geologists in a small study area in the Portland Hills (60 km2) found roughly 200 landslides using a LIDAR derived high resolution DEM (Table 3).  The same area also has roughly 300 mapped landslide points in the 1996-1997 storm event inventories.  SLIDO release-1 has roughly 50 landslides located in this same area, roughly 10 of which are from 1:24,000 scale geologic maps and roughly 40 from landslide specific mapping done in the 70's.  
Since this area (the small study area in the Portland Hills) of SLIDO release-1 was compiled from geologic mapping done at a relatively small scale, and other mapping performed specifically to locate landslides, the area is likely one of the areas that should be considered to have higher accuracy with regard to landslides.  The number of landslides in SLIDO release-1 within this small study area, compared to the LIDAR mapping would be roughly 25%.  Therefore, this percentage (~25%) should be considered an upper value of accuracy of SLIDO release-1 for most areas, except for the previously mentioned new landslide specific mapping (Lincoln County Coast and City of Oregon City) recently completed by DOGAMI.  In conclusion, most of SLIDO release-1 should be considered to have located between 0% - 25% of the actual landslides at any location.</supplinf></descript>
		<timeperd>
			<timeinfo>
				<sngdate>
					<caldate>unknown</caldate>
				</sngdate>
			</timeinfo>
			<current>publication date</current>
		</timeperd>
		<status>
			<progress>Planned</progress>
			<update>Unknown</update>
		</status>
		<spdom>
			<bounding>
				<westbc Sync="TRUE">-124.801620</westbc><eastbc Sync="TRUE">-116.406080</eastbc><northbc Sync="TRUE">46.274057</northbc><southbc Sync="TRUE">41.926115</southbc></bounding>
			<lboundng><leftbc Sync="TRUE">223091.623031</leftbc><rightbc Sync="TRUE">2348897.736549</rightbc><bottombc Sync="TRUE">90768.883530</bottombc><topbc Sync="TRUE">1649259.199475</topbc></lboundng></spdom>
		<keywords>
			<theme>
				<themekt>None</themekt><themekey>Landslide</themekey><themekey>Oregon</themekey><themekey>GIS Database</themekey><themekey>Statewide </themekey><themekey>SLIDO</themekey></theme>
			<place><placekey>Oregon</placekey><placekey>Statewide</placekey></place></keywords>
		<useconst>Restrictions and legal prerequisites for using the data set after use is granted. These include any access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on using the data set. For example: Maps in this publication depict ???. The maps cannot serve as a substitute for site-specific investigations by qualified practitioners. Site-specific data may give results that differ from those shown on the maps.</useconst>
		<ptcontac>
			<cntinfo>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
				</cntaddr>
				<cntperp><cntper>William J. Burns</cntper><cntorg>Oregon Department of Geology and Mineral Industries</cntorg></cntperp><cntpos>Engineering Geologist</cntpos><cntvoice>971-673-1538</cntvoice><cntfax>971-673-1562</cntfax><cntemail>bill.burns@dogami.state.or.us</cntemail></cntinfo>
		</ptcontac>
		<accconst>DOGAMI makes no warranty as to the currency, completeness, accuracy or utility of any specific data.  This disclaimer applies both to individual use of the data and aggregate use with other data. It is strongly recommended that careful attention be paid to the contents of the metadata file associated with these data.</accconst><native Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350</native><natvform Sync="TRUE">Shapefile</natvform><browse><browsen>SLIDO Release 1</browsen></browse><datacred>Recognition of those who contributed to the data set.</datacred></idinfo>
	<dataqual>
		<lineage>
			<procstep>
				<procdesc>See report text for details.  In general: Paper or stable-based film copies of original reference geologic maps were collected.  Examination was made to ensure each original map had adequate map control  information to allow successful georeferencing.  Maps were scanned (color or grayscale) at 300 dots per inch and provided as tagged image format (tiff)  files.  Georeferencing was performed with Blue Marble Geographics Geographic Transformer.  This software allows entering numerous points to establish the basis for assigning world coordinates to the image coordinates.  The software calculates error on the fly, and all maps were processed with a tolerance of 1 pixel error.  In the processing, each map was projected with the same software into the Oregon Lambert Projection.  A decision was made regarding whether the map would be digitized 'heads-up' or go through further processing in a raster-to-vector program.  Able Software Co. R2V software was used for conversion.  While some map images could be processed directly in R2V, most maps were traced onto mylar.  The mylar was then scanned, georeferenced and projected.  The resulting image was then processed in R2V to yield linework.  Linework inspection was done to determine completeness and accuracy.  Finally, the linework was processed by a polygon building utility that runs in the MapInfo Professional GIS software.  Polygon and line attributing were then performed, with the resulting file appended into a master polygon file and separate fault line file and fold line file.
</procdesc>
			</procstep>
			<procstep><procdesc Sync="TRUE">Metadata imported.</procdesc><srcused Sync="TRUE">C:\Documents and Settings\deb schueller\Desktop\metadata-how-to\DOGAMI_General_Metadata_Template.xml</srcused><date Sync="TRUE">20080409</date><time Sync="TRUE">17070500</time></procstep><srcinfo><srccontr>See report text.</srccontr></srcinfo><procstep><procdesc Sync="TRUE">Metadata imported.</procdesc><srcused Sync="TRUE">E:\Bill_DOGAMI_General_Metadata.xml</srcused><date Sync="TRUE">20080415</date><time Sync="TRUE">17062300</time></procstep><procstep><procdesc Sync="TRUE">Metadata imported.</procdesc><srcused Sync="TRUE">S:\SLIDO - Statewide Landslide Information Database of Oregon\SLIDO Release 1 - Submit to Pubs\SLIDO version 1 - Resubmit to Pubs\Metadata\metadata.xml</srcused><date Sync="TRUE">20080430</date><time Sync="TRUE">11025000</time></procstep><procstep><procdesc Sync="TRUE">Dataset copied.</procdesc><srcused Sync="TRUE">S:\SLIDO - Statewide Landslide Information Database of Oregon\SLIDOv1</srcused><date Sync="TRUE">20080430</date><time Sync="TRUE">11031400</time></procstep></lineage>
		<attracc><attraccr>Attribute accuracy is very good for both the spatial and tabular databases.  Numerous queries were run to check accuracy and consistency of attribute information.  Queries were run separately and to compare the data sets against each other.  An iterative process was run to find discrepancies and then corrections were  made to the respective data sets to achieve consistency.
</attraccr></attracc><logic>MapInfo Professional version 8.0 does not establish data set topology. This version of MapInfo can check regions (polygons) for misalignment errors such as gaps (slivers), polygon overlaps, self intersections, and duplicate nodes. If found, these errors were corrected.</logic><posacc><horizpa><horizpar>Horizontal positional accuracy of this data equates to the original reference map scale.  The range of map scales used varies from 1:24,000 to 1:500,000.  This data set is predominantly the result of many raster-to-vector (R2V) data conversions performed on scanned images of paper maps.  Raster scanning of paper maps and the R2V process introduce some horizontal accuracy displacement.  This displacement has not been quantified.
</horizpar></horizpa><vertacc><vertaccr>not available</vertaccr></vertacc></posacc><complete>This digital dataset delineates the landslides throguhout Oregon.  The data is an  integration of 257 original reference geologic maps.  A data structure was developed that preserves the original  interpretations of each mapper.  
</complete></dataqual>
	<eainfo>
		<overview><eaover>Detailed summary of the information contained in a data set.</eaover><eadetcit>Reference to the complete description of the entity types, attributes, and attribute values for the data set.</eadetcit></overview><detailed Name="SLIDOv1"><enttyp><enttypl Sync="TRUE">SLIDOv1</enttypl><enttypt Sync="TRUE">Feature Class</enttypt><enttypc Sync="TRUE">15093</enttypc></enttyp><attr><attrlabl Sync="TRUE">FID</attrlabl><attalias Sync="TRUE">FID</attalias><attrtype Sync="TRUE">OID</attrtype><attwidth Sync="TRUE">4</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale><attrdef Sync="TRUE">Internal feature number.</attrdef><attrdefs Sync="TRUE">ESRI</attrdefs><attrdomv><udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom></attrdomv></attr><attr><attrlabl Sync="TRUE">Shape</attrlabl><attalias Sync="TRUE">Shape</attalias><attrtype Sync="TRUE">Geometry</attrtype><attwidth Sync="TRUE">0</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale><attrdef Sync="TRUE">Feature geometry.</attrdef><attrdefs Sync="TRUE">ESRI</attrdefs><attrdomv><udom Sync="TRUE">Coordinates defining the features.</udom></attrdomv></attr><attr><attrlabl Sync="TRUE">ID</attrlabl><attalias Sync="TRUE">ID</attalias><attrtype Sync="TRUE">Float</attrtype><attwidth Sync="TRUE">19</attwidth><atnumdec Sync="TRUE">11</atnumdec></attr><attr><attrlabl Sync="TRUE">REF_ID_COD</attrlabl><attalias Sync="TRUE">REF_ID_COD</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">50</attwidth></attr><attr><attrlabl Sync="TRUE">UNIQUE_ID</attrlabl><attalias Sync="TRUE">UNIQUE_ID</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">50</attwidth></attr><attr><attrlabl Sync="TRUE">MAP_UNIT_L</attrlabl><attalias Sync="TRUE">MAP_UNIT_L</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">50</attwidth></attr><attr><attrlabl Sync="TRUE">Shape_Leng</attrlabl><attalias Sync="TRUE">Shape_Leng</attalias><attrtype Sync="TRUE">Float</attrtype><attwidth Sync="TRUE">19</attwidth><atnumdec Sync="TRUE">11</atnumdec></attr><attr><attrlabl Sync="TRUE">Shape_Area</attrlabl><attalias Sync="TRUE">Shape_Area</attalias><attrtype Sync="TRUE">Float</attrtype><attwidth Sync="TRUE">19</attwidth><attrdef Sync="TRUE">Area of feature in internal units squared.</attrdef><attrdefs Sync="TRUE">ESRI</attrdefs><attrdomv><udom Sync="TRUE">Positive real numbers that are automatically generated.</udom></attrdomv><atnumdec Sync="TRUE">11</atnumdec></attr><attr><attrlabl Sync="TRUE">Descrip</attrlabl><attalias Sync="TRUE">Descrip</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">25</attwidth></attr></detailed></eainfo>
	<distinfo>
		<stdorder>
			<digform>
				<digtinfo>
					<transize Sync="TRUE">13.767</transize><dssize Sync="TRUE">13.767</dssize></digtinfo>
			</digform>
			<turnarnd>One week</turnarnd><fees>$25</fees></stdorder>
		<distliab>Although these data have been processed successfully on a computer system at the Oregon Department of Geology and Mineral Industries (DOGAMI), no warranty expressed or implied is made regarding the accuracy or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data. It is strongly recommended that these data are directly acquired from DOGAMI, and not indirectly through other sources which may have changed the data in some way. It is also strongly recommended that careful attention be paid to the contents of the metadata file associated with these data. The Oregon Department of Geology and Mineral Industries shall not be held liable for improper or incorrect use of the data described and/or contained herein.</distliab><resdesc>Spatial data files available in shape file (.shp) format (ESRI).</resdesc><distrib><cntinfo><cntorgp><cntorg>Nature of the Northwest Information Center</cntorg><cntper>Donald Haines</cntper></cntorgp><cntpos>Manager</cntpos><cntvoice>503-872-2750</cntvoice><cntfax>971-673-1562</cntfax><cntemail>don.haines@dogami.state.or.us</cntemail><hours>9 am to 5 pm PST</hours><cntaddr><addrtype>physical address</addrtype><address>800 N.E. Oregon Street, Suite 177</address><city>Portland</city><state>OR</state><postal>97232</postal><country>USA</country></cntaddr></cntinfo></distrib><techpreq>Geographic Information System software</techpreq></distinfo>
	<metainfo>
		<metc>
			<cntinfo>
				<cntaddr>
					<addrtype>mailing and physical address</addrtype>
				</cntaddr>
				<hours>8:30 am to 4:30 pm PST</hours>
				<cntvoice>971-673-1538</cntvoice><cntpos>Engineering Geologist</cntpos><cntfax>971-673-1562</cntfax><cntemail>bill.burns@dogami.state.or.us</cntemail><cntperp><cntper>William J. Burns</cntper><cntorg>Oregon Department of Geology and Mineral Industries</cntorg></cntperp></cntinfo>
		</metc>
		<metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn>
		<metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv>
		<mettc Sync="TRUE">local time</mettc>
		<langmeta Sync="TRUE">en</langmeta><metextns><metprof>TNC Metadata Profile (pending)</metprof></metextns><metd Sync="TRUE">20080626</metd><metextns><onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink><metprof Sync="TRUE">ESRI Metadata Profile</metprof></metextns></metainfo>
	<Esri><CreaDate>20080430</CreaDate><CreaTime>11031400</CreaTime><SyncOnce>FALSE</SyncOnce><SyncDate>20080626</SyncDate><SyncTime>13340900</SyncTime><ModDate>20080626</ModDate><ModTime>13340900</ModTime><MetaID>{E8A25A59-7855-4990-B5DC-79FFBC0CB027}</MetaID></Esri><dataIdInfo><envirDesc Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350</envirDesc><dataLang><languageCode Sync="TRUE" value="en"></languageCode></dataLang><idCitation><resTitle Sync="TRUE">SLIDOv1</resTitle><presForm><PresFormCd Sync="TRUE" value="005"></PresFormCd></presForm></idCitation><spatRpType><SpatRepTypCd Sync="TRUE" value="001"></SpatRepTypCd></spatRpType><dataExt><geoEle><GeoBndBox esriExtentType="native"><westBL Sync="TRUE">223091.623031</westBL><eastBL Sync="TRUE">2348897.736549</eastBL><northBL Sync="TRUE">1649259.199475</northBL><southBL Sync="TRUE">90768.88353</southBL><exTypeCode Sync="TRUE">1</exTypeCode></GeoBndBox></geoEle></dataExt><geoBox esriExtentType="decdegrees"><westBL Sync="TRUE">-124.80162</westBL><eastBL Sync="TRUE">-116.40608</eastBL><northBL Sync="TRUE">46.274057</northBL><southBL Sync="TRUE">41.926115</southBL><exTypeCode Sync="TRUE">1</exTypeCode></geoBox></dataIdInfo><mdLang><languageCode Sync="TRUE" value="en"></languageCode></mdLang><mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName><mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer><mdChar><CharSetCd Sync="TRUE" value="004"></CharSetCd></mdChar><mdHrLv><ScopeCd Sync="TRUE" value="005"></ScopeCd></mdHrLv><mdHrLvName Sync="TRUE">dataset</mdHrLvName><distInfo><distributor><distorTran><onLineSrc><orDesc Sync="TRUE">002</orDesc><linkage Sync="TRUE">file://\\rocks\staff-public\Publications\NEW publications\FINAL COPY\SLIDO-1\for CD\GIS Files\SLIDOv1.shp</linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc><transSize Sync="TRUE">13.767</transSize></distorTran><distorFormat><formatName Sync="TRUE">Shapefile</formatName></distorFormat></distributor></distInfo><spdoinfo><direct Sync="TRUE">Vector</direct><ptvctinf><esriterm Name="SLIDOv1"><efeatyp Sync="TRUE">Simple</efeatyp><efeageom Sync="TRUE">Polygon</efeageom><esritopo Sync="TRUE">FALSE</esritopo><efeacnt Sync="TRUE">15093</efeacnt><spindex Sync="TRUE">TRUE</spindex><linrefer Sync="TRUE">FALSE</linrefer></esriterm><sdtsterm Name="SLIDOv1"><sdtstype Sync="TRUE">G-polygon</sdtstype><ptvctcnt Sync="TRUE">15093</ptvctcnt></sdtsterm></ptvctinf></spdoinfo><spref><horizsys><cordsysn><geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn><projcsn Sync="TRUE">NAD_1983_Oregon_Statewide_Lambert_Feet_Intl</projcsn></cordsysn><planar><planci><plance Sync="TRUE">coordinate pair</plance><plandu Sync="TRUE">international feet</plandu><coordrep><absres Sync="TRUE">0.000000</absres><ordres Sync="TRUE">0.000000</ordres></coordrep></planci><mapproj><mapprojn Sync="TRUE">Lambert Conformal Conic</mapprojn><lambertc><stdparll Sync="TRUE">43.000000</stdparll><stdparll Sync="TRUE">45.500000</stdparll><longcm Sync="TRUE">-120.500000</longcm><latprjo Sync="TRUE">41.750000</latprjo><feast Sync="TRUE">1312335.958005</feast><fnorth Sync="TRUE">0.000000</fnorth></lambertc></mapproj></planar><geodetic><horizdn Sync="TRUE">North American Datum of 1983</horizdn><ellips Sync="TRUE">Geodetic Reference System 80</ellips><semiaxis Sync="TRUE">6378137.000000</semiaxis><denflat Sync="TRUE">298.257222</denflat></geodetic></horizsys></spref><refSysInfo><RefSystem><refSysID><identCode Sync="TRUE">NAD_1983_Oregon_Statewide_Lambert_Feet_Intl</identCode></refSysID></RefSystem></refSysInfo><spatRepInfo><VectSpatRep><topLvl><TopoLevCd Sync="TRUE" value="001"></TopoLevCd></topLvl><geometObjs Name="SLIDOv1"><geoObjTyp><GeoObjTypCd Sync="TRUE" value="001"></GeoObjTypCd></geoObjTyp><geoObjCnt Sync="TRUE">15093</geoObjCnt></geometObjs></VectSpatRep></spatRepInfo><mdDateSt Sync="TRUE">20080626</mdDateSt></metadata>
