Parent Layer: Landslide Data (SLIDO)

Name: Historic Landslides 1996_2000

Display Field: DATE

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: 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. 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. 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 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 goals of SLIDO Release 2 were 1) update SLIDOr1, 2) improve historically active landslide portion of the database through review of local municipality (city or county) data, 3) compile references that have detailed data on regionally significant or typical landslides, 4) add non-spatial data related to landslides such as landslide type, activity, certainty of identification, process, estimated age, etc. in specified areas, 5) populate and convene an Oregon Framework Implementation Team (FIT) landslide element subcommittee to develop standards for the statewide landslide theme. Also develop the landslide element stewardship standard.Historic landslide points were digitized from data from Hofmeister, R.L. (2000) and from data provided by the Oregon Department of Transportation (ODOT), the Federal Emergency Management Agency (FEMA), and the city of Portland. The points were then attributed and split into separate feature classes based on five year intervals.

Service Item Id: dc85a20913794bc2bded7f1dd68a3cb7

Copyright Text: William Burns, Ian Madin, Lina Ma, Katherine Mickelson, Evan Saint-Pierre

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 3969804.8999343812
YMin: 651793.509842515
XMax: 4550267.652230978
YMax: 967837.0895669311
Spatial Reference: 2914  (2914)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• REF_ID_COD ( type: esriFieldTypeString, alias: Reference ID Code, length: 50 )
• UNIQUE_ID ( type: esriFieldTypeString, alias: SLIDO Unique ID, length: 50 )
• DATA_SOURC ( type: esriFieldTypeString, alias: Data Source, length: 100 )
• LOC_METHOD ( type: esriFieldTypeString, alias: Data Location Method, length: 100 )
• ORIG_ID ( type: esriFieldTypeString, alias: Unique ID from Original Study, length: 25 )
• SLIDE_NAME ( type: esriFieldTypeString, alias: Landslide Name, length: 50 )
• DATE ( type: esriFieldTypeString, alias: DATE, length: 25 )
• LENGTH_ft ( type: esriFieldTypeSingle, alias: Lenght in Feet )
• WIDTH_ft ( type: esriFieldTypeSingle, alias: Width in Feet )
• DEPTH_ft ( type: esriFieldTypeSingle, alias: Depth in Feet )
• SLOPE ( type: esriFieldTypeSingle, alias: Slope in Degrees )
• TYPE_MOVE ( type: esriFieldTypeString, alias: Type of Movement, length: 50 )
• MOVE_CLASS ( type: esriFieldTypeString, alias: Movement Classification, length: 50 )
• CONTR_FACT ( type: esriFieldTypeString, alias: Factors Contributing to Slide, length: 100 )
• LOSSES ( type: esriFieldTypeSingle, alias: Losses in $ )
• TYPE_MTRL ( type: esriFieldTypeString, alias: TYPE_MTRL, length: 25 )
• AREA_ft2 ( type: esriFieldTypeSingle, alias: AREA_ft2 )
• VOLUME_ft3 ( type: esriFieldTypeSingle, alias: VOLUME_ft3 )
• DEEP_SHAL ( type: esriFieldTypeString, alias: DEEP_SHAL, length: 25 )
• Annual_Cost ( type: esriFieldTypeSingle, alias: Annual_Cost )
• Repair_Cost ( type: esriFieldTypeSingle, alias: Repair_Cost )
• COMMENTS ( type: esriFieldTypeString, alias: COMMENTS, length: 254 )
• DAMAGES ( type: esriFieldTypeString, alias: DAMAGES, length: 254 )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata