Serveur d'exploration sur la télématique

Attention, ce site est en cours de développement !
Attention, site généré par des moyens informatiques à partir de corpus bruts.
Les informations ne sont donc pas validées.
***** Acces problem to record *****\

Identifieur interne : 000135 ( Pmc/Corpus ); précédent : 0001349; suivant : 0001360 ***** probable Xml problem with record *****

Links to Exploration step


Le document en format XML

<record>
<TEI>
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en">A framework for detecting unfolding emergencies using humans as sensors</title>
<author>
<name sortKey="Avvenuti, Marco" sort="Avvenuti, Marco" uniqKey="Avvenuti M" first="Marco" last="Avvenuti">Marco Avvenuti</name>
<affiliation>
<nlm:aff id="Aff1">Department of Information Engineering, University of Pisa, Largo L. Lazzarino 1, 56122 Pisa, Italy</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Cimino, Mario G C A" sort="Cimino, Mario G C A" uniqKey="Cimino M" first="Mario G. C. A." last="Cimino">Mario G. C. A. Cimino</name>
<affiliation>
<nlm:aff id="Aff1">Department of Information Engineering, University of Pisa, Largo L. Lazzarino 1, 56122 Pisa, Italy</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Cresci, Stefano" sort="Cresci, Stefano" uniqKey="Cresci S" first="Stefano" last="Cresci">Stefano Cresci</name>
<affiliation>
<nlm:aff id="Aff2">Bell Labs, Alcatel-Lucent, Route de Villejust, 91620 Nozay, Paris, France</nlm:aff>
</affiliation>
<affiliation>
<nlm:aff id="Aff3">Institute of Informatics and Telematics (IIT), National Research Council (CNR), Via G. Moruzzi 1, 56124 Pisa, Italy</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Marchetti, Andrea" sort="Marchetti, Andrea" uniqKey="Marchetti A" first="Andrea" last="Marchetti">Andrea Marchetti</name>
<affiliation>
<nlm:aff id="Aff3">Institute of Informatics and Telematics (IIT), National Research Council (CNR), Via G. Moruzzi 1, 56124 Pisa, Italy</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Tesconi, Maurizio" sort="Tesconi, Maurizio" uniqKey="Tesconi M" first="Maurizio" last="Tesconi">Maurizio Tesconi</name>
<affiliation>
<nlm:aff id="Aff3">Institute of Informatics and Telematics (IIT), National Research Council (CNR), Via G. Moruzzi 1, 56124 Pisa, Italy</nlm:aff>
</affiliation>
</author>
</titleStmt>
<publicationStmt>
<idno type="wicri:source">PMC</idno>
<idno type="pmid">26811805</idno>
<idno type="pmc">4717126</idno>
<idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4717126</idno>
<idno type="RBID">PMC:4717126</idno>
<idno type="doi">10.1186/s40064-016-1674-y</idno>
<date when="2016">2016</date>
<idno type="wicri:Area/Pmc/Corpus">000135</idno>
<idno type="wicri:explorRef" wicri:stream="Pmc" wicri:step="Corpus" wicri:corpus="PMC">000135</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title xml:lang="en" level="a" type="main">A framework for detecting unfolding emergencies using humans as sensors</title>
<author>
<name sortKey="Avvenuti, Marco" sort="Avvenuti, Marco" uniqKey="Avvenuti M" first="Marco" last="Avvenuti">Marco Avvenuti</name>
<affiliation>
<nlm:aff id="Aff1">Department of Information Engineering, University of Pisa, Largo L. Lazzarino 1, 56122 Pisa, Italy</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Cimino, Mario G C A" sort="Cimino, Mario G C A" uniqKey="Cimino M" first="Mario G. C. A." last="Cimino">Mario G. C. A. Cimino</name>
<affiliation>
<nlm:aff id="Aff1">Department of Information Engineering, University of Pisa, Largo L. Lazzarino 1, 56122 Pisa, Italy</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Cresci, Stefano" sort="Cresci, Stefano" uniqKey="Cresci S" first="Stefano" last="Cresci">Stefano Cresci</name>
<affiliation>
<nlm:aff id="Aff2">Bell Labs, Alcatel-Lucent, Route de Villejust, 91620 Nozay, Paris, France</nlm:aff>
</affiliation>
<affiliation>
<nlm:aff id="Aff3">Institute of Informatics and Telematics (IIT), National Research Council (CNR), Via G. Moruzzi 1, 56124 Pisa, Italy</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Marchetti, Andrea" sort="Marchetti, Andrea" uniqKey="Marchetti A" first="Andrea" last="Marchetti">Andrea Marchetti</name>
<affiliation>
<nlm:aff id="Aff3">Institute of Informatics and Telematics (IIT), National Research Council (CNR), Via G. Moruzzi 1, 56124 Pisa, Italy</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Tesconi, Maurizio" sort="Tesconi, Maurizio" uniqKey="Tesconi M" first="Maurizio" last="Tesconi">Maurizio Tesconi</name>
<affiliation>
<nlm:aff id="Aff3">Institute of Informatics and Telematics (IIT), National Research Council (CNR), Via G. Moruzzi 1, 56124 Pisa, Italy</nlm:aff>
</affiliation>
</author>
</analytic>
<series>
<title level="j">SpringerPlus</title>
<idno type="eISSN">2193-1801</idno>
<imprint>
<date when="2016">2016</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<textClass></textClass>
</profileDesc>
</teiHeader>
<front>
<div type="abstract" xml:lang="en">
<p>The advent of online social networks (OSNs) paired with the ubiquitous proliferation of smartphones have enabled social sensing systems. In the last few years, the aptitude of humans to spontaneously collect and timely share context information has been exploited for emergency detection and crisis management. Apart from event-specific features, these systems share technical approaches and architectural solutions to address the issues with capturing, filtering and extracting meaningful information from data posted to OSNs by networks of human sensors. This paper proposes a conceptual and architectural framework for the design of emergency detection systems based on the “human as a sensor” (HaaS) paradigm. An ontology for the HaaS paradigm in the context of emergency detection is defined. Then, a modular architecture, independent of a specific emergency type, is designed. The proposed architecture is demonstrated by an implemented application for detecting earthquakes via Twitter. Validation and experimental results based on messages posted during earthquakes occurred in Italy are reported.</p>
</div>
</front>
<back>
<div1 type="bibliography">
<listBibl>
<biblStruct>
<analytic>
<author>
<name sortKey="Adam, Nr" uniqKey="Adam N">NR Adam</name>
</author>
<author>
<name sortKey="Shafiq, B" uniqKey="Shafiq B">B Shafiq</name>
</author>
<author>
<name sortKey="Staffin, R" uniqKey="Staffin R">R Staffin</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Aggarwal, Cc" uniqKey="Aggarwal C">CC Aggarwal</name>
</author>
<author>
<name sortKey="Abdelzaher, T" uniqKey="Abdelzaher T">T Abdelzaher</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Allen, Rm" uniqKey="Allen R">RM Allen</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Bagrow, Jp" uniqKey="Bagrow J">JP Bagrow</name>
</author>
<author>
<name sortKey="Wang, D" uniqKey="Wang D">D Wang</name>
</author>
<author>
<name sortKey="Barabasi, A L" uniqKey="Barabasi A">A-L Barabasi</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Bartoli, G" uniqKey="Bartoli G">G Bartoli</name>
</author>
<author>
<name sortKey="Fantacci, R" uniqKey="Fantacci R">R Fantacci</name>
</author>
<author>
<name sortKey="Gei, F" uniqKey="Gei F">F Gei</name>
</author>
<author>
<name sortKey="Marabissi, D" uniqKey="Marabissi D">D Marabissi</name>
</author>
<author>
<name sortKey="Micciullo, L" uniqKey="Micciullo L">L Micciullo</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Chu, Z" uniqKey="Chu Z">Z Chu</name>
</author>
<author>
<name sortKey="Gianvecchio, S" uniqKey="Gianvecchio S">S Gianvecchio</name>
</author>
<author>
<name sortKey="Wang, H" uniqKey="Wang H">H Wang</name>
</author>
<author>
<name sortKey="Jajodia, S" uniqKey="Jajodia S">S Jajodia</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Cimino, Mg" uniqKey="Cimino M">MG Cimino</name>
</author>
<author>
<name sortKey="Lazzerini, B" uniqKey="Lazzerini B">B Lazzerini</name>
</author>
<author>
<name sortKey="Marcelloni, F" uniqKey="Marcelloni F">F Marcelloni</name>
</author>
<author>
<name sortKey="Ciaramella, A" uniqKey="Ciaramella A">A Ciaramella</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Cresci, S" uniqKey="Cresci S">S Cresci</name>
</author>
<author>
<name sortKey="Di Pietro, R" uniqKey="Di Pietro R">R Di Pietro</name>
</author>
<author>
<name sortKey="Petrocchi, M" uniqKey="Petrocchi M">M Petrocchi</name>
</author>
<author>
<name sortKey="Spognardi, A" uniqKey="Spognardi A">A Spognardi</name>
</author>
<author>
<name sortKey="Tesconi, M" uniqKey="Tesconi M">M Tesconi</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Crooks, A" uniqKey="Crooks A">A Crooks</name>
</author>
<author>
<name sortKey="Croitoru, A" uniqKey="Croitoru A">A Croitoru</name>
</author>
<author>
<name sortKey="Stefanidis, A" uniqKey="Stefanidis A">A Stefanidis</name>
</author>
<author>
<name sortKey="Radzikowski, J" uniqKey="Radzikowski J">J Radzikowski</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="D Ndrea, E" uniqKey="D Ndrea E">E D’Andrea</name>
</author>
<author>
<name sortKey="Ducange, P" uniqKey="Ducange P">P Ducange</name>
</author>
<author>
<name sortKey="Lazzerini, B" uniqKey="Lazzerini B">B Lazzerini</name>
</author>
<author>
<name sortKey="Marcelloni, F" uniqKey="Marcelloni F">F Marcelloni</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Earle, P" uniqKey="Earle P">P Earle</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Earle, Ps" uniqKey="Earle P">PS Earle</name>
</author>
<author>
<name sortKey="Bowden, Dc" uniqKey="Bowden D">DC Bowden</name>
</author>
<author>
<name sortKey="Guy, M" uniqKey="Guy M">M Guy</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Foresti, Gl" uniqKey="Foresti G">GL Foresti</name>
</author>
<author>
<name sortKey="Farinosi, M" uniqKey="Farinosi M">M Farinosi</name>
</author>
<author>
<name sortKey="Vernier, M" uniqKey="Vernier M">M Vernier</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Gao, L" uniqKey="Gao L">L Gao</name>
</author>
<author>
<name sortKey="Song, C" uniqKey="Song C">C Song</name>
</author>
<author>
<name sortKey="Gao, Z" uniqKey="Gao Z">Z Gao</name>
</author>
<author>
<name sortKey="Barabasi, A L" uniqKey="Barabasi A">A-L Barabási</name>
</author>
<author>
<name sortKey="Bagrow, Jp" uniqKey="Bagrow J">JP Bagrow</name>
</author>
<author>
<name sortKey="Wang, D" uniqKey="Wang D">D Wang</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Goolsby, R" uniqKey="Goolsby R">R Goolsby</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Hall, M" uniqKey="Hall M">M Hall</name>
</author>
<author>
<name sortKey="Frank, E" uniqKey="Frank E">E Frank</name>
</author>
<author>
<name sortKey="Holmes, G" uniqKey="Holmes G">G Holmes</name>
</author>
<author>
<name sortKey="Pfahringer, B" uniqKey="Pfahringer B">B Pfahringer</name>
</author>
<author>
<name sortKey="Reutemann, P" uniqKey="Reutemann P">P Reutemann</name>
</author>
<author>
<name sortKey="Witten, Ih" uniqKey="Witten I">IH Witten</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Hughes, Al" uniqKey="Hughes A">AL Hughes</name>
</author>
<author>
<name sortKey="Palen, L" uniqKey="Palen L">L Palen</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Imran, M" uniqKey="Imran M">M Imran</name>
</author>
<author>
<name sortKey="Castillo, C" uniqKey="Castillo C">C Castillo</name>
</author>
<author>
<name sortKey="Diaz, F" uniqKey="Diaz F">F Diaz</name>
</author>
<author>
<name sortKey="Vieweg, S" uniqKey="Vieweg S">S Vieweg</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Kleinberg, J" uniqKey="Kleinberg J">J Kleinberg</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Lampos, V" uniqKey="Lampos V">V Lampos</name>
</author>
<author>
<name sortKey="Cristianini, N" uniqKey="Cristianini N">N Cristianini</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Middleton, Se" uniqKey="Middleton S">SE Middleton</name>
</author>
<author>
<name sortKey="Middleton, L" uniqKey="Middleton L">L Middleton</name>
</author>
<author>
<name sortKey="Modafferi, S" uniqKey="Modafferi S">S Modafferi</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Sakai, T" uniqKey="Sakai T">T Sakai</name>
</author>
<author>
<name sortKey="Tamura, K" uniqKey="Tamura K">K Tamura</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Sakaki, T" uniqKey="Sakaki T">T Sakaki</name>
</author>
<author>
<name sortKey="Okazaki, M" uniqKey="Okazaki M">M Okazaki</name>
</author>
<author>
<name sortKey="Matsuo, Y" uniqKey="Matsuo Y">Y Matsuo</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Sheth, A" uniqKey="Sheth A">A Sheth</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Srivastava, M" uniqKey="Srivastava M">M Srivastava</name>
</author>
<author>
<name sortKey="Abdelzaher, T" uniqKey="Abdelzaher T">T Abdelzaher</name>
</author>
<author>
<name sortKey="Szymanski, B" uniqKey="Szymanski B">B Szymanski</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Yin, J" uniqKey="Yin J">J Yin</name>
</author>
<author>
<name sortKey="Lampert, A" uniqKey="Lampert A">A Lampert</name>
</author>
<author>
<name sortKey="Cameron, M" uniqKey="Cameron M">M Cameron</name>
</author>
<author>
<name sortKey="Robinson, B" uniqKey="Robinson B">B Robinson</name>
</author>
<author>
<name sortKey="Power, R" uniqKey="Power R">R Power</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
</listBibl>
</div1>
</back>
</TEI>
<pmc article-type="research-article">
<pmc-dir>properties open_access</pmc-dir>
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Springerplus</journal-id>
<journal-id journal-id-type="iso-abbrev">Springerplus</journal-id>
<journal-title-group>
<journal-title>SpringerPlus</journal-title>
</journal-title-group>
<issn pub-type="epub">2193-1801</issn>
<publisher>
<publisher-name>Springer International Publishing</publisher-name>
<publisher-loc>Cham</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="pmid">26811805</article-id>
<article-id pub-id-type="pmc">4717126</article-id>
<article-id pub-id-type="publisher-id">1674</article-id>
<article-id pub-id-type="doi">10.1186/s40064-016-1674-y</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Research</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>A framework for detecting unfolding emergencies using humans as sensors</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Avvenuti</surname>
<given-names>Marco</given-names>
</name>
<address>
<email>marco.avvenuti@unipi.it</email>
</address>
<xref ref-type="aff" rid="Aff1"></xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Cimino</surname>
<given-names>Mario G. C. A.</given-names>
</name>
<address>
<email>mario.cimino@unipi.it</email>
</address>
<xref ref-type="aff" rid="Aff1"></xref>
</contrib>
<contrib contrib-type="author" corresp="yes">
<contrib-id contrib-id-type="orcid">http://orcid.org/0000-0003-0170-2445</contrib-id>
<name>
<surname>Cresci</surname>
<given-names>Stefano</given-names>
</name>
<address>
<email>stefano.cresci@iit.cnr.it</email>
</address>
<xref ref-type="aff" rid="Aff2"></xref>
<xref ref-type="aff" rid="Aff3"></xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Marchetti</surname>
<given-names>Andrea</given-names>
</name>
<address>
<email>andrea.marchetti@iit.cnr.it</email>
</address>
<xref ref-type="aff" rid="Aff3"></xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Tesconi</surname>
<given-names>Maurizio</given-names>
</name>
<address>
<email>maurizio.tesconi@iit.cnr.it</email>
</address>
<xref ref-type="aff" rid="Aff3"></xref>
</contrib>
<aff id="Aff1">
<label></label>
Department of Information Engineering, University of Pisa, Largo L. Lazzarino 1, 56122 Pisa, Italy</aff>
<aff id="Aff2">
<label></label>
Bell Labs, Alcatel-Lucent, Route de Villejust, 91620 Nozay, Paris, France</aff>
<aff id="Aff3">
<label></label>
Institute of Informatics and Telematics (IIT), National Research Council (CNR), Via G. Moruzzi 1, 56124 Pisa, Italy</aff>
</contrib-group>
<pub-date pub-type="epub">
<day>19</day>
<month>1</month>
<year>2016</year>
</pub-date>
<pub-date pub-type="pmc-release">
<day>19</day>
<month>1</month>
<year>2016</year>
</pub-date>
<pub-date pub-type="collection">
<year>2016</year>
</pub-date>
<volume>5</volume>
<elocation-id>43</elocation-id>
<history>
<date date-type="received">
<day>3</day>
<month>9</month>
<year>2015</year>
</date>
<date date-type="accepted">
<day>6</day>
<month>1</month>
<year>2016</year>
</date>
</history>
<permissions>
<copyright-statement>© Avvenuti et al. 2016</copyright-statement>
<license license-type="OpenAccess">
<license-p>
<bold>Open Access</bold>
This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (
<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/4.0/">http://creativecommons.org/licenses/by/4.0/</ext-link>
), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.</license-p>
</license>
</permissions>
<abstract id="Abs1">
<p>The advent of online social networks (OSNs) paired with the ubiquitous proliferation of smartphones have enabled social sensing systems. In the last few years, the aptitude of humans to spontaneously collect and timely share context information has been exploited for emergency detection and crisis management. Apart from event-specific features, these systems share technical approaches and architectural solutions to address the issues with capturing, filtering and extracting meaningful information from data posted to OSNs by networks of human sensors. This paper proposes a conceptual and architectural framework for the design of emergency detection systems based on the “human as a sensor” (HaaS) paradigm. An ontology for the HaaS paradigm in the context of emergency detection is defined. Then, a modular architecture, independent of a specific emergency type, is designed. The proposed architecture is demonstrated by an implemented application for detecting earthquakes via Twitter. Validation and experimental results based on messages posted during earthquakes occurred in Italy are reported.</p>
</abstract>
<kwd-group xml:lang="en">
<title>Keywords</title>
<kwd>Twitter</kwd>
<kwd>Social sensing</kwd>
<kwd>Social media mining</kwd>
<kwd>Event detection</kwd>
<kwd>Crisis informatics</kwd>
<kwd>Emergency management</kwd>
</kwd-group>
<custom-meta-group>
<custom-meta>
<meta-name>issue-copyright-statement</meta-name>
<meta-value>© The Author(s) 2016</meta-value>
</custom-meta>
</custom-meta-group>
</article-meta>
</front>
<body>
<sec id="Sec1">
<title>Background</title>
<p>Established public safety systems are based on centralized emergency detection approaches, often relying on expensive infrastructures of physical sensors which may not be available everywhere. The proliferation of handheld devices, equipped with a large number of sensors and communication capabilities, can significantly extend, or possibly substitute, conventional sensing by enabling the collection of data through networks of humans. Novel paradigms such as crowd-, urban- or citizen-sensing have been coined to describe how information can be sourced from the average individual in a coordinated way. Data gathering can be either participatory or opportunistic, depending on whether the user intentionally contributes to the acquisition campaign (possibly receiving an incentive), or she simply acts as the bearer of a sensing device from which data is transparently collected by some situation-aware system (Sheth
<xref ref-type="bibr" rid="CR47">2009</xref>
; Kapadia et al.
<xref ref-type="bibr" rid="CR31">2009</xref>
; Cimino et al.
<xref ref-type="bibr" rid="CR12">2012</xref>
).</p>
<p>In this scenario, the advent of online social network (OSN) platforms, such as Twitter, Weibo and Instagram, that have grown bigger becoming a primary hub for public expression and interaction, has added facilities for ubiquitous and real-time data-sharing (Demirbas et al.
<xref ref-type="bibr" rid="CR18">2010</xref>
). These unprecedented sensing and sharing opportunities have enabled situations where individuals not only play the role of sensor operators, but also act as data sources themselves. In fact, humans have a great aptitude in processing and filtering observations from their surroundings and, with communication facilities at hand, in readily sharing the information they collect (Srivastava et al.
<xref ref-type="bibr" rid="CR49">2012</xref>
). This spontaneous behavior has driven a new challenging research field, called “social sensing” (Aggarwal and Abdelzaher
<xref ref-type="bibr" rid="CR2">2013</xref>
), investigating how human-sourced data, modeled by the “human as a sensor” (HaaS) paradigm (Wang et al.
<xref ref-type="bibr" rid="CR50">2014</xref>
), can be gathered and used to gain situational awareness and to nowcast events (Lampos and Cristianini
<xref ref-type="bibr" rid="CR34">2012</xref>
) in different domains such as health, transportation, energy, social and political crisis, and even warfare. Among the advantages of social sensing is the natural tendency of OSN users to promptly convey information about the context (Liang et al.
<xref ref-type="bibr" rid="CR35">2013</xref>
; Cresci et al.
<xref ref-type="bibr" rid="CR14">2015b</xref>
) and that those proactively posted messages, especially when witnessing emergency situations, are likely to be free of pressure or influence (Zhou et al.
<xref ref-type="bibr" rid="CR53">2012</xref>
). The utmost case is Twitter, where users are encouraged to make their messages (
<italic>tweets</italic>
) publicly available by default and where, due to the 140 characters length limitation, they are forced to share more topic-specific content.</p>
<p>Given this picture, it is not surprising that OSNs, and Twitter in particular, have drawn the attention of designers of decision support systems for emergency management, and that during recent disasters, such as the Tōhoku earthquake and tsunami (Japan—2011), the Hurricane Sandy (Central and North America—2012) and the Himalayan earthquake (Nepal—2015), civil protection agencies turned to the Web and to OSN data to help tracking stricken locations, assessing the damage and coordinating the rescue efforts. Based on the observation that an unfolding emergency is likely to give rise to a burst of alerting messages, which may be used to early detect the event, followed by more reflective messages, whose content may be used to understand its consequences, several systems have focused on the collection and analysis of messages shared in areas affected by disasters (Hughes and Palen
<xref ref-type="bibr" rid="CR28">2009</xref>
; Bagrow et al.
<xref ref-type="bibr" rid="CR8">2011</xref>
; Adam et al.
<xref ref-type="bibr" rid="CR1">2012</xref>
; Gao et al.
<xref ref-type="bibr" rid="CR24">2014</xref>
; Avvenuti et al.
<xref ref-type="bibr" rid="CR5">2014a</xref>
. However, such information is often unstructured, heterogeneous and fragmented over a large number of messages in such a way that it cannot be directly used. It is therefore mandatory to turn that messy data into a number of clear and concise messages for emergency responders (Cresci et al.
<xref ref-type="bibr" rid="CR15">2015b</xref>
). Challenging issues highlighted and faced by pioneer systems include the real-time acquisition of unstructured data not specifically targeted to the system (data is often free text without structure or codified semantics) (Goolsby
<xref ref-type="bibr" rid="CR25">2010</xref>
), the extraction of critical data overwhelmed by high flood of meaningless babbles, the identification of the most stricken areas in the aftermath of an emergency (Cresci et al.
<xref ref-type="bibr" rid="CR15">2015c</xref>
; Sakai and Tamura
<xref ref-type="bibr" rid="CR43">2015</xref>
), security and privacy issues including the lack of guarantee that human sensors correctly deliver information about specific facts at specific times (Rosi et al.
<xref ref-type="bibr" rid="CR42">2011</xref>
).</p>
<p>Despite these common findings, an analysis of the state-of-the-art in the field of social sensing-based emergency management systems highlights a multitude of domain-specific, unstructured and heterogeneous solutions. In fact, in the literature the design of monolithic and vertical ad-hoc solutions still prevails over architectural approaches addressing modularity, generality and flexibility (Imran et al.
<xref ref-type="bibr" rid="CR29">2015</xref>
). This paper presents a framework for detecting emergent crisis events using humans as sensors. According to the framework, different emergency types (e.g., seismic, hydrological, meteorological) can be detected by configuring a software architecture, where re-usable components can adapt to different contents and patterns of messages posted to the OSN while the event unfolds. The contribution of the paper is both conceptual and practical. To the purpose of deepening and sharing the understanding of the properties and relationships of data provided by human sensors, we have defined a terminology and an ontology for the HaaS paradigm in the context of emergency detection. From the practical point of view, we have designed a domain-independent, architectural and modular framework that encompasses the vast majority of systems proposed to date. The effectiveness of the proposed architecture in solving common problems, such as data capturing, data filtering and emergency event detection, has been demonstrated by a proof-of-concept implementation involving earthquake detection via Twitter. The application has been validated using datasets of tweets collected during earthquakes occurred in Italy.</p>
</sec>
<sec id="Sec2">
<title>Related work</title>
<p>In this section, we outline the most relevant works in the field, discussing the main differences with our approach as well as the main similarities, in order to point out the works that inspired our architectural model. Thus, this section corroborates our approach under the more general umbrella of the HaaS paradigm for emergency management.</p>
<p>Several initiatives, both in scientific and in application environments, have been developed in the last few years with the aim of exploiting information available on social media during emergencies. Works proposed in the literature either describe working systems employing solutions for some of the fundamental challenges of emergency management, or focus on a single specific challenge and thoroughly study it. The systems surveyed in this section present different degrees of maturity. Some have been deployed and tested in real-life scenarios, while others remain under development (Imran et al.
<xref ref-type="bibr" rid="CR29">2015</xref>
). The vast majority of these systems share goals or functionalities with the framework we are proposing and can be mapped, totally or in part, on the architecture subsequently defined. Among the proposed systems some approaches are tailored to suit requirements of a specific kind of emergency and are therefore domain-specific. Overall, many of the surveyed works present shortcomings regarding their reusability.</p>
<p>The works presented in Bartoli et al. (
<xref ref-type="bibr" rid="CR9">2015</xref>
) and Foresti et al. (
<xref ref-type="bibr" rid="CR23">2015</xref>
) describe novel emergency management platforms for smart public safety and situational awareness. The proposed solutions exploit both wireless sensor networks and social media to support decision-makers during crises. In Bartoli et al. (
<xref ref-type="bibr" rid="CR9">2015</xref>
) a high-level framework is proposed which includes subsystems designed for the acquisition and the analysis of heterogeneous data. The subsystems working on social media data perform the data acquisition and data analysis tasks and can be directly mapped to the corresponding components of our architecture. In this framework data acquisition from social media has a marginal impact since it is activated only after the detection of an emergency. Thus Bartoli et al. (
<xref ref-type="bibr" rid="CR9">2015</xref>
) only marginally deals with the challenges related to the acquisition and handling of a big stream of social media data. An example of an application scenario for the system is also proposed for hydrological risks such as floods and landslides. The ASyEM system (Foresti et al.
<xref ref-type="bibr" rid="CR23">2015</xref>
) focuses on data acquisition and data fusion. Authors introduce an offline methodology for the extraction of emergency-specific terms which are subsequently used by the online system to gather relevant messages from social media sources. The detection of an emergency is performed by means of a neural tree network previously trained during the offline phase. Both Bartoli et al. (
<xref ref-type="bibr" rid="CR9">2015</xref>
) and Foresti et al. (
<xref ref-type="bibr" rid="CR23">2015</xref>
) lack a data filtering component. Similarly to Foresti et al. (
<xref ref-type="bibr" rid="CR23">2015</xref>
), the work discussed in Salfinger et al. (
<xref ref-type="bibr" rid="CR46">2015</xref>
) employs data fusion techniques in a system designed to increase situational awareness during emergencies. Authors propose a high-level architecture for an adaptive framework exploiting both traditionally sensed data as well as social media data.</p>
<p>Among the various kinds of emergencies, seismic events are those which have been investigated the most in the last few years. Earthquake emergency management is a topic worth studying not only for the big threat seismic events pose on communities and infrastructures. The detailed earthquake characterization obtainable from seismographic networks can be exploited as a baseline for novel social media-based emergency management systems and leveraged to achieve better results in terms of responsiveness and situational awareness. The opportunities granted by the application of the HaaS paradigm to earthquake detection and response have been firstly envisioned in works such as Earle (
<xref ref-type="bibr" rid="CR20">2010</xref>
), Allen (
<xref ref-type="bibr" rid="CR3">2012</xref>
), and Crooks et al. (
<xref ref-type="bibr" rid="CR17">2013</xref>
).</p>
<p>The study described in Sakaki et al. (
<xref ref-type="bibr" rid="CR45">2010</xref>
,
<xref ref-type="bibr" rid="CR44">2013</xref>
) is one among the first works proposing techniques for emergency management based on social media data. Authors investigate the design and development of a social alert detection and earthquake reporting system. The detection of an event is performed by means of a bayesian statistical model. Authors carried out experiments to assess the quality of the detections and their responsiveness. Detection results are evaluated only by means of the Recall metric (ratio of correctly detected earthquakes among the total occurred earthquakes) and the system was able to timely detect 67.9 % (53 out of 78) of the earthquakes with JMA (Japan Meteorological Agency) scale 2 or more which occurred over 2 months. It is worth noting that the JMA scale can not be directly mapped into the worldwide-adopted Richter magnitude scale used in Table
<xref rid="Tab1" ref-type="table">1</xref>
to evaluate our system
<xref ref-type="fn" rid="Fn1">1</xref>
. The approach proposed in Sakaki et al. (
<xref ref-type="bibr" rid="CR45">2010</xref>
,
<xref ref-type="bibr" rid="CR44">2013</xref>
) is tested on both earthquakes and tornadoes and the achieved results seem convincing towards the employment of this solution for other large-scale emergencies as well. However, the work only focuses on the event detection task, without dealing with the definition of a full working system. Moreover, data acquisition is performed by means of the Twitter Search API
<xref ref-type="fn" rid="Fn2">2</xref>
which accesses to only a portion of the amount of tweets produced. While this limitation can be negligible for large scale events, it can impair the system’s ability to detect events felt by a small number of social sensors, thus limiting the reusability of this system for small-scale emergencies such as landslips, traffic jams, car accidents, etc.</p>
<p>US Geological Survey (USGS) efforts towards the development of an earthquake detection system based solely on Twitter data are described in Earle et al. (
<xref ref-type="bibr" rid="CR21">2012</xref>
). The solution is evaluated with different settings according to the sensitivity of the event detection module. However, even in its best configuration, the system could only detect 48 globally distributed earthquakes out of the 5175 earthquakes occurred during the same time window. Also this system acquires data via the Twitter Search API, thus suffering from the same limitations described above. Basic data filtering concerns are taken into account and relevant messages are selected with a heuristic approach. Event detection is performed by a STA/LTA (short-term average/long-term average) algorithm. Although representing an interesting demonstration of the possibility to perform emergency event detection via social media, this system has a few shortcomings which severely limit its performances. The deeper level of analysis supported in our proposed architecture and performed in our implementation allow us to outperform USGS’s system. Overall, we believe the main reasons for our better performances lie in the adoption of more sophisticated filtering techniques (i.e. machine learning classifiers instead of heuristics) and a more powerful event detection algorithm (i.e. a burst detection algorithm instead of a STA/LTA). USGS kept on working on the project and recently announced the official employment of a Twitter earthquake detection system named TED (Tweet Earthquake Dispatch). As claimed by USGS, such detection system proved more responsive than those based on seismographs in regions where the number of seismographic stations is low
<xref ref-type="fn" rid="Fn3">3</xref>
<sup>,</sup>
<xref ref-type="fn" rid="Fn4">4</xref>
.</p>
<p>In Avvenuti et al. (
<xref ref-type="bibr" rid="CR5">2014a</xref>
,
<xref ref-type="bibr" rid="CR6">b</xref>
,
<xref ref-type="bibr" rid="CR7">2015</xref>
) is described the development of the Earthquake Alert and Report System (EARS). EARS is a real-time platform designed for the detection and the assessment of the consequences of earthquakes from social media data. The proposed solution employs data mining and natural language processing techniques to enhance situational awareness after seismic events. Although the proposed system is domain-specific and employed only in the field of earthquake emergency management, the discussion in Avvenuti et al. (
<xref ref-type="bibr" rid="CR6">2014b</xref>
) addresses issues common to all social media emergency management systems. Preliminary results of the works proposed in Sakaki et al. (
<xref ref-type="bibr" rid="CR45">2010</xref>
,
<xref ref-type="bibr" rid="CR44">2013</xref>
); Earle et al.
<xref ref-type="bibr" rid="CR21">2012</xref>
) and Avvenuti et al. (
<xref ref-type="bibr" rid="CR5">2014a</xref>
,
<xref ref-type="bibr" rid="CR6">b</xref>
,
<xref ref-type="bibr" rid="CR7">2015</xref>
) are overall encouraging, especially in relation to the responsiveness of the detections. In the present work we built on the key features of these systems in order to design a solution applicable to a broad range of emergencies.</p>
<p>Situational awareness during emergencies is the goal of the work described in Yin et al. (
<xref ref-type="bibr" rid="CR51">2012</xref>
). The Emergency Situation Awareness (ESA) platform operates over the Twitter stream by comparing terms used in recent tweets with those of a baseline. The baseline has been generated in an offline phase and represents a statistical model of the terms used during a fixed time window of several months. ESA raises alerts for every term which appears in recent tweets significantly more than in the baseline. The drawback of this approach is that the baseline does not account for topic seasonality. Moreover ESA does not perform data filtering neither employs keywords for the data acquisition and therefore many of the generated alerts are of little interest. ESA represents however one of the first domain-independent approaches to the problem of emergency management from social media. The core of the general ESA platform has been later expanded with ad-hoc filters and tailored to perform event detection in the earthquakes (Robinson et al.
<xref ref-type="bibr" rid="CR41">2013</xref>
) and wildfires (Power et al.
<xref ref-type="bibr" rid="CR39">2013</xref>
) domains. Other works have instead investigated the exploitation of social sensors for the detection of traffic jams (D’Andrea et al.
<xref ref-type="bibr" rid="CR19">2015</xref>
).</p>
<p>Crowdsourced crisis mapping from Twitter data is the goal of the systems proposed in Middleton et al. (
<xref ref-type="bibr" rid="CR37">2014</xref>
), Cresci et al. (
<xref ref-type="bibr" rid="CR15">2015c</xref>
). Crisis mapping concerns with the capturing, processing and display of data during a crisis with the goal of increasing situational awareness. Following an approach adopted in other previously reviewed works, these systems are composed of both offline and real-time (online) subsystems. The offline subsystems calculate baseline statistics during a historical period when no disasters occurred. Among the real-time subsystems Middleton et al. (
<xref ref-type="bibr" rid="CR37">2014</xref>
) also includes a data filtering component which, similarly to Earle et al. (
<xref ref-type="bibr" rid="CR21">2012</xref>
), applies heuristic rules to select relevant tweets. On the contrary, Cresci et al. (
<xref ref-type="bibr" rid="CR15">2015c</xref>
) uses machine learning techniques to filter and analyze data.</p>
<p>Lastly, the study in Imran et al. (
<xref ref-type="bibr" rid="CR29">2015</xref>
) presents a survey on computational techniques for social media data processing during emergencies and can be considered as a further reference for works in the fields of social media emergency management, crisis informatics and crisis mapping.</p>
</sec>
<sec id="Sec3">
<title>Core concepts and functionalities</title>
<p>
<fig id="Fig1">
<label>Fig. 1</label>
<caption>
<p>An ontological view of the HaaS paradigm for emergency management</p>
</caption>
<graphic xlink:href="40064_2016_1674_Fig1_HTML" id="MO1"></graphic>
</fig>
</p>
<p>Our conceptual framework is intended to operate in a broad class of domains. For this reason it should evolve from an explicit formal specification of terms and of relationships among them. This way, experts are supported with shared understanding of their domains of interest. A good specification serves as a basis to communicate in development, to guarantee consistency, to minimize misunderstanding and missed information, to overcome barriers to the acquisition of specifications, to reuse and analyze domain knowledge, and to separate it from operational knowledge. Among the suitable formalisms, ontologies are structured vocabularies with definitions of basic concepts and relations among them. Ontologies have interesting properties that can be formally verified, such as completeness, correctness, consistency, and unambiguity (Siegemund et al.
<xref ref-type="bibr" rid="CR48">2011</xref>
).</p>
<p>In this section we introduce the terminology of the “human as a sensor” (HaaS) paradigm via an ontology diagram. In Fig.
<xref rid="Fig1" ref-type="fig">1</xref>
base concepts are enclosed in gray ovals and connected by properties, represented by black directed edges. The fundamental property is on the right:
<italic>Decision System detects Emergency</italic>
. This property cannot be directly sensed (i.e., instantiated) by the system, and is therefore represented as an
<italic>abstract</italic>
property, shown by a dotted edge. Indeed the overall decision system is aimed at indirectly detecting emergencies by means of a series of information provided by sensors. As the system should be scalable in terms of types of emergency, different specific emergencies have been considered. In figure,
<italic>Seismic</italic>
,
<italic>Hydrological</italic>
,
<italic>Meteorological</italic>
, and
<italic>Terrorist</italic>
are examples of specialized concepts, shown with white ovals and connected by white directed edges to the base concept.</p>
<p>A
<italic>Decision System</italic>
is
<italic>owned by a Public Safety Agency</italic>
, and
<italic>exploits</italic>
both
<italic>Artificial</italic>
and
<italic>Social Detection Systems</italic>
. The former is a conventional system based on physical sensors: an
<italic>Artificial Detection System analyzes Observations</italic>
, which are
<italic>provided by Artificial Sensors</italic>
, i.e., a type of specialized
<italic>Sensor</italic>
. Another type of specialized sensor is human
<italic>Sense</italic>
, which is interpreted by
<italic>Humans</italic>
. Here, the concept
<italic>Human acts as a Sensor</italic>
can then be derived as a specialized human. Indeed, both
<italic>Human</italic>
and
<italic>Sensor</italic>
are in the
<italic>Territory</italic>
, where
<italic>Emergency occurs</italic>
and
<italic>Effects</italic>
of it are
<italic>measured by Sensors</italic>
. Differently from an artificial sensor, a
<italic>Human as a Sensor</italic>
is able to directly
<italic>perceive</italic>
an emergency and
<italic>owns a Terminal to deliver Messages in an Online Social Network</italic>
. For this reason, he can
<italic>alert via an Online Social Network</italic>
.
<italic>Location</italic>
is a structural property of a terminal. Specialized examples of Online Social Networks are
<italic>Twitter</italic>
,
<italic>Weibo</italic>
, and
<italic>Instagram</italic>
.
<fig id="Fig2">
<label>Fig. 2</label>
<caption>
<p>Use cases of the HaaS paradigm for emergency management</p>
</caption>
<graphic xlink:href="40064_2016_1674_Fig2_HTML" id="MO2"></graphic>
</fig>
</p>
<p>In the context of online detection, a structural property of a message is the
<italic>timestamp</italic>
. Other properties are content-based and must be recognized as specialized types: a
<italic>Trusted Message</italic>
, i.e., a message which is not sent for malicious, disruptive or abusive purposes (Mendoza et al.
<xref ref-type="bibr" rid="CR36">2010</xref>
; Castillo et al.
<xref ref-type="bibr" rid="CR10">2011</xref>
); a
<italic>Primary Message</italic>
, i.e., a message sent by a user who is actually present at the referred event and can directly describe it (Kumar et al.
<xref ref-type="bibr" rid="CR33">2013</xref>
; Morstatter et al.
<xref ref-type="bibr" rid="CR38">2014</xref>
); an
<italic>Emergency Message</italic>
, i.e., a message reporting an actual social emergency and not, for instance, reporting a personal problem via an idiom made of emergency words (Avvenuti et al.
<xref ref-type="bibr" rid="CR5">2014a</xref>
). If all these properties are available in a single message, that message can be considered an instance of a further specialized concept, the
<italic>Ongoing Emergency Message</italic>
, which is a message reporting an ongoing emergency. In addition, an Ongoing Emergency Message must have another property: being
<italic>temporally close to</italic>
another message of the same typology. This way, the
<italic>Social Detection System recognizes</italic>
a number of temporally close messages. Thus, the detection of an actual social emergency encompasses many messages, differently arranged in time depending on the type of emergency.</p>
<p>Managing a
<italic>Social Detection System</italic>
requires interaction between different external agents (people or systems), represented in Fig.
<xref rid="Fig2" ref-type="fig">2</xref>
as UML use cases. Here, interacting agents are called actors and are represented by the “stick man” icon, whereas functionalities available to actors are represented by an oval shape. An actor can communicate with the system through an association to a functionality, represented as a link. Use cases have been related to other use cases by the
<italic>extend</italic>
and
<italic>include</italic>
relationships, allowing to increment a use case and to specify a piece of the use case in a modular way, respectively. A relationship is represented as a dashed directed arrow, whose direction denotes dependency.</p>
<p>More specifically, for a given emergency type (e.g., earthquake, flooding, or their subtypes) the
<italic>Decision System</italic>
asks the
<italic>Social Detection System</italic>
(hereafter called System for the sake of brevity) to be prepared to
<italic>get alerts of that emergency type</italic>
. This functionality includes the activation of the
<italic>content-based filtering of messages</italic>
, which is in charge of providing, among the messages captured from the
<italic>Online Social Network</italic>
actor (e.g., Twitter), only those containing information related to the unfolding emergency situation. We call this use case the
<italic>online process</italic>
.</p>
<p>Emergency-specific knowledge of the content of messages is thus necessary to extend the System’s capability in recognising multiple emergency types. Such a knowledge can be extracted from a
<italic>message corpus</italic>
, a large and structured set of messages (electronically stored and processed), used for statistical analysis and hypothesis testing, checking occurrences or validating filtering within a specific emergency type. Extracted knowledge can be encoded as: (1)
<italic>terms</italic>
that are frequently contained in the target messages, established via statistical methods; (2)
<italic>features</italic>
extracted from a
<italic>training set</italic>
of target messages, established via machine learning methods; (3) parameters of collections of messages related to the same emergency event, established via statistical methods.</p>
<p>Thus, when a new emergency type has to be managed, the
<italic>content-based filtering of messages</italic>
functionality must be previously extended with emergency-specific knowledge provided by the
<italic>configure filters</italic>
functionality. This process is managed by the actor responsible for the System’s maintenance and configuration, the
<italic>Social Network Analyst</italic>
. Configuring filters includes
<italic>creating training sets and extracting terms from corpus</italic>
.
<italic>To build a corpus</italic>
includes to
<italic>annotate corpus</italic>
, in collaboration with a number of
<italic>Annotators</italic>
. We call the
<italic>configure filters</italic>
use case the
<italic>offline process</italic>
.</p>
</sec>
<sec id="Sec4">
<title>Architectural design</title>
<p>The “human as a sensor” (HaaS) paradigm for emergency management so far determined has been used as a reference for designing an efficient, flexible and scalable software architecture. The analysis conducted in the previous section, as well as the findings reported in previous works, highlighted the fundamental challenges related to processing social media data for the detection of unfolding emergency situations (Imran et al.
<xref ref-type="bibr" rid="CR29">2015</xref>
). Such challenges comprehend: (1) data capturing, (2) data filtering and (3) emergency event detection. The challenge related to data capturing lies in gathering, among the sheer amount of social media messages, the most complete and specific set of messages for the detection of a given type of emergency. However, not all collected messages are actually related to an unfolding emergency, hence the need of a data filtering step to further reduce the noise among collected messages and retain only the relevant ones. Finally, techniques are needed in order to analyze relevant messages and infer the occurrence of an emergency event. The general framework for emergency management that we are proposing efficiently deals with all these aspects.</p>
<p>In this section the system logic is represented by a number of components and actors. A component represents a modular piece of logic whose external behavior can be concisely described to offer a platform-independent view. Each component may be developed in any programming language and by using one or more classes or procedures, since its internal algorithmic implementation is not detailed. Indeed, each component in the model can be replaced by another component supporting the same interfaces, thus providing modularity. Each actor represents a role played by a user interacting with the system components. Subsequently, a behavioral description of the system within its life cycle is also provided by means of a sequence of exchange messages between actors and components.</p>
<sec id="Sec5">
<title>Static view of the logical architecture</title>
<p>Figure
<xref rid="Fig3" ref-type="fig">3</xref>
shows a UML static view of the system, made by components and their interfaces. Here, a component is represented by a box, with provided and required interfaces represented by the “lollipop” and “socket” icons, respectively. Actors are represented by the “stick man” icon. Components that are external to the design are colored in dark gray. Some specific types of components or subsystems, such as repository, storage, knowledge base, web, are characterized by a special icon or shape. The usage of a component by an actor or by another component is represented by the socket icon or by the dashed arrow, respectively. The architecture is focused on the social detection system, i.e., on the HaaS input channel. The
<italic>Human as a Sensor</italic>
actor is represented on the bottom left as an actor using the
<italic>Terminal</italic>
subsystem to deliver messages to the
<italic>Online Social Network</italic>
subsystem. The
<italic>Online Social Network</italic>
subsystem feeds the main data flow carried out in the online mode of operation, i.e., the detection process. In figure, the components involved in the online process are arranged in a stack of components, enclosed in a dotted box, where the
<italic>Online Social Network</italic>
is a the bottom.</p>
<p>More specifically, the
<italic>Emergency Message Capturing</italic>
component accesses the
<italic>Online Social Network</italic>
’s global stream of data, via a streaming API, to collect emergency messages. The messages are captured according to the
<italic>Emergency-specific Terms</italic>
provided by the knowledge base, and then pushed to the
<italic>Emergency Messages</italic>
repository, which acts as a buffer with respect to the large data stream provided by the
<italic>Online Social Network</italic>
. The
<italic>Primary Messages Selection</italic>
component takes data from this buffer and provides only primary messages to the
<italic>Trusted Messages Selection</italic>
component, which, in turn, provides only trusted messages to the next component. The semantics of both
<italic>primary</italic>
and
<italic>trusted</italic>
is compliant with the HaaS ontology. The latter component employs a statically defined
<italic>Trusted Message Model</italic>
, which is the same for all types of emergencies. Both components implement fast and coarse-grained filtering to avoid congestion due to the large number of messages.
<fig id="Fig3">
<label>Fig. 3</label>
<caption>
<p>The logical architecture of a decision support system for emergency management based on social sensing</p>
</caption>
<graphic xlink:href="40064_2016_1674_Fig3_HTML" id="MO3"></graphic>
</fig>
<fig id="Fig4">
<label>Fig. 4</label>
<caption>
<p>Communication diagram of the online process in a decision support system for emergency management based on social sensing</p>
</caption>
<graphic xlink:href="40064_2016_1674_Fig4_HTML" id="MO4"></graphic>
</fig>
</p>
<p>The next filtering component is the
<italic>Ongoing Emergency Messages Selection</italic>
, which is fed by the
<italic>Trusted Message Selection</italic>
component and implements the namesake concept of the HaaS ontology. This component carries out a fine-grained filtering, employing an
<italic>Ongoing Emergency Message Model</italic>
knowledge base. The outgoing messages are subsequently sent to the
<italic>Emergency Event Detection</italic>
component, which is able to detect an actual collective emergency. Since each type of emergency needs a different parameterization, this component is based on the
<italic>Emergency-specific Parameters</italic>
knowledge base configured by the
<italic>Social Network Analyst</italic>
. The detected event is then gelolocated by the
<italic>Emergency Geolocation</italic>
component. Finally, the geolocated emergency is provided to the
<italic>Analysis System</italic>
, which is able to interoperate with a
<italic>Decision System</italic>
of a
<italic>Public Safety Agency</italic>
.</p>
<p>In the offline mode of operation, the setting of parametric models and knowledge bases for each type of emergency is covered. This offline process is managed by the
<italic>Social Network Analyst</italic>
(on the bottom right) with the help of some
<italic>Annotators</italic>
.</p>
<p>More specifically, given a new type of emergency the web is first accessed to find, via
<italic>Emergency Management Agency and News Archives</italic>
, some historical examples of the same type of emergency. Subsequently, an
<italic>Emergency-specific corpus</italic>
of messages is created via the
<italic>Corpus Building</italic>
component, accessing to the
<italic>Online Social Network</italic>
via a historical search API managed by the
<italic>Historical Messages Capturing</italic>
component.</p>
<p>Emergency-specific terms are then created by means of the
<italic>Offline Terms Building</italic>
component, which uses both the corpus and a
<italic>Static Message Baseline</italic>
component. A baseline represents common terms in online social networks, which hampers filtering and does not provide relevant information. For this reason, such terms are removed from messages.</p>
<p>Subsequently, an
<italic>Emergency-specific Training Set</italic>
is created by selecting and annotating messages in the corpus, via an
<italic>Annotation Tool</italic>
. The training set is finally used to train the
<italic>Ongoing Emergency Message Model</italic>
via the
<italic>Machine Learning Classifier</italic>
that exploits a set of features defined on the message corpus itself.</p>
<p>The next subsection provides a dynamic view of the above logical architecture.</p>
</sec>
<sec id="Sec6">
<title>Dynamic view of the logical architecture</title>
<p>In this subsection we focus on the sequence of steps performed by the diverse components in both online and offline processes. Figure
<xref rid="Fig4" ref-type="fig">4</xref>
shows the online process, via a UML communication diagram. Here, interacting components are connected by temporary links. Messages among components are shown as labeled arrows attached to links. Each message has a sequence number, name and arguments. A message may be asynchronous or synchronous. On an asynchronous call, the execution of the sender continues immediately after the call is issued, and the processing of the message is made by the receiver concurrently with the execution of the sender. On a synchronous call, the execution of the sender is blocked during the execution of the invoked procedure. When the receiver has carried out the procedure, it returns the generated values to the sender, which is awakened and allowed to continue execution. In a communication diagram, synchronous messages are shown with filled arrow head, whereas asynchronous messages have an open arrow head. A return message is denoted by a dashed open arrow head.
<fig id="Fig5">
<label>Fig. 5</label>
<caption>
<p>Communication diagram of the offline process in a decision support system for emergency management based on social sensing</p>
</caption>
<graphic xlink:href="40064_2016_1674_Fig5_HTML" id="MO5"></graphic>
</fig>
</p>
<p>Let us suppose that the offline process (as described later in Fig.
<xref rid="Fig5" ref-type="fig">5</xref>
) was previously performed so that the system is ready-to-use for a given type of emergency. The online process evolves as in the following: (1) the
<italic>Decision System</italic>
makes the
<italic>getAlerts</italic>
call to the
<italic>Analysis System</italic>
component, providing the
<italic>emergencyType</italic>
as a parameter (e.g., “earthquake”, “flooding”); (2–4) the
<italic>Analysis System</italic>
makes the
<italic>beginDetection</italic>
,
<italic>beginSelection</italic>
and
<italic>beginCapturing</italic>
calls to the
<italic>Emergency Event Detection</italic>
,
<italic>Ongoing Emergency Messages Selection</italic>
, and
<italic>Emergency Messages Capturing</italic>
components, respectively, providing the
<italic>emergencyType</italic>
as a parameter; (5) the
<italic>Emergency Messages Capturing</italic>
component makes the
<italic>beginStreaming</italic>
call to the
<italic>Online Social Network</italic>
component, providing the
<italic>emergengyTerms</italic>
as a parameter. The latter call is synchronous, so as to avoid losing data from the
<italic>Online Social Network</italic>
’s stream. The sixth step is made of a number of substeps iteratively carried out for each message delivered by the
<italic>Online Social Network</italic>
; for this purpose, the whole step for a given message is referred to as 6.*, whereas the single substep is referred to as 6.*.1, 6.*.2, and so on.</p>
<p>Each emergency message delivered by the
<italic>Online Social Network</italic>
to the
<italic>Emergency Messages Capturing</italic>
component (6.*.1), is then delivered to the
<italic>Primary Messages Selection</italic>
component (6.*.2), which
<italic>checks whether the message is primary or not</italic>
(6.*.3). If the message is primary, it is delivered to the
<italic>Trusted Messages Selection</italic>
component (6.*.4), which
<italic>checks whether the message is trusted or not</italic>
(6.*.5). If the message is trusted, it is delivered to the
<italic>Ongoing Emergency Messages Selection</italic>
component (6.*.6), which, in turn,
<italic>checks whether the message refers to an ongoing emergency or not</italic>
(6.*.7). If the message refers to an ongoing emergency, it is delivered to the
<italic>Emergency Event Detection</italic>
component (6.*.8), which according to an arbitrary detection algorithm (i.e., a message-burst detection algorithm),
<italic>checks whether to trigger the detection of an event or not</italic>
(6.*.9). When an event occurs, it is received (7) and geolocated (8) by the
<italic>Emergency Geolocation</italic>
component, and the
<italic>Analysis System</italic>
is finally
<italic>notified with an alert</italic>
(9) by the
<italic>Emergency Geolocation</italic>
component itself.</p>
<p>The offline process, described in Fig.
<xref rid="Fig5" ref-type="fig">5</xref>
, is aimed at providing the
<italic>Emergency Messages Capturing</italic>
component with
<italic>Emergency-specific Terms</italic>
, as well as training the
<italic>Machine Learning Classifier</italic>
component for a new type of emergency. At the beginning, the
<italic>Social Network Analyst</italic>
is provided with some occurrences of the new type of emergency via historical archives. He needs to build some collection of messages related to such occurrences.</p>
<p>In the first step the
<italic>Social Network Analyst configures the Corpus Building</italic>
component (1) with some parameters derived from the archives and purposely targeted on each specific occurrence (e.g., date and location of the emergency). Then, the
<italic>Social Network Analyst asks the Corpus Building</italic>
component to
<italic>build the corpus</italic>
(2). This is made through two substeps: the
<italic>Corpus Building</italic>
component asks the
<italic>Historical Messages Capturing</italic>
component to
<italic>capture messages</italic>
with the above parameters (2.1), and the
<italic>Historical Messages Capturing</italic>
component
<italic>gets message blocks from the Online Social Network</italic>
component (2.2), by using a historical search API. Message blocks are then returned and collected to build the corpus (2.3–2.4).</p>
<p>The
<italic>Social Network Analyst</italic>
, by using the returned corpus and a baseline of messages from the OSN, asks the
<italic>Offline Terms Building</italic>
component to
<italic>extract Emergency-specific Terms</italic>
(3) which are then deployed on a knowledge base (3.1). He also
<italic>enables the annotation campaign</italic>
of the corpus (4) by enrolling a number of
<italic>annotators</italic>
(4.*). At the end of the annotation campaign (4.2) the
<italic>Social Network Analyst</italic>
creates the training set of messages (4.3). The training set is then used by the
<italic>Social Network Analyst</italic>
to train the
<italic>Machine Learning Classifier</italic>
component (5) by exploiting the annotated corpus and a set of features defined on the corpus itself. At the end of the training, an
<italic>Ongoing Emergency Message Model</italic>
is created (5.1).</p>
<p>The model so far created will be used by the
<italic>Ongoing Emergency Messages Selection</italic>
component during the online process. The
<italic>Trusted Messages Selection</italic>
and the
<italic>Primary Messages Selection</italic>
components are ready-to-use for any type of emergencies, and then they do not require training nor setting procedures.</p>
<p>Finally, the
<italic>Emergency Messages Capturing</italic>
component will employ the
<italic>Emergency-specific Terms</italic>
created at the third step of the offline process to extract emergency messages from the
<italic>Online Social Network</italic>
during the online process.</p>
</sec>
</sec>
<sec id="Sec7">
<title>System implementation</title>
<p>This section describes an implementation of the logical architecture proposed in the previous section, by means of a prototypical application in the domain of
<italic>Seismic</italic>
emergencies. Such application implements the components involved in the online process (i.e., with reference to Fig.
<xref rid="Fig3" ref-type="fig">3</xref>
, those arranged in a stack on top of
<italic>Online Social Network</italic>
and enclosed in a dotted, light grey box) to act as a Twitter-based earthquake detector.</p>
<sec id="Sec8">
<title>Emergency Messages Capturing</title>
<p>The
<italic>Emergency Messages Capturing</italic>
component is in charge of gathering messages potentially related to an emergency. As the overall online process relies on data collected at this stage, this component plays a crucial role within the framework. As shown in Fig.
<xref rid="Fig3" ref-type="fig">3</xref>
,
<italic>Emergency Messages Capturing</italic>
interfaces directly to the
<italic>Online Social Networking</italic>
platform, provided by Twitter, and exploits the
<italic>Emergency-specific Terms</italic>
knowledge base, which is generated and updated by the offline process. This knowledge base contains the keywords used by the
<italic>Emergency Messages Capturing</italic>
component to query the Twitter platform in order to capture earthquake-related messages (e.g., for
<italic>Seismic</italic>
emergencies in Italy, it contains the two italian terms “terremoto” (earthquake) and “scossa” (tremor)).</p>
<p>Among the methods provided by Twitter for data capturing, the implemented system exploits the Streaming API
<xref ref-type="fn" rid="Fn5">5</xref>
to open a persistent connection with a stream of tweets. The Streaming API gives access to a global stream of messages, optionally filtered by search keywords. In contrast with the Search API used in the systems described in Sakaki et al. (
<xref ref-type="bibr" rid="CR45">2010</xref>
,
<xref ref-type="bibr" rid="CR44">2013</xref>
), Earle et al. (
<xref ref-type="bibr" rid="CR21">2012</xref>
), Yin et al. (
<xref ref-type="bibr" rid="CR51">2012</xref>
), Robinson et al. (
<xref ref-type="bibr" rid="CR41">2013</xref>
), which gives access only to a subset of all the tweets produced, the Streaming API potentially makes it possible to capture all the tweets matching the search criteria. To guarantee the robustness and the reliability of the system we also implemented additional mechanisms that manage rate-limit and generic connection problems in the use of the Streaming API. Such mechanisms include the adoption of a backup streaming connection to avoid loss of data in case of a sudden disconnection from the primary stream, and mechanisms to perform automatic reconnection upon disconnecting from a stream. Twitter rate-limits for the Streaming API
<xref ref-type="fn" rid="Fn6">6</xref>
are set so as to deliver, at any given time, at most 1 % of the total worldwide Twitter traffic, per streaming connection. However, our system never suffered from such a limitation over a 2 months long experiment, during which the collected tweets never generated a traffic exceeding the 1 % threshold. Applications exploiting Twitter’s Streaming API should also guarantee a rapid processing of delivered messages. Clients which are unable to process messages fast enough will be automatically disconnected by Twitter. This situation is commonly refered to as
<italic>Falling Behind</italic>
. Following Twitter’s guidelines, in our implementation we decoupled the data capturing and analysis phases by rapidly storing messages in a NoSQL MongoDB
<xref ref-type="fn" rid="Fn7">7</xref>
database. Such messages are later properly formatted and copied in a relational MySQL database for further processing.</p>
<p>It should be noted that not all the messages gathered in this first step are actually related to an unfolding seismic event. In fact, some messages can be misleading for the event detection task and must be filtered out as noise (Earle et al.
<xref ref-type="bibr" rid="CR21">2012</xref>
). For example, their contents could be maliciously fictitious, convey reported news or talk about past of future events. This motivates the filtering components required by the architecture and described in the following.</p>
</sec>
<sec id="Sec9">
<title>Primary Messages Selection</title>
<p>The
<italic>Primary Messages Selection</italic>
component is the first filtering module in the proposed architecture and is therefore fed with the whole stream of messages gathered by the
<italic>Emergency Messages Capturing</italic>
component. Due to the potentially large volume of messages to be processed at this stage, this component performs a fast coarse-grained filtering of incoming messages by applying heuristic rules to select
<italic>firsthand</italic>
tweets sent by
<italic>eyewitness</italic>
users who are actually present at the referred event and can directly describe it (Kumar et al.
<xref ref-type="bibr" rid="CR33">2013</xref>
; Morstatter et al. (
<xref ref-type="bibr" rid="CR38">2014</xref>
)).</p>
<p>Studying the characteristics of the messages shared on Twitter in the aftermath of seismic events led us to the observation that genuine reports of earthquakes do not follow any information diffusion model and are not influenced by other reports. However, this scenario rapidly evolves over time as the news of the earthquake spreads over the different medias, so that subsequent reports are in growing percentage influenced by other news. Thus, we concluded that the best results for the event detection task could be achieved by considering only spontaneous and independent messages. The
<italic>Primary Messages Selection</italic>
component therefore discards retweet messages, reply messages and messages shared by accounts belonging to a blacklist of 345 Twitter profiles that publish official information about recent emergencies. We are aware that the heuristics exploited by the
<italic>Primary Messages Selection</italic>
component might not be enough to discard all derivative messages. Nonetheless, they represent a computationally efficient way of filtering out the vast majority of useless messages. Furthermore, the modular and architectural solution we propose is particularly suitable for being expanded with alternative approaches and algorithmic solutions to this task.
<fig id="Fig6">
<label>Fig. 6</label>
<caption>
<p>A burst of messages registered after a moderate earthquake</p>
</caption>
<graphic xlink:href="40064_2016_1674_Fig6_HTML" id="MO6"></graphic>
</fig>
</p>
</sec>
<sec id="Sec10">
<title>Trusted Messages Selection</title>
<p>Another possible flaw for all social mining systems lies in the vulnerability to intentional attacks performed by malicious users (Mendoza et al.
<xref ref-type="bibr" rid="CR36">2010</xref>
; Castillo et al.
<xref ref-type="bibr" rid="CR10">2011</xref>
). In our application, security concerns can arise if groups of people collude to generate fictitious tweets referring to an earthquake. The online
<italic>Trusted Messages Selection</italic>
component exploits the
<italic>Trusted Message Model</italic>
to select trusted, reliable messages. Many already developed classifiers can be exploited for this task, such as the ones proposed in Chu et al. (
<xref ref-type="bibr" rid="CR11">2012</xref>
) and Amleshwaram et al. (
<xref ref-type="bibr" rid="CR4">2013</xref>
). In our implementation we employ a domain-independent machine learning classifier trained to distinguish between “fake” and “real” accounts (Cresci et al.
<xref ref-type="bibr" rid="CR16">2014</xref>
,
<xref ref-type="bibr" rid="CR13">2015a</xref>
). The classifier has been trained on a set of 3900 equally distributed fake and real accounts and was able to correctly classify more than 95 % of the accounts of the training set. In the online mode of operation, the
<italic>Trusted Messages Selection</italic>
component exploits the trained model and the Weka tool (Hall et al.
<xref ref-type="bibr" rid="CR27">2009</xref>
) to infer the class (fake, real) a user who posted a message belongs to. The
<italic>Trusted Messages Selection</italic>
component performs this operation for every message it receives from the
<italic>Primary Messages Selection</italic>
component. Messages posted by fake users are automatically discarded by the system. In addition, users repeatedly triggering false detections are added to the same account blacklist exploited by the
<italic>Primary Messages Selection</italic>
component. To further protect the system from harmful attacks, we consider only a single message per user, and messages from different users but with the same contents are considered only once. While we understand that these solutions do not fully address the problem of malicious attacks, we are confident that our efforts represent a first response to security concerns in social mining systems. In fact, the adopted solutions require potential attackers to put considerably much effort into the creation of plausible accounts. The employment of the solutions proposed in Chu et al. (
<xref ref-type="bibr" rid="CR11">2012</xref>
) and Amleshwaram et al. (
<xref ref-type="bibr" rid="CR4">2013</xref>
) for the classification of “automated” versus “non-automated” accounts, might represent another possible way to tackling this problem and stands as promising ground for future work.</p>
</sec>
<sec id="Sec11">
<title>Ongoing Emergency Messages Selection</title>
<p>To further enforce the
<italic>Primary</italic>
,
<italic>Trusted</italic>
and
<italic>Emergency</italic>
message properties, the
<italic>Ongoing Emergency Messages Selection</italic>
component performs a fine-grained filtering by means of the
<italic>Ongoing Emergency Message Model</italic>
, a machine learning classifier which has been trained in the offline process. Again, we exploited Weka to train and generate the classifier. The
<italic>Emergency-specific Training Set</italic>
for earthquakes is composed of more than 1400 tweets divided into two balanced sets of messages: tweets related and tweets not related to a seismic event in progress. During the offline phase, tweets of the training set were manually classified by the
<italic>Annotators</italic>
using the ad-hoc
<italic>Annotation Tool</italic>
web interface
<xref ref-type="fn" rid="Fn8">8</xref>
. Our analysis of the messages reporting earthquakes has highlighted a few interesting characteristics that help distinguish between tweets related and tweets not related to an unfolding seismic event. Tweets referring to an earthquake are generally very short, they present fewer punctuation than normal tweets and often contain slang or offensive words. This is because people reporting an earthquake are usually scared about the event and the content of the messages they write tend to reflect this emotion. Instead, tweets referring to official news of an earthquake or talking about a past earthquake present a longer, more structured message. Tweets not related to a recent earthquake also include a higher number of mentions and URLs than spontaneous earthquake reports. Thus, we defined the following set of features that takes into account the results of the previous analysis: (1) character count; (2) word count; (3) punctuation count; (4) URL count; (5) mention count; (6) slang/offensive word count. Notably, some of the features that we defined for this task are also supported by the findings of recent related works (Imran et al.
<xref ref-type="bibr" rid="CR30">2013</xref>
; Gupta et al.
<xref ref-type="bibr" rid="CR26">2013</xref>
).</p>
<p>Training the classifier with this set of features produced correct classifications in more than 90 % of the tweets of the
<italic>Emergency-specific Training Set</italic>
. The classifier was obtained using the decision tree J48, corresponding to the Java implementation of the C4.5 algorithm (Quinlan
<xref ref-type="bibr" rid="CR40">1993</xref>
) with a tenfold cross validation. In the online mode of operation, the prediction is performed by invoking the classifier every time a message is delivered to the
<italic>Ongoing Emergency Messages Selection</italic>
component. As Weka generally needs less than a second to predict the class of a new tweet by means of our decision tree model, it is feasible to use the fine-grained classifier filter at this stage of the system since most of the noisy messages have already been filtered out by previous components.</p>
</sec>
<sec id="Sec12">
<title>Emergency event detection</title>
<p>The detection of a seismic event is triggered by an exceptional growth in the frequency of messages that have passed the filtering phases. In our system, we adopt a novel event detection approach which is based on a burst detection algorithm. A burst is defined as a large number of occurrences of a phenomenon within a short time window (Zhang and Shasha
<xref ref-type="bibr" rid="CR52">2006</xref>
). Burst detection techniques are commonly applied to various fields such as the detection of topics in data streams. Our system triggers the detection of a seismic event when it identifies a burst of
<italic>Ongoing Emergency Messages</italic>
. Figure
<xref rid="Fig6" ref-type="fig">6</xref>
displays a rug plot of the arrival times of
<italic>Ongoing Emergency Messages</italic>
, as well as a histogram plot showing their frequency per minute, during a 3.4 magnitude earthquake occurred at 15:47:49, August 9 2014, in Tuscany regional district. After the occurrence time of the earthquake, denoted by the red vertical dashed line, a big burst of tweets was recorded by our system.
<table-wrap id="Tab1">
<label>Table 1</label>
<caption>
<p>Earthquake detection validation</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="left" rowspan="2">Magnitude</th>
<th align="left" rowspan="2">Earthquakes</th>
<th align="left" colspan="3">Detection results</th>
<th align="left" colspan="3">Validation metrics</th>
</tr>
<tr>
<th align="left">TP</th>
<th align="left">FP</th>
<th align="left">FN</th>
<th align="left">Precision (%)</th>
<th align="left">Recall (%)</th>
<th align="left">F-Measure (%)</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" colspan="8">
<italic>System validation against all the earthquakes registered by INGV</italic>
</td>
</tr>
<tr>
<td align="left">>2.0</td>
<td char="." align="char">404</td>
<td char="." align="char">17</td>
<td char="." align="char">30</td>
<td char="." align="char">387</td>
<td char="." align="char">36.17</td>
<td align="left">4.21</td>
<td align="left">7.54</td>
</tr>
<tr>
<td align="left">>2.5</td>
<td char="." align="char">102</td>
<td char="." align="char">16</td>
<td char="." align="char">30</td>
<td char="." align="char">86</td>
<td char="." align="char">34.78</td>
<td align="left">15.69</td>
<td align="left">21.62</td>
</tr>
<tr>
<td align="left">>3.0</td>
<td char="." align="char">26</td>
<td char="." align="char">13</td>
<td char="." align="char">17</td>
<td char="." align="char">13</td>
<td char="." align="char">43.33</td>
<td align="left">50.00</td>
<td align="left">46.43</td>
</tr>
<tr>
<td align="left">>3.5</td>
<td char="." align="char">11</td>
<td char="." align="char">9</td>
<td char="." align="char">3</td>
<td char="." align="char">2</td>
<td char="." align="char">75.00</td>
<td align="left">81.82</td>
<td align="left">78.26</td>
</tr>
<tr>
<td align="left">>4.0</td>
<td char="." align="char">7</td>
<td char="." align="char">5</td>
<td char="." align="char">0</td>
<td char="." align="char">2</td>
<td char="." align="char">
<italic>100</italic>
</td>
<td align="left">71.43</td>
<td align="left">83.33</td>
</tr>
<tr>
<td align="left">>4.5</td>
<td char="." align="char">2</td>
<td char="." align="char">2</td>
<td char="." align="char">0</td>
<td char="." align="char">0</td>
<td char="." align="char">
<italic>100</italic>
</td>
<td align="left">
<italic>100</italic>
</td>
<td align="left">
<italic>100</italic>
</td>
</tr>
<tr>
<td align="left" colspan="8">
<italic>System validation against earthquakes that generated at least one report on Twitter</italic>
</td>
</tr>
<tr>
<td align="left">>2.0</td>
<td char="." align="char">128</td>
<td char="." align="char">17</td>
<td char="." align="char">30</td>
<td char="." align="char">111</td>
<td char="." align="char">36.17</td>
<td align="left">13.28</td>
<td align="left">19.43</td>
</tr>
<tr>
<td align="left">>2.5</td>
<td char="." align="char">55</td>
<td char="." align="char">16</td>
<td char="." align="char">30</td>
<td char="." align="char">39</td>
<td char="." align="char">34.78</td>
<td align="left">29.09</td>
<td align="left">31.68</td>
</tr>
<tr>
<td align="left">>3.0</td>
<td char="." align="char">21</td>
<td char="." align="char">13</td>
<td char="." align="char">17</td>
<td char="." align="char">8</td>
<td char="." align="char">43.33</td>
<td align="left">61.90</td>
<td align="left">50.98</td>
</tr>
<tr>
<td align="left">>3.5</td>
<td char="." align="char">9</td>
<td char="." align="char">9</td>
<td char="." align="char">3</td>
<td char="." align="char">0</td>
<td char="." align="char">75.00</td>
<td align="left">
<italic>100</italic>
</td>
<td align="left">85.71</td>
</tr>
<tr>
<td align="left">>4.0</td>
<td char="." align="char">5</td>
<td char="." align="char">5</td>
<td char="." align="char">0</td>
<td char="." align="char">0</td>
<td char="." align="char">
<italic>100</italic>
</td>
<td align="left">
<italic>100</italic>
</td>
<td align="left">
<italic>100</italic>
</td>
</tr>
<tr>
<td align="left">>4.5</td>
<td char="." align="char">2</td>
<td char="." align="char">2</td>
<td char="." align="char">0</td>
<td char="." align="char">0</td>
<td char="." align="char">
<italic>100</italic>
</td>
<td align="left">
<italic>100</italic>
</td>
<td align="left">
<italic>100</italic>
</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<p>Excellent values for the validation metrics are reported in italics</p>
</table-wrap-foot>
</table-wrap>
</p>
<p>Works in Kleinberg (
<xref ref-type="bibr" rid="CR32">2003</xref>
), Ebina et al. (
<xref ref-type="bibr" rid="CR22">2011</xref>
) discuss various burst detection algorithms. Our
<italic>Emergency Event Detection</italic>
component implements the hierarchical algorithm proposed in Ebina et al. (
<xref ref-type="bibr" rid="CR22">2011</xref>
) since it is computationally light and can adapt well to both big and small bursts. An efficient algorithm is necessary because of the real-time nature of our system, and the ability to detect both big and small bursts fits well with the need of a flexible, scalable and reusable system.</p>
</sec>
</sec>
<sec id="Sec13">
<title>Experimental studies</title>
<p>The validation of the proposed
<italic>Social Detection System</italic>
has been carried out exploiting official data released by the National Institute of Geophysics and Volcanology
<xref ref-type="fn" rid="Fn9">9</xref>
(INGV), the authority responsible for monitoring seismic events in Italy. INGV uses different channels, including a dedicated Twitter account
<xref ref-type="fn" rid="Fn10">10</xref>
, to distribute detailed information about seismic events having magnitude 2 or more, which have been detected by their seismographic network. To validate the proposed architecture, we cross-checked all the events detected by the prototypical application described in the previous section, against the official reports released by INGV. This approach allowed us to validate our system with stronger metrics than the ones used in similar works, such as Sakaki et al. (
<xref ref-type="bibr" rid="CR45">2010</xref>
,
<xref ref-type="bibr" rid="CR44">2013</xref>
), Earle et al. (
<xref ref-type="bibr" rid="CR21">2012</xref>
) and Yin et al. (
<xref ref-type="bibr" rid="CR51">2012</xref>
), Robinson et al. (
<xref ref-type="bibr" rid="CR41">2013</xref>
). Specifically, the majority of social media emergency management systems have been validated with a focus on correct detections. However, the problem of false detections is often understated, despite being a critical factor in emergency management (Middleton et al.
<xref ref-type="bibr" rid="CR37">2014</xref>
). Therefore, we classified earthquake detection results as in the following:
<list list-type="bullet">
<list-item>
<p>
<italic>True Positives (TP)</italic>
events detected by our system and confirmed by INGV;</p>
</list-item>
<list-item>
<p>
<italic>False Positives (FP)</italic>
events detected by our system, but not confirmed by INGV;</p>
</list-item>
<list-item>
<p>
<italic>False Negatives (FN)</italic>
events reported by INGV but not detected by our system.</p>
</list-item>
</list>
</p>
<p>True Negatives (TN) are widely used in information retrieval and classification tasks together with TP, FP and FN. However, in our scenario TN are not applicable, as it would mean counting the number of earthquakes that did not happen and that our system did not detect. In addition, we also computed the following standard metric
<list list-type="bullet">
<list-item>
<p>
<italic>Precision</italic>
, ratio of correctly detected events among the total number of detected events:
<disp-formula id="Equ1">
<alternatives>
<tex-math id="M1">\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\textit{Precision}=\frac{TP}{TP+FP}$$\end{document}</tex-math>
<mml:math id="M2" display="block">
<mml:mrow>
<mml:mi mathvariant="italic">Precision</mml:mi>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>P</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>P</mml:mi>
<mml:mo>+</mml:mo>
<mml:mi>F</mml:mi>
<mml:mi>P</mml:mi>
</mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:math>
<graphic xlink:href="40064_2016_1674_Article_Equ1.gif" position="anchor"></graphic>
</alternatives>
</disp-formula>
</p>
</list-item>
<list-item>
<p>
<italic>Recall (a.k.a. Sensitivity)</italic>
, ratio of correctly detected events among the total number of occurred events:
<disp-formula id="Equ2">
<alternatives>
<tex-math id="M3">\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\textit{Recall}=\frac{TP}{TP+FN}$$\end{document}</tex-math>
<mml:math id="M4" display="block">
<mml:mrow>
<mml:mi mathvariant="italic">Recall</mml:mi>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>P</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>P</mml:mi>
<mml:mo>+</mml:mo>
<mml:mi>F</mml:mi>
<mml:mi>N</mml:mi>
</mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:math>
<graphic xlink:href="40064_2016_1674_Article_Equ2.gif" position="anchor"></graphic>
</alternatives>
</disp-formula>
</p>
</list-item>
<list-item>
<p>
<italic>F-Measure</italic>
, harmonic mean of Precision and Recall:
<disp-formula id="Equ3">
<alternatives>
<tex-math id="M5">\documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$\textit{F-Measure}=2*\frac{Precision*Recall}{Precision+Recall}$$\end{document}</tex-math>
<mml:math id="M6" display="block">
<mml:mrow>
<mml:mi mathvariant="italic">F</mml:mi>
<mml:mo>-</mml:mo>
<mml:mi mathvariant="italic">Measure</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>2</mml:mn>
<mml:mrow></mml:mrow>
<mml:mo></mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mi>P</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>i</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>i</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>n</mml:mi>
<mml:mrow></mml:mrow>
<mml:mo></mml:mo>
<mml:mi>R</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>P</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>i</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>i</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>n</mml:mi>
<mml:mo>+</mml:mo>
<mml:mi>R</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>l</mml:mi>
</mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:math>
<graphic xlink:href="40064_2016_1674_Article_Equ3.gif" position="anchor"></graphic>
</alternatives>
</disp-formula>
</p>
</list-item>
</list>
We were not able to compute other well-known metrics such as Specificity, Accuracy and Mathews Correlation Coefficient since they rely on the True Negatives (TN) count. Employed metrics are anyway exhaustive and allow a thorough validation of detection results. Table
<xref rid="Tab1" ref-type="table">1</xref>
summarizes event detection validation against earthquakes registered by INGV over a 66 days time window starting from 2013-07-19 to 2013-09-23. The number of earthquakes reported in Table
<xref rid="Tab1" ref-type="table">1</xref>
refers only to real earthquakes detected by INGV and therefore corresponds to the sum of TP and FN. FP instead represent false detections by our system.</p>
<p>We first evaluated the
<italic>Social Detection System</italic>
against all the earthquakes having a magnitude greater than 2.0, registered by INGV within the given time window. Results show that the detection of earthquakes with magnitude lower than 3 is a very challenging task. This is because the majority of these earthquakes are only detected by seismographic stations and not by people. For events with a magnitude equal to or greater than 3.5, results show a good performance of the system, as demonstrated by the encouraging values of F-Measure: 78.26 % for magnitude >3.5, 83.33 % for magnitude >4 and 100 % for magnitude >4.5. This is especially significant given that seismic events of a magnitude around 3 are considered “light” earthquakes and are generally perceived only by a very small number of social sensors.</p>
<p>The majority (68 %) of the earthquakes occurred during the 66 days validation time window were extremely light and did not generate any report on Twitter. A detection system based solely on tweets is obviously incapable of detecting such events and this is reflected by the high number of False Negatives (FN) and by the low Recall for earthquakes with magnitude lower than 3.</p>
<p>In the emergency management scenario, light seismic events only detected by seismographic stations clearly do not pose any threat to communities and infrastructures and earthquakes of interest are those actually felt by the population at large. Therefore we re-validated the system against those earthquakes that generated at least one report on Twitter. Results for this experiment are displayed in the bottom half of Table
<xref rid="Tab1" ref-type="table">1</xref>
and show an overall improvement in the system performances. It is worth noting that the proposed
<italic>Social Detection System</italic>
achieves flawless results (Precision, Recall and F-Measure = 100 %) for earthquakes of magnitude 4.0 or more and still performs very well on earthquakes which have a magnitude in the region of 3.5 (Precision = 75 %, Recall = 100 % and F-Measure = 85.71 %).
<fig id="Fig7">
<label>Fig. 7</label>
<caption>
<p>System responsiveness validation. Distribution of detection delays versus INGV notification delays</p>
</caption>
<graphic xlink:href="40064_2016_1674_Fig7_HTML" id="MO10"></graphic>
</fig>
</p>
<p>Figure
<xref rid="Fig7" ref-type="fig">7</xref>
characterizes the system’s responsiveness by means of boxplot and scatterplot distributions of the detection delays of our system compared to the notification delays of INGV official reports. The detection delays of our
<italic>Social Detection System</italic>
are computed as the difference between the occurrence timestamp of an earthquake and the timestamp of the corresponding detection triggered by the
<italic>Emergency Event Detection</italic>
component. INGV notification delays are computed as the difference between the occurrence timestamp of an earthquake and the timestamp of the corresponding official report released by INGV. The detection delays reported in Fig.
<xref rid="Fig7" ref-type="fig">7</xref>
have been computed considering only True Positive detections.</p>
<p>INGV official reports are the timeliest publicly available source of information about earthquakes in Italy. Anyway, INGV notification delays are considerably higher than the detection delays of our system. In Fig.
<xref rid="Fig7" ref-type="fig">7</xref>
this is evident from the massive gap between the spreads (or boxes) of the two distributions. Earthquake detection responsiveness of our system is even more valuable since early reports of severe earthquakes might be of interest not only to emergency responders, but also to all breaking news agencies looking for fresh information to publish as well as to insurance companies and financial advisors.</p>
<p>Among all the detections performed by our system, 87 % occurred within 5 minutes of the earthquake and 43 % occurred within 2 minutes. These results are promising, especially considering that the proposed framework is adaptable to other emergency scenarios where automatic detection equipment, playing the role of seismographs for seismic events, might not be available. Being able to automatically detect a considerable percentage of emergency situations within minutes of the event would surely benefit emergency responders.</p>
</sec>
<sec id="Sec14">
<title>Conclusions and future work</title>
<p>In this paper we have discussed how the HaaS paradigm can be exploited for emergency detection. Core concepts, major roles and functionalities have been specified to operate in a broad class of emergencies. The design of architectural components reusable for many types of events, and possibly adaptive with respect to the different characteristics of each type, has been detailed. Related works have been discussed via the proposed architectural model, to systematize the available solutions under our modular and platform-independent conceptual framework. The implementation of an actual Twitter-based earthquake detector has been then presented, to show the effectiveness of our approach. Furthermore, a real-world case of application has been discussed and analyzed, discovering the most interesting properties of our approach. In addition, the architecture has been validated under more comprehensive metrics with respect to the existing literature.</p>
<p>As a future work, to better assess the system over its whole life cycle, it should be cross-validated on other real-world scenarios, involving emergencies of different types and sizes. Afterwards, the next key investigation activities along this line of research should be to employ real-time data provided by bursts of messages as a mine of information for situational awareness and damage assessment. Specifically, qualitative analyses of relevant messages can be performed to increase the overall situational awareness in the aftermath of an emergency. Qualitative analyses of the textual content of messages can be performed via natural language processing techniques and might lead to time-evolving term-clouds, highlighting those textual bits which convey critical and actionable information. In parallel, analyses of the multimedia content of messages can be carried out by means of image filtering and image clustering techniques. However, despite providing valuable insights into the unfolding scenario, the output of qualitative analyses still requires to be interpreted by domain-experts. In contrast, quantitative analyses could provide unambiguous outputs which might prove even more valuable to decision-makers and emergency responders. Specifically, for seismic events, a quantitative approach to the estimation of the impact of an earthquake can be performed by training statistical regression models to estimate earthquake intensity from the characteristics of social media reports.</p>
<p>In the future we look forward to addressing these issues by extending our modular framework to include components performing analyses aimed at increasing situational awareness and capable of providing early damage assessments.</p>
</sec>
</body>
<back>
<fn-group>
<fn id="Fn1">
<label>1</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://earthquake.usgs.gov/learn/topics/mag_vs_int.php">http://earthquake.usgs.gov/learn/topics/mag_vs_int.php</ext-link>
.</p>
</fn>
<fn id="Fn2">
<label>2</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://dev.twitter.com/rest/reference/get/search/tweets">https://dev.twitter.com/rest/reference/get/search/tweets</ext-link>
.</p>
</fn>
<fn id="Fn3">
<label>3</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://www.livescience.com/45385-earthquake-alerts-from-twitter.html">http://www.livescience.com/45385-earthquake-alerts-from-twitter.html</ext-link>
.</p>
</fn>
<fn id="Fn4">
<label>4</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://blog.twitter.com/2015/usgs-twitter-data-earthquake-detection">https://blog.twitter.com/2015/usgs-twitter-data-earthquake-detection</ext-link>
.</p>
</fn>
<fn id="Fn5">
<label>5</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://dev.twitter.com/streaming/overview">https://dev.twitter.com/streaming/overview</ext-link>
.</p>
</fn>
<fn id="Fn6">
<label>6</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://dev.twitter.com/streaming/overview/messages-types#limit_notices">https://dev.twitter.com/streaming/overview/messages-types#limit_notices</ext-link>
.</p>
</fn>
<fn id="Fn7">
<label>7</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://www.mongodb.org/">http://www.mongodb.org/</ext-link>
.</p>
</fn>
<fn id="Fn8">
<label>8</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://wafi.iit.cnr.it/sosnlp/sosnlp/annotation_tool">http://wafi.iit.cnr.it/sosnlp/sosnlp/annotation_tool</ext-link>
.</p>
</fn>
<fn id="Fn9">
<label>9</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://www.ingv.it/en/">http://www.ingv.it/en/</ext-link>
.</p>
</fn>
<fn id="Fn10">
<label>10</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://twitter.com/ingvterremoti">https://twitter.com/ingvterremoti</ext-link>
.</p>
</fn>
</fn-group>
<ack>
<title>Authors' contributions</title>
<p>MA, MGCAC, SC, AM, and MT are all responsible for the concept of the paper, the results presented and the writing. All authors have read and approved the manuscript.</p>
<sec id="d30e2110">
<title>Acknowledgements</title>
<p>This research was partially supported by the .it domain registration authority (Registro .it) funded project SoS - Social Sensing (
<ext-link ext-link-type="uri" xlink:href="http://socialsensing.it/en">http://socialsensing.it/en</ext-link>
).</p>
</sec>
<sec id="FPar1">
<title>Competing interests</title>
<p>The authors declare that they have no competing interests.</p>
</sec>
</ack>
<ref-list id="Bib1">
<title>References</title>
<ref id="CR1">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Adam</surname>
<given-names>NR</given-names>
</name>
<name>
<surname>Shafiq</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Staffin</surname>
<given-names>R</given-names>
</name>
</person-group>
<article-title>Spatial computing and social media in the context of disaster management</article-title>
<source>IEEE Intell Syst</source>
<year>2012</year>
<volume>27</volume>
<issue>6</issue>
<fpage>90</fpage>
<lpage>96</lpage>
<pub-id pub-id-type="doi">10.1109/MIS.2012.113</pub-id>
</element-citation>
</ref>
<ref id="CR2">
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Aggarwal</surname>
<given-names>CC</given-names>
</name>
<name>
<surname>Abdelzaher</surname>
<given-names>T</given-names>
</name>
</person-group>
<person-group person-group-type="editor">
<name>
<surname>Aggarwal</surname>
<given-names>CC</given-names>
</name>
</person-group>
<article-title>Social sensing</article-title>
<source>Managing and mining sensor data</source>
<year>2013</year>
<edition>1</edition>
<publisher-loc>New York</publisher-loc>
<publisher-name>Springer</publisher-name>
<fpage>237</fpage>
<lpage>297</lpage>
</element-citation>
</ref>
<ref id="CR3">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Allen</surname>
<given-names>RM</given-names>
</name>
</person-group>
<article-title>Transforming earthquake detection?</article-title>
<source>Science</source>
<year>2012</year>
<volume>335</volume>
<issue>6066</issue>
<fpage>297</fpage>
<lpage>298</lpage>
<pub-id pub-id-type="doi">10.1126/science.1214650</pub-id>
<pub-id pub-id-type="pmid">22267802</pub-id>
</element-citation>
</ref>
<ref id="CR4">
<mixed-citation publication-type="other">Amleshwaram AA, Reddy N, Yadav S, Gu G, Yang C (2013) Cats: characterizing automation of twitter spammers. In: Fifth international conference on communication systems and networks (COMSNETS), 2013, pp 1–10. IEEE</mixed-citation>
</ref>
<ref id="CR5">
<mixed-citation publication-type="other">Avvenuti M, Cresci S, La Polla MN, Marchetti A, Tesconi M (2014a) Earthquake emergency management by social sensing. In: IEEE international conference on pervasive computing and communications workshops (PERCOM Workshops), 2014, pp 587–592. IEEE</mixed-citation>
</ref>
<ref id="CR6">
<mixed-citation publication-type="other">Avvenuti M, Cresci S, Marchetti A, Meletti C, Tesconi M (2014b) EARS (Earthquake Alert and Report System): a real time decision support system for earthquake crisis management. In: Proceedings of the 20th ACM SIGKDD international conference on knowledge discovery and data mining, pp 1749–1758. ACM</mixed-citation>
</ref>
<ref id="CR7">
<mixed-citation publication-type="other">Avvenuti M, Del Vigna F, Cresci S, Marchetti A, Tesconi M (2015) Pulling information from social media in the aftermath of unpredictable disasters. In: 2nd international conference on information and communication technologies for disaster management (ICT-DM), 2015. IEEE</mixed-citation>
</ref>
<ref id="CR8">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Bagrow</surname>
<given-names>JP</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Barabasi</surname>
<given-names>A-L</given-names>
</name>
</person-group>
<article-title>Collective response of human populations to large-scale emergencies</article-title>
<source>PloS one</source>
<year>2011</year>
<volume>6</volume>
<issue>3</issue>
<fpage>17680</fpage>
<pub-id pub-id-type="doi">10.1371/journal.pone.0017680</pub-id>
</element-citation>
</ref>
<ref id="CR9">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Bartoli</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Fantacci</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Gei</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Marabissi</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Micciullo</surname>
<given-names>L</given-names>
</name>
</person-group>
<article-title>A novel emergency management platform for smart public safety</article-title>
<source>Int J Commun Syst</source>
<year>2015</year>
<volume>28</volume>
<issue>5</issue>
<fpage>928</fpage>
<lpage>943</lpage>
<pub-id pub-id-type="doi">10.1002/dac.2716</pub-id>
</element-citation>
</ref>
<ref id="CR10">
<mixed-citation publication-type="other">Castillo C, Mendoza M, Poblete B (2011) Information credibility on twitter. In: Proceedings of the 20th international conference on world wide web, pp 675–684. ACM</mixed-citation>
</ref>
<ref id="CR11">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chu</surname>
<given-names>Z</given-names>
</name>
<name>
<surname>Gianvecchio</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Jajodia</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Detecting automation of twitter accounts: are you a human, bot, or cyborg?</article-title>
<source>IEEE Trans Dependable Secure Comput</source>
<year>2012</year>
<volume>9</volume>
<issue>6</issue>
<fpage>811</fpage>
<lpage>824</lpage>
<pub-id pub-id-type="doi">10.1109/TDSC.2012.75</pub-id>
</element-citation>
</ref>
<ref id="CR12">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Cimino</surname>
<given-names>MG</given-names>
</name>
<name>
<surname>Lazzerini</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Marcelloni</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Ciaramella</surname>
<given-names>A</given-names>
</name>
</person-group>
<article-title>An adaptive rule-based approach for managing situation-awareness</article-title>
<source>Exp Syst Appl</source>
<year>2012</year>
<volume>39</volume>
<issue>12</issue>
<fpage>10796</fpage>
<lpage>10811</lpage>
<pub-id pub-id-type="doi">10.1016/j.eswa.2012.03.014</pub-id>
</element-citation>
</ref>
<ref id="CR13">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Cresci</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Di Pietro</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Petrocchi</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Spognardi</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Tesconi</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>Fame for sale: efficient detection of fake Twitter followers</article-title>
<source>Decis Support Syst</source>
<year>2015</year>
<volume>80</volume>
<fpage>56</fpage>
<lpage>71</lpage>
<pub-id pub-id-type="doi">10.1016/j.dss.2015.09.003</pub-id>
</element-citation>
</ref>
<ref id="CR14">
<mixed-citation publication-type="other">Cresci S, Tesconi M, Cimino A, Dell’Orletta F (2015b) A linguistically-driven approach to cross-event damage assessment of natural disasters from social media messages. In: Proceedings of the 24th international conference on world wide web companion, pp 1195–1200. International World Wide Web Conferences Steering Committee</mixed-citation>
</ref>
<ref id="CR15">
<mixed-citation publication-type="other">Cresci S, Cimino A, Dell’Orletta F, Tesconi M (2015c) Crisis mapping during natural disasters via text analysis of social media messages. In: Web Information Systems Engineering-WISE 2015, pp 250–258. Springer</mixed-citation>
</ref>
<ref id="CR16">
<mixed-citation publication-type="other">Cresci S, Petrocchi M, Spognardi A, Tesconi M, Di Pietro R (2014) A criticism to society (as seen by twitter analytics). In: IEEE 34th international conference on distributed computing systems workshops (ICDCSW), 2014, pp 194–200. IEEE</mixed-citation>
</ref>
<ref id="CR17">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Crooks</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Croitoru</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Stefanidis</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Radzikowski</surname>
<given-names>J</given-names>
</name>
</person-group>
<article-title># Earthquake: Twitter as a distributed sensor system</article-title>
<source>Trans GIS</source>
<year>2013</year>
<volume>17</volume>
<issue>1</issue>
<fpage>124</fpage>
<lpage>147</lpage>
<pub-id pub-id-type="doi">10.1111/j.1467-9671.2012.01359.x</pub-id>
</element-citation>
</ref>
<ref id="CR18">
<mixed-citation publication-type="other">Demirbas M, Bayir MA, Akcora CG, Yilmaz YS, Ferhatosmanoglu H (2010) Crowd-sourced sensing and collaboration using twitter. In: IEEE international symposium on a world of wireless mobile and multimedia networks (WoWMoM), 2010, pp 1–9. IEEE</mixed-citation>
</ref>
<ref id="CR19">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>D’Andrea</surname>
<given-names>E</given-names>
</name>
<name>
<surname>Ducange</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Lazzerini</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Marcelloni</surname>
<given-names>F</given-names>
</name>
</person-group>
<article-title>Real-time detection of traffic from twitter stream analysis</article-title>
<source>IEEE Trans Intell Transp Syst</source>
<year>2015</year>
<volume>16</volume>
<issue>4</issue>
<fpage>2269</fpage>
<lpage>2283</lpage>
<pub-id pub-id-type="doi">10.1109/TITS.2015.2404431</pub-id>
</element-citation>
</ref>
<ref id="CR20">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Earle</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>Earthquake twitter</article-title>
<source>Nat Geosci</source>
<year>2010</year>
<volume>3</volume>
<issue>4</issue>
<fpage>221</fpage>
<lpage>222</lpage>
<pub-id pub-id-type="doi">10.1038/ngeo832</pub-id>
</element-citation>
</ref>
<ref id="CR21">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Earle</surname>
<given-names>PS</given-names>
</name>
<name>
<surname>Bowden</surname>
<given-names>DC</given-names>
</name>
<name>
<surname>Guy</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>Twitter earthquake detection: earthquake monitoring in a social world</article-title>
<source>Ann Geophys</source>
<year>2012</year>
<volume>54</volume>
<issue>6</issue>
<fpage>708</fpage>
<lpage>715</lpage>
</element-citation>
</ref>
<ref id="CR22">
<mixed-citation publication-type="other">Ebina R, Nakamura K, Oyanagi S (2011) A real-time burst detection method. In: 23rd IEEE international conference on tools with artificial intelligence (ICTAI), 2011, pp 1040–1046. IEEE</mixed-citation>
</ref>
<ref id="CR23">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Foresti</surname>
<given-names>GL</given-names>
</name>
<name>
<surname>Farinosi</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Vernier</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>Situational awareness in smart environments: socio-mobile and sensor data fusion for emergency response to disasters</article-title>
<source>J Ambient Intell Humaniz Comput</source>
<year>2015</year>
<volume>6</volume>
<issue>2</issue>
<fpage>239</fpage>
<lpage>257</lpage>
<pub-id pub-id-type="doi">10.1007/s12652-014-0227-x</pub-id>
</element-citation>
</ref>
<ref id="CR24">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Gao</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Song</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Gao</surname>
<given-names>Z</given-names>
</name>
<name>
<surname>Barabási</surname>
<given-names>A-L</given-names>
</name>
<name>
<surname>Bagrow</surname>
<given-names>JP</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>D</given-names>
</name>
</person-group>
<article-title>Quantifying information flow during emergencies</article-title>
<source>Sci Rep</source>
<year>2014</year>
<volume>4</volume>
<fpage>3997</fpage>
<pub-id pub-id-type="pmid">24499738</pub-id>
</element-citation>
</ref>
<ref id="CR25">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Goolsby</surname>
<given-names>R</given-names>
</name>
</person-group>
<article-title>Social media as crisis platform: the future of community maps/crisis maps</article-title>
<source>ACM Trans Intell Syst Technol (TIST)</source>
<year>2010</year>
<volume>1</volume>
<issue>1</issue>
<fpage>7</fpage>
</element-citation>
</ref>
<ref id="CR26">
<mixed-citation publication-type="other">Gupta A, Lamba H, Kumaraguru P, Joshi A (2013) Faking sandy: characterizing and identifying fake images on twitter during hurricane sandy. In: Proceedings of the 22nd international conference on world wide web companion, pp 729–736. International World Wide Web Conferences Steering Committee</mixed-citation>
</ref>
<ref id="CR27">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hall</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Frank</surname>
<given-names>E</given-names>
</name>
<name>
<surname>Holmes</surname>
<given-names>G</given-names>
</name>
<name>
<surname>Pfahringer</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Reutemann</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Witten</surname>
<given-names>IH</given-names>
</name>
</person-group>
<article-title>The weka data mining software: an update</article-title>
<source>ACM SIGKDD Explor Newsl</source>
<year>2009</year>
<volume>11</volume>
<issue>1</issue>
<fpage>10</fpage>
<lpage>18</lpage>
<pub-id pub-id-type="doi">10.1145/1656274.1656278</pub-id>
</element-citation>
</ref>
<ref id="CR28">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hughes</surname>
<given-names>AL</given-names>
</name>
<name>
<surname>Palen</surname>
<given-names>L</given-names>
</name>
</person-group>
<article-title>Twitter adoption and use in mass convergence and emergency events</article-title>
<source>Int J Emerg Manag</source>
<year>2009</year>
<volume>6</volume>
<issue>3</issue>
<fpage>248</fpage>
<lpage>260</lpage>
<pub-id pub-id-type="doi">10.1504/IJEM.2009.031564</pub-id>
</element-citation>
</ref>
<ref id="CR29">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Imran</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Castillo</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Diaz</surname>
<given-names>F</given-names>
</name>
<name>
<surname>Vieweg</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Processing social media messages in mass emergency: a survey</article-title>
<source>ACM Comput Surv (CSUR)</source>
<year>2015</year>
<volume>47</volume>
<issue>4</issue>
<fpage>67</fpage>
<pub-id pub-id-type="doi">10.1145/2771588</pub-id>
</element-citation>
</ref>
<ref id="CR30">
<mixed-citation publication-type="other">Imran M, Elbassuoni SM, Castillo C, Diaz F, Meier P (2013) Extracting information nuggets from disaster-related messages in social media. In: Proceedings of ISCRAM, Baden-Baden, Germany</mixed-citation>
</ref>
<ref id="CR31">
<mixed-citation publication-type="other">Kapadia A, Kotz D, Triandopoulos N (2009) Opportunistic sensing: security challenges for the new paradigm. In: Communication systems and networks and workshops, 2009. COMSNETS 2009. First International, pp 1–10. IEEE</mixed-citation>
</ref>
<ref id="CR32">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kleinberg</surname>
<given-names>J</given-names>
</name>
</person-group>
<article-title>Bursty and hierarchical structure in streams</article-title>
<source>Data Min Knowl Discov</source>
<year>2003</year>
<volume>7</volume>
<issue>4</issue>
<fpage>373</fpage>
<lpage>397</lpage>
<pub-id pub-id-type="doi">10.1023/A:1024940629314</pub-id>
</element-citation>
</ref>
<ref id="CR33">
<mixed-citation publication-type="other">Kumar S, Morstatter F, Zafarani R, Liu H (2013) Whom should i follow?: identifying relevant users during crises. In: Proceedings of the 24th ACM conference on hypertext and social media, pp 139–147. ACM</mixed-citation>
</ref>
<ref id="CR34">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lampos</surname>
<given-names>V</given-names>
</name>
<name>
<surname>Cristianini</surname>
<given-names>N</given-names>
</name>
</person-group>
<article-title>Nowcasting events from the social web with statistical learning</article-title>
<source>ACM Trans Intell Syst Technol (TIST)</source>
<year>2012</year>
<volume>3</volume>
<issue>4</issue>
<fpage>72</fpage>
</element-citation>
</ref>
<ref id="CR35">
<mixed-citation publication-type="other">Liang Y, Caverlee J, Mander J (2013) Text vs. images: on the viability of social media to assess earthquake damage. In: Proceedings of the 22nd international conference on world wide web companion, pp 1003–1006. International World Wide Web Conferences Steering Committee</mixed-citation>
</ref>
<ref id="CR36">
<mixed-citation publication-type="other">Mendoza M, Poblete B, Castillo C (2010) Twitter under crisis: can we trust what we rt? In: Proceedings of the first workshop on social media analytics, pp 71–79. ACM</mixed-citation>
</ref>
<ref id="CR37">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Middleton</surname>
<given-names>SE</given-names>
</name>
<name>
<surname>Middleton</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Modafferi</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Real-time crisis mapping of natural disasters using social media</article-title>
<source>IEEE Intell Syst</source>
<year>2014</year>
<volume>29</volume>
<issue>2</issue>
<fpage>9</fpage>
<lpage>17</lpage>
<pub-id pub-id-type="doi">10.1109/MIS.2013.126</pub-id>
</element-citation>
</ref>
<ref id="CR38">
<mixed-citation publication-type="other">Morstatter F, Lubold N, Pon-Barry H, Pfeffer J, Liu H (2014) Finding eyewitness tweets during crises. In: Proceedings of the ACL 2014 workshop on language technologies and computational social science, p 23. ACL</mixed-citation>
</ref>
<ref id="CR39">
<mixed-citation publication-type="other">Power R, Robinson B, Ratcliffe D (2013) Finding fires with twitter. In: Australasian language technology association workshop, p 80</mixed-citation>
</ref>
<ref id="CR40">
<mixed-citation publication-type="other">Quinlan JR (1993) C4.5: Programs for machine learning, vol 1. Morgan kaufmann, San Francisco</mixed-citation>
</ref>
<ref id="CR41">
<mixed-citation publication-type="other">Robinson B, Power R, Cameron M (2013) A sensitive twitter earthquake detector. In: Proceedings of the 22nd international conference on world wide web companion, pp. 999–1002. International World Wide Web Conferences Steering Committee</mixed-citation>
</ref>
<ref id="CR42">
<mixed-citation publication-type="other">Rosi A, Mamei M, Zambonelli F, Dobson S, Stevenson G, Ye J (2011) Social sensors and pervasive services: approaches and perspectives. In: 2011 IEEE international conference on pervasive computing and communications workshops (PERCOM Workshops), pp 525–530. IEEE</mixed-citation>
</ref>
<ref id="CR43">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sakai</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Tamura</surname>
<given-names>K</given-names>
</name>
</person-group>
<article-title>Real-time analysis application for identifying bursty local areas related to emergency topics</article-title>
<source>SpringerPlus</source>
<year>2015</year>
<volume>4</volume>
<issue>1</issue>
<fpage>1</fpage>
<lpage>17</lpage>
<pub-id pub-id-type="doi">10.1186/2193-1801-4-1</pub-id>
<pub-id pub-id-type="pmid">25674489</pub-id>
</element-citation>
</ref>
<ref id="CR44">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sakaki</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Okazaki</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Matsuo</surname>
<given-names>Y</given-names>
</name>
</person-group>
<article-title>Tweet analysis for real-time event detection and earthquake reporting system development</article-title>
<source>IEEE Trans Knowl Data Eng</source>
<year>2013</year>
<volume>25</volume>
<issue>4</issue>
<fpage>919</fpage>
<lpage>931</lpage>
<pub-id pub-id-type="doi">10.1109/TKDE.2012.29</pub-id>
</element-citation>
</ref>
<ref id="CR45">
<mixed-citation publication-type="other">Sakaki T, Okazaki M, Matsuo Y (2010) Earthquake shakes twitter users: real-time event detection by social sensors. In: Proceedings of the 19th international conference on world wide web, pp. 851–860. ACM</mixed-citation>
</ref>
<ref id="CR46">
<mixed-citation publication-type="other">Salfinger A, Retschitzegger W, Schwinger W, et al (2015) crowdSA–towards adaptive and situation-driven crowd-sensing for disaster situation awareness. In: IEEE international inter-disciplinary conference on cognitive methods in situation awareness and decision support (CogSIMA), 2015, pp 14–20. IEEE</mixed-citation>
</ref>
<ref id="CR47">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sheth</surname>
<given-names>A</given-names>
</name>
</person-group>
<article-title>Citizen sensing, social signals, and enriching human experience</article-title>
<source>IEEE Internet Comput</source>
<year>2009</year>
<volume>13</volume>
<issue>4</issue>
<fpage>87</fpage>
<lpage>92</lpage>
<pub-id pub-id-type="doi">10.1109/MIC.2009.77</pub-id>
</element-citation>
</ref>
<ref id="CR48">
<mixed-citation publication-type="other">Siegemund K, Thomas EJ, Zhao Y, Pan J, Assmann U (2011) Towards ontology-driven requirements engineering. In: Workshop on semantic web enabled software engineering at 10th international semantic web conference (ISWC)</mixed-citation>
</ref>
<ref id="CR49">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Srivastava</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Abdelzaher</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Szymanski</surname>
<given-names>B</given-names>
</name>
</person-group>
<article-title>Human-centric sensing</article-title>
<source>Philos Trans R Soc A Math Phys Eng Sci</source>
<year>2012</year>
<volume>370</volume>
<issue>1958</issue>
<fpage>176</fpage>
<lpage>197</lpage>
<pub-id pub-id-type="doi">10.1098/rsta.2011.0244</pub-id>
</element-citation>
</ref>
<ref id="CR50">
<mixed-citation publication-type="other">Wang D, Amin MT, Li S, Abdelzaher T, Kaplan L, Gu S, Pan C, Liu H, Aggarwal CC, Ganti R et al (2014) Using humans as sensors: an estimation-theoretic perspective. In: Proceedings of the 13th international symposium on information processing in sensor networks, pp 35–46. IEEE Press</mixed-citation>
</ref>
<ref id="CR51">
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yin</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Lampert</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Cameron</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Robinson</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Power</surname>
<given-names>R</given-names>
</name>
</person-group>
<article-title>Using social media to enhance emergency situation awareness</article-title>
<source>IEEE Intell Syst</source>
<year>2012</year>
<volume>27</volume>
<issue>6</issue>
<fpage>52</fpage>
<lpage>59</lpage>
<pub-id pub-id-type="doi">10.1109/MIS.2012.6</pub-id>
</element-citation>
</ref>
<ref id="CR52">
<mixed-citation publication-type="other">Zhang X, Shasha D (2006) Better burst detection. In: Proceedings of the 22nd international conference on data engineering, 2006. ICDE’06, pp 146–146. IEEE</mixed-citation>
</ref>
<ref id="CR53">
<mixed-citation publication-type="other">Zhou A, Qian W, Ma H (2012) Social media data analysis for revealing collective behaviors. In: Proceedings of the 18th ACM SIGKDD international conference on knowledge discovery and data mining, pp 1402–1402. ACM</mixed-citation>
</ref>
</ref-list>
</back>
</pmc>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/TelematiV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000135  | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 000135  | SxmlIndent | more

Pour mettre un lien sur cette page dans le réseau Wicri

{{Explor lien
   |wiki=    Ticri/CIDE
   |area=    TelematiV1
   |flux=    Pmc
   |étape=   Corpus
   |type=    RBID
   |clé=     
   |texte=   
}}

Wicri

This area was generated with Dilib version V0.6.31.
Data generation: Thu Nov 2 16:09:04 2017. Site generation: Sun Mar 10 16:42:28 2024