<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing with OASIS Tables v3.0 20080202//EN" "journalpub-oasis3.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:oasis="http://docs.oasis-open.org/ns/oasis-exchange/table" dtd-version="3.0"><?xmltex \makeatother\@nolinetrue\makeatletter?>
  <front>
    <journal-meta>
<journal-id journal-id-type="publisher">NHESS</journal-id>
<journal-title-group>
<journal-title>Natural Hazards and Earth System Sciences</journal-title>
<abbrev-journal-title abbrev-type="publisher">NHESS</abbrev-journal-title>
<abbrev-journal-title abbrev-type="nlm-ta">Nat. Hazards Earth Syst. Sci.</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub">1684-9981</issn>
<publisher><publisher-name>Copernicus Publications</publisher-name>
<publisher-loc>Göttingen, Germany</publisher-loc>
</publisher>
</journal-meta>

    <article-meta>
      <article-id pub-id-type="doi">10.5194/nhess-16-103-2016</article-id><title-group><article-title>Assessing the performance of regional landslide <?xmltex \hack{\newline}?> early warning models: the EDuMaP method</article-title>
      </title-group><?xmltex \runningtitle{Performance of regional landslide early warning models: the EDuMaP method}?><?xmltex \runningauthor{M.~Calvello and L.~Piciullo}?>
      <contrib-group>
        <contrib contrib-type="author" corresp="no" rid="aff1">
          <name><surname>Calvello</surname><given-names>M.</given-names></name>
          
        <ext-link>https://orcid.org/0000-0002-3899-1722</ext-link></contrib>
        <contrib contrib-type="author" corresp="yes" rid="aff1">
          <name><surname>Piciullo</surname><given-names>L.</given-names></name>
          <email>lucapiciullo@gmail.com</email>
        <ext-link>https://orcid.org/0000-0003-3108-1256</ext-link></contrib>
        <aff id="aff1"><institution>Department of Civil Engineering, University of Salerno, Fisciano, Italy</institution>
        </aff>
      </contrib-group>
      <author-notes><corresp id="corr1">L. Piciullo (lucapiciullo@gmail.com)</corresp></author-notes><pub-date><day>18</day><month>January</month><year>2016</year></pub-date>
      
      <volume>16</volume>
      <issue>1</issue>
      <fpage>103</fpage><lpage>122</lpage>
      <history>
        <date date-type="received"><day>11</day><month>September</month><year>2015</year></date>
           <date date-type="rev-request"><day>8</day><month>October</month><year>2015</year></date>
           <date date-type="rev-recd"><day>14</day><month>December</month><year>2015</year></date>
           <date date-type="accepted"><day>22</day><month>December</month><year>2015</year></date>
      </history>
      <permissions>
<license license-type="open-access">
<license-p>This work is licensed under a Creative Commons Attribution 3.0 Unported License. To view a copy of this license, visit <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/3.0/">http://creativecommons.org/licenses/by/3.0/</ext-link></license-p>
</license>
</permissions><self-uri xlink:href="https://nhess.copernicus.org/articles/.html">This article is available from https://nhess.copernicus.org/articles/.html</self-uri>
<self-uri xlink:href="https://nhess.copernicus.org/articles/.pdf">The full text article is available as a PDF file from https://nhess.copernicus.org/articles/.pdf</self-uri>


      <abstract>
    <p>A schematic of the components of regional early warning systems for
rainfall-induced landslides is herein proposed, based on a clear distinction
between warning models and warning systems. According to this framework an
early warning system comprises a warning model as well as a monitoring and
warning strategy, a communication strategy and an emergency plan. The paper
proposes the evaluation of regional landslide warning models by means of an
original approach, called the “event, duration matrix,
performance” (EDuMaP) method, comprising three successive steps:
identification and analysis of the events, i.e., landslide events and
warning events derived from available landslides and warnings databases;
definition and computation of a duration matrix, whose elements
report the time associated with the occurrence of landslide events in
relation to the occurrence of warning events, in their respective classes;
evaluation of the early warning model performance by means of
performance criteria and indicators applied to the duration matrix. During
the first step the analyst identifies and classifies the landslide and
warning events, according to their spatial and temporal characteristics, by
means of a number of model parameters. In the second step, the analyst
computes a time-based duration matrix with a number of rows and columns
equal to the number of classes defined for the warning and landslide events,
respectively. In the third step, the analyst computes a series of model
performance indicators derived from a set of performance criteria, which
need to be defined by considering, once again, the features of the warning
model. The applicability, potentialities and limitations of the EDuMaP
method are tested and discussed using real landslides and warning data from
the municipal early warning system operating in Rio de Janeiro (Brazil).</p>
  </abstract>
    </article-meta>
  </front>
<body>
      

      <?xmltex \hack{\newpage}?>
<sec id="Ch1.S1" sec-type="intro">
  <title>Introduction</title>
      <p>In generic terms, early warning constitutes a process whereby information
generated from tailored observations of natural phenomena is provided to
communities at risk, or to institutions which are involved in emergency
response operations, so that certain tasks may be executed before a
catastrophic event impacts such communities (Villagrán de León et
al., 2013). Landslide early warning systems (LEWSs) mitigate the risk to
life associated with the occurrence of landslides by temporarily removing
people – i.e., the elements at risk – from hazardous areas whenever landslide
risk is considered to be unacceptable. According to Glade and Nadim (2014),
the installation of an early warning system is often a
cost-effective risk mitigation measure and in some instances the only
suitable option for sustainable management of disaster risks. Within the
landslide risk management framework proposed by Fell et al. (2005),
landslide early warning systems may be considered a non-structural passive
mitigation option to be employed in areas where risk, occasionally, rises
above previously defined acceptability levels.</p>
      <p>In the “priority for action 2” established by the Hyogo Framework for
Action – i.e., identify, assess and monitor disaster risks and enhance early
warning – the following key activity is identified: establish institutional
capacities to ensure that early warning systems are subject to regular
system testing and performance assessments (Hyogo Framework for Action,
2005). Despite the fact that the scientific literature reports many studies
on landslide early warning systems, either addressing a single landslide at
slope scale (Lollino et al., 2002; Blikra, 2008; Intrieri et al., 2012;
Michoud et al., 2013; Thiebes et al., 2013a; among others) or concurrent
phenomena in areas of relevant extension at municipal/regional/national
scale (NOAA-USGS (2005), Martelloni et al. (2012), Calvello et
al. (2015a, b), Stähli et al. (2015), Segoni et al. (2015), among others), no standard
requirements exist for assessing their performance. To this aim, many
questions need to be addressed, among which are the following: how are data of registered
landslides and warnings used to check on the performance of early warning
models? How are model errors quantified? How are false alerts (FAs) and missed
alerts (MAs)
defined when the warning model includes more than two warning levels? What
are the most relevant model performance indicators? All the previous
questions may be summed up; how should model validation be performed by
LEWSs managers? The answer to this question is not trivial, despite
what it may seem at first sight.</p>
      <p>The performance quantification issue is often overlooked, both by system
managers and by researchers dealing with warning models for LEWSs. For
instance, the main focus of researchers dealing with warning systems for
rainfall-induced landslides at regional scale, which are typically based on
empirical rainfall thresholds (Guzzetti et al. (2007) and references
therein), is on improving the correlation between rainfall indicators and
landslides. However, literature studies rarely back analyze the relationship between
warnings, which would have been issued adopting those
correlations, and landslides. Especially for LEWSs operating at regional scale (ReLEWSs),
empirical evaluations are often carried out by simply analyzing the time
frames during which significant high-consequence landslides occurred in the
test area (Keefer et al., 1987; Baum and Godt, 2010; Capparelli and Tiranti,
2010; Aleotti, 2004). Alternatively, the performance evaluation is based on
2 by 2 contingency tables computed for the joint frequency distribution of
landslides and alerts, both considered as dichotomous variables (Yu et al.,
2003; Cheung et al., 2006; Godt et al., 2006; Restrepo et al., 2008; Tiranti
and Rabuffetti, 2010; Kirschbaum et al., 2012; Martelloni et al., 2012;
Peres and Cancelliere, 2012; Staley et al., 2013; Lagomarsino et al., 2013, 2015;
Greco et al., 2013; Segoni et al., 2014; Gariano et al., 2015; Stähli et al., 2015).
The four elements of these tables – i.e., correct
alerts (CAs) or true positives; missed alerts, false negatives or type II errors;
false alerts, false positives or type I errors; true negatives (TNs) – are then
used to assess the weight of the correct predictions in relation to the
model errors by means of a series of statistical indicators of the model
performance. In all these cases, however, model performance is assessed,
neglecting some important aspects that are peculiar to ReLEWSs, such as the possible occurrence of multiple landslides in the warning
zone,
the duration of the warnings in relation to the time of occurrence of the
landslides, the level of the issued warning in relation to the landslide
spatial density in the warning zone and the relative importance system managers
attribute to different types of errors.</p>
      <p>This paper proposes a methodology in which the analyst is able to explicitly
consider all the above-mentioned aspects for the performance assessment of a
landslide regional warning model to be employed within a ReLEWS. The
original approach, called the “event, duration matrix,
performance (EDuMaP) method, comprises three successive steps:
definition and temporal analysis of warning events (WE) and landslide events (LE),
computation of a duration matrix and evaluation of the warning model
performance. The key element of the EDuMaP method is the definition and
computation of a duration matrix, whose elements report the time associated
with the occurrence of landslide events in relation to the occurrence of
warning events, in their respective classes. The applicability of the EDuMaP
method is tested and discussed using both synthetic data and real landslides
and warnings data from the municipal early warning system operating in Rio
de Janeiro (Brazil).</p>
</sec>
<sec id="Ch1.S2">
  <title>Landslide early warning systems</title>
<sec id="Ch1.S2.SS1">
  <title>Regional systems for rainfall-induced landslides</title>
      <p>Warning systems for landslides can be designed and used at different
reference scales. Two categories of LEWSs
can be defined on the basis of their scale of analysis and operation:
“local” systems and “regional” systems (International Centre of
Geohazards, 2012; Thiebes et al., 2012; Calvello et al., 2015b). ReLEWSs are used
to assess the probability of occurrence of landslides over
appropriately defined homogeneous alert zones of relevant extension,
typically through the prediction and monitoring of meteorological variables,
in order to give generalized warnings to the population. Differently, the
main aim of local landslide warning systems is the temporary evacuation of
people from areas where, at specific times, the risk level to which they are
exposed is considered to be intolerably high. The scale inevitably also
influences the stakeholders involved, the data to be used, the type of
forecasting, the emergency phases, the communication strategies and many
other activities necessary for designing and operating such systems.</p>
      <p>The literature presents many examples of landslide early warning systems
operating at local scale (Lollino et al., 2002; Blikra, 2008; Intrieri et
al., 2012; Thiebes et al., 2013b; among others), while the
scientific references to regional warning systems are much rarer (Wilson (2004), NOAA-USGS (2005),
Lagomarsino et al. (2013), Calvello et al. (2015b), Stähli et al. (2015)
and references therein). The characteristics of landslide warning
systems at local scale are strongly affected by numerous constraints and
factors, from time to time different, related to the characteristics of the
boundary value problem to address. An interesting contribution aiming at
providing guidance for the design of such systems is proposed by the
International Centre of Geohazards (2012), wherein the authors deal with the
technical and practical issues related to monitoring and early warning for
landslides and identify the best technologies available in the context of
both hazard assessment and system design. Concerning regional warning
systems, a few examples of systems for rainfall-induced landslides currently
operating around the world are presented in the following.</p>
      <p>In the USA, the US Geological Survey has long been working on ReLEWSs in a
