Loss estimation for landslides in mountain areas – An integrated toolbox for vulnerability assessment and damage documentation

Global environmental change includes changes in a wide range of global scale phenomena, which are expected to affect a number of physical processes, as well as the vulnerability of the communities that will experience their impact. Decision-makers are in need of tools that will enable them to assess the loss of such processes under different future scenarios and to design risk reduction strategies. In this paper, a tool is presented that can be used by a range of end-users (e.g. local authorities, decision makers, etc.) for the assessment of the monetary loss from future landslide events, with a particular focus on torrential processes. The toolbox includes three functions: a) enhancement of the post-event damage data collection process, b) assessment of monetary loss of future events and c) continuous updating and improvement of an existing vulnerability curve by adding data of recent events. All functions of the tool are demonstrated through examples of its application.

Overthrowing the Tyranny of Alphabetical Ordering in Documentation Systems

Software developers are often unsure of the exact name of the API method they need to use to invoke the desired behavior. Most state-of-the-art documentation browsers present API artefacts in alphabetical order. Albeit easy to implement, alphabetical order does not help much: if the developer knew the name of the required method, he could have just searched for it in the first place. In a context where multiple projects use the same API, and their source code is available, we can improve the API presentation by organizing the elements in the order in which they are more likely to be used by the developer. Usage frequency data for methods is gathered by analyzing other projects from the same ecosystem and this data is used then to improve tools. We present a preliminary study on the potential of this approach to improve the API presentation by reducing the time it takes to find the method that implements a given feature. We also briefly present our experience with two proof-of-concept tools implemented for Smalltalk and Java.

Proposals for Specific Activities of the Basic Mandate and Priority Action Projects, 2nd round 2005: Documentation for the ESAPP Advisory Board Meeting of June 15th, 2005

Budget frame-figures for 2nd half 2005; priority listing of proposals for PAP 2nd round 2005; evaluation sheets of approved, revised and rejected proposals for Specific Activities of the BM and PAP.

The 1987 debris flows in Switzerland: documentation and analysis

A great number of debris flows occurred during the flood catastrophes of the summer of 1987 in the Swiss Alps. Aerial photography, field investigations and eyewitness accounts documented and analysed the events. As an example of the reconstructed major events, the large debris flow in the Varuna valley involved an estimated peak discharge between 400 and 800 m3/s and an event magnitude of 200,000 m3. Several single pulses were observed; the duration of each of them appeared to be not more than a few minutes. Apart from incision into weak bedrock, the maximum erosion depth seemed to depend on the channel gradient. Based on approximately 600 events, typical starting zones and rainfall conditions are discussed with regard to the triggering conditions. Existing and new empirical formulae are proposed to estimate the most important flow parameters. These values are compared to debris flow data from Canada and Japan.