Lessons Learned: Development of a GIS based Landslide Hazard Management System

Size: px
Start display at page:

Download "Lessons Learned: Development of a GIS based Landslide Hazard Management System"

Transcription

1 Lessons Learned: Development of a GIS based Landslide Hazard Management System By Wael Zatar and Paulus Wahjudi (Marshall University) Lawrence Douglas and Hussein Elkhansa (WVDOT) Geohazards Forum August 6, 2015

2 2

3 3

4 4

5 Landslide issues Problems: Receiving Reports Locating and tracking landslides: fixed, paved over, new or old Funding allocation: proper respond and repair method Coordination and prioritization Accuracy of inventory 5

6 Challenges Data Collection Data Input Data Processing Data Analysis & Assessment Presenting the Information 6

7 Data Collection How are landslides being reported? Civilians State workers Landslide validation? Who should officially record it? County Workers? DOT employees? County Engineers? State Engineers? 7

8 Data Collection What data to collect? Address? Location? Driving Directions? Landmark? When to collect it? Is it time sensitive? Before and After Repair? Lesson Learned: Possible Points of failure 8

9 Web Application Framework Civilian Report Resolved and Tagged with comment Not a slide County Worker Report District Engineer Review Engineer Decision A slide Assigned a unique slide number & collect data Determine Action Calculate Hazard Rating 9

10 Data Input What is being recorded? What is pertinent to a landslide? Latitude & Longitude Date and Time Pictures Guardrails Type Condition Road Center Ditch location Utilities location ADT? Vegetation? Lesson Learned: Quantity Quality 10

11 11

12 Civilian Report 12

13 13

14 DOT Worker Report 14

15 Data Processing Data Storage Database needs to be compatible (and accessible) with other system Compatibility with GIS products (ESRI, Bentley s gint) Data Validation Post Processing Data review before submission to the database Supported format (shapefiles) Lesson Learned: Flexibility 15

16 Architecture Mobile Devices ArcCatalog ArcSDE API ArcMap MS SQL Server Web Application PC Table Feature Class Raster Dataset 16

17 Data Analysis From Data to Information What will it be used for? Historical Record Tracking Landslides Hazards Repairs Does it require additional data? Append new data over time New data pertaining to the slide (core boring, repair method) Lesson Learned: Focus on addressing the main problem 17

18 Hazard Rating Matrix Develop the hazard rating matrix that fits best for West Virginia Utilize 15 criteria with varying impact factor (1 5) 5: Very important 1: Least impact Four category with odd point scaling (1,3,5,7) 1 point: low risk 7 point: high risk Rating Calculation: Total points between 45 to 315 determines the risk 18

19 Hazard Rating Matrix Components 1. Potential Loss of life [5] 2. Average Daily Traffic [4] 3. Percent of Decision Sight Distance (% DSD) [4] 4. Emergency Route/School Bus Distance [3] 5. Impact to Road Structure and Adjacent Features (i.e., such as culverts, tunnels, bridge/flyover and their technical elements) [3] 6. Expected Damage to Structures (i.e. Building, Utilities, Railroad, and other Roads/Structure) [3] 19

20 Hazard Rating Matrix Components 7. Rate of Movement (inches/year) [3] 8. Amount of Surface Water (Hydrology) [3] 9. Posted Traffic Speed [3] 10. Detour Route Distance [3] 11. Length of Landslide [3] 12. Repair Cost [3] 13. Vertical & Horizontal Displacement of Scarp [2] 14. Annual Maintenance Cost [3] 15. Level of Ground Water (Hydrogeology) [1] 20

21 Data Analysis Tracking Landslides 21

22 Presenting the Information 22

23 Interactive Flex Map 23

24 24

25 25

26 26

27 Hazard Rating Matrix History 27

28 Thank you. Questions? 28