The LSI coverage is an Inventory of Landslides (Also Known As Mass Wasting Events). It has three related data tables: lsi_data, related by lsi_uniqid; lsi_src_dat; related through the lsi_data by source_idno; and lsi_dispute_dat (latter dataset currently unpopulated), related by lsi_uniqid.
To support the Landslide Hazard Zonation project, as well as to provide an ongoing, supported platform to place landslide information that is regularly collected by a variety of agencies, both public and private.
This dataset is intended for use in land management, planning, regulation, research and monitoring.
publication date
Washington State Department ot Natural Resources
Forest Practices Division
1111 Washington St. SE
P.O. Box 47012
Boyd and Vaugeois, 2003, On the Development of a Landslide Inventory, Geological Society of America Annual Meeting The WA-DNR initiated work on this project in 1999 by acquiring existing data and developing standardized data architectures for data compilation. The project received funding from an Interagency Contract. All available landslide inventories and mass wasting map units from watershed analysis were collected from the various landowners. Landslide inventories were also gathered from other agencies collecting this data outside the T/F/W watershed analysis arena, such as the USFS, tribal entities, and universities.
This data is a compilation of many different landslide datasets from a variety of authors, collecting information for several different purposes. At present, no statements can be made to the accuracy of the the attributes, other than due diligence was made in accurately portraying the information that the authors supplied. Information on the sources of the various datasets are in related tables (lsi_src_dat).
For landslide information collected by the Landslide Hazard Zonation Team, there are stated accuracy elements in related tables (lsi_data).
no tests have been made on the logical consistency of this dataset at present
This dataset is in the latter part of the compilation of data. Landslides are an ongoing phenomena, not static and as such, is not complete.
This data is a compilation of many different landslide datasets from a variety of authors, collecting information for several different purposes. At present, no statements can be made to the accuracy of the the attributes, other than due diligence was made in accurately portraying the information that the authors supplied. Information on the sources of the various datasets are in related tables (lsi_src_dat).
For data collected by the Landslide Hazard Zonation team, the mapping resolution is 1:12,000, from which a horizontal resolution of plus or minus 20 feet is inferred.
n/a
This data is a compilation of many different landslide datasets from a variety of authors, collecting information for several different purposes. Information on the sources of the various datasets are in the related table lsi_src_dat that is bundled with the dataset.
the compilation involved taking a variety of disparate data sources and normalizing them to a standard data architecture. current updates to the dataset involve using arcgis 8.x to spatially update (add or amend) the LSI coverage. Tolerances have been set at: dangle = 0, nodesnap, weed, and grain = 0.1, and snap = 1.
1111 Washington St SE
Washington State Department of Natural Resources
Forest Practices Division
1111 Washington St. S.E.
P.O. Box 47012
Metadata imported.
Dataset copied.
Dataset copied.
Metadata imported.
Metadata imported.
Feature geometry.
ESRI
unique value given to every landslide. note: landslides may have several parts. each part of the same landslide is assigned the same number. landslides can be nested (poly or line in poly issue). nested landslides are assigned different numbers.
LHZ project
what type of feature does this describe (e.g. headscarp, body, toe)
LHZ project
headscarp-a cuspate or linear escarpment that delineates the uppermost portion of a landslide
LHZ project
body of landslide
LHZ
toe-the distal end of a landslide, often lobate in shape with steep edges and a disrupted surface expression
LHZ project
runout-the path of destruction that follows a mobilized landsle as it moves downslope. typically, easily identified immediately following failure
lhz project
deposit-the location where the landslide material stopped moving
lhz project
presence in dispute-the presence of this landslide has been called into question
lhz project
non-landslide as agreed in dispute-if, after a dispute resolution, a landslide is found to not exist, then it will be coded as a non-landslide
lhz project
non-unique identifier assigned by the geologist, unique only for their study area
geologist derived
each set of landslide data is assigned a unique number so that we can relate it to LSI_src_dat to track where we got the information from
lhz project
describes the dominant type of landslide process described by this feature
lhz project protocol-modified from varnes
shallow rapid, undifferentiated
lhz project protocol
debris flow
lhz project protocol
debris slide/avalanche
lhz project protocol
deep-seated, undifferentiated
lhz project protocol
shallow, sporadic deep-seated (not used by LHZ protocol)
Watershed Analysis
Large, Persistent Deep-Seated (not used by LHZ project)
Watershed Analysis
earthflow
lhz project protocol
rock topple
lhz project protocol
snow avalanche
lhz project protocol
how certain the author was of the landslide identification
LHZ project
definite: author was certain that the feature identified was a landslide
LHZ Project Protocol
Probable: author was almost certain (probable) that the feature was a landslide
LHZ Project Protocol
Questionable: author was not certain that the feature was a landslide
LHZ Project Protocol
date of identification (typically, the photo year the landslide was identified on), throughout most of washington, slide scars are revegetated within 15 years
LHZ Project Protocol
estimated size of failure
watershed analysis
very small (1-100 square yds)
lhz project and watershed analysis
small (101-500 square yards)
lhz project and watershed analysis
medium (501-2000 sq. yards)
lhz project and watershed analysis
large (2001-5000 sq yards)
lhz project and watershed analysis
very large (greater than 5000 sq yds)
lhz project and watershed analysis
date of identification (typically, the photo year the landslide was identified on), some slides do not move again after initial movement
LHZ Project Protocol
name of the watershed administrative unit the data was collected in
either stated or compared with existing databases
what agency or entity supplied the data
LHZ Project
Name of the contact person who supplied the data
Self Identified
person who did the landslide inventory or hazard zone study
item: Name identified person
number of the source contact, including area code
self identified
Internal feature number.
ESRI
for deep-seated landslides only-how active is the landslide feature?
LHZ protocol-modified from the transportation research board
Active-Recent
LHZ protocol. further description of these values and how to interpret them are found in the protocol.
Dormant-distinct
LHZ protocol. further description of these values and how to interpret them are found in the protocol.
Dormant-Indistinct
LHZ protocol. further description of these values and how to interpret them are found in the protocol.
Relict-not related to current climatic conditions (e.g., post glacial slope relaxation)
LHZ protocol. further description of these values and how to interpret them are found in the protocol.
Feature geometry.
ESRI
each set of landslide data is assigned a unique number so that we can relate it to LSI_src_dat to track where we got the information from
lhz project
date of identification (typically, the photo year the landslide was identified on), some slides do not move again after initial movement
LHZ Project Protocol
estimated size of failure at a later time
watershed analysis
very small (1-100 square yards)
watershed analysis mass wasting module
small (101-500 square yards)
watershed analysis mass wasting module
medium (501-2000 sq. yrds)
watershed analysis mass wasting module
large (2001-5000 sq yds)
watershed analysis mass wasting module
very large (greater than 5000 sq yds)
watershed analysis mass wasting module
estimated size of failure
watershed analysis
very small (1-100 square yards)
watershed analysis mass wasting module
small (101-500 square yards)
watershed analysis mass wasting module
medium (501-2000 sq. yrds)
watershed analysis mass wasting module
large (2001-5000 sq yds)
watershed analysis mass wasting module
very large (greater than 5000 sq yds)
watershed analysis mass wasting module
the geomorphic feature (landform) the landslide occured on, if it occured on a known landform
LHZ project protocol
inner gorge
LHZ Project Protocol
bedrock hollow
LHZ Project Protocol
avalanche chute
LHZ Project Protocol
terrace face
LHZ Project Protocol
convergent headwall
LHZ Project Protocol
rock outcrop
LHZ Project Protocol
other
LHZ Project Protocol
deep-seated landslide
LHZ Project Protocol
stream influenced
LHZ Project Protocol
the planimetric shape of the slope on which the slide occurred
LHZ project
concave-convergent: curved like the inner surface of a ball
LHZ project protocol
concave-planar
LHZ project protocol
planar-a straight, uncurved slope
LHZ Project Protocol
convex-planar
lhz project protocol
convex-divergent: curved like the outer surface of a ball
lhz project protocol
the percent slope on which the landslide failed (Source: field, photo, or calculated from a DEM)
LHZ project Protocol
does the landslide deliver to a rule-identified public resource or threaten public safety ?
LHZ project and watershed analysis
yes, delivery occurred (visible or field evidence)
LHZ Project Protocol
no, analyst has visible or field evidence that delivery did not occur
LHZ Project Protocol
Probable: probable delivery occured (not visible, but proximal suggestive)
LHZ Project Protocol
Indeterminant as to whether delivery occured
LHZ Project Protocol
associated landuse or activity on site when failure was observed
lhz project protocol and watershed analysis
clearcut (timber 0-5 yrs)
lhz project and watershed analysis
young stands (timber 5-15 years)
lhz project and watershed analysis
submature timber (15-50 years)
lhz project and watershed analysis
mature timber (greater than 50 years)
lhz project and watershed analysis
road or culvert
lhz project and watershed analysis
partial cut
lhz project
yarding scar
lhz project
alpine area
lhz project
other (i.e. non-forest use, e.g., housing, agriculture)
lhz project and watershed analysis
elevation(in feet) of the landslide initiation site
LHZ and WSA protocols use topographic sheets or DEMs
the full photo number the slide was identified on (if appropriate)
lhz protocol uses the photo image
for deep-seated landslides only-what is the mechanical failure type
LHZ protocol-modified from Varnes
Rotational
LHZ protocol. further description of these values and how to interpret them are found in the protocol.
Translational
LHZ protocol. further description of these values and how to interpret them are found in the protocol.
Combination or Complex
LHZ protocol. further description of these values and how to interpret them are found in the protocol.
Earthflow
LHZ protocol. further description of these values and how to interpret them are found in the protocol.
the full photo number the slide was identified on (if appropriate)
lhz protocol uses the photo image
data source date of publication
data source map label
data source
code of data source used to relate tables in coverage
name of the watershed administrative unit the data was collected in
either stated or compared with existing databases
Washington State Department of Natural Resources
Forest Practices Division
1111 Washington St SE
P.O. Box 47012
The Washington State Department of Natural Resources (DNR) provides these geographic data "as is." DNR makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. DNR further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although these data have been processed successfully on computers of DNR, no warranty, expressed or implied, is made by DNR regarding the use of these data on any other system, nor does the fact of distribution constitute or imply any such warranty. In no event shall the DNR have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the geographic data or arising out of the delivery, installation, operation, or support by DNR.
http://www.dnr.wa.gov/BusinessPermits/Topics/ForestPracticesApplications/Pages/fp_gis_spatial_data.aspx
Due to staffing cutbacks, we can not fill custom orders. Information is provided in a downloadable data format only.
Washington State Department of Natural Resources
Forest Practices Division
1111 Washington St SE
P.O. Box 47012