number of states: California, Colorado, Oregon and Washington (Chleborad,
2000; Chleborad et al., 2008; Baum and Godt, 2010; NOAA-USGS, 2005; Cannon et al., 2011). The state
of knowledge and resources available to issue alerts of
precipitation-induced shallow, rapidly moving landslides and debris flows
vary across the USA; for instance, in the city of Seattle, WA, the alert
system includes four levels – Null, Outlook, Watch and Alarm – and warnings
are based on the measured or expected exceedance of cumulated rainfall and
intensity-duration thresholds combined with criteria using monitored soil
moisture (Godt et al., 2006). In Hong Kong (Chan and Pun, 2004; Cheung et
al., 2006; <uri>http://www.weather.gov.hk/wservice/warning/landslip.htm</uri>), the
correlation model between rainfall events and landslides is based on an
increasing probability of landslide occurrence depending on the measured
rolling 24 h rainfall for four different types of man-made slopes: soil cuts,
rock cuts, fills and retaining structures. In Japan, a nationwide
early warning system for landslide disasters was created by the government
in 2005 (Osanai et al., 2010); the occurrences of debris flows and slope
failures are related to several rainfall indices (e.g., 60<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula> cumulative
rainfall, soil–water index), whose thresholds have been mainly computed
considering rainfall data recorded as not triggering disasters. In Brazil,
the municipal system operating in Rio de Janeiro (d'Orsi et al., 1997;
d'Orsi, 2012; Calvello et al., 2015a, b) issues two different co-existing
alert sets, rainfall warnings and landslide warnings; the landslide warnings are based on the comparison between rainfall
measured
by the monitoring stations and rainfall thresholds and they are related to
an expected spatial density of landslides. In Europe, two national systems
for rainfall-induced landslides have been recently implemented:
one in Norway, managed
by the Norwegian Water Resources and Energy Directorate (Devoli et al.,
2015), and the other in Italy, designed and operated by the research center
CNR-IRPI on behalf of the national civil protection (Rossi et al., 2012). The
Norwegian system is a national early warning system for landslides and
floods, with the aim of assisting road and railway authorities, as well as
local authorities and policy makers, in taking preventive measures before
the occurrence of potentially dangerous events. The Italian system, which is
called SANF, is based on sub-hourly rainfall measurements obtained by a
national network of 1950 rain gauges, quantitative rainfall forecasts and
cumulated rainfall-duration rainfall thresholds. Besides the national
system, following a recent national law written on this subject (DPCM,
2004), other relevant experiences are also present in many Italian regions,
such as in Emilia Romagna (Berti et al., 2012; Lagomarsino et al., 2013),
Piemonte (Tiranti and Rabuffetti, 2010), Campania (DGR n. 299/2005), Toscana
(DGR n. 895/2013, DGR n. 395/2015), Umbria (DGR n. 2312/2007) and Sicily
(DPRS n. 626/2014).</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F1"><caption><p>Scheme of the components of regional early warning systems for
rainfall-induced landslides. Legend: RE is rainfall events; LE is landslide
events; WE is warning events; ReCoL is regional correlation law;
ReLWaM is regional landslide warning model; ReLEWS is regional landslide
early warning system.</p></caption>
          <?xmltex \igopts{width=236.157874pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f01.pdf"/>

        </fig>

</sec>
<sec id="Ch1.S2.SS2">
  <title>Early warning systems, warning models and correlation laws</title>
      <p>Di Biagio and Kjekstad (2007) use a block diagram to propose a schematic of
the structure of landslide early warning systems in four main steps:
monitoring, data analysis and forecasting, warning and response. Bell et al. (2008)
propose a scheme of integrated LEWSs combining both the natural
scientific components (e.g., geotechnics, engineering, data measurement,
transmission and storage, analysis) and the social system (e.g., legal
framework, demands from different stakeholders). Intrieri et al. (2013)
describe LEWSs as the balanced combination of four main activities: design,
monitoring, forecasting and education. Calvello et al. (2015b) state that
the objectives of LEWSs should be defined by considering the scale of analysis
and the type of landslides; they also represent the process of designing and
managing landslide early warning systems by a “wheel” with four concentric
rings identifying: the necessary skills, the activities to be performed, the
means to be used and the basic elements of the system.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T1" specific-use="star"><caption><p>Components of regional landslide early warning systems (ReLEWS) for
rainfall-induced landslides, relevance for system parts – i.e., regional
correlation law (ReCoL), regional landslide warning model (ReLWaM) – and
system actors – i.e., citizens, managers and scientists.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="8">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="center"/>
     <oasis:colspec colnum="4" colname="col4" align="center"/>
     <oasis:colspec colnum="5" colname="col5" align="left"/>
     <oasis:colspec colnum="6" colname="col6" align="center"/>
     <oasis:colspec colnum="7" colname="col7" align="center"/>
     <oasis:colspec colnum="8" colname="col8" align="left"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">Components</oasis:entry>  
         <oasis:entry rowsep="1" namest="col2" nameend="col4">Relevance for system parts </oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry rowsep="1" namest="col6" nameend="col8">Relevance for system actors </oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">ReCoL</oasis:entry>  
         <oasis:entry colname="col3">ReLWaM</oasis:entry>  
         <oasis:entry colname="col4">ReLEWS</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">Citizens</oasis:entry>  
         <oasis:entry colname="col7">Managers</oasis:entry>  
         <oasis:entry colname="col8">Scientists</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Warning events</oasis:entry>  
         <oasis:entry colname="col2">yes</oasis:entry>  
         <oasis:entry colname="col3">yes</oasis:entry>  
         <oasis:entry colname="col4">yes</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7">yes</oasis:entry>  
         <oasis:entry colname="col8">yes</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Landslide events</oasis:entry>  
         <oasis:entry colname="col2">yes</oasis:entry>  
         <oasis:entry colname="col3">yes</oasis:entry>  
         <oasis:entry colname="col4">yes</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7">yes</oasis:entry>  
         <oasis:entry colname="col8">yes</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Other variables</oasis:entry>  
         <oasis:entry colname="col2">yes</oasis:entry>  
         <oasis:entry colname="col3">yes</oasis:entry>  
         <oasis:entry colname="col4">yes</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7">yes</oasis:entry>  
         <oasis:entry colname="col8">yes</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Warning events</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">yes</oasis:entry>  
         <oasis:entry colname="col4">yes</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">yes</oasis:entry>  
         <oasis:entry colname="col7">yes</oasis:entry>  
         <oasis:entry colname="col8">partly</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Decision-making</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">yes</oasis:entry>  
         <oasis:entry colname="col4">yes</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">yes</oasis:entry>  
         <oasis:entry colname="col7">yes</oasis:entry>  
         <oasis:entry colname="col8">partly</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Monitoring and warning strategy</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4">yes</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7">yes</oasis:entry>  
         <oasis:entry colname="col8">yes</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Communication strategy</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4">yes</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">yes</oasis:entry>  
         <oasis:entry colname="col7">yes</oasis:entry>  
         <oasis:entry colname="col8">yes</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Emergency plan</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4">yes</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">yes</oasis:entry>  
         <oasis:entry colname="col7">yes</oasis:entry>  
         <oasis:entry colname="col8">partly</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <p>Figure 1 and Table 1 show an original schematic of the components of
regional early warning systems for rainfall-induced landslides. The proposed
scheme is based on a clear distinction among correlation laws, warning
models and warning systems. Within this framework, a regional correlation
law for rainfall-induced landslides, is defined as a functional relationship
between RE and LE (see Sect. 3.1 for
details on the definition, classification, identification and analysis of
landslide events), eventually including other relevant monitored variables.
A regional landslide warning model includes the regional correlation law as
well as warning events (see Sect. 3.1 for details on the definition,
classification, identification and analysis of warning events) and decision-making procedures to issue the warnings.
ReLEWS includes the regional warning model and the following components:
monitoring and warning strategy, communication strategy and emergency plan.
Each component of ReLEWs may also be related to a number of actors involved
with their deployment, operational activities and management. As reported in
Table 1, three classes of such actors are herein identified:
citizens, managers and scientists. All the system components are relevant for more
than one class of actor. For instance, it is important to highlight that
both the decision-making and emergency plan components, within which the
evacuation procedures and the procedures used to issue and withdraw the
warnings are defined, are significantly influenced by people's risk
perception as well as by operational aspects the managers need to address in
cooperation with the scientists.</p>
</sec>
</sec>
<sec id="Ch1.S3">
  <title>Framework for the performance analysis of regional landslide warning models</title>
      <p>Maskrey (1997) states that the effectiveness of an early warning system
should be judged less on whether warnings are issued per se but rather on
the basis of whether the warnings facilitate appropriate and timely
decision-making by those most at risk. Calvello et al. (2015b) state that
the design of landslide warning systems require synergy between technical
and social skills. According to them, the main objective of the designers of
the technical subsystem is the definition of efficient processes, while the
procedures defined within the social subsystem are important in making
landslide early warning systems an effective tool to reduce risk to life.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F2"><caption><p>Scheme of the “events, duration matrix, performance” (EDuMaP) method.</p></caption>
        <?xmltex \igopts{width=199.169291pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f02.pdf"/>

      </fig>

      <p>Following the previous statements and the scheme proposed in Fig. 1, the
technical performance of a regional landslide early warning system
is herein evaluated by means of the EDuMaP method (Fig. 2), which assesses the performance of the
warning model, employed by that system. The EDuMaP method comprises the
following three successive steps:
<list list-type="bullet"><list-item>
      <p>events analysis, i.e., LE and WE derived
from available landslides and warnings databases;</p></list-item><list-item>
      <p>definition and computation of a duration matrix, whose elements report the
time associated with the occurrence of landslide events in relation to the
occurrence of warning events, in their respective classes;</p></list-item><list-item>
      <p>evaluation of the early warning model performance by means of performance
criteria and indicators applied to the duration matrix computed in the previous step.</p></list-item></list></p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T2" specific-use="star"><caption><p>Input parameters for the classification, identification and
temporal analysis of landslide events (LE) and warning events (WE).</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="3">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:thead>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Parameters of the events analysis</oasis:entry>  
         <oasis:entry colname="col2">Symbol</oasis:entry>  
         <oasis:entry colname="col3">Relevant for</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">1. Warning levels</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>W</mml:mi><mml:mtext>lev</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Classification of WE</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">2. Landslide density criterion</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Classification of LE</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">3. Lead time</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Identification of WE</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">4. Landslide typology</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>typ</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Identification of LE</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">5. Minimum interval between landslide events</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Identification of LE</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">6. Over time</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Identification of LE</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">7. Area of analysis</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Temporal analyses of LE and WE</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">8. Spatial discretization adopted for warnings</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>A</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Temporal analyses of LE and WE</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">9. Time frame of analysis</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Temporal analyses of LE and WE</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">10. Temporal discretization of analysis</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">Temporal analyses of LE and WE</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <?xmltex \floatpos{t}?><fig id="Ch1.F3" specific-use="star"><caption><p>Scheme of the relationships among rainfall events, landslide
events and warning events for the definition and computation of the duration matrix.</p></caption>
        <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f03.png"/>

      </fig>

<sec id="Ch1.S3.SS1">
  <title>Events analysis: landslide and warning events</title>
      <p>Despite the fact that regional warning models typically associate descriptors with their
warning levels which consider the potential number of landslides
affecting the warning zone, only few examples exist, in the literature,
that evaluate the system performance differentiating among warning levels and
among the number of concurrent landslides registered during the warning
phases (Yu et al., 2003; Calvello et al., 2015b). The “events analysis”
step of the EDuMaP method aims at defining the most appropriate LE and WE to be used to assess the model
performance. To this aim, databases of recorded landslides and warnings must
be available (Fig. 3). The results of the analysis depend on the values
assumed by a series of well-identified parameters (Table 2), which are
defined to allow the analyst to make choices on how to select and group
landslides and warnings.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T3" specific-use="star"><caption><p>Examples of landslide density criteria which can be used to
classify the landslide events.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="4">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:colspec colnum="4" colname="col4" align="left"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">LE</oasis:entry>  
         <oasis:entry colname="col2">Absolute</oasis:entry>  
         <oasis:entry colname="col3">Relative criterion</oasis:entry>  
         <oasis:entry colname="col4">Mixed criterion</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">class</oasis:entry>  
         <oasis:entry colname="col2">criterion</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mo>(</mml:mo></mml:math></inline-formula>no. of landslides/area<inline-formula><mml:math display="inline"><mml:mo>)</mml:mo></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mo>(</mml:mo></mml:math></inline-formula>no. of</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">landslides<inline-formula><mml:math display="inline"><mml:mo>)</mml:mo></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">0</oasis:entry>  
         <oasis:entry colname="col3">0</oasis:entry>  
         <oasis:entry colname="col4">0</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">2</oasis:entry>  
         <oasis:entry colname="col2">1</oasis:entry>  
         <oasis:entry colname="col3">from 0.001 to 0.02 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">3</oasis:entry>  
         <oasis:entry colname="col2">2 to 10</oasis:entry>  
         <oasis:entry colname="col3">from 0.021 to 0.1 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">from 2 to MIN(10; 0.1 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula>)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">4</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math display="inline"><mml:mo>&gt;</mml:mo></mml:math></inline-formula> 10</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mo>&gt;</mml:mo></mml:math></inline-formula> 0.1 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4"><inline-formula><mml:math display="inline"><mml:mo>&gt;</mml:mo></mml:math></inline-formula> MIN(10; 0.1 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula>)</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <p>Figure 3 exemplifies the relationships among rainfall, landslide and warning
data for the performance analysis of a warning model employed for
rainfall-induced landslides within regional systems. The assessment of the
model performance requires the preliminary identification of LE and WE from analyses carried out,
respectively, on landslide and warning databases. Landslide events are
herein defined as a series of landslides grouped on the basis of their
characteristics, so as to implicitly evaluate and classify the magnitude of
a set of multiple phenomena occurring in a given area within a given time
period. Landslide events are retrieved from the landslides database
according to data, classification, spatial and temporal characteristics of
the landslide records. As reported in the figure, the previous four
characteristics may be associated with the following four questions words: how
(e.g., how does the database report landslide data?), what (e.g., what types
of landslides are relevant for the warning model?), where (e.g., where did
landslides occur in relation to the alert zones of the warning system?) and
when (e.g., when did landslides occur?). Warning events are herein defined a
set of warning levels issued within a given warning zone, grouped
considering their temporal characteristics. Warning events are retrieved
from the warnings database according to decision-making and warning levels
criteria, respectively, addressing the procedures employed to activate the
warnings and the meaning of the warning levels in relation to the warnings
issued in the alert zones. Looking at the proposed scheme, it is evident
that the identification and computation of the duration matrix (see
following section for a detailed explanation of the second step of the
EDuMaP method) does not require rainfall data, as it only depends on
temporal analyses carried out on the landslide and warning events. For
completeness, however, the figure also reports the typical relationships
employed among rainfall, landslide and warning events. Warning events
(i.e., the warning model output) are indeed typically generated by evaluating the
characteristics of the monitored rainfall in relation to appropriately
defined rainfall thresholds, which are in turn based on a correlation law
between rainfall events (i.e., the triggering factor) and landslide events
(i.e., the hazard for which warnings are issued).</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F4" specific-use="star"><caption><p>Exemplification of the meaning of parameters: minimum interval
between landslide events, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, and over time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> <bold>(a)</bold>;
lead time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> <bold>(b)</bold>.</p></caption>
          <?xmltex \igopts{width=398.338583pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f04.pdf"/>

        </fig>

      <p>The identification of landslide events and warning events from the
respective databases is influenced by a series of choices the analyst needs
to make in selecting and grouping, respectively, landslides and warnings.
These choices must be carried out considering the characteristics of the
warning model whose performance the analyst wants to assess. Table 2 reports
the 10 parameters which need to be defined to carry on the events analysis:
<list list-type="order"><list-item>
      <p>warning levels, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>W</mml:mi><mml:mtext>lev</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, i.e., number of warning classes used by the model;</p></list-item><list-item>
      <p>landslide density criterion, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, i.e., thresholds used to
differentiate among <inline-formula><mml:math display="inline"><mml:mi>k</mml:mi></mml:math></inline-formula> classes of landslide events on the basis of their
spatial characteristics;
<?xmltex \hack{\newpage}?></p></list-item><list-item>
      <p>lead time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, i.e., value of the time interval between the sending
out of the first warning level identified within a warning event and the
assumed beginning of the warning event;</p></list-item><list-item>
      <p>landslide typology, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>typ</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, i.e., landslides addressed by the warning model;</p></list-item><list-item>
      <p>minimum interval between landslide events, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, i.e., time
quantifying the maximum temporal gap among landslides included within a
single landslide event;</p></list-item><list-item>
      <p>over time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, i.e., time interval between the last landslide
identified within a landslide event and the assumed ending of the landslide event;</p></list-item><list-item>
      <p>area of analysis, <inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>, i.e., area for which both landslides and warnings data
are available;</p></list-item><list-item>
      <p>spatial discretization adopted for warnings, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>A</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>,
i.e., subdivision of the area of analysis in <inline-formula><mml:math display="inline"><mml:mi>k</mml:mi></mml:math></inline-formula> classes on the basis of the spatial
criteria adopted to issue the warnings;</p></list-item><list-item>
      <p>time frame of analysis, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi><mml:mo>,</mml:mo></mml:mrow></mml:math></inline-formula> i.e., temporal length of
databases for which both landslides and warnings data are available;</p></list-item><list-item>
      <p>temporal discretization of analysis, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:math></inline-formula>, i.e., minimum unit of
time used to identify landslide and warning events.</p></list-item></list>
The first two parameters, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>W</mml:mi><mml:mtext>lev</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, are relevant for the
classification of the warning and landslide events, respectively. Concerning
the second parameter, Table 3 reports three examples of landslide density
criteria which could be used to classify landslide events in four classes:
the first criterion is based on the number of landslides, the second one on
the number of landslides per unit area and the third one is a combination of
the previous two. The following four parameters are relevant for the
identification of the warning and landslide events. In particular,
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>typ</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> is used to select, from the landslides database, only the
landslides which are considered relevant for the early warnings. The meaning
of <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> is schematized in Fig. 4.
Figure 4a reports one set of landslides and three series of landslide events
identified considering three different combination of values for <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>
and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>. Figure 4b reports one set of warning levels (in four
classes) and three series of warning events identified considering three
different values of <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>. It is important to highlight that the latter
two variables should be seen as time variables which are relevant for
decision-making purposes. The lead time is related, for instance, to how
evacuation procedures are defined within the warning system; the over time
may be related to the procedures issued to withdraw the warnings. The last
four parameters, whose meaning is straightforward, are relevant for the
temporal analyses of both landslide events and warning events.</p>
</sec>
<sec id="Ch1.S3.SS2">
  <title>Duration matrix</title>
      <p>The key element of the numerical evaluation of the performance of a warning
model is the definition and computation of a matrix, herein called
“duration matrix” (Fig. 5), whose elements report the time associated
with the occurrence of landslide events in relation to the occurrence of
warning events, in their respective classes. The classification of landslide
events and warning events (see parameters <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>den</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>W</mml:mi><mml:mtext>lev</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> in Table 2)
establishes the structure of the duration matrix. Indeed, the number of rows
and columns of the matrix is equal to the number of classes defined for the
warning and landslide events, respectively. The matrix reported in Fig. 5a
is drawn as a 4 by 4 matrix, under the hypothesis of four classes of
warning events, indicated with numbers from 1 to 4 and letters representing
the descriptors no, medium, high and very high, and four classes of landslide
events, indicated with numbers from 1 to 4 and letters representing the
descriptors no, small, intermediate and large. Each element of the duration
matrix, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, is computed, within the time frame of the analysis,
<inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi></mml:mrow></mml:math></inline-formula>, as follows:

                <disp-formula id="Ch1.E1" content-type="numbered"><mml:math display="block"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:munder><mml:mo movablelimits="false">∑</mml:mo><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi></mml:mrow></mml:munder><mml:msub><mml:mtext>time</mml:mtext><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo></mml:mrow></mml:math></disp-formula>

          where <inline-formula><mml:math display="inline"><mml:mi>i</mml:mi></mml:math></inline-formula> is the number of classes of the warning events, <inline-formula><mml:math display="inline"><mml:mi>j</mml:mi></mml:math></inline-formula> is the number of
classes of the landslide events and time<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> is amount of time for which a
class <inline-formula><mml:math display="inline"><mml:mi>i</mml:mi></mml:math></inline-formula>th warning events is concomitant with a class <inline-formula><mml:math display="inline"><mml:mi>j</mml:mi></mml:math></inline-formula>th landslide event.</p>
      <p>Figure 5b shows a graphical example of temporal analysis needed for the
computation, following Eq. (1), of the elements of the duration matrix. It is
important to highlight that the dimension of the elements of the duration
matrix, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, is time and that the sum of all elements, <inline-formula><mml:math display="inline"><mml:mrow><mml:munder><mml:mo movablelimits="false">∑</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:munder><mml:mspace linebreak="nobreak" width="0.125em"/><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>,
is always equal to the time frame of the analysis, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi></mml:mrow></mml:math></inline-formula>.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T4" specific-use="star"><caption><p>Synthetic data exemplifying the performance of a regional landslide
warning model: warnings issued and corresponding warning events.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="7">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:colspec colnum="4" colname="col4" align="left"/>
     <oasis:colspec colnum="5" colname="col5" align="left"/>
     <oasis:colspec colnum="6" colname="col6" align="left"/>
     <oasis:colspec colnum="7" colname="col7" align="left"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry namest="col1" nameend="col4" align="center">Warnings issued </oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry rowsep="1" namest="col6" nameend="col7" align="center">Warning event </oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Level</oasis:entry>  
         <oasis:entry colname="col2">From (date and hour)</oasis:entry>  
         <oasis:entry colname="col3">To (date and hour)</oasis:entry>  
         <oasis:entry colname="col4">Duration</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">ID</oasis:entry>  
         <oasis:entry colname="col7">Class</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4">(h:mm)</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7"/>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Medium</oasis:entry>  
         <oasis:entry colname="col2">13 Jan 2000 13:00</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 16:00</oasis:entry>  
         <oasis:entry colname="col4">3:00</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">WE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">2 (M)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">High</oasis:entry>  
         <oasis:entry colname="col2">13 Jan 2000 16:00</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 17:30</oasis:entry>  
         <oasis:entry colname="col4">1:30</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">WE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">3 (H)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Very high</oasis:entry>  
         <oasis:entry colname="col2">13 Jan 2000 17:30</oasis:entry>  
         <oasis:entry colname="col3">14 Jan 2000 06:00</oasis:entry>  
         <oasis:entry colname="col4">12:30</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">WE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (VH)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Medium</oasis:entry>  
         <oasis:entry colname="col2">14 Jan 2000 06:00</oasis:entry>  
         <oasis:entry colname="col3">14 Jan 2000 18:00</oasis:entry>  
         <oasis:entry colname="col4">12:00</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">WE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">2 (M)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">High</oasis:entry>  
         <oasis:entry colname="col2">18 Mar 2000 07:30</oasis:entry>  
         <oasis:entry colname="col3">18 Mar 2000 18:00</oasis:entry>  
         <oasis:entry colname="col4">10:30</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">WE_2000_02</oasis:entry>  
         <oasis:entry colname="col7">3 (H)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Medium</oasis:entry>  
         <oasis:entry colname="col2">22 Nov 2000 10:00</oasis:entry>  
         <oasis:entry colname="col3">22 Nov 2000 12:00</oasis:entry>  
         <oasis:entry colname="col4">2:00</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">WE_2000_03</oasis:entry>  
         <oasis:entry colname="col7">2 (M)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Very high</oasis:entry>  
         <oasis:entry colname="col2">22 Nov 2000 12:00</oasis:entry>  
         <oasis:entry colname="col3">23 Nov 2000 07:30</oasis:entry>  
         <oasis:entry colname="col4">19:30</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">WE_2000_03</oasis:entry>  
         <oasis:entry colname="col7">3 (H)</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <?xmltex \floatpos{t}?><fig id="Ch1.F5" specific-use="star"><caption><p>Structure of the duration matrix <bold>(a)</bold> and graphical
exemplification of the temporal analysis needed for its computation <bold>(b)</bold>.</p></caption>
          <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f05.pdf"/>

        </fig>

      <p>To further clarify how the duration matrix is computed, Tables 4 and 5
report a set of synthetic data exemplifying the performance of a fictitious
regional landslide warning model, herein created considering a time frame of
1 year (the year 2000). Table 4 shows the set of warnings issued by the
model – together with the information which are supposedly retrieved from
the warnings database – and the corresponding warning events. Table 5 shows
the set of landslides recorded during the same time frame – together with
the information retrieved from the landslides database – and the
corresponding landslide events. Both the warning and the landslide events
have been derived following the procedure described in the previous section,
assuming the following parameters' values: four warning levels, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>W</mml:mi><mml:mtext>lev</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>;
landslide density thresholds, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>den</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to 0 (class 1), 1 (class 2),
2 to 10 (class 3), <inline-formula><mml:math display="inline"><mml:mo>&gt;</mml:mo></mml:math></inline-formula> 10 (class 4); lead time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to
0; <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>typ</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> equal to all the landslides recorded in the database,
independently of the values assumed by typology and accuracy of time record;
minimum interval between landslide events, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to
12 h; over time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to 0; constant area of analysis, <inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>;
spatial discretization adopted for warnings, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>A</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, equal to the
area of analysis; time frame of the analysis, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi></mml:mrow></mml:math></inline-formula>, equal to 1 year;
temporal discretization of the analysis, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:math></inline-formula>, equal to 1 h.</p>
      <p>Three landslide events occurred in the year 2000, herein identified as
LE_2000_01 (from 13 to 14 January), LE_2000_02 (18 March) and
LE_2000_03 (22 November), and classified in the following
classes: 4 (L), 2 (S), 3 (I). On the same dates of the landslide events, the
following three warning events are recorded: WE_2000_01 (from 13:00 LT on 13 January to 18:00 LT on
14 January), with warning levels varying from 2 (M) to 4 (VH); WE_2000_02
(from 07:30 to 18:00 LT on 18 March), with warning
level equal to 3 (M); WE_2000_03, (from 10:00 LT on 22 November to 19:30 LT on 23 November) with warning levels varying
from 2 (M) to 3 (H). The total number of distinct warning levels issued is, in
this case, equal to seven. Table 6 and Fig. 6 report the result of the
temporal analysis conducted, for the year-long time frame, on these events.
The resulting duration matrix is shown in Fig. 6.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T5" specific-use="star"><caption><p>Synthetic data exemplifying the performance of a regional landslide
warning model: landslide database and corresponding landslide events.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="7">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:colspec colnum="4" colname="col4" align="left"/>
     <oasis:colspec colnum="5" colname="col5" align="left"/>
     <oasis:colspec colnum="6" colname="col6" align="left"/>
     <oasis:colspec colnum="7" colname="col7" align="center"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry rowsep="1" namest="col1" nameend="col4" align="center">Landslide database </oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry rowsep="1" namest="col6" nameend="col7" align="center">Landslide event </oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Number</oasis:entry>  
         <oasis:entry colname="col2">Typology</oasis:entry>  
         <oasis:entry colname="col3">Date and hour</oasis:entry>  
         <oasis:entry colname="col4">Accuracy of time record</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">ID</oasis:entry>  
         <oasis:entry colname="col7">class</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 10:20</oasis:entry>  
         <oasis:entry colname="col4">exact time</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">15</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 10:00 to 11:00</oasis:entry>  
         <oasis:entry colname="col4">time interval</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">3</oasis:entry>  
         <oasis:entry colname="col2">B</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 10:00 to 11:00</oasis:entry>  
         <oasis:entry colname="col4">interval estimated</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">2</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 12:35</oasis:entry>  
         <oasis:entry colname="col4">exact time</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">B</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 12:40</oasis:entry>  
         <oasis:entry colname="col4">exact time</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">4</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 12:00 to 13:00</oasis:entry>  
         <oasis:entry colname="col4">time interval</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">2</oasis:entry>  
         <oasis:entry colname="col2">C</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 12:00 to 13:00</oasis:entry>  
         <oasis:entry colname="col4">time interval</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">3</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 13:00 to 14:00</oasis:entry>  
         <oasis:entry colname="col4">interval estimated</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 19:15</oasis:entry>  
         <oasis:entry colname="col4">exact time</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">B</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 19:20</oasis:entry>  
         <oasis:entry colname="col4">exact time</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">2</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 20:00 to 21:00</oasis:entry>  
         <oasis:entry colname="col4">time interval</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">7</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 21:00 to 22:00</oasis:entry>  
         <oasis:entry colname="col4">time interval</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">2</oasis:entry>  
         <oasis:entry colname="col2">B</oasis:entry>  
         <oasis:entry colname="col3">13 Jan 2000 21:00 to 22:00</oasis:entry>  
         <oasis:entry colname="col4">time interval</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">14 Jan 2000 01:45</oasis:entry>  
         <oasis:entry colname="col4">exact time</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col7">4 (L)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">18 Mar 2000 12:30</oasis:entry>  
         <oasis:entry colname="col4">exact time</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_02</oasis:entry>  
         <oasis:entry colname="col7">2 (S)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">18 mar 2000 17:00 to 18:00</oasis:entry>  
         <oasis:entry colname="col4">time interval</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_02</oasis:entry>  
         <oasis:entry colname="col7">2 (S)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">2</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">22 Nov 2000 11:00 to 12:00</oasis:entry>  
         <oasis:entry colname="col4">time interval</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_03</oasis:entry>  
         <oasis:entry colname="col7">3 (I)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">B</oasis:entry>  
         <oasis:entry colname="col3">22 Nov 2000 13:20</oasis:entry>  
         <oasis:entry colname="col4">exact time</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_03</oasis:entry>  
         <oasis:entry colname="col7">3 (I)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">2</oasis:entry>  
         <oasis:entry colname="col2">A</oasis:entry>  
         <oasis:entry colname="col3">22 Nov 2000 16:00 to 17:00</oasis:entry>  
         <oasis:entry colname="col4">time interval</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_03</oasis:entry>  
         <oasis:entry colname="col7">3 (I)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">1</oasis:entry>  
         <oasis:entry colname="col2">C</oasis:entry>  
         <oasis:entry colname="col3">22 Nov 2000 16:00 to 17:00</oasis:entry>  
         <oasis:entry colname="col4">interval estimated</oasis:entry>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">LE_2000_03</oasis:entry>  
         <oasis:entry colname="col7">3 (I)</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <?xmltex \floatpos{t}?><fig id="Ch1.F6" specific-use="star"><caption><p>Graphical representation of temporal analysis reported in Table 6.</p></caption>
          <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f06.png"/>

        </fig>

</sec>
<sec id="Ch1.S3.SS3">
  <title>Performance assessment: criteria and indicators</title>
      <p>Typically, the evaluation of system performance and accuracy uses
statistical indicators derived from 2 by 2 contingency tables. It is
straightforward to understand that a good performance of a regional
landslide warning model must be associated to few missed and false alerts.
However, when landslide events and warning events are not expressed as
dichotomous variables, the identification of missed or false alerts is not
unambiguous. To properly evaluate performance, another key issue to consider
is the relative importance assigned by the system managers to the different
types of errors. The latter is, in turn, related to the meaning assigned to
the warnings issued in the alert zones in terms of expected number of
landslides. To address these issues, the “performance assessment” step of
the EDuMaP method is based on the definition of a series of performance
criteria and indicators applied to the duration matrix.</p>
      <p>A first judgment on the results from the duration matrix may be based on the
computation of the distribution of landslide events and warning events in
relation to each other, in their respective classes. To this purpose, the
following matrix normalizations may be employed:
<?xmltex \hack{\newpage}?><?xmltex \hack{\vspace*{-8mm}}?>

                <disp-formula specific-use="align" content-type="numbered"><mml:math display="block"><mml:mtable displaystyle="true"><mml:mlabeledtr id="Ch1.E2"><mml:mtd/><mml:mtd/><mml:mtd><mml:mrow><mml:msub><mml:mtext>d_LE</mml:mtext><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mstyle displaystyle="true"><mml:mfrac style="display"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow><mml:munderover><mml:mo movablelimits="false">∑</mml:mo><mml:mrow><mml:mi>k</mml:mi><mml:mo>=</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow><mml:mn mathvariant="normal">4</mml:mn></mml:munderover><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>k</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mstyle><mml:msub><mml:mtext>N_LE</mml:mtext><mml:mi>j</mml:mi></mml:msub><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mo>(</mml:mo><mml:mtext>for</mml:mtext><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi>j</mml:mi><mml:mo>=</mml:mo><mml:mn mathvariant="normal">2</mml:mn><mml:mo>-</mml:mo><mml:mn mathvariant="normal">4</mml:mn><mml:mo>)</mml:mo><mml:mo>,</mml:mo></mml:mrow></mml:mtd></mml:mlabeledtr><mml:mlabeledtr id="Ch1.E3"><mml:mtd/><mml:mtd/><mml:mtd><mml:mrow><mml:msub><mml:mtext>d_WE</mml:mtext><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mstyle displaystyle="true"><mml:mfrac style="display"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow><mml:munderover><mml:mo movablelimits="false">∑</mml:mo><mml:mrow><mml:mi>k</mml:mi><mml:mo>=</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow><mml:mn mathvariant="normal">4</mml:mn></mml:munderover><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>k</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mstyle><mml:msub><mml:mtext>N_WL</mml:mtext><mml:mi>i</mml:mi></mml:msub><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mo>(</mml:mo><mml:mtext>for</mml:mtext><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn mathvariant="normal">2</mml:mn><mml:mo>-</mml:mo><mml:mn mathvariant="normal">4</mml:mn><mml:mo>)</mml:mo><mml:mo>,</mml:mo></mml:mrow></mml:mtd></mml:mlabeledtr></mml:mtable></mml:math></disp-formula>

            <?xmltex \hack{\newpage}?><?xmltex \hack{\noindent}?>where <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula> is the element of the original duration matrix,
d_LE<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> is the element of the duration matrix normalized in relation to the
landslide events, N_LE<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mi>j</mml:mi></mml:msub></mml:math></inline-formula> is the number of landslide events classified as
class <inline-formula><mml:math display="inline"><mml:mi>j</mml:mi></mml:math></inline-formula> within the time frame of the analysis, d_WE<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> is the element of the
duration matrix normalized in relation to the warning events and
N_WL<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mi>i</mml:mi></mml:msub></mml:math></inline-formula> is the number of warning levels of class <inline-formula><mml:math display="inline"><mml:mi>i</mml:mi></mml:math></inline-formula> within in the time frame
of the analysis.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T6" specific-use="star"><caption><p>Temporal analysis of warning events (WE) and landslide events (LE)
using data from Tables 4 and 5.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="9">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="right"/>
     <oasis:colspec colnum="4" colname="col4" align="left"/>
     <oasis:colspec colnum="5" colname="col5" align="left"/>
     <oasis:colspec colnum="6" colname="col6" align="center"/>
     <oasis:colspec colnum="7" colname="col7" align="left"/>
     <oasis:colspec colnum="8" colname="col8" align="left"/>
     <oasis:colspec colnum="9" colname="col9" align="center"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry rowsep="1" namest="col1" nameend="col3" align="center">Time </oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry rowsep="1" namest="col5" nameend="col6" align="center">Warning event </oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry rowsep="1" namest="col8" nameend="col9" align="center">Landslide event </oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">From (date and hour)</oasis:entry>  
         <oasis:entry colname="col2">To (date and hour)</oasis:entry>  
         <oasis:entry colname="col3">Duration (h)</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">ID</oasis:entry>  
         <oasis:entry colname="col6">Class</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8">ID</oasis:entry>  
         <oasis:entry colname="col9">Class</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">1 Jan 2000 00:00</oasis:entry>  
         <oasis:entry colname="col2">13 Jan 2000 10:00</oasis:entry>  
         <oasis:entry colname="col3">298</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">1</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">13 Jan 2000 10:00</oasis:entry>  
         <oasis:entry colname="col2">13 Jan 2000 13:00</oasis:entry>  
         <oasis:entry colname="col3">3</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">1</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col9">4</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">13 Jan 2000 13:00</oasis:entry>  
         <oasis:entry colname="col2">13 Jan 2000 16:00</oasis:entry>  
         <oasis:entry colname="col3">3</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_01</oasis:entry>  
         <oasis:entry colname="col6">2</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col9">4</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">13 Jan 2000 16:00</oasis:entry>  
         <oasis:entry colname="col2">13 Jan 2000 17:30</oasis:entry>  
         <oasis:entry colname="col3">1</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_01</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col9">4</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">13 Jan 2000 17:30</oasis:entry>  
         <oasis:entry colname="col2">14 Jan 2000 01:45</oasis:entry>  
         <oasis:entry colname="col3">8</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_01</oasis:entry>  
         <oasis:entry colname="col6">4</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8">LE_2000_01</oasis:entry>  
         <oasis:entry colname="col9">4</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">14 Jan 2000 01:45</oasis:entry>  
         <oasis:entry colname="col2">14 Jan 2000 06:00</oasis:entry>  
         <oasis:entry colname="col3">4</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_01</oasis:entry>  
         <oasis:entry colname="col6">4</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">14 Jan 2000 06:00</oasis:entry>  
         <oasis:entry colname="col2">14 Jan 2000 18:00</oasis:entry>  
         <oasis:entry colname="col3">12</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_01</oasis:entry>  
         <oasis:entry colname="col6">2</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">14 Jan 2000 18:00</oasis:entry>  
         <oasis:entry colname="col2">18 Mar 2000 07:30</oasis:entry>  
         <oasis:entry colname="col3">1525</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">1</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">18 Mar 2000 07:30</oasis:entry>  
         <oasis:entry colname="col2">18 Mar 2000 12:30</oasis:entry>  
         <oasis:entry colname="col3">5</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_02</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">18 Mar 2000 12:30</oasis:entry>  
         <oasis:entry colname="col2">18 Mar 2000 18:00</oasis:entry>  
         <oasis:entry colname="col3">5</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_02</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8">LE_2000_02</oasis:entry>  
         <oasis:entry colname="col9">2</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">18 Mar 2000 18:00</oasis:entry>  
         <oasis:entry colname="col2">22 Nov 2000 10:00</oasis:entry>  
         <oasis:entry colname="col3">5968</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">1</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">22 Nov 2000 10:00</oasis:entry>  
         <oasis:entry colname="col2">22 Nov 2000 11:00</oasis:entry>  
         <oasis:entry colname="col3">1</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_03</oasis:entry>  
         <oasis:entry colname="col6">2</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">22 Nov 2000 11:00</oasis:entry>  
         <oasis:entry colname="col2">22 Nov 2000 12:00</oasis:entry>  
         <oasis:entry colname="col3">1</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_03</oasis:entry>  
         <oasis:entry colname="col6">2</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8">LE_2000_03</oasis:entry>  
         <oasis:entry colname="col9">3</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">22 Nov 2000 12:00</oasis:entry>  
         <oasis:entry colname="col2">22 Nov 2000 17:00</oasis:entry>  
         <oasis:entry colname="col3">5</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_03</oasis:entry>  
         <oasis:entry colname="col6">4</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8">LE_2000_03</oasis:entry>  
         <oasis:entry colname="col9">3</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">22 Nov 2000 17:00</oasis:entry>  
         <oasis:entry colname="col2">23 Nov 2000 07:30</oasis:entry>  
         <oasis:entry colname="col3">14</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5">WE_2000_03</oasis:entry>  
         <oasis:entry colname="col6">4</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">23 Nov 2000 07:30</oasis:entry>  
         <oasis:entry colname="col2">31 Dec 2000 23:59</oasis:entry>  
         <oasis:entry colname="col3">928</oasis:entry>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6">1</oasis:entry>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9">1</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup>

</oasis:table><?xmltex \hack{\vspace*{2mm}}?></table-wrap>

      <?xmltex \floatpos{t}?><fig id="Ch1.F7" specific-use="star"><caption><p>Examples of performance criteria which can be used for the
analysis of the duration matrix: alert classification criterion (A) and
grade of correctness criterion (B).</p></caption>
          <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f07.pdf"/>

          <?xmltex \hack{\vspace*{2mm}}?>
        </fig>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T7"><caption><p>Duration matrix: results using data from Table 6.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="6">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="right"/>
     <oasis:colspec colnum="4" colname="col4" align="center"/>
     <oasis:colspec colnum="5" colname="col5" align="center"/>
     <oasis:colspec colnum="6" colname="col6" align="center"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry rowsep="1" namest="col3" nameend="col6" align="center">LE duration (h) </oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">1 (no)</oasis:entry>  
         <oasis:entry colname="col4">2 (M)</oasis:entry>  
         <oasis:entry colname="col5">3 (H)</oasis:entry>  
         <oasis:entry colname="col6">4 (VH)</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">WE</oasis:entry>  
         <oasis:entry colname="col2">1 (no)</oasis:entry>  
         <oasis:entry colname="col3">8719</oasis:entry>  
         <oasis:entry colname="col4">0</oasis:entry>  
         <oasis:entry colname="col5">0</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">duration</oasis:entry>  
         <oasis:entry colname="col2">2 (M)</oasis:entry>  
         <oasis:entry colname="col3">13</oasis:entry>  
         <oasis:entry colname="col4">0</oasis:entry>  
         <oasis:entry colname="col5">1</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">(h)</oasis:entry>  
         <oasis:entry colname="col2">3 (H)</oasis:entry>  
         <oasis:entry colname="col3">5</oasis:entry>  
         <oasis:entry colname="col4">5</oasis:entry>  
         <oasis:entry colname="col5">0</oasis:entry>  
         <oasis:entry colname="col6">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">4 (VH)</oasis:entry>  
         <oasis:entry colname="col3">18</oasis:entry>  
         <oasis:entry colname="col4">0</oasis:entry>  
         <oasis:entry colname="col5">5</oasis:entry>  
         <oasis:entry colname="col6">8</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup>

</oasis:table><?xmltex \hack{\vspace*{2mm}}?></table-wrap>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T8" specific-use="star"><caption><p>Performance indicators derived from the two performance criteria
reported in Fig. 7 using data from duration matrix reported in Table 7.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="5">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:colspec colnum="4" colname="col4" align="left"/>
     <oasis:colspec colnum="5" colname="col5" align="left"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">Performance indicator</oasis:entry>  
         <oasis:entry colname="col2">Performance</oasis:entry>  
         <oasis:entry colname="col3">Symbol</oasis:entry>  
         <oasis:entry colname="col4">Formula</oasis:entry>  
         <oasis:entry colname="col5">Value</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">criterion</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Efficiency index</oasis:entry>  
         <oasis:entry colname="col2">Criterion A</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>eff</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">(CA <inline-formula><mml:math display="inline"><mml:mo>+</mml:mo></mml:math></inline-formula> TN)/<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi mathvariant="normal">Σ</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula> <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula> (excluding <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mn>11</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col5">0.44</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Hit rate</oasis:entry>  
         <oasis:entry colname="col2">Criterion A</oasis:entry>  
         <oasis:entry colname="col3">HR<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mtext>L</mml:mtext></mml:msub></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">CA/(CA <inline-formula><mml:math display="inline"><mml:mo>+</mml:mo></mml:math></inline-formula> MA)</oasis:entry>  
         <oasis:entry colname="col5">0.67</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Predictive power</oasis:entry>  
         <oasis:entry colname="col2">Criterion A</oasis:entry>  
         <oasis:entry colname="col3">PP<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mtext>W</mml:mtext></mml:msub></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">CA/(CA <inline-formula><mml:math display="inline"><mml:mo>+</mml:mo></mml:math></inline-formula> FA)</oasis:entry>  
         <oasis:entry colname="col5">0.33</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Threat score</oasis:entry>  
         <oasis:entry colname="col2">Criterion A</oasis:entry>  
         <oasis:entry colname="col3">TS</oasis:entry>  
         <oasis:entry colname="col4">CA/(CA <inline-formula><mml:math display="inline"><mml:mo>+</mml:mo></mml:math></inline-formula> MA <inline-formula><mml:math display="inline"><mml:mo>+</mml:mo></mml:math></inline-formula> FA)</oasis:entry>  
         <oasis:entry colname="col5">0.29</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Odds ratio</oasis:entry>  
         <oasis:entry colname="col2">Criterion A</oasis:entry>  
         <oasis:entry colname="col3">OR</oasis:entry>  
         <oasis:entry colname="col4">(CA <inline-formula><mml:math display="inline"><mml:mo>+</mml:mo></mml:math></inline-formula> TN)/(MA <inline-formula><mml:math display="inline"><mml:mo>+</mml:mo></mml:math></inline-formula> FA)</oasis:entry>  
         <oasis:entry colname="col5">0.77</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Misclassification rate</oasis:entry>  
         <oasis:entry colname="col2">Criterion A</oasis:entry>  
         <oasis:entry colname="col3">MR</oasis:entry>  
         <oasis:entry colname="col4">1 <inline-formula><mml:math display="inline"><mml:mo>-</mml:mo></mml:math></inline-formula> <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>eff</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col5">0.56</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Missed alert rate</oasis:entry>  
         <oasis:entry colname="col2">Criterion A</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>R</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">1 <inline-formula><mml:math display="inline"><mml:mo>-</mml:mo></mml:math></inline-formula> HR</oasis:entry>  
         <oasis:entry colname="col5">0.33</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">False alert rate</oasis:entry>  
         <oasis:entry colname="col2">Criterion A</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>R</mml:mi><mml:mtext>FA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">1 <inline-formula><mml:math display="inline"><mml:mo>-</mml:mo></mml:math></inline-formula> PP</oasis:entry>  
         <oasis:entry colname="col5">0.67</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Error rate</oasis:entry>  
         <oasis:entry colname="col2">Criterion B</oasis:entry>  
         <oasis:entry colname="col3">ER</oasis:entry>  
         <oasis:entry colname="col4">(Red <inline-formula><mml:math display="inline"><mml:mo>+</mml:mo></mml:math></inline-formula> Pur)/<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi mathvariant="normal">Σ</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mspace linebreak="nobreak" width="0.125em"/><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula> (excluding <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mn>11</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col5">0.56</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Probability of serious mistakes</oasis:entry>  
         <oasis:entry colname="col2">Criterion B</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mtext>SM</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">Pur/<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi mathvariant="normal">Σ</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mspace linebreak="nobreak" width="0.125em"/><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula> (excluding <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mn>11</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col5">0.39</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Probability of serious no-warning mistakes</oasis:entry>  
         <oasis:entry colname="col2">Criterion B</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NW</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">Pur<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mrow><mml:mi>i</mml:mi><mml:mn mathvariant="normal">4</mml:mn></mml:mrow></mml:msub></mml:math></inline-formula>/<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi mathvariant="normal">Σ</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mspace width="0.125em" linebreak="nobreak"/><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula> (for <inline-formula><mml:math display="inline"><mml:mi>i</mml:mi></mml:math></inline-formula> <inline-formula><mml:math display="inline"><mml:mo>=</mml:mo></mml:math></inline-formula> 1, <inline-formula><mml:math display="inline"><mml:mi>j</mml:mi></mml:math></inline-formula> <inline-formula><mml:math display="inline"><mml:mo>=</mml:mo></mml:math></inline-formula> 2–4)</oasis:entry>  
         <oasis:entry colname="col5">1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Probability of serious no-landslides mistakes</oasis:entry>  
         <oasis:entry colname="col2">Criterion B</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NL</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">Pur<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mrow><mml:mn mathvariant="normal">4</mml:mn><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>/<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi mathvariant="normal">Σ</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mspace width="0.125em" linebreak="nobreak"/><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula> (for <inline-formula><mml:math display="inline"><mml:mi>i</mml:mi></mml:math></inline-formula> <inline-formula><mml:math display="inline"><mml:mo>=</mml:mo></mml:math></inline-formula> 2–4, <inline-formula><mml:math display="inline"><mml:mi>j</mml:mi></mml:math></inline-formula> <inline-formula><mml:math display="inline"><mml:mo>=</mml:mo></mml:math></inline-formula> 1)</oasis:entry>  
         <oasis:entry colname="col5">0.5</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Index of severity of missed alerts</oasis:entry>  
         <oasis:entry colname="col2">Criteria A and B</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">(Pur &amp; MA)/MA</oasis:entry>  
         <oasis:entry colname="col5">0.86</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Index of severity of false alerts</oasis:entry>  
         <oasis:entry colname="col2">Criteria A and B</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>FA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">(Pur &amp; FA)/FA</oasis:entry>  
         <oasis:entry colname="col5">0.64</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <p>Figure 7 reports a graphical representation of a more comprehensive analysis
of the duration matrix based on a set of two performance criteria, both of
them assigning a performance meaning to all but one element of the matrix,
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mn>11</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>, which expresses the number of hours when no warnings are issued
and no landslides occur. Both criteria purposefully neglect element
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mn>11</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>, whose value is typically orders of magnitude higher than the
values of the other elements, in order to allow a more useful relative
assessment of the information located in the remaining part of the duration
matrix. The first criterion (A) fulfills the task of employing an alert
classification scheme derived from a 2 by 2 contingency table, thus
identifying CAs, FAs, MAs and TNs. The second criterion (B) assigns a color code to the elements
of the matrix in relation to their grade of correctness, herein classified
in four classes as follows: green (Gre) for the elements which are assumed to
be representative of the best model response, yellow (Yel) for elements
representative of minor model errors, red (Red) for elements representative of
a significant model errors and purple (Pur) for elements representative of the
worst model errors.</p>
      <p>A number of performance indicators may be derived from the two performance
criteria previously described. Table 8 reports their names, symbols, formulas
and values (computed using the duration matrix data from Table 7). The
performance indicators related to the alert classification criterion (A) are
a series of statistical indicators which are commonly derived from
contingency tables: efficiency index, also called efficiency (Martelloni et
al., 2012; Lagomarsino et al., 2013) or accuracy (Kirschbaum et al., 2012);
hit rate (Tiranti and Rabuffetti, 2010; Cheung et al., 2006), also called
sensitivity (Martelloni et al., 2012; Lagomarsino et al., 2013), probability
of detection (Kirschbaum et al., 2012; Restrepo et al., 2008; Gariano et
al., 2015) or true positive rate (Staley et al., 2013); predictive power,
also called positive predictive power (Martelloni et al., 2012); threat
score (Staley et al., 2013; Tiranti and Rabuffetti, 2010), also called
critical success index (Cheung et al., 2006); odds ratio (Martelloni et al.,
2012); misclassification rate (Martelloni et al., 2012); missed alert rate,
also called false negative rate (Martelloni et al., 2012; Lagomarsino et
al., 2013); and false alert rate, also called probability of false alarms
(Gariano et al., 2015). The other performance indicators, either related to
the grade of correctness criterion (B) or to both criteria at once, have
been named and defined following a similar reasoning.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F8" specific-use="star"><caption><p>Subdivision of the Rio de Janeiro municipal territory for early
warning purposes, susceptibility map and location of the rainfall monitoring stations.</p></caption>
          <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f08.png"/>

        </fig>

</sec>
</sec>
<sec id="Ch1.S4">
  <title>Application of proposed method to a case study</title>
<sec id="Ch1.S4.SS1">
  <title>The Alerta Rio early warning system</title>
      <p>The territory of the city of Rio de Janeiro (Brazil) has long been affected
by landslides which often caused, in the last decades, widespread
destruction and a significant number of casualties in different areas of the
city. The high frequency of these phenomena is to be ascribed both to the
geologic, geomorphologic and climatic characteristics of the city
(i.e., weathered soils, extensive mountainous areas and a tropical climate) and to
the presence of areas characterized by high density of population and by
unplanned and spontaneous land occupation (e.g., Coelho Netto et al., 2007).
The “Alerta Rio” system (d'Orsi et al., 2004; Calvello et al., 2015b) is a
ReLEWS operated by the GEO-Rio Foundation in the municipality of Rio de
Janeiro, Brazil, designed to inform stakeholders of the possible occurrence
of rainfall induced landslides. The municipality of Rio de Janeiro covers
around 1200 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula> and is divided, for warning purposes, into four alert
zones (Fig. 8): Baia de Guanabara (390 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula>), Zona Sul (40 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula>),
Baia de Sepetiba (492 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula>) and Jacarepaguà (302 km<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula>). Landslide
warnings are currently based on the comparison between rainfall measured by
a network of 33 rain gauges and rainfall thresholds defined considering the
antecedent cumulated rainfall for the following three durations: 1, 24 and 96 h.
The three cumulated rainfall measures are treated
independently by means of a series of either/or rules which define warning
levels associated to four landslide probabilities of occurrence: (1) low, if
mass movements triggered by rainfall are not expected; (2) medium, if only
occasional occurrences of landslides triggered by rainfall are expected,
predominantly in artificial slopes; (3) high, for an expected diffuse
occurrence of landslides in both natural and artificial slopes; (4) very
high, if the expected areal distribution of landslides is significant and
the phenomena are expected to be widespread in slopes and roads cuts.
Landslide warnings are issued, at any given time, over the whole affected
alert zone without explicitly differentiating among areas characterized by
different levels of landslide susceptibility, as defined by a municipal
susceptibility map available at 1 : 10 000 (D'Orsi, 2012). This landslide
susceptibility map is also reported in Fig. 8 because the parametric
analysis presented in the following sections to evaluate the performance of
the Alerta Rio warning model according to the EDuMaP method allows us to
explicitly consider the extent of the area most susceptible to landslides
for the classification of the landslide events (i.e., definition of the input
parameter <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>).</p>
</sec>
<sec id="Ch1.S4.SS2">
  <title>Setup of parametric analysis</title>
      <p>The analysis presented herein uses data on recorded landslides and issued
warnings of the Alerta Rio system for the 3-year period 2010–2012 in two
alert zones: Baia de Guanabara and Zona Sul. Since 2010 the GEO-Rio
foundation has been publishing information on landslide occurrences by means of
yearly landslide reports (<uri>http://www0.rio.rj.gov.br/alertario/</uri>) which
comprise the time of occurrence, the main characteristics and the location
of the recorded phenomena. The warnings database has been created from
information directly gathered at the GEO-Rio Foundation. For the chosen
period of analysis Calvello et al. (2015b) show that 72 % of the recorded
landslides occurred in Baia de Guanabara, where seven warning events reached a
high or very high warning level, and 10 % of the recorded landslides occurred
in Zona Sul, where five warning events reached a high or very high warning
level.</p>
      <p>The parametric analysis conducted herein has a twofold purpose: to compare
the performance of the Alerta Rio early warning model in two different alert
zones of the city and to evaluate the effect of the choices the analyst needs
to make to define LE and WE on the
performance indicators computed according to the EDuMaP method within a
given alert zone. To investigate the latter, the Baia de Guanabara alert
zone was chosen.</p>

<?xmltex \floatpos{p}?><table-wrap id="Ch1.T9" orientation="landscape"><caption><p>Simulations of the parametric analysis: values of the input
parameters needed to define the landslide and warning events.</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.85}[.85]?><oasis:tgroup cols="15">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:colspec colnum="4" colname="col4" align="left"/>
     <oasis:colspec colnum="5" colname="col5" align="left"/>
     <oasis:colspec colnum="6" colname="col6" align="left"/>
     <oasis:colspec colnum="7" colname="col7" align="left"/>
     <oasis:colspec colnum="8" colname="col8" align="left"/>
     <oasis:colspec colnum="9" colname="col9" align="left"/>
     <oasis:colspec colnum="10" colname="col10" align="left"/>
     <oasis:colspec colnum="11" colname="col11" align="left"/>
     <oasis:colspec colnum="12" colname="col12" align="left"/>
     <oasis:colspec colnum="13" colname="col13" align="left"/>
     <oasis:colspec colnum="14" colname="col14" align="left"/>
     <oasis:colspec colnum="15" colname="col15" align="left"/>
     <oasis:thead>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">ZS-T1</oasis:entry>  
         <oasis:entry colname="col3">G-T1</oasis:entry>  
         <oasis:entry colname="col4">G-U1</oasis:entry>  
         <oasis:entry colname="col5">G-T2</oasis:entry>  
         <oasis:entry colname="col6">G-T3</oasis:entry>  
         <oasis:entry colname="col7">G-T4</oasis:entry>  
         <oasis:entry colname="col8">G-Z1</oasis:entry>  
         <oasis:entry colname="col9">G-W1</oasis:entry>  
         <oasis:entry colname="col10">G-A1</oasis:entry>  
         <oasis:entry colname="col11">G-B1</oasis:entry>  
         <oasis:entry colname="col12">G-C1</oasis:entry>  
         <oasis:entry colname="col13">G-E1</oasis:entry>  
         <oasis:entry colname="col14">G-F1</oasis:entry>  
         <oasis:entry colname="col15">G-W5</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>W</mml:mi><mml:mtext>lev</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">4</oasis:entry>  
         <oasis:entry colname="col3">4</oasis:entry>  
         <oasis:entry colname="col4">4</oasis:entry>  
         <oasis:entry colname="col5">4</oasis:entry>  
         <oasis:entry colname="col6">4</oasis:entry>  
         <oasis:entry colname="col7">4</oasis:entry>  
         <oasis:entry colname="col8">4</oasis:entry>  
         <oasis:entry colname="col9">4</oasis:entry>  
         <oasis:entry colname="col10">4</oasis:entry>  
         <oasis:entry colname="col11">4</oasis:entry>  
         <oasis:entry colname="col12">4</oasis:entry>  
         <oasis:entry colname="col13">4</oasis:entry>  
         <oasis:entry colname="col14">4</oasis:entry>  
         <oasis:entry colname="col15">4</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col3">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col4">mixed (<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mtext>susc</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col5">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col6">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col7">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col8">mixed (<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mtext>susc</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col9">mixed (<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mtext>susc</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col10">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col11">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col12">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col13">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col14">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>  
         <oasis:entry colname="col15">mixed (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>)</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0</oasis:entry>  
         <oasis:entry colname="col3">0</oasis:entry>  
         <oasis:entry colname="col4">0</oasis:entry>  
         <oasis:entry colname="col5">0</oasis:entry>  
         <oasis:entry colname="col6">0</oasis:entry>  
         <oasis:entry colname="col7">0</oasis:entry>  
         <oasis:entry colname="col8">0</oasis:entry>  
         <oasis:entry colname="col9">0</oasis:entry>  
         <oasis:entry colname="col10">0</oasis:entry>  
         <oasis:entry colname="col11">1 h</oasis:entry>  
         <oasis:entry colname="col12">3 h</oasis:entry>  
         <oasis:entry colname="col13">1 h</oasis:entry>  
         <oasis:entry colname="col14">0</oasis:entry>  
         <oasis:entry colname="col15">0</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>typ</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">ALL</oasis:entry>  
         <oasis:entry colname="col3">ALL</oasis:entry>  
         <oasis:entry colname="col4">ALL</oasis:entry>  
         <oasis:entry colname="col5">ALL</oasis:entry>  
         <oasis:entry colname="col6">ALL</oasis:entry>  
         <oasis:entry colname="col7">ALL</oasis:entry>  
         <oasis:entry colname="col8">R-I</oasis:entry>  
         <oasis:entry colname="col9">T1</oasis:entry>  
         <oasis:entry colname="col10">ALL</oasis:entry>  
         <oasis:entry colname="col11">ALL</oasis:entry>  
         <oasis:entry colname="col12">ALL</oasis:entry>  
         <oasis:entry colname="col13">ALL</oasis:entry>  
         <oasis:entry colname="col14">ALL</oasis:entry>  
         <oasis:entry colname="col15">T1</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">12 h</oasis:entry>  
         <oasis:entry colname="col3">12 h</oasis:entry>  
         <oasis:entry colname="col4">12 h</oasis:entry>  
         <oasis:entry colname="col5">12 h</oasis:entry>  
         <oasis:entry colname="col6">12 h</oasis:entry>  
         <oasis:entry colname="col7">12 h</oasis:entry>  
         <oasis:entry colname="col8">12 h</oasis:entry>  
         <oasis:entry colname="col9">12 h</oasis:entry>  
         <oasis:entry colname="col10">12 h</oasis:entry>  
         <oasis:entry colname="col11">12 h</oasis:entry>  
         <oasis:entry colname="col12">24 h</oasis:entry>  
         <oasis:entry colname="col13">12 h</oasis:entry>  
         <oasis:entry colname="col14">24 h</oasis:entry>  
         <oasis:entry colname="col15">12 h</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0</oasis:entry>  
         <oasis:entry colname="col3">0</oasis:entry>  
         <oasis:entry colname="col4">0</oasis:entry>  
         <oasis:entry colname="col5">0</oasis:entry>  
         <oasis:entry colname="col6">0</oasis:entry>  
         <oasis:entry colname="col7">0</oasis:entry>  
         <oasis:entry colname="col8">0</oasis:entry>  
         <oasis:entry colname="col9">0</oasis:entry>  
         <oasis:entry colname="col10">6 h</oasis:entry>  
         <oasis:entry colname="col11">6 h</oasis:entry>  
         <oasis:entry colname="col12">12 h</oasis:entry>  
         <oasis:entry colname="col13">0</oasis:entry>  
         <oasis:entry colname="col14">0</oasis:entry>  
         <oasis:entry colname="col15">0</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">A</oasis:entry>  
         <oasis:entry colname="col2">ZS</oasis:entry>  
         <oasis:entry colname="col3">G</oasis:entry>  
         <oasis:entry colname="col4">G</oasis:entry>  
         <oasis:entry colname="col5">G</oasis:entry>  
         <oasis:entry colname="col6">G</oasis:entry>  
         <oasis:entry colname="col7">G</oasis:entry>  
         <oasis:entry colname="col8">G</oasis:entry>  
         <oasis:entry colname="col9">G</oasis:entry>  
         <oasis:entry colname="col10">G</oasis:entry>  
         <oasis:entry colname="col11">G</oasis:entry>  
         <oasis:entry colname="col12">G</oasis:entry>  
         <oasis:entry colname="col13">G</oasis:entry>  
         <oasis:entry colname="col14">G</oasis:entry>  
         <oasis:entry colname="col15">G</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>A</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">ZS</oasis:entry>  
         <oasis:entry colname="col3">G</oasis:entry>  
         <oasis:entry colname="col4">G</oasis:entry>  
         <oasis:entry colname="col5">G</oasis:entry>  
         <oasis:entry colname="col6">G</oasis:entry>  
         <oasis:entry colname="col7">G</oasis:entry>  
         <oasis:entry colname="col8">G</oasis:entry>  
         <oasis:entry colname="col9">G</oasis:entry>  
         <oasis:entry colname="col10">G</oasis:entry>  
         <oasis:entry colname="col11">G</oasis:entry>  
         <oasis:entry colname="col12">G</oasis:entry>  
         <oasis:entry colname="col13">G</oasis:entry>  
         <oasis:entry colname="col14">G</oasis:entry>  
         <oasis:entry colname="col15">G</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">2010–12</oasis:entry>  
         <oasis:entry colname="col3">2010–12</oasis:entry>  
         <oasis:entry colname="col4">2010–12</oasis:entry>  
         <oasis:entry colname="col5">2010</oasis:entry>  
         <oasis:entry colname="col6">2011</oasis:entry>  
         <oasis:entry colname="col7">2012</oasis:entry>  
         <oasis:entry colname="col8">2010–12</oasis:entry>  
         <oasis:entry colname="col9">2010–12</oasis:entry>  
         <oasis:entry colname="col10">2010–12</oasis:entry>  
         <oasis:entry colname="col11">2010–12</oasis:entry>  
         <oasis:entry colname="col12">2010–12</oasis:entry>  
         <oasis:entry colname="col13">2010–12</oasis:entry>  
         <oasis:entry colname="col14">2010–12</oasis:entry>  
         <oasis:entry colname="col15">2010–12</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col3">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col4">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col5">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col6">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col7">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col8">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col9">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col10">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col11">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col12">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col13">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col14">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col15">1<inline-formula><mml:math display="inline"><mml:msup><mml:mi/><mml:mo>′</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T10"><caption><p>Duration matrix of simulation ZS_T1.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="6">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="right"/>
     <oasis:colspec colnum="4" colname="col4" align="right"/>
     <oasis:colspec colnum="5" colname="col5" align="right"/>
     <oasis:colspec colnum="6" colname="col6" align="right"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry rowsep="1" namest="col3" nameend="col6" align="center">LE duration (h) </oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">1 (no)</oasis:entry>  
         <oasis:entry colname="col4">2 (S)</oasis:entry>  
         <oasis:entry colname="col5">3 (I)</oasis:entry>  
         <oasis:entry colname="col6">4 (L)</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">WE</oasis:entry>  
         <oasis:entry colname="col2">1 (no)</oasis:entry>  
         <oasis:entry colname="col3">8185.1</oasis:entry>  
         <oasis:entry colname="col4">19.1</oasis:entry>  
         <oasis:entry colname="col5">20.4</oasis:entry>  
         <oasis:entry colname="col6">0.0</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">duration</oasis:entry>  
         <oasis:entry colname="col2">2 (M)</oasis:entry>  
         <oasis:entry colname="col3">288.4</oasis:entry>  
         <oasis:entry colname="col4">16.7</oasis:entry>  
         <oasis:entry colname="col5">0.7</oasis:entry>  
         <oasis:entry colname="col6">0.0</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">(h)</oasis:entry>  
         <oasis:entry colname="col2">3 (H)</oasis:entry>  
         <oasis:entry colname="col3">90.0</oasis:entry>  
         <oasis:entry colname="col4">6.0</oasis:entry>  
         <oasis:entry colname="col5">3.1</oasis:entry>  
         <oasis:entry colname="col6">32.4</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">4 (VH)</oasis:entry>  
         <oasis:entry colname="col3">28.5</oasis:entry>  
         <oasis:entry colname="col4">0.1</oasis:entry>  
         <oasis:entry colname="col5">38.1</oasis:entry>  
         <oasis:entry colname="col6">31.4</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T11"><caption><p>Duration matrix of simulation G_T1.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="6">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="right"/>
     <oasis:colspec colnum="4" colname="col4" align="center"/>
     <oasis:colspec colnum="5" colname="col5" align="center"/>
     <oasis:colspec colnum="6" colname="col6" align="right"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry rowsep="1" namest="col3" nameend="col6" align="center">LE duration (h) </oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">1 (no)</oasis:entry>  
         <oasis:entry colname="col4">2 (S)</oasis:entry>  
         <oasis:entry colname="col5">3 (I)</oasis:entry>  
         <oasis:entry colname="col6">4 (L)</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">WE</oasis:entry>  
         <oasis:entry colname="col2">1 (no)</oasis:entry>  
         <oasis:entry colname="col3">8281.8</oasis:entry>  
         <oasis:entry colname="col4">0.4</oasis:entry>  
         <oasis:entry colname="col5">0.0</oasis:entry>  
         <oasis:entry colname="col6">0.0</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">duration</oasis:entry>  
         <oasis:entry colname="col2">2 (M)</oasis:entry>  
         <oasis:entry colname="col3">302.0</oasis:entry>  
         <oasis:entry colname="col4">0.0</oasis:entry>  
         <oasis:entry colname="col5">0.0</oasis:entry>  
         <oasis:entry colname="col6">5.4</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">(h)</oasis:entry>  
         <oasis:entry colname="col2">3 (H)</oasis:entry>  
         <oasis:entry colname="col3">100.1</oasis:entry>  
         <oasis:entry colname="col4">0.2</oasis:entry>  
         <oasis:entry colname="col5">0.0</oasis:entry>  
         <oasis:entry colname="col6">2.8</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">4 (VH)</oasis:entry>  
         <oasis:entry colname="col3">54.8</oasis:entry>  
         <oasis:entry colname="col4">0.0</oasis:entry>  
         <oasis:entry colname="col5">0.0</oasis:entry>  
         <oasis:entry colname="col6">12.6</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <p>Table 9 shows the values used for each simulation of the parametric analysis
for the 10 input parameters needed to define the landslide and warning
events. The values of the input parameters chosen for simulations
ZS_T1 and G_T1, which refer to
the two base cases for the alert zones Zona Sul and Baia de Guanabara, respectively,
adequately represent the structure and the operative procedures of the
warning model employed within Alerta Rio. For these two simulations, the
following values of the 10 input parameters are used: area of analysis,
<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>, equal to ZS and G, respectively; warning levels, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>W</mml:mi><mml:mtext>lev</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to 4;
landslide density, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, defined according to the mixed
criterion shown in Table 3; lead time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to 0; landslide
typology, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>typ</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to all recorded landslides; minimum interval
between landslide events, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to 12 h; over time,
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to 0; spatial discretization adopted for warnings,
<inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>A</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, equal to the area of analysis A; time frame of analysis,
<inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi><mml:mo>,</mml:mo></mml:mrow></mml:math></inline-formula> equal to the 3-year period 2010–2012; temporal
discretization of analysis, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:math></inline-formula>, equal to 1 min. All the remaining
simulations, from G-U01 to G-W05, refer to the alert zone Baia de Guanabara.
These simulations are used to explore the sensitivity of the performance
evaluation of the Alerta Rio regional warning model to changes in the input
parameters, whose values differ, depending on choices made by the analyst,
also under the same set of landslides and warnings data. To this purpose,
the input parameters investigated are landslide density,
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, defined according to the mixed criterion shown in Table 3
either in relation to the whole area of analysis (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>) or in relation to the
extent of the area most susceptible to landslides (<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mtext>susc</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>); lead time,
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, varying from 0 to 3 h; landslide typology,
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>typ</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to all recorded landslides (ALL), all typologies of
landslides excluding rock falls (R-I) and earth slides in artificial slopes (T1);
minimum interval between landslide events, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, equal to
12 and 24 h; over time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, varying from 0 to 12 h; and time
frame of analysis, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi><mml:mo>,</mml:mo></mml:mrow></mml:math></inline-formula> equal to the whole 3-year period
2010–2012 or to the single years 2010, 2011 and 2012.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F9" specific-use="star"><caption><p>Simulations for the base cases of alert zones Guanabara (G-T1) and
Zona Sul (ZS-T1): distribution of the elements of the duration matrix in
terms of criterion A (correct alerts, CAs; missed alerts, MAs; false alerts,
FAs; true negatives, TNs) and criterion B (color code following a grade of
correctness from green to purple).</p></caption>
          <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f09.pdf"/>

        </fig>

      <?xmltex \floatpos{t}?><fig id="Ch1.F10" specific-use="star"><caption><p>Simulations for the base cases of alert zones Guanabara (G-T1)
and Zona Sul (ZS-T1). Number of landslide events (LE) and warning levels
issued, normalized, respectively, in relation to <bold>(a, c)</bold> landslide events,
d_LE<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> (Eq. 2), and <bold>(b, d)</bold> warning events (WE), d_WE<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> (Eq. 3).</p></caption>
          <?xmltex \igopts{width=284.527559pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f10.png"/>

        </fig>

      <?xmltex \floatpos{t}?><fig id="Ch1.F11" specific-use="star"><caption><p>Simulations for different cases of alert zone Guanabara,
G_T1 to G_W5 (see Table 9 for the input
parameters used for the events analysis): values of performance indicators
related to the success <bold>(a)</bold> and to the errors <bold>(b)</bold> of the warning model.</p></caption>
          <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f11.png"/>

        </fig>

      <?xmltex \floatpos{t}?><fig id="Ch1.F12" specific-use="star"><caption><p>Simulations for different cases of alert zone Guanabara,
G_T1 to G_W5 (see Table 9 for the input
parameters used for the events analysis): values of all the performance
indicators related to errors of the warning model, grouped to highlight the
effect of parameters <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>typ</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> <bold>(a)</bold> and parameters
<inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> <bold>(b)</bold>.</p></caption>
          <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/16/103/2016/nhess-16-103-2016-f12.png"/>

        </fig>

</sec>
<sec id="Ch1.S4.SS3">
  <title>Results of parametric analysis</title>
      <p>The duration matrices of Tables 10 and 11 report the results of the first
two simulations of the parametric analysis, ZS_T1 and
G_T1, which only differ in relation to the area of analysis,
the Zona Sul and the Baia de Guanabara alert zones, respectively. Figures 9
and 10 show a comparison of the results of the first two simulations,
ZS_T1 and G_T1. Considering performance
criterion A, Zona Sul and Baia de Guanabara both present a high rate of TNs and a low rate of MAs. The low rate of
computed MAs also turns into a good predicting capability in relation to
intermediate and large landslide events occurring in these zones. Baia de
Guanabara shows time values associated to CAs much higher
than the corresponding values in Zona Sul: 18.3 % versus
3.2 % of the total considered time. These differences justify the fact
that the value of efficiency index (<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>eff</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>) computed for Baia de
Guanabara, 75 %, is higher than that computed for Zona Sul, 66 %;
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>R</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> is also slightly higher for Zona Sul. The results for Zona
Sul also highlight a relatively high rate of FAs (32 %), probably due to
values of rainfall thresholds inadequately low for this alert zone. This
condition, together with a low value of CAs, explains
the high value of the missed alert rate
(91 %) for Zona Sul. Considering performance criterion B, approximately
the same time rate of yellow elements (minor model errors) and red elements
(significant model errors) are observed for the two alert zones. Significant
is, however, the difference in the time rate of purple elements (worst model
errors), which is much higher for Zona Sul than for Baia de Guanabara. It is
interesting to notice that Zona Sul has a low rate of MAs, yet <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> is
equal to 1 because the only value of MA is a serious model error. Finally,
slightly high values are computed for Zona Sul for the probability of
serious mistakes (<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mtext>SM</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>), probability of serious no-warning mistakes
(<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NW</mml:mtext></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> and probability of serious no-landslides mistakes
(<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NL</mml:mtext></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula>.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T12" specific-use="star"><caption><p>Values of the performance indicators for all the simulations of
the parametric analysis.</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.98}[.98]?><oasis:tgroup cols="15">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="center"/>
     <oasis:colspec colnum="4" colname="col4" align="center"/>
     <oasis:colspec colnum="5" colname="col5" align="center"/>
     <oasis:colspec colnum="6" colname="col6" align="center"/>
     <oasis:colspec colnum="7" colname="col7" align="center"/>
     <oasis:colspec colnum="8" colname="col8" align="center"/>
     <oasis:colspec colnum="9" colname="col9" align="center"/>
     <oasis:colspec colnum="10" colname="col10" align="center"/>
     <oasis:colspec colnum="11" colname="col11" align="center"/>
     <oasis:colspec colnum="12" colname="col12" align="center"/>
     <oasis:colspec colnum="13" colname="col13" align="center"/>
     <oasis:colspec colnum="14" colname="col14" align="center"/>
     <oasis:colspec colnum="15" colname="col15" align="center"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">Performance</oasis:entry>  
         <oasis:entry colname="col2">ZS-T1</oasis:entry>  
         <oasis:entry colname="col3">G-T1</oasis:entry>  
         <oasis:entry colname="col4">G-U1</oasis:entry>  
         <oasis:entry colname="col5">G-T2</oasis:entry>  
         <oasis:entry colname="col6">G-T3</oasis:entry>  
         <oasis:entry colname="col7">G-T4</oasis:entry>  
         <oasis:entry colname="col8">G-Z1</oasis:entry>  
         <oasis:entry colname="col9">G-W1</oasis:entry>  
         <oasis:entry colname="col10">G-A1</oasis:entry>  
         <oasis:entry colname="col11">G-B1</oasis:entry>  
         <oasis:entry colname="col12">G-C1</oasis:entry>  
         <oasis:entry colname="col13">G-E1</oasis:entry>  
         <oasis:entry colname="col14">G-F1</oasis:entry>  
         <oasis:entry colname="col15">G-W5</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">indicator</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9"/>  
         <oasis:entry colname="col10"/>  
         <oasis:entry colname="col11"/>  
         <oasis:entry colname="col12"/>  
         <oasis:entry colname="col13"/>  
         <oasis:entry colname="col14"/>  
         <oasis:entry colname="col15"/>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>eff</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0.66</oasis:entry>  
         <oasis:entry colname="col3">0.75</oasis:entry>  
         <oasis:entry colname="col4">0.73</oasis:entry>  
         <oasis:entry colname="col5">0.71</oasis:entry>  
         <oasis:entry colname="col6">0.92</oasis:entry>  
         <oasis:entry colname="col7">1.00</oasis:entry>  
         <oasis:entry colname="col8">0.71</oasis:entry>  
         <oasis:entry colname="col9">0.64</oasis:entry>  
         <oasis:entry colname="col10">0.78</oasis:entry>  
         <oasis:entry colname="col11">0.78</oasis:entry>  
         <oasis:entry colname="col12">0.68</oasis:entry>  
         <oasis:entry colname="col13">0.75</oasis:entry>  
         <oasis:entry colname="col14">0.65</oasis:entry>  
         <oasis:entry colname="col15">0.60</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">HR<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mtext>L</mml:mtext></mml:msub></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0.74</oasis:entry>  
         <oasis:entry colname="col3">0.83</oasis:entry>  
         <oasis:entry colname="col4">0.76</oasis:entry>  
         <oasis:entry colname="col5">0.79</oasis:entry>  
         <oasis:entry colname="col6">0.98</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.74</oasis:entry>  
         <oasis:entry colname="col9">0.99</oasis:entry>  
         <oasis:entry colname="col10">0.85</oasis:entry>  
         <oasis:entry colname="col11">0.83</oasis:entry>  
         <oasis:entry colname="col12">0.46</oasis:entry>  
         <oasis:entry colname="col13">0.81</oasis:entry>  
         <oasis:entry colname="col14">0.49</oasis:entry>  
         <oasis:entry colname="col15">1.00</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">PP<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mtext>W</mml:mtext></mml:msub></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0.09</oasis:entry>  
         <oasis:entry colname="col3">0.46</oasis:entry>  
         <oasis:entry colname="col4">0.48</oasis:entry>  
         <oasis:entry colname="col5">0.40</oasis:entry>  
         <oasis:entry colname="col6">0.83</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.43</oasis:entry>  
         <oasis:entry colname="col9">0.16</oasis:entry>  
         <oasis:entry colname="col10">0.53</oasis:entry>  
         <oasis:entry colname="col11">0.54</oasis:entry>  
         <oasis:entry colname="col12">0.65</oasis:entry>  
         <oasis:entry colname="col13">0.46</oasis:entry>  
         <oasis:entry colname="col14">0.50</oasis:entry>  
         <oasis:entry colname="col15">0.06</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">TS</oasis:entry>  
         <oasis:entry colname="col2">0.09</oasis:entry>  
         <oasis:entry colname="col3">0.42</oasis:entry>  
         <oasis:entry colname="col4">0.42</oasis:entry>  
         <oasis:entry colname="col5">0.36</oasis:entry>  
         <oasis:entry colname="col6">0.82</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.38</oasis:entry>  
         <oasis:entry colname="col9">0.16</oasis:entry>  
         <oasis:entry colname="col10">0.49</oasis:entry>  
         <oasis:entry colname="col11">0.49</oasis:entry>  
         <oasis:entry colname="col12">0.37</oasis:entry>  
         <oasis:entry colname="col13">0.42</oasis:entry>  
         <oasis:entry colname="col14">0.33</oasis:entry>  
         <oasis:entry colname="col15">0.06</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">OR</oasis:entry>  
         <oasis:entry colname="col2">1.98</oasis:entry>  
         <oasis:entry colname="col3">2.95</oasis:entry>  
         <oasis:entry colname="col4">2.74</oasis:entry>  
         <oasis:entry colname="col5">2.50</oasis:entry>  
         <oasis:entry colname="col6">11.51</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">2.42</oasis:entry>  
         <oasis:entry colname="col9">1.78</oasis:entry>  
         <oasis:entry colname="col10">3.58</oasis:entry>  
         <oasis:entry colname="col11">3.64</oasis:entry>  
         <oasis:entry colname="col12">2.17</oasis:entry>  
         <oasis:entry colname="col13">2.99</oasis:entry>  
         <oasis:entry colname="col14">1.87</oasis:entry>  
         <oasis:entry colname="col15">1.47</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">MR</oasis:entry>  
         <oasis:entry colname="col2">0.34</oasis:entry>  
         <oasis:entry colname="col3">0.25</oasis:entry>  
         <oasis:entry colname="col4">0.27</oasis:entry>  
         <oasis:entry colname="col5">0.29</oasis:entry>  
         <oasis:entry colname="col6">0.08</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.29</oasis:entry>  
         <oasis:entry colname="col9">0.36</oasis:entry>  
         <oasis:entry colname="col10">0.22</oasis:entry>  
         <oasis:entry colname="col11">0.22</oasis:entry>  
         <oasis:entry colname="col12">0.32</oasis:entry>  
         <oasis:entry colname="col13">0.25</oasis:entry>  
         <oasis:entry colname="col14">0.35</oasis:entry>  
         <oasis:entry colname="col15">0.40</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>R</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0.26</oasis:entry>  
         <oasis:entry colname="col3">0.17</oasis:entry>  
         <oasis:entry colname="col4">0.24</oasis:entry>  
         <oasis:entry colname="col5">0.21</oasis:entry>  
         <oasis:entry colname="col6">0.02</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.26</oasis:entry>  
         <oasis:entry colname="col9">0.01</oasis:entry>  
         <oasis:entry colname="col10">0.15</oasis:entry>  
         <oasis:entry colname="col11">0.17</oasis:entry>  
         <oasis:entry colname="col12">0.54</oasis:entry>  
         <oasis:entry colname="col13">0.19</oasis:entry>  
         <oasis:entry colname="col14">0.51</oasis:entry>  
         <oasis:entry colname="col15">0.00</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>R</mml:mi><mml:mtext>FA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0.91</oasis:entry>  
         <oasis:entry colname="col3">0.54</oasis:entry>  
         <oasis:entry colname="col4">0.52</oasis:entry>  
         <oasis:entry colname="col5">0.60</oasis:entry>  
         <oasis:entry colname="col6">0.17</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.57</oasis:entry>  
         <oasis:entry colname="col9">0.84</oasis:entry>  
         <oasis:entry colname="col10">0.47</oasis:entry>  
         <oasis:entry colname="col11">0.46</oasis:entry>  
         <oasis:entry colname="col12">0.35</oasis:entry>  
         <oasis:entry colname="col13">0.54</oasis:entry>  
         <oasis:entry colname="col14">0.50</oasis:entry>  
         <oasis:entry colname="col15">0.94</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">ER</oasis:entry>  
         <oasis:entry colname="col2">0.34</oasis:entry>  
         <oasis:entry colname="col3">0.25</oasis:entry>  
         <oasis:entry colname="col4">0.27</oasis:entry>  
         <oasis:entry colname="col5">0.29</oasis:entry>  
         <oasis:entry colname="col6">0.08</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.29</oasis:entry>  
         <oasis:entry colname="col9">0.36</oasis:entry>  
         <oasis:entry colname="col10">0.22</oasis:entry>  
         <oasis:entry colname="col11">0.22</oasis:entry>  
         <oasis:entry colname="col12">0.32</oasis:entry>  
         <oasis:entry colname="col13">0.25</oasis:entry>  
         <oasis:entry colname="col14">0.35</oasis:entry>  
         <oasis:entry colname="col15">0.40</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mtext>SM</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0.13</oasis:entry>  
         <oasis:entry colname="col3">0.05</oasis:entry>  
         <oasis:entry colname="col4">0.09</oasis:entry>  
         <oasis:entry colname="col5">0.05</oasis:entry>  
         <oasis:entry colname="col6">0.05</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.11</oasis:entry>  
         <oasis:entry colname="col9">0.13</oasis:entry>  
         <oasis:entry colname="col10">0.03</oasis:entry>  
         <oasis:entry colname="col11">0.03</oasis:entry>  
         <oasis:entry colname="col12">0.04</oasis:entry>  
         <oasis:entry colname="col13">0.05</oasis:entry>  
         <oasis:entry colname="col14">0.07</oasis:entry>  
         <oasis:entry colname="col15">0.17</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NW</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0.00</oasis:entry>  
         <oasis:entry colname="col3">0.00</oasis:entry>  
         <oasis:entry colname="col4">0.52</oasis:entry>  
         <oasis:entry colname="col5">0.00</oasis:entry>  
         <oasis:entry colname="col6">0.00</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.73</oasis:entry>  
         <oasis:entry colname="col9">0.00</oasis:entry>  
         <oasis:entry colname="col10">0.00</oasis:entry>  
         <oasis:entry colname="col11">0.00</oasis:entry>  
         <oasis:entry colname="col12">0.10</oasis:entry>  
         <oasis:entry colname="col13">0.00</oasis:entry>  
         <oasis:entry colname="col14">0.13</oasis:entry>  
         <oasis:entry colname="col15">0.00</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NL</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0.12</oasis:entry>  
         <oasis:entry colname="col3">0.07</oasis:entry>  
         <oasis:entry colname="col4">0.07</oasis:entry>  
         <oasis:entry colname="col5">0.07</oasis:entry>  
         <oasis:entry colname="col6">0.09</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.09</oasis:entry>  
         <oasis:entry colname="col9">0.15</oasis:entry>  
         <oasis:entry colname="col10">0.06</oasis:entry>  
         <oasis:entry colname="col11">0.05</oasis:entry>  
         <oasis:entry colname="col12">0.05</oasis:entry>  
         <oasis:entry colname="col13">0.07</oasis:entry>  
         <oasis:entry colname="col14">0.08</oasis:entry>  
         <oasis:entry colname="col15">0.15</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">1.00</oasis:entry>  
         <oasis:entry colname="col3">0.00</oasis:entry>  
         <oasis:entry colname="col4">0.59</oasis:entry>  
         <oasis:entry colname="col5">0.00</oasis:entry>  
         <oasis:entry colname="col6">0.00</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.59</oasis:entry>  
         <oasis:entry colname="col9">0.00</oasis:entry>  
         <oasis:entry colname="col10">0.00</oasis:entry>  
         <oasis:entry colname="col11">0.04</oasis:entry>  
         <oasis:entry colname="col12">0.14</oasis:entry>  
         <oasis:entry colname="col13">0.04</oasis:entry>  
         <oasis:entry colname="col14">0.15</oasis:entry>  
         <oasis:entry colname="col15">0.00</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>FA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col2">0.35</oasis:entry>  
         <oasis:entry colname="col3">0.23</oasis:entry>  
         <oasis:entry colname="col4">0.24</oasis:entry>  
         <oasis:entry colname="col5">0.21</oasis:entry>  
         <oasis:entry colname="col6">0.64</oasis:entry>  
         <oasis:entry colname="col7">0.00</oasis:entry>  
         <oasis:entry colname="col8">0.31</oasis:entry>  
         <oasis:entry colname="col9">0.37</oasis:entry>  
         <oasis:entry colname="col10">0.18</oasis:entry>  
         <oasis:entry colname="col11">0.18</oasis:entry>  
         <oasis:entry colname="col12">0.15</oasis:entry>  
         <oasis:entry colname="col13">0.23</oasis:entry>  
         <oasis:entry colname="col14">0.25</oasis:entry>  
         <oasis:entry colname="col15">0.43</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

      <p>Simulations G_T1 to G_W5 refer to the alert
zone Baia de Guanabara and may thus be used to explore the sensitivity of
the performance evaluation to the changes in the values of the other input
parameters (Table 12, Figs. 11 and 12). The simulations addressing the parameters
landslide density, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, and landslide typology, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mtext>typ</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, are
the following: G_T1, G_U1, G_Z1, G_W1 and G_W5. The definition of the
landslide density parameter, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mtext>den</mml:mtext><mml:mo>(</mml:mo><mml:mi>k</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, in relation to the whole area
of analysis (<inline-formula><mml:math display="inline"><mml:mi>A</mml:mi></mml:math></inline-formula>) or in relation to the extent of the area most susceptible to
landslides (<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>A</mml:mi><mml:mtext>susc</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>) does not play an important role for some performance
indicators (e.g., EI<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mrow><mml:mo>(</mml:mo><mml:mtext>A</mml:mtext><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:math></inline-formula>, GC<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mrow><mml:mo>(</mml:mo><mml:mtext>B</mml:mtext><mml:mo>)</mml:mo></mml:mrow></mml:msub></mml:math></inline-formula>, PP<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mtext>W</mml:mtext></mml:msub></mml:math></inline-formula>, HR, OR, R<inline-formula><mml:math display="inline"><mml:msub><mml:mi/><mml:mtext>FA</mml:mtext></mml:msub></mml:math></inline-formula>) while it may be very
relevant for others (e.g., <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NW</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NL</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>) (Table 12). The area considered
when computing this parameter has, indeed, a strong influence on the number
of landslides set as thresholds to differentiate among classes of landslide
events. In particular, when the area reduces, the threshold values decrease
and, other parameters being equal, the number of very large and large
landslide events tends to increase. The latter implies an increasing
probability of MAs and of the worst model errors (Pur) in this region of the
matrix. For instance, the fact that simulation G_U1 shows
high values of <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NW</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> (Table 12) depends on a single missed
landslide event classified as class 4 (L), differently from the
classification 3 (I) resulting from the base simulation G_T1.
As far as landslide typology is concerned, the results from the two
combinations associated only to the occurrence of earth slides on artificial
slopes (G_W1 and G_W5) are similar and show
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>eff(A)</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> less than 70 %, HR around 100 %, very few MAs, around
35 % of FAs and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>FA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> values much higher than the rest of the simulations (Table 12).
Probably the latter is due to two concurrent factors: threshold values which
are set too low for this landslide typology and lower average duration of the
landslide events due to the reduced number of landslides compared to the
other simulations. Concerning the three parameters lead time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>,
over time, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, and minimum interval between landslide events,
<inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, the simulations relevant to explore their importance are
the following: G_T1, G_A1, G_B1, G_C1, G_E1 and G_F1. High
values of <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> considerably increase the values of the
performance indicators related to the rate of MAs (<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>R</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula>, ER, MR, <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mtext>SM</mml:mtext><mml:mo>-</mml:mo><mml:mtext>NW</mml:mtext></mml:mrow></mml:msub></mml:mrow></mml:math></inline-formula>), while
the rate of FAs does not change significantly. This is due to the fact that
the higher the value of <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> is, the lower  the number of
landslide events, the higher  the duration of each landslide event and the
higher  the chance to have time periods associated to landslide events
without warning events. These results seem to indicate that an appropriate
performance evaluation needs parameter <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mtext>LE</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> to be set, by the
analyst, to a value lower than 24 h. The comparison of results for
G_T1 and G_A1 shows that the introduction of a
<inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> of 6 h increases the performance by reducing the FAs and
increasing the CAs. Consequently <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>I</mml:mi><mml:mtext>FA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>R</mml:mi><mml:mtext>MA</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> slightly decrease
compared to the case G_T1 (Table 12), for which <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>OVER</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> is equal to
0. On the contrary, parameter <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>t</mml:mi><mml:mtext>LEAD</mml:mtext></mml:msub></mml:mrow></mml:math></inline-formula> does not play an important role
for this analysis. Finally, the simulations which are relevant to explore
the importance of the time frame of analysis, <inline-formula><mml:math display="inline"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:mi>T</mml:mi></mml:mrow></mml:math></inline-formula>, are the
followings: G_T1, G_T2, G_T3 and G_T4. The resulting values of the performance indicators from
these simulations highlight the importance played by the data set used for
the performance analysis. Indeed, the inconsistency between the results of
the two simulations which consider the single years 2011 and 2012
(G_T3 and G_T4) and the rest of the simulations may be ascribed to the very
limited amount of data available for those years, for which very few landslides
occurred and very few warnings were issued.</p>
</sec>
</sec>
<sec id="Ch1.S5" sec-type="conclusions">
  <title>Conclusions</title>
      <p>A regional landslide early warning system may be schematized as a system
with the following components: regional warning model, monitoring and
warning strategy, communication strategy and emergency plan. The focus of this
article was on the performance evaluation of regional warning models for
rainfall-induced landslides, that is to say on the effectiveness of the
functional relationship between rainfall events and landslide events used
within the decision-making procedures adopted to issue the warnings. It is
import to highlight that the proposed performance assessment method does not
address other important issues related to system effectiveness, such as
risk perception, policy adopted to communicate with the people at risk,
evacuation procedures, monitoring network and instruments used to issue the warnings.</p>
      <p>The proposed approach, which has been called EDuMaP method, evaluates the
performance of a regional landslide warning model following three successive
steps: (1) identification and analysis of landslide events and warning events
derived from available landslides and warnings databases, (2) definition and
computation of a duration matrix reporting the time associated with the
occurrence of landslide events in relation to the occurrence of warning
events and (3) evaluation of the model performance by means of criteria and
indicators applied to the duration matrix.</p>
      <p>The main innovations introduced by the EDuMaP method, in relation to means
more commonly used to assess the performance of such models, are the following:
<?xmltex \hack{\newpage}?>
<list list-type="bullet"><list-item>
      <p>recorded landslides and issued warnings are not analyzed as a series of
individual occurrences but they are grouped within landslide and warning
events, respectively, which consider their spatial and temporal
characteristics by means of 10 input parameters;</p></list-item><list-item>
      <p>the evaluation of the correlation between landslide and warning events is
based not on counting the pairs on which the two data sets agree or
disagree but rather on computing the duration of the agreement/disagreement;</p></list-item><list-item>
      <p>the correspondence between landslide and warning events is expressed not as
a 2 by 2 confusion matrix but as a matrix, herein called duration matrix,
whose number of columns and rows depends on the schemes adopted to classify,
respectively, landslide events and warning events;</p></list-item><list-item>
      <p>the assessment of the duration matrix is based on performance indicators
derived from a set of performance criteria, which must be defined by the
system analyst/manager considering the specific characteristics and aims of
the early warning system under evaluation.</p></list-item></list>
Concerning the latter issue, two performance criteria have been used herein.
The first criterion is defined in accordance to a standard alert
classification scheme derived from a 2 by 2 contingency table, thus
identifying correct alerts, false alerts, missed alerts and true negatives.
The second criterion is defined by assigning a color
code to the elements of matrix, from green to purple, in relation to their grade of correctness. Both
criteria purposefully neglect the duration matrix element <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mn>11</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>, whose
value is typically orders of magnitude higher than the values of the other
elements. Other criteria could be used to assess the results of a duration
matrix. It is important to highlight, however, that a reasonable performance
criterion should keep the latter assumption. Indeed, if a criterion does
consider the value of the element <inline-formula><mml:math display="inline"><mml:mrow><mml:msub><mml:mi>d</mml:mi><mml:mn>11</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula>, the resulting performance
indicators would be positively “biased” for obvious reasons
(i.e., rainfall-induced landslides do not occur when it does not rain).</p>
      <p>The applicability of the EDuMaP method has been tested by conducting a
parametric analysis using 3 years of landslides and warnings data from
the municipal landslide early warning system operating in Rio de Janeiro
(Brazil). The input parameters most affecting the results of the events
analysis and, thus, the value of the elements of duration matrix for the
different simulations, are as follows: the landslide density thresholds used to
differentiate among the classes of landslide events, the set of landslides
considered in the simulations, the time set as the minimum time interval
between landslide events, the time interval between the last landslide
identified within a landslide event and the assumed ending of the landslide
event, the area of analysis and the time frame of the analysis. For instance,
the criterion herein employed to define landslide density does not work
well when the number of landslides per unit
area is computed using the area mapped as the most susceptible instead of
the whole area of analysis. The latter does not mean that a higher number of
landslides occurs outside the most susceptible area; it only means that the
thresholds used in the criterion more adequately represent a landslide
density computed over the whole alert zone. Another parameter to which the
results are very sensitive is the time interval used to identify the number
of landslides to include within a single landslide event. When this period
becomes too long (equal to or higher than 24 h), the duration of some
landslide events increases too much, and thus some time intervals are
misleadingly accounted for as serious missed alerts. Finally, as expected,
the performance assessment has proved to be very sensitive to the number of
data used, mainly function of the two parameters defining the type of
landslides and the time frame of the analysis. Of course, the results of the
performed analysis cannot be easily generalized. This is true for a number
of reasons: they have to be considered specific of the warning model adopted
by the Rio de Janeiro early warning system; not all the input parameters
were tested in the parametric analysis; the time for which both landslides
and warnings data are available is relatively short.</p>
      <p>In conclusion, the EDuMaP method proved its applicability to a real case
study, by means of a sensitivity analysis which also gave some preliminary
indications on the relative importance of the input parameters needed to
apply it. The EDuMaP method is proposed to be used for the performance
evaluation of any regional landslide early warning systems for which
landslides and warnings data are available. Moreover, given its
characteristics, it may also be easily adapted to evaluate the efficiency of
regional early warning models addressing other natural hazards.</p>
</sec>

      
      </body>
    <back><ack><title>Acknowledgements</title><p>The authors thank the GPE staff of the GEO-Rio Foundation in Rio de Janeiro
and Ricardo d'Orsi for their kindness in sharing the databases used and
their availability to share information about the Alerta Rio early warning system.</p><p>The work described in this paper was financially supported by the PhD programme
of the civil engineering department at the University of Salerno
and by the Project of National Relevance (PRIN) “Landslide risk mitigation
through sustainable countermeasures”, funded by the Italian Ministry of
Education (MIUR). <?xmltex \hack{\newline}?><?xmltex \hack{\newline}?>
Edited by: T. Glade <?xmltex \hack{\newline}?>
Reviewed by: two anonymous referees</p></ack><ref-list>
    <title>References</title>

      <ref id="bib1.bib1"><label>1</label><mixed-citation>
Aleotti, P.: A warning system for rainfall-induced shallow failures, Eng.
Geol., 73, 247–265, 2004.</mixed-citation></ref>
      <ref id="bib1.bib2"><label>2</label><mixed-citation>Baum, R. L. and Godt, J. W.: Early warning of rainfall-induced shallow
landslides and debris flows in the USA, Landslides, 7, 259–272, 2010.
 </mixed-citation></ref><?xmltex \hack{\newpage}?>
      <ref id="bib1.bib3"><label>3</label><mixed-citation>
Bell, R., Thiebes, B., Glade, T., Vinogradov, R., Kuhlmann, H., Schauerte,
W., Burghaus, S., Krummel, H., Janik, M., and Paulsen, H.: The technical
concept within the Integrative Landslide Early Warning System (ILEWS),
landslides and engineered slopes, from the past to the future, in:
Proceedings of the 10th International Symposium on Landslides and Engineered
Slopes, 30 June–4 July 2008, Xi'an, China, 1083–1088, 2008.</mixed-citation></ref>
      <ref id="bib1.bib4"><label>4</label><mixed-citation>Berti, M., Martina, M. L. V., Franceschini, S., Pignone, A., Simoni, A., and
Pizziolo, M.: Probabilistic rainfall thresholds for landslide occurrence
using a Bayesian approach, J. Geophys. Res., 117, F04006, <ext-link xlink:href="http://dx.doi.org/10.1029/2012JF002367" ext-link-type="DOI">10.1029/2012JF002367</ext-link>, 2012.</mixed-citation></ref>
      <ref id="bib1.bib5"><label>5</label><mixed-citation>
Blikra, L. H.: The Åknes rockslide: monitoring, threshold values and
early-warning, in: Landslides and Engineered Slopes, edited by: Chen, Z.,
Zhang, J. M., Ho, K., Wu, F. Q., and Li, Z. K., Taylor &amp; Francis Group,
London, 1089–1094, 2008.</mixed-citation></ref>
      <ref id="bib1.bib6"><label>6</label><mixed-citation>Calvello, M., d'Orsi, R., Piciullo, L., Paes, N. M., Magalhaes, M. A.,
Coelho, R., and Lacerda, W. A.: The community-based alert and alarm system
for rainfall induced landslides in Rio de Janeiro, Brazil, in: Engineering
Geology for Society and Territory “Landslide Processes”, Proc. XII Int. IAEG
Congress, Torino, Italy, 2, 653–657, <ext-link xlink:href="http://dx.doi.org/10.1007/978-3-319-09057-3_109" ext-link-type="DOI">10.1007/978-3-319-09057-3_109</ext-link>, 2015a.</mixed-citation></ref>
      <ref id="bib1.bib7"><label>7</label><mixed-citation>
Calvello, M., d'Orsi, R. N., Piciullo, L., Paes, N., Magalhaes, M., and
Lacerda, W. A.: The Rio de Janeiro early warning system for rainfall-induced
landslides: analysis of performance for the years 2010–2013, Int.
J. Disast. Risk Reduc., 12, 3–15, 2015b.</mixed-citation></ref>
      <ref id="bib1.bib8"><label>8</label><mixed-citation>
Cannon, S., Boldt, E., Laber, J., Kean, J., and Staley, D.: Rainfall
intensity–duration thresholds for postfire debris-flow emergency response
planning, Nat. Hazards, 59, 209–236, 2011.</mixed-citation></ref>
      <ref id="bib1.bib9"><label>9</label><mixed-citation>
Capparelli, G. and Tiranti, D.: Application of the MoniFLaIR early warning system
for rainfall induced landslides in Piedmont region (Italy), Landslides, 7, 401–410, 2010.</mixed-citation></ref>
      <ref id="bib1.bib10"><label>10</label><mixed-citation>
Chan, R. K. S. and Pun, W. K.: Landslip warning system in Hong Kong, Geotec.
Instrum. News, 22, 33–35, 2004.</mixed-citation></ref>
      <ref id="bib1.bib11"><label>11</label><mixed-citation>
Cheung, P. Y., Wong, M. C., and Yeung, H. Y.: Application of rainstorm
nowcast to real-time warning of landslide hazards in Hong Kong, in: WMO PWS,
Workshop on Warnings of Real-Time Hazards by Using Nowcasting Technology,
9–13 October 2006, Sydney, Australia, 2006.</mixed-citation></ref>
      <ref id="bib1.bib12"><label>12</label><mixed-citation>
Chleborad, A. F.: A Method for Anticipating the Occurrence of Precipitation
induced Landslides in Seattle, Washington, US Geological Survey, Open-File
Report 00-469, US Geological Survey, Denver, USA, 29 pp., 2000.</mixed-citation></ref>
      <ref id="bib1.bib13"><label>13</label><mixed-citation>
Chleborad, A. F., Baum, R. L., and Godt, J. W.: A prototype system for
forecasting landslides in the Seattle, Washington, Area. in: Engineering
Geology and Landslides of the Seattle, Washington, Area: Geological Society
of America Reviews in Engineering Geology, edited by: Highland, L. M., Baum,
R. L., and Godt, J. W., Geological Society of America, Boulder, 103–120, 2008.</mixed-citation></ref>
      <ref id="bib1.bib14"><label>14</label><mixed-citation>Coelho Netto, A. L., Avelar, A. S., Fernandes, M. C., and Lacerda, W. A.:
Landslide susceptibility in a mountainous geoecosystem, Tijuca Massif, Rio de
Janeiro: The role of morphometric subdivision of the terrain, Geomorphology,
87, 120–131, <ext-link xlink:href="http://dx.doi.org/10.1016/j.geomorph.2006.03.041" ext-link-type="DOI">10.1016/j.geomorph.2006.03.041</ext-link>, 2007.</mixed-citation></ref>
      <ref id="bib1.bib15"><label>15</label><mixed-citation>Devoli, G., Ingeborg, K., Monica, S., Nils-Kristian, O., Ragnar, E., Erik,
J., and Hervé, C.: Landslide early warning system and web tools for
real-time scenarios and for distribution of warning messages in Norway, in:
Engineering Geology for Society and Territory “Landslide Processes”,
Proc. XII Int. IAEG Congress, Torino, Italy, 625–629, <ext-link xlink:href="http://dx.doi.org/10.1007/978-3-319-09057-3_104" ext-link-type="DOI">10.1007/978-3-319-09057-3_104</ext-link>, 2015.</mixed-citation></ref>
      <ref id="bib1.bib16"><label>16</label><mixed-citation>
DGR: n. 2312 del 27/12/2007, Deliberazione di Giunta Regionale dell'Umbria:
Disposizioni in attuazione dell'art, 3 bis della Legge 100/2012 e della
Direttiva del Presidente del Consiglio dei Ministri del 27.02.2004 – Sistema
di Allertamento Regionale e Centro Funzionale Regionale, Umbria, Italy, 2007.</mixed-citation></ref>
      <ref id="bib1.bib17"><label>17</label><mixed-citation>
DGR: n. 895 del 29/18/2013, Deliberazione di Giunta Regionale della Toscana:
Sistema di Allertamento Regionale e Centro Funzionale Regionale, Bollettino
ufficiale della regione Toscana, n. 46 del 13/11/2013, Toscana, Italy, 2013.</mixed-citation></ref>
      <ref id="bib1.bib18"><label>18</label><mixed-citation>
DGR: n. 395 del 7/04/2015, Deliberazione di Giunta Regionale della Toscana:
Sistema di Allertamento Regionale e Centro Funzionale Regionale, Bollettino
ufficiale della regione Toscana, n. 15 del 15/4/2015, Toscana, Italy, 2015.</mixed-citation></ref>
      <ref id="bib1.bib19"><label>19</label><mixed-citation>
Di Biagio, E. and Kjekstad, O.: Early Warning, Instrumentation and Monitoring
Landslides, in: Proceedings of the 2nd Regional Training Course, RECLAIM II,
29 January–2 February 2007, Phuket, Thailand, 2007.</mixed-citation></ref>
      <ref id="bib1.bib20"><label>20</label><mixed-citation>d'Orsi, R. N.: Landslide risk reduction measures by the Rio de Janeiro city
government, in: Improving the Assessment of Disaster Risks to Strengthen
Financial Resilience, Special Joint G20 Publication, Government of Mexico
and World Bank, 77–91, available at: <uri>http://www.preventionweb.net/english/professional/publications/v.php?id=29011</uri>
(last access: 6 October 2015), 2012.</mixed-citation></ref>
      <ref id="bib1.bib21"><label>21</label><mixed-citation>
d'Orsi, R. N., D'Avila, C., Ortigao, J. A. R., Moraes, L., and Santos, M.
D.: Rio-Watch: the Rio de Janeiro landslide watch, in: Proceedings of the
2nd PSL Pan-Am Symposium on Landslides, Rio de Janeiro, Brazil, 21–30, 1997.</mixed-citation></ref>
      <ref id="bib1.bib22"><label>22</label><mixed-citation>
d'Orsi, R. N., Feijó, R. L., and Paes, N. M.: 2,500 Operational days of
Alerta Rio system: history and technical improvements of Rio de Janeiro
warning system for severe weather, in: Landslides: Evaluation and
Stabilization, edited by: Lacerda, W. A., Ehrlich, M., Fontoura, S. A. B.,
and Sayao, A. S. F., Taylor &amp; Francis Group, London, 831–836, 2004.</mixed-citation></ref>
      <ref id="bib1.bib23"><label>23</label><mixed-citation>
DPCM: 27/02/2004, Direttiva Presidente Consiglio dei Ministri: Indirizzi
operativi per la gestione operativa e funzionale del sistema di allertamento
nazionale, statale e regionale per il rischio idrogeologico ed idraulico ai
fini di protezione civile, in: Gazzetta Ufficiale n. 59 del 11/03/2004,
Roma, Italy, 2004.</mixed-citation></ref>
      <ref id="bib1.bib24"><label>24</label><mixed-citation>
DPGR: n. 299 del 30/06/2005, Decreto del Presidente della
Giunta Regionale della Campania: Il Sistema di Allertamento Regionale per il
rischio Idrogeologico e Idraulico ai fini di protezione civile, Bollettino
ufficiale della regione Campania, n. speciale 01/08/2005, Campania, Italy, 2005.</mixed-citation></ref>
      <ref id="bib1.bib25"><label>25</label><mixed-citation>
DPRS: n. 626/GAB del 30/10/2014, Direttiva del Presidente della Regione
Siciliana: Competenze, struttura organizzativa e procedure di allertamento
del Centro Funzionale Decentrato Multirischio Integrato della Regione
Siciliana – Settore IDRO, Sicilia, Italy, 2014.</mixed-citation></ref>
      <ref id="bib1.bib26"><label>26</label><mixed-citation>
Fell, R., Ho, K. K. S., Lacasse, S., and Leroi, E.: A framework for
landslide risk assessment and management, in: Landslide Risk Management,
edited by: Hungr, O., Fell, R., Couture, R., and Eberhardt, E., Taylor and
Francis, London, 3–26, 2005.</mixed-citation></ref>
      <ref id="bib1.bib27"><label>27</label><mixed-citation>
Gariano, S. L., Brunetti, M. T., Iovine, G., Melillo, M., Peruccacci, S.,
Terranova, O., Vennari, C., and Guzzetti, F.: Calibration and validation of
rainfall thresholds for shallow landslide forecasting in Sicily, southern
Italy, Geomorphology, 228, 653–665, 2015.</mixed-citation></ref>
      <ref id="bib1.bib28"><label>28</label><mixed-citation>
Glade, T. and Nadim, F.: Early warning systems for natural hazards and
risks, Nat. Hazards, 70, 1669–1671, 2014.</mixed-citation></ref>
      <ref id="bib1.bib29"><label>29</label><mixed-citation>
Godt, J. W., Baum, R. L., and Chleborad, A. F.: Rainfall characteristics for
shallow landsliding in Seattle, Washington, USA, Earth Surf. Proc. Land.,
31, 97–110, 2006.</mixed-citation></ref>
      <ref id="bib1.bib30"><label>30</label><mixed-citation>
Greco, R., Giorgio, M., Capparelli, G., and Versace, P.: Early warning of
rainfall-induced landslides based on empirical mobility function predictor,
Eng. Geol., 153, 68–79, 2013.</mixed-citation></ref>
      <ref id="bib1.bib31"><label>31</label><mixed-citation>
Guzzetti, F., Peruccacci, S., Rossi, M., and Stark, C. P.: Rainfall
thresholds for the initiation of landslides in central and southern Europe,
Meteorol. Atmos. Phys., 98, 239–67, 2007.</mixed-citation></ref>
      <ref id="bib1.bib32"><label>32</label><mixed-citation>
Hyogo Framework for Action 2005–2015: Building the Resilience of Nations
and Communities to Disasters, World Conference on Disaster Reduction
18–22 January 2005, Kobe, Hyogo, Japan, 22 pp., 2005.</mixed-citation></ref>
      <ref id="bib1.bib33"><label>33</label><mixed-citation>International Centre of Geohazards: Guidelines for landslide monitoring and
early warning systems in Europe – design and required technology, in:
Project SafeLand “Living With Landslide Risk in Europe: Assessment, Effects
of Global Change, and Risk Management Strategies”, D4.8,
<uri>http://www.safeland-fp7.eu</uri> (last access: April 2015), 2012.</mixed-citation></ref>
      <ref id="bib1.bib34"><label>34</label><mixed-citation>
Intrieri, E., Gigli, G., Mugnai, F., Fanti, R., and Casagli, N.: Design and
implementation of a landslide early warning system, Eng. Geol., 147/148, 124–136, 2012.</mixed-citation></ref>
      <ref id="bib1.bib35"><label>35</label><mixed-citation>Intrieri, E., Gigli, G., Casagli, N., and Nadim, F.: Brief communication
“Landslide Early Warning System: toolbox and general concepts”, Nat.
Hazards Earth Syst. Sci., 13, 85–90, <ext-link xlink:href="http://dx.doi.org/10.5194/nhess-13-85-2013" ext-link-type="DOI">10.5194/nhess-13-85-2013</ext-link>, 2013.</mixed-citation></ref>
      <ref id="bib1.bib36"><label>36</label><mixed-citation>
Keefer, D. K., Wilson, R. C., Mark, R. K., Brabb, E. E., Brown III, W. M.,
Ellen, S. D., Harp, E. L., Wieczoreck, G. F., Alger, C. S., and Zatkin, R.
S.: Real-time landslide warning during heavy rainfall, Science, 238, 921–926, 1987.</mixed-citation></ref>
      <ref id="bib1.bib37"><label>37</label><mixed-citation>Kirschbaum, D. B., Adler, R., Hong, Y., Kumar, S., Peters-Lidard, C., and
Lerner-Lam, A.: Advances in landslide nowcasting: evaluation of a global and
regional modeling approach, Environ. Earth Sci., 66, 1683–1696, <ext-link xlink:href="http://dx.doi.org/10.1007/s12665-011-0990-3" ext-link-type="DOI">10.1007/s12665-011-0990-3</ext-link>, 2012.</mixed-citation></ref>
      <ref id="bib1.bib38"><label>38</label><mixed-citation>
Lagomarsino, D., Segoni, S., Fanti, R., and Catani, F.: Updating and tuning
a regional-scale landslide early warning system, Landslides, 10, 91–97, 2013.</mixed-citation></ref>
      <ref id="bib1.bib39"><label>39</label><mixed-citation>Lagomarsino, D., Segoni, S., Rosi, A., Rossi, G., Battistini, A., Catani,
F., and Casagli, N.: Quantitative comparison between two different
methodologies to define rainfall thresholds for landslide forecasting, Nat.
Hazards Earth Syst. Sci., 15, 2413–2423, <ext-link xlink:href="http://dx.doi.org/10.5194/nhess-15-2413-2015" ext-link-type="DOI">10.5194/nhess-15-2413-2015</ext-link>, 2015.</mixed-citation></ref>
      <ref id="bib1.bib40"><label>40</label><mixed-citation>
Lollino, G., Arattano, M., and Cuccureddu, M.: The use of the automatic
inclinometric system for landslide early warning: the case of Cabella Ligure
(North-Western Italy), Phys. Chem. Earth, 27, 1545–1550, 2002.</mixed-citation></ref>
      <ref id="bib1.bib41"><label>41</label><mixed-citation>
Martelloni, G., Segoni, S., Fanti, R., and Catani, F.: Rainfall thresholds
for the forecasting of landslide occurrence at regional scale, Landslides,
9, 485–495, 2012.</mixed-citation></ref>
      <ref id="bib1.bib42"><label>42</label><mixed-citation>Maskrey, A.: Report on National and Local Capabilities for Early Warning,
IDNDR Early Warning Programme, available at: <uri>http://www.unisdr.org/2006/ppew/whats-ew/pdf/national-and-local-capabilities-ew-maskrey.pdf</uri>
last access: 15 July 2015, IDNDR Secretariat, Geneva, 33 pp., 1997.</mixed-citation></ref>
      <ref id="bib1.bib43"><label>43</label><mixed-citation>Michoud, C., Bazin, S., Blikra, L. H., Derron, M.-H., and Jaboyedoff, M.:
Experiences from site-specific landslide early warning systems, Nat. Hazards
Earth Syst. Sci., 13, 2659–2673, <ext-link xlink:href="http://dx.doi.org/10.5194/nhess-13-2659-2013" ext-link-type="DOI">10.5194/nhess-13-2659-2013</ext-link>, 2013.</mixed-citation></ref>
      <ref id="bib1.bib44"><label>44</label><mixed-citation>NOAA-USGS Debris Flow Task Force: NOAA-USGS Debris-Flow Warning System,
Final report, US Geological Survey Circular 1283, available at:
<uri>http://pubs.usgs.gov/circ/2005/1283/pdf/Circular1283.pdf</uri>, last access:
November 2014, US Geological Survey, Reston, Virginia, USA, 47 pp., 2005.</mixed-citation></ref>
      <ref id="bib1.bib45"><label>45</label><mixed-citation>
Osanai, N., Shimizu, T., Kuramoto, K., Kojima, S., and Noro, T.: Japanese
early-warning for debris flows and slope failures using rainfall indices
with Radial Basis Function Network, Landslides, 7, 325–338, 2010.</mixed-citation></ref>
      <ref id="bib1.bib46"><label>46</label><mixed-citation>
Peres, D. J. and Cancelliere, A.: Development of rainfall thresholds for
landslide early warning in Sicily: a method based on the use of rainfall
annual maxima series, Rend. Online Soc. Geol. It., 21, 580–582, 2012.</mixed-citation></ref>
      <ref id="bib1.bib47"><label>47</label><mixed-citation>Restrepo, P., Jorgensen, D. P., Cannon, S. H., Costa, J., Laber, J., Major,
J., Martner, B., Purpura, J., and Werner, K.: Joint NOAA/NWS/USGS prototype
debris flow warning system for recently burned areas in southern California,
B. Am. Meteorol. Soc., 89, 1845, <ext-link xlink:href="http://dx.doi.org/10.1175/2008BAMS2416.1" ext-link-type="DOI">10.1175/2008BAMS2416.1</ext-link>, 2008.</mixed-citation></ref>
      <ref id="bib1.bib48"><label>48</label><mixed-citation>
Rossi, M., Peruccacci, S., Brunetti, M. T., Marchesini, I., Luciani, S.,
Ardizzone, F., Balducci, V., Bianchi, C., Cardinali, M., Fiorucci, F.,
Mondini, A. C., Reichenbach, P., Salvati, P., Santangelo, M., Bartolini, D.,
Gariano, S. L., Palladino, M., Vessia, G., Viero, A., Antronico, L.,
Borselli, L., Deganutti, A. M., Iovine, G., Luino, F., Parise, M., Polemio,
M., and Guzzetti, F.: SANF: National warning system for rainfall-induced
landslides in Italy, in: Landslides and Engineered Slopes: Protecting
Society through Improved Understanding, edited by: Eberhardt, E., Froese,
C., Turner, K., and Leroueil, S., Taylor &amp; Francis, London, 1895–1899, 2012.</mixed-citation></ref>
      <ref id="bib1.bib49"><label>49</label><mixed-citation>
Segoni, S., Rossi, G., Rosi, A., and Catani, F.: Landslides triggered by
rainfall: a semiautomated procedure to define consistent intensity-duration
thresholds, Comput. Geosci., 3063, 123–131, 2014.</mixed-citation></ref>
      <ref id="bib1.bib50"><label>50</label><mixed-citation>Segoni, S., Battistini, A., Rossi, G., Rosi, A., Lagomarsino, D., Catani,
F., Moretti, S., and Casagli, N.: Technical Note: An operational landslide
early warning system at regional scale based on space–time-variable
rainfall thresholds, Nat. Hazards Earth Syst. Sci., 15, 853–861,
<ext-link xlink:href="http://dx.doi.org/10.5194/nhess-15-853-2015" ext-link-type="DOI">10.5194/nhess-15-853-2015</ext-link>, 2015.</mixed-citation></ref>
      <ref id="bib1.bib51"><label>51</label><mixed-citation>Stähli, M., Sättele, M., Huggel, C., McArdell, B. W., Lehmann, P.,
Van Herwijnen, A., Berne, A., Schleiss, M., Ferrari, A., Kos, A., Or, D.,
and Springman, S. M.: Monitoring and prediction in early warning systems for
rapid mass movements, Nat. Hazards Earth Syst. Sci., 15, 905–917,
<ext-link xlink:href="http://dx.doi.org/10.5194/nhess-15-905-2015" ext-link-type="DOI">10.5194/nhess-15-905-2015</ext-link>, 2015.</mixed-citation></ref>
      <ref id="bib1.bib52"><label>52</label><mixed-citation>Staley, D. M., Kean, J. W., Cannon, S. H., Schmidt, K. M., and Laber, J. L.:
Objective definition of rainfall intensity–duration thresholds for the
initiation of post-fire debris flows in southern California, Landslides, 10,
547–562, <ext-link xlink:href="http://dx.doi.org/10.1007/s10346-012-0341-9" ext-link-type="DOI">10.1007/s10346-012-0341-9</ext-link>, 2013.</mixed-citation></ref>
      <ref id="bib1.bib53"><label>53</label><mixed-citation>
Thiebes, B., Glade, T., and Bell, R.: Landslide analysis and integrative
early warning-local and regional case studies, in: Landslides and Engineered
Slopes: Protecting Society through Improved Understanding, edited by:
Eberhardt, E., Taylor &amp; Francis Group, London, 1915–1921, 2012.</mixed-citation></ref>
      <ref id="bib1.bib54"><label>54</label><mixed-citation>Thiebes, B., Bell, R., Glade, T., Jäger, S., Mayer, J., Anderson, M.,
and Holcombe, L.: Integration of a limit-equilibrium model into a landslide
early warning system, Landslides, 11, 859–875, <ext-link xlink:href="http://dx.doi.org/10.1007/s10346-013-0416-2" ext-link-type="DOI">10.1007/s10346-013-0416-2</ext-link>, 2013a.</mixed-citation></ref>
      <ref id="bib1.bib55"><label>55</label><mixed-citation>
Thiebes, B., Glade, T., and Bell, R.: Landslide analysis and integrative
early warning local and regional case studies, in: Landslides and Engineered
Slopes, edited by: Eberhardt, E., Froese, C. R., Turner, A. K., and
Leroueil, S., Taylor &amp; Francis Group, London, 1915–1921, 2013b.</mixed-citation></ref>
      <ref id="bib1.bib56"><label>56</label><mixed-citation>
Tiranti, D. and Rabuetti, D.: Estimation of rainfall thresholds triggering
shallow landslides for an operational warning system implementation,
Landslides, 7, 471–481, 2010.</mixed-citation></ref>
      <ref id="bib1.bib57"><label>57</label><mixed-citation>Villagrán de León, J. C., Pruessner, I., and Breedlove, H.: Alert
and Warning Frameworks in the Context of Early Warning Systems, a
Comparative Review, Intersections No. 12, United Nations University
Institute for Environment and Human Security, Bonn, 2013.
 </mixed-citation></ref><?xmltex \hack{\newpage}?>
      <ref id="bib1.bib58"><label>58</label><mixed-citation>
Wilson, R. C.: The rise and fall of a debris-flow warning system for the San
Francisco Bay Region, California, in: Landslide Hazard and Risk, edited by:
Glade, T., Anderson, M., and Crozier, M. J., Wiley, New York, 493–516, 2004.</mixed-citation></ref>
      <ref id="bib1.bib59"><label>59</label><mixed-citation>
Yu, Y. F., Lam, J. S., and Siu, C. K.: Interim Report on Review of Landslip
Warning Criteria, Special Projects Division, Special Project Report 4/2003,
Geotechnical Engineering Office, Civil Engineering Department, SAR Government,
Hong Kong, 20 pp., 2003.</mixed-citation></ref>

  </ref-list><app-group content-type="float"><app><title/>

    </app></app-group></back>
    <!--<article-title-html>Assessing the performance of regional landslide  early warning models: the EDuMaP method</article-title-html>
<abstract-html><p class="p">A schematic of the components of regional early warning systems for
rainfall-induced landslides is herein proposed, based on a clear distinction
between warning models and warning systems. According to this framework an
early warning system comprises a warning model as well as a monitoring and
warning strategy, a communication strategy and an emergency plan. The paper
proposes the evaluation of regional landslide warning models by means of an
original approach, called the “event, duration matrix,
performance” (EDuMaP) method, comprising three successive steps:
identification and analysis of the events, i.e., landslide events and
warning events derived from available landslides and warnings databases;
definition and computation of a duration matrix, whose elements
report the time associated with the occurrence of landslide events in
relation to the occurrence of warning events, in their respective classes;
evaluation of the early warning model performance by means of
performance criteria and indicators applied to the duration matrix. During
the first step the analyst identifies and classifies the landslide and
warning events, according to their spatial and temporal characteristics, by
means of a number of model parameters. In the second step, the analyst
computes a time-based duration matrix with a number of rows and columns
equal to the number of classes defined for the warning and landslide events,
respectively. In the third step, the analyst computes a series of model
performance indicators derived from a set of performance criteria, which
need to be defined by considering, once again, the features of the warning
model. The applicability, potentialities and limitations of the EDuMaP
method are tested and discussed using real landslides and warning data from
the municipal early warning system operating in Rio de Janeiro (Brazil).</p></abstract-html>
<ref-html id="bib1.bib1"><label>1</label><mixed-citation>
Aleotti, P.: A warning system for rainfall-induced shallow failures, Eng.
Geol., 73, 247–265, 2004.
</mixed-citation></ref-html>
<ref-html id="bib1.bib2"><label>2</label><mixed-citation>
Baum, R. L. and Godt, J. W.: Early warning of rainfall-induced shallow
landslides and debris flows in the USA, Landslides, 7, 259–272, 2010.

</mixed-citation></ref-html>
<ref-html id="bib1.bib3"><label>3</label><mixed-citation>
Bell, R., Thiebes, B., Glade, T., Vinogradov, R., Kuhlmann, H., Schauerte,
W., Burghaus, S., Krummel, H., Janik, M., and Paulsen, H.: The technical
concept within the Integrative Landslide Early Warning System (ILEWS),
landslides and engineered slopes, from the past to the future, in:
Proceedings of the 10th International Symposium on Landslides and Engineered
Slopes, 30 June–4 July 2008, Xi'an, China, 1083–1088, 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib4"><label>4</label><mixed-citation>
Berti, M., Martina, M. L. V., Franceschini, S., Pignone, A., Simoni, A., and
Pizziolo, M.: Probabilistic rainfall thresholds for landslide occurrence
using a Bayesian approach, J. Geophys. Res., 117, F04006, <a href="http://dx.doi.org/10.1029/2012JF002367" target="_blank">doi:10.1029/2012JF002367</a>, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib5"><label>5</label><mixed-citation>
Blikra, L. H.: The Åknes rockslide: monitoring, threshold values and
early-warning, in: Landslides and Engineered Slopes, edited by: Chen, Z.,
Zhang, J. M., Ho, K., Wu, F. Q., and Li, Z. K., Taylor &amp; Francis Group,
London, 1089–1094, 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib6"><label>6</label><mixed-citation>
Calvello, M., d'Orsi, R., Piciullo, L., Paes, N. M., Magalhaes, M. A.,
Coelho, R., and Lacerda, W. A.: The community-based alert and alarm system
for rainfall induced landslides in Rio de Janeiro, Brazil, in: Engineering
Geology for Society and Territory “Landslide Processes”, Proc. XII Int. IAEG
Congress, Torino, Italy, 2, 653–657, <a href="http://dx.doi.org/10.1007/978-3-319-09057-3_109" target="_blank">doi:10.1007/978-3-319-09057-3_109</a>, 2015a.
</mixed-citation></ref-html>
<ref-html id="bib1.bib7"><label>7</label><mixed-citation>
Calvello, M., d'Orsi, R. N., Piciullo, L., Paes, N., Magalhaes, M., and
Lacerda, W. A.: The Rio de Janeiro early warning system for rainfall-induced
landslides: analysis of performance for the years 2010–2013, Int.
J. Disast. Risk Reduc., 12, 3–15, 2015b.
</mixed-citation></ref-html>
<ref-html id="bib1.bib8"><label>8</label><mixed-citation>
Cannon, S., Boldt, E., Laber, J., Kean, J., and Staley, D.: Rainfall
intensity–duration thresholds for postfire debris-flow emergency response
planning, Nat. Hazards, 59, 209–236, 2011.
</mixed-citation></ref-html>
<ref-html id="bib1.bib9"><label>9</label><mixed-citation>
Capparelli, G. and Tiranti, D.: Application of the MoniFLaIR early warning system
for rainfall induced landslides in Piedmont region (Italy), Landslides, 7, 401–410, 2010.
</mixed-citation></ref-html>
<ref-html id="bib1.bib10"><label>10</label><mixed-citation>
Chan, R. K. S. and Pun, W. K.: Landslip warning system in Hong Kong, Geotec.
Instrum. News, 22, 33–35, 2004.
</mixed-citation></ref-html>
<ref-html id="bib1.bib11"><label>11</label><mixed-citation>
Cheung, P. Y., Wong, M. C., and Yeung, H. Y.: Application of rainstorm
nowcast to real-time warning of landslide hazards in Hong Kong, in: WMO PWS,
Workshop on Warnings of Real-Time Hazards by Using Nowcasting Technology,
9–13 October 2006, Sydney, Australia, 2006.
</mixed-citation></ref-html>
<ref-html id="bib1.bib12"><label>12</label><mixed-citation>
Chleborad, A. F.: A Method for Anticipating the Occurrence of Precipitation
induced Landslides in Seattle, Washington, US Geological Survey, Open-File
Report 00-469, US Geological Survey, Denver, USA, 29 pp., 2000.
</mixed-citation></ref-html>
<ref-html id="bib1.bib13"><label>13</label><mixed-citation>
Chleborad, A. F., Baum, R. L., and Godt, J. W.: A prototype system for
forecasting landslides in the Seattle, Washington, Area. in: Engineering
Geology and Landslides of the Seattle, Washington, Area: Geological Society
of America Reviews in Engineering Geology, edited by: Highland, L. M., Baum,
R. L., and Godt, J. W., Geological Society of America, Boulder, 103–120, 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib14"><label>14</label><mixed-citation>
Coelho Netto, A. L., Avelar, A. S., Fernandes, M. C., and Lacerda, W. A.:
Landslide susceptibility in a mountainous geoecosystem, Tijuca Massif, Rio de
Janeiro: The role of morphometric subdivision of the terrain, Geomorphology,
87, 120–131, <a href="http://dx.doi.org/10.1016/j.geomorph.2006.03.041" target="_blank">doi:10.1016/j.geomorph.2006.03.041</a>, 2007.
</mixed-citation></ref-html>
<ref-html id="bib1.bib15"><label>15</label><mixed-citation>
Devoli, G., Ingeborg, K., Monica, S., Nils-Kristian, O., Ragnar, E., Erik,
J., and Hervé, C.: Landslide early warning system and web tools for
real-time scenarios and for distribution of warning messages in Norway, in:
Engineering Geology for Society and Territory “Landslide Processes”,
Proc. XII Int. IAEG Congress, Torino, Italy, 625–629, <a href="http://dx.doi.org/10.1007/978-3-319-09057-3_104" target="_blank">doi:10.1007/978-3-319-09057-3_104</a>, 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib16"><label>16</label><mixed-citation>
DGR: n. 2312 del 27/12/2007, Deliberazione di Giunta Regionale dell'Umbria:
Disposizioni in attuazione dell'art, 3 bis della Legge 100/2012 e della
Direttiva del Presidente del Consiglio dei Ministri del 27.02.2004 – Sistema
di Allertamento Regionale e Centro Funzionale Regionale, Umbria, Italy, 2007.
</mixed-citation></ref-html>
<ref-html id="bib1.bib17"><label>17</label><mixed-citation>
DGR: n. 895 del 29/18/2013, Deliberazione di Giunta Regionale della Toscana:
Sistema di Allertamento Regionale e Centro Funzionale Regionale, Bollettino
ufficiale della regione Toscana, n. 46 del 13/11/2013, Toscana, Italy, 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib18"><label>18</label><mixed-citation>
DGR: n. 395 del 7/04/2015, Deliberazione di Giunta Regionale della Toscana:
Sistema di Allertamento Regionale e Centro Funzionale Regionale, Bollettino
ufficiale della regione Toscana, n. 15 del 15/4/2015, Toscana, Italy, 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib19"><label>19</label><mixed-citation>
Di Biagio, E. and Kjekstad, O.: Early Warning, Instrumentation and Monitoring
Landslides, in: Proceedings of the 2nd Regional Training Course, RECLAIM II,
29 January–2 February 2007, Phuket, Thailand, 2007.
</mixed-citation></ref-html>
<ref-html id="bib1.bib20"><label>20</label><mixed-citation>
d'Orsi, R. N.: Landslide risk reduction measures by the Rio de Janeiro city
government, in: Improving the Assessment of Disaster Risks to Strengthen
Financial Resilience, Special Joint G20 Publication, Government of Mexico
and World Bank, 77–91, available at: <a href="http://www.preventionweb.net/english/professional/publications/v.php?id=29011" target="_blank">http://www.preventionweb.net/english/professional/publications/v.php?id=29011</a>
(last access: 6 October 2015), 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib21"><label>21</label><mixed-citation>
d'Orsi, R. N., D'Avila, C., Ortigao, J. A. R., Moraes, L., and Santos, M.
D.: Rio-Watch: the Rio de Janeiro landslide watch, in: Proceedings of the
2nd PSL Pan-Am Symposium on Landslides, Rio de Janeiro, Brazil, 21–30, 1997.
</mixed-citation></ref-html>
<ref-html id="bib1.bib22"><label>22</label><mixed-citation>
d'Orsi, R. N., Feijó, R. L., and Paes, N. M.: 2,500 Operational days of
Alerta Rio system: history and technical improvements of Rio de Janeiro
warning system for severe weather, in: Landslides: Evaluation and
Stabilization, edited by: Lacerda, W. A., Ehrlich, M., Fontoura, S. A. B.,
and Sayao, A. S. F., Taylor &amp; Francis Group, London, 831–836, 2004.
</mixed-citation></ref-html>
<ref-html id="bib1.bib23"><label>23</label><mixed-citation>
DPCM: 27/02/2004, Direttiva Presidente Consiglio dei Ministri: Indirizzi
operativi per la gestione operativa e funzionale del sistema di allertamento
nazionale, statale e regionale per il rischio idrogeologico ed idraulico ai
fini di protezione civile, in: Gazzetta Ufficiale n. 59 del 11/03/2004,
Roma, Italy, 2004.
</mixed-citation></ref-html>
<ref-html id="bib1.bib24"><label>24</label><mixed-citation>
DPGR: n. 299 del 30/06/2005, Decreto del Presidente della
Giunta Regionale della Campania: Il Sistema di Allertamento Regionale per il
rischio Idrogeologico e Idraulico ai fini di protezione civile, Bollettino
ufficiale della regione Campania, n. speciale 01/08/2005, Campania, Italy, 2005.
</mixed-citation></ref-html>
<ref-html id="bib1.bib25"><label>25</label><mixed-citation>
DPRS: n. 626/GAB del 30/10/2014, Direttiva del Presidente della Regione
Siciliana: Competenze, struttura organizzativa e procedure di allertamento
del Centro Funzionale Decentrato Multirischio Integrato della Regione
Siciliana – Settore IDRO, Sicilia, Italy, 2014.
</mixed-citation></ref-html>
<ref-html id="bib1.bib26"><label>26</label><mixed-citation>
Fell, R., Ho, K. K. S., Lacasse, S., and Leroi, E.: A framework for
landslide risk assessment and management, in: Landslide Risk Management,
edited by: Hungr, O., Fell, R., Couture, R., and Eberhardt, E., Taylor and
Francis, London, 3–26, 2005.
</mixed-citation></ref-html>
<ref-html id="bib1.bib27"><label>27</label><mixed-citation>
Gariano, S. L., Brunetti, M. T., Iovine, G., Melillo, M., Peruccacci, S.,
Terranova, O., Vennari, C., and Guzzetti, F.: Calibration and validation of
rainfall thresholds for shallow landslide forecasting in Sicily, southern
Italy, Geomorphology, 228, 653–665, 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib28"><label>28</label><mixed-citation>
Glade, T. and Nadim, F.: Early warning systems for natural hazards and
risks, Nat. Hazards, 70, 1669–1671, 2014.
</mixed-citation></ref-html>
<ref-html id="bib1.bib29"><label>29</label><mixed-citation>
Godt, J. W., Baum, R. L., and Chleborad, A. F.: Rainfall characteristics for
shallow landsliding in Seattle, Washington, USA, Earth Surf. Proc. Land.,
31, 97–110, 2006.
</mixed-citation></ref-html>
<ref-html id="bib1.bib30"><label>30</label><mixed-citation>
Greco, R., Giorgio, M., Capparelli, G., and Versace, P.: Early warning of
rainfall-induced landslides based on empirical mobility function predictor,
Eng. Geol., 153, 68–79, 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib31"><label>31</label><mixed-citation>
Guzzetti, F., Peruccacci, S., Rossi, M., and Stark, C. P.: Rainfall
thresholds for the initiation of landslides in central and southern Europe,
Meteorol. Atmos. Phys., 98, 239–67, 2007.
</mixed-citation></ref-html>
<ref-html id="bib1.bib32"><label>32</label><mixed-citation>
Hyogo Framework for Action 2005–2015: Building the Resilience of Nations
and Communities to Disasters, World Conference on Disaster Reduction
18–22 January 2005, Kobe, Hyogo, Japan, 22 pp., 2005.
</mixed-citation></ref-html>
<ref-html id="bib1.bib33"><label>33</label><mixed-citation>
International Centre of Geohazards: Guidelines for landslide monitoring and
early warning systems in Europe – design and required technology, in:
Project SafeLand “Living With Landslide Risk in Europe: Assessment, Effects
of Global Change, and Risk Management Strategies”, D4.8,
<a href="http://www.safeland-fp7.eu" target="_blank">http://www.safeland-fp7.eu</a> (last access: April 2015), 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib34"><label>34</label><mixed-citation>
Intrieri, E., Gigli, G., Mugnai, F., Fanti, R., and Casagli, N.: Design and
implementation of a landslide early warning system, Eng. Geol., 147/148, 124–136, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib35"><label>35</label><mixed-citation>
Intrieri, E., Gigli, G., Casagli, N., and Nadim, F.: Brief communication
“Landslide Early Warning System: toolbox and general concepts”, Nat.
Hazards Earth Syst. Sci., 13, 85–90, <a href="http://dx.doi.org/10.5194/nhess-13-85-2013" target="_blank">doi:10.5194/nhess-13-85-2013</a>, 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib36"><label>36</label><mixed-citation>
Keefer, D. K., Wilson, R. C., Mark, R. K., Brabb, E. E., Brown III, W. M.,
Ellen, S. D., Harp, E. L., Wieczoreck, G. F., Alger, C. S., and Zatkin, R.
S.: Real-time landslide warning during heavy rainfall, Science, 238, 921–926, 1987.
</mixed-citation></ref-html>
<ref-html id="bib1.bib37"><label>37</label><mixed-citation>
Kirschbaum, D. B., Adler, R., Hong, Y., Kumar, S., Peters-Lidard, C., and
Lerner-Lam, A.: Advances in landslide nowcasting: evaluation of a global and
regional modeling approach, Environ. Earth Sci., 66, 1683–1696, <a href="http://dx.doi.org/10.1007/s12665-011-0990-3" target="_blank">doi:10.1007/s12665-011-0990-3</a>, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib38"><label>38</label><mixed-citation>
Lagomarsino, D., Segoni, S., Fanti, R., and Catani, F.: Updating and tuning
a regional-scale landslide early warning system, Landslides, 10, 91–97, 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib39"><label>39</label><mixed-citation>
Lagomarsino, D., Segoni, S., Rosi, A., Rossi, G., Battistini, A., Catani,
F., and Casagli, N.: Quantitative comparison between two different
methodologies to define rainfall thresholds for landslide forecasting, Nat.
Hazards Earth Syst. Sci., 15, 2413–2423, <a href="http://dx.doi.org/10.5194/nhess-15-2413-2015" target="_blank">doi:10.5194/nhess-15-2413-2015</a>, 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib40"><label>40</label><mixed-citation>
Lollino, G., Arattano, M., and Cuccureddu, M.: The use of the automatic
inclinometric system for landslide early warning: the case of Cabella Ligure
(North-Western Italy), Phys. Chem. Earth, 27, 1545–1550, 2002.
</mixed-citation></ref-html>
<ref-html id="bib1.bib41"><label>41</label><mixed-citation>
Martelloni, G., Segoni, S., Fanti, R., and Catani, F.: Rainfall thresholds
for the forecasting of landslide occurrence at regional scale, Landslides,
9, 485–495, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib42"><label>42</label><mixed-citation>
Maskrey, A.: Report on National and Local Capabilities for Early Warning,
IDNDR Early Warning Programme, available at: <a href="http://www.unisdr.org/2006/ppew/whats-ew/pdf/national-and-local-capabilities-ew-maskrey.pdf" target="_blank">http://www.unisdr.org/2006/ppew/whats-ew/pdf/national-and-local-capabilities-ew-maskrey.pdf</a>
last access: 15 July 2015, IDNDR Secretariat, Geneva, 33 pp., 1997.
</mixed-citation></ref-html>
<ref-html id="bib1.bib43"><label>43</label><mixed-citation>
Michoud, C., Bazin, S., Blikra, L. H., Derron, M.-H., and Jaboyedoff, M.:
Experiences from site-specific landslide early warning systems, Nat. Hazards
Earth Syst. Sci., 13, 2659–2673, <a href="http://dx.doi.org/10.5194/nhess-13-2659-2013" target="_blank">doi:10.5194/nhess-13-2659-2013</a>, 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib44"><label>44</label><mixed-citation>
NOAA-USGS Debris Flow Task Force: NOAA-USGS Debris-Flow Warning System,
Final report, US Geological Survey Circular 1283, available at:
<a href="http://pubs.usgs.gov/circ/2005/1283/pdf/Circular1283.pdf" target="_blank">http://pubs.usgs.gov/circ/2005/1283/pdf/Circular1283.pdf</a>, last access:
November 2014, US Geological Survey, Reston, Virginia, USA, 47 pp., 2005.
</mixed-citation></ref-html>
<ref-html id="bib1.bib45"><label>45</label><mixed-citation>
Osanai, N., Shimizu, T., Kuramoto, K., Kojima, S., and Noro, T.: Japanese
early-warning for debris flows and slope failures using rainfall indices
with Radial Basis Function Network, Landslides, 7, 325–338, 2010.
</mixed-citation></ref-html>
<ref-html id="bib1.bib46"><label>46</label><mixed-citation>
Peres, D. J. and Cancelliere, A.: Development of rainfall thresholds for
landslide early warning in Sicily: a method based on the use of rainfall
annual maxima series, Rend. Online Soc. Geol. It., 21, 580–582, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib47"><label>47</label><mixed-citation>
Restrepo, P., Jorgensen, D. P., Cannon, S. H., Costa, J., Laber, J., Major,
J., Martner, B., Purpura, J., and Werner, K.: Joint NOAA/NWS/USGS prototype
debris flow warning system for recently burned areas in southern California,
B. Am. Meteorol. Soc., 89, 1845, <a href="http://dx.doi.org/10.1175/2008BAMS2416.1" target="_blank">doi:10.1175/2008BAMS2416.1</a>, 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib48"><label>48</label><mixed-citation>
Rossi, M., Peruccacci, S., Brunetti, M. T., Marchesini, I., Luciani, S.,
Ardizzone, F., Balducci, V., Bianchi, C., Cardinali, M., Fiorucci, F.,
Mondini, A. C., Reichenbach, P., Salvati, P., Santangelo, M., Bartolini, D.,
Gariano, S. L., Palladino, M., Vessia, G., Viero, A., Antronico, L.,
Borselli, L., Deganutti, A. M., Iovine, G., Luino, F., Parise, M., Polemio,
M., and Guzzetti, F.: SANF: National warning system for rainfall-induced
landslides in Italy, in: Landslides and Engineered Slopes: Protecting
Society through Improved Understanding, edited by: Eberhardt, E., Froese,
C., Turner, K., and Leroueil, S., Taylor &amp; Francis, London, 1895–1899, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib49"><label>49</label><mixed-citation>
Segoni, S., Rossi, G., Rosi, A., and Catani, F.: Landslides triggered by
rainfall: a semiautomated procedure to define consistent intensity-duration
thresholds, Comput. Geosci., 3063, 123–131, 2014.
</mixed-citation></ref-html>
<ref-html id="bib1.bib50"><label>50</label><mixed-citation>
Segoni, S., Battistini, A., Rossi, G., Rosi, A., Lagomarsino, D., Catani,
F., Moretti, S., and Casagli, N.: Technical Note: An operational landslide
early warning system at regional scale based on space–time-variable
rainfall thresholds, Nat. Hazards Earth Syst. Sci., 15, 853–861,
<a href="http://dx.doi.org/10.5194/nhess-15-853-2015" target="_blank">doi:10.5194/nhess-15-853-2015</a>, 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib51"><label>51</label><mixed-citation>
Stähli, M., Sättele, M., Huggel, C., McArdell, B. W., Lehmann, P.,
Van Herwijnen, A., Berne, A., Schleiss, M., Ferrari, A., Kos, A., Or, D.,
and Springman, S. M.: Monitoring and prediction in early warning systems for
rapid mass movements, Nat. Hazards Earth Syst. Sci., 15, 905–917,
<a href="http://dx.doi.org/10.5194/nhess-15-905-2015" target="_blank">doi:10.5194/nhess-15-905-2015</a>, 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib52"><label>52</label><mixed-citation>
Staley, D. M., Kean, J. W., Cannon, S. H., Schmidt, K. M., and Laber, J. L.:
Objective definition of rainfall intensity–duration thresholds for the
initiation of post-fire debris flows in southern California, Landslides, 10,
547–562, <a href="http://dx.doi.org/10.1007/s10346-012-0341-9" target="_blank">doi:10.1007/s10346-012-0341-9</a>, 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib53"><label>53</label><mixed-citation>
Thiebes, B., Glade, T., and Bell, R.: Landslide analysis and integrative
early warning-local and regional case studies, in: Landslides and Engineered
Slopes: Protecting Society through Improved Understanding, edited by:
Eberhardt, E., Taylor &amp; Francis Group, London, 1915–1921, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib54"><label>54</label><mixed-citation>
Thiebes, B., Bell, R., Glade, T., Jäger, S., Mayer, J., Anderson, M.,
and Holcombe, L.: Integration of a limit-equilibrium model into a landslide
early warning system, Landslides, 11, 859–875, <a href="http://dx.doi.org/10.1007/s10346-013-0416-2" target="_blank">doi:10.1007/s10346-013-0416-2</a>, 2013a.
</mixed-citation></ref-html>
<ref-html id="bib1.bib55"><label>55</label><mixed-citation>
Thiebes, B., Glade, T., and Bell, R.: Landslide analysis and integrative
early warning local and regional case studies, in: Landslides and Engineered
Slopes, edited by: Eberhardt, E., Froese, C. R., Turner, A. K., and
Leroueil, S., Taylor &amp; Francis Group, London, 1915–1921, 2013b.
</mixed-citation></ref-html>
<ref-html id="bib1.bib56"><label>56</label><mixed-citation>
Tiranti, D. and Rabuetti, D.: Estimation of rainfall thresholds triggering
shallow landslides for an operational warning system implementation,
Landslides, 7, 471–481, 2010.
</mixed-citation></ref-html>
<ref-html id="bib1.bib57"><label>57</label><mixed-citation>
Villagrán de León, J. C., Pruessner, I., and Breedlove, H.: Alert
and Warning Frameworks in the Context of Early Warning Systems, a
Comparative Review, Intersections No. 12, United Nations University
Institute for Environment and Human Security, Bonn, 2013.

</mixed-citation></ref-html>
<ref-html id="bib1.bib58"><label>58</label><mixed-citation>
Wilson, R. C.: The rise and fall of a debris-flow warning system for the San
Francisco Bay Region, California, in: Landslide Hazard and Risk, edited by:
Glade, T., Anderson, M., and Crozier, M. J., Wiley, New York, 493–516, 2004.
</mixed-citation></ref-html>
<ref-html id="bib1.bib59"><label>59</label><mixed-citation>
Yu, Y. F., Lam, J. S., and Siu, C. K.: Interim Report on Review of Landslip
Warning Criteria, Special Projects Division, Special Project Report 4/2003,
Geotechnical Engineering Office, Civil Engineering Department, SAR Government,
Hong Kong, 20 pp., 2003.
</mixed-citation></ref-html>--></article>
