PAGE 1

Vassilis Tsironis | MYGEOSS Second Call for Innovative Apps | June 15, 2016

User Manual DOCUMENTATION ON HOW TO USE DISASTERHUB APP

PAGE 2

Contents

List of Figures................................................................................................................................................. 3

Introduction .................................................................................................................................................. 4

Sign In / Sign Up .......................................................................................................................................... 4

Sign In ......................................................................................................................................................... 5

Sign UP ....................................................................................................................................................... 5

View Events ................................................................................................................................................... 6

Send a Geotag ............................................................................................................................................... 8

View a specific Event ................................................................................................................................... 12

Example of crowd generated event........................................................................................................ 12

Example of EO generated event ............................................................................................................. 14

Annex A ........................................................................................................................................................ 17

PAGE 3

List of Figures

Figure 1: The most basics tools & frameworks used by DisasterHub. ..................................................... 4

Figure 2: On the left the Sign In screen, on the right the Sign Up screen. .............................................. 5

Figure 3: The main screen showing a near real-time feed of events and basic information about

these. .............................................................................................................................................................. 6

Figure 4: Screen showing the slide menu of the main screen with the available filter options. ........... 7

Figure 5: The geotagging screen showing the GPS retrieval. ................................................................... 8

Figure 6: The geotagging screen with the steps needed to create a geotag. From left to right you

can see that the procedure needs only three steps: 1) place marker to the required location on the

map, 2) click on the tick button of the footer; note that in the footer you can also see the

coordinates of the geotagging marker’s location and 3) select the hazard from the action sheet that

appears........................................................................................................................................................... 9

Figure 7: The post screen of the geotagging mechanism showing the various UI elements. .............. 10

Figure 8: From left to right and from top to bottom the complementary functionalities of the

geotagging mechanism are shown. Top-left GPS retrieval button along with layer management

buttons. Top-right management popover panel for base layers. Bottom-left management popover

panel for overlay layers. Bottom-right geotagging map with OSM as base layer and Natura 2000

overlay enabled. ............................................................................................................................................ 11

Figure 9: The event screen depicting a forest fire. ................................................................................... 12

Figure 10: The event screen showing a user geotag that indicates a forest fire. On the left the event

screen and on the right the event with the popover pane showing the more options. ...................... 13

Figure 11: The event screen showing the result of the more options that are related with a crowd

generated event. On the left the event screen showing the geotags that are related with the current

geotag. On the right the event screen showing a fire polygon detected through a polar-orbiting

satellite that is related with the current geotag. ...................................................................................... 14

Figure 12: The event screen showing a fire polygon detected from SEVIRI. On the left the event

screen and on the right the event with the popover pane showing the more options. ...................... 15

Figure 13: From left to right and from top to bottom the event screen showing relative events

with forest fire event fe2635. Top-left the refined SEVIRI fire polygons of event fe2635. Top-right

the refined SEVIRI fire polygons along with fire polygons detected from polar-orbiting satellites.

Bottom-left the fire polygons detected from the satellites along with user geotags. Bottom-right

the fire polygons detected from the satellites, the user geotags and the Natura 2000 layer enabled

showing that this forest fire threatens a natural habitat. ........................................................................ 16

PAGE 4

Introduction

DisasterHub is a mobile app that aspires to enable the fusion of crowd generated data

(Crowdsourcing) with data acquired from Earth Observation (EO).

Development started on February, 2016 as part of the MYGEOSS Second Call For Innovative Apps in

the environmental and social domains (http://digitalearthlab.jrc.ec.europa.eu/mygeoss/call.cfm)

and now a first release is available through MYGEOSS.

It is entirely built on top of open source tools and frameworks (see Figure 1 below) and uses only

data that share the GEOSS Data Sharing Principles

(https://www.earthobservations.org/geoss_dsp.shtml), along with data gathered from its users (see

Annex A).

Figure 1: The most basics tools & frameworks used by DisasterHub.

So, DisasterHub provides its users with two main functionalities:

1. View hazardous events, as these were generated from EO services1 or other users (i.e.

Crowdsourcing),

2. Send a geotag indicating a hazardous event.

In the next sections and through a step-by-step approach, the user will get a clear picture of how to

use DisasterHub app. What follows are the Sign In / Sign Up sections which show the necessary

steps for a user to gain access to the main functionalities of DisasterHub.

Sign In / Sign Up

When a user starts DisasterHub for a first time, then she sees a screen with two tabs. In the first tab

the user is asked for username and password in order to sign in the app, whereas in the second tab

the user is able to sign up the app by sending the necessary information (see Figure 2 below).

1 Currently only one EO service is integrated in DisasterHub, the FireHub service which is a service that provides near real-time monitoring of forest fires over the region of Greece.

PAGE 5

Figure 2: On the left the Sign In screen, on the right the Sign Up screen.

SIGN IN

In order to sign in DisasterHub you have to provide information about two fields: username and

password.

The procedure is easy. DisasterHub is trying to validate you through the Authentication service

implemented through the AuthO broker (https://auth0.com/) and if the procedure is successful

you will be redirected to the main screen of the app, otherwise you will receive an error message.

SIGN UP

In order to sign up DisasterHub you have to provide information about three fields: email,

username and password.

Then DisasterHub records the information given in two places: in the Authentication service that is

implemented with the AuthO broker and in a backup database server installed in the premises of

National Observatory of Athens (NOA).

In the next section the main screen of the app is described along with the information that provides

to its users at first glance.

PAGE 6

View Events

In the main screen of DisasterHub, the users get a near real-time feed of events either generated

from EO services or Crowdsourcing (see Figure 3 below). These events concern one of the following

hazards: Earthquake, Flood, Forest Fire, Heat Wave and Smoke Plume.

Currently only one EO service is integrated in DisasterHub, the FireHub service

(http://195.251.203.238/seviri/), which is a near real-time space based monitoring Web GIS platform

that is fully operational nowadays in the region of Greece since it is being used by the Fire Service

and Civil Authorities of Greece, and is also winner of the 2014 Best Service Challenge award

(http://www.copernicus-

masters.com/index.php?kat=winners.html&anzeige=winner_bsc2014.html). FireHub is using a

multitude of satellites, geostationary and polar-orbiting, and further processing chains in order to

provide its users with accurate information of high spatial resolution about forest fires.

So, the feed of events that a user gets in the main screen is comprised of forest fire events in the

region of Greece generated through FireHub, as well as events generated through DisasterHub and

Crowdsourcing concerning the aforementioned hazards and the globe as a whole.

Figure 3: The main screen showing a near real-time feed of events and basic information about these.

The feed of events is being refreshed every one minute, but the user can force its refresh by pulling

from the top of the main screen. The user can also load more events though scrolling on the

Illustrative icon of

the hazard

Creation Date & time

of the event

Information about the user or the

sensor (e.g. satellite instrument)

that created the event

Basic information (at a first

glance) about the event

This is the

geotagging button

PAGE 7

bottom of the main screen. DisasterHub is using an infinite scroll approach in which the events are

sorted by date & time in descending order so as the user to see first the latest events and through

the loading more feature to get the older ones.

Another important feature in the main screen is the slide menu, that offers the user some very

useful options, such as: (i) sign out from the app, (ii) read information about DisasterHub, and the

most important (iii) filter the feed of events according to her needs (see Figure 4 below). In the 3rd

option the user can filter the events based on the type of observation (i.e. events generated

through Earth Observation or Crowdsourcing) and on the type of hazard (i.e. events that concern

Earthquakes, or events that concern Floods, etc.).

Figure 4: Screen showing the slide menu of the main screen with the available filter options.

Finally, if a user wants to view information about a specific event and how is this event related with

other events, then she has to choose one of them through the main screen’s feed and the app will

navigate her to the event screen. However, if she wants to send her own geotag indicating a new

hazardous event, then she has to click on the button which is the bottom right corner of the main

screen (see Figure 3 above).

The next section describes the first of the basic functionalities of DisasterHub, which is the hazard

geotagging or how a user can send a geotag indicating a geolocation stricken from a hazardous

event.

Filter events according to

observation type

Filter events according to hazard

PAGE 8

Send a Geotag

It is already mentioned that in order for a user to send a geotag, she has to click on the geotagging

button found in the bottom right corner of the main screen of DisasterHub (see Figure 3 above).

Then the user will be navigated to the next screen that contains a map built with OpenLayers 3 and

will see a message that informs her about the app trying to retrieve her GPS location if not retrieved

yet. If her GPS location is successfully retrieved she will see a pulsing, blue marker on the map, and

at the bottom of the screen a footer that contains the coordinates of her current location in

hemisphere, degrees, minutes, and seconds (HDMS) format along with a tick button (see Figure 5

below).

Figure 5: The geotagging screen showing the GPS retrieval.

In order for a user to send a geotag she has to interact with the map, namely to zoom or move

the map to the location that she wants to place the geotag. In that case a geotag marker anchored

to the center of the map will appear and the user will have to move the map in a manner that will

allow the marker to match the required geotag location. Note that the coordinates at the footer of

the screen will change in every interaction with the map, indicating the location of the geotag

marker (see Figure 6 below). If the user is confident that the geotag marker is placed to the correct

location, then she can click on the tick button of the footer. In that case an action sheet will appear

where the user can select the hazard (see Figure 6 below).

The blue pulsing marker showing

user’s current geolocation

The footer containing the

coordinates of user’s

current geolocation along

with the tick button

PAGE 9

Figure 6: The geotagging screen with the steps needed to create a geotag. From left to right you can see that the procedure needs only three steps: 1) place marker to the required location on the map, 2) click on the tick button of the footer; note that in the footer you can also see the coordinates of

the geotagging marker’s location and 3) select the hazard from the action sheet that appears.

PAGE 10

By selecting the indicatory hazard of the geotag, the user is navigated to the post screen of the app

where she can either complete the geotagging by clicking on the Post Geotag button or attach a

short text information that better describes the geotag and/or a photo and then post the geotag to

DisasterHub’s server capacity using the Server Side API that was built for these purposes (see

Figure 7 below).

Figure 7: The post screen of the geotagging mechanism showing the various UI elements.

If the geotag is successfully posted in DisasterHub’s server capacity, then a message indicating the

success will be shown in the user and the app will automatically navigate her to the previous screen

with the map centered to the marker of the geotag that was just ingested by the DisasterHub

system. The user can continue to send other geotags following the same procedure as described in

the previous lines.

The figure below (Figure 8) show some complementary functionalities that were not described yet

but they are provided to the user during the geotagging procedure, such as managing the base and

overlay layers or forcing the retrieval of GPS location.

In the next section the other basic functionality of DisasterHub will be described, namely the

mechanism of viewing information about a specific event and its relation (if any) with other events.

Send a photo that portrays the

hazard. Don’t forget: “one

picture worth a thousand words”

Basic information of the

geotag, such as: hazard,

creation date, geotag

location, user location.

Add a short text info giving

important information to

those that are going to act

(e.g. fire brigades)

Click on this button to

complete geotagging

PAGE 11

Figure 8: From left to right and from top to bottom the complementary functionalities of the geotagging mechanism are shown. Top-left GPS retrieval button along with layer management

buttons. Top-right management popover panel for base layers. Bottom-left management popover panel for overlay layers. Bottom-right geotagging map with OSM as base layer and Natura 2000

overlay enabled.

This button forces

GPS location retrieval.

These buttons allow the user

to manage the base and

overlay layers used by the app.

PAGE 12

View a specific Event

The user can view information about a specific event. In order to do that she has to go to the main

screen of DisasterHub where she can view the near real-time feed of events and click on that

specific event that she wants to view its information. The app will then navigate her to the event

screen, in which she can view basic information about that event or through the More Options

button she can further investigate its relation to other events (see Figure 9 below).

Figure 9: The event screen depicting a forest fire.

- So, how is the more options functionality of the event view mechanism used and what is

the outcome of this?

This question will be answered in the next lines through easy to understand examples that show

how can we relate an event generated through Earth Observation with an event generated through

Crowdsourcing.

EXAMPLE OF CROWD GENERATED EVENT

For the purposes of the current example the event with id g508 that concerns a Forest Fire will be

used. The following figure (Figure 10) shows how this event will appear to a DisasterHub user if she

chooses to view it and what are the more options:

The more options button.

The same buttons with

those in geotagging screen

that allow the user to

manage the map layers.

The fire polygons as detected

in the current event from the

SEVIRI instrument of the

MSG-2 satellite.

This button enables a

modal pane that shows the

basic event information.

PAGE 13

Figure 10: The event screen showing a user geotag that indicates a forest fire. On the left the event screen and on the right the event with the popover pane showing the more options.

So, the user can check if there are any fire polygons detected from the SEVIRI instrument of the

MSG-2 satellite (either RAW or Refined) that can be related with the current geotag, as well as fire

polygons detected from the respective instruments of Polar-Orbiting Weather satellites (such as

Aqua and Terra MODIS, NPP VISS, NOAA 18 and NOAA 19 AVHRR) and geotags from other users.

- But how does DisasterHub defines the relation between a user geotag and other geotags or

events generated from EO observations (e.g. space borne observations)?

The approach is simple. DisasterHub relates two geotags if these geotags satisfy three criteria:

1. Indicate the same hazard,

2. Are within a distance of 10 kilometers,

3. Are within a time interval of 12 hours

The same approach applies between a geotag and the fire polygons detected from a satellite. The

geotag must satisfy the following criteria:

1. Indicate a forest fire,

2. Is within a distance of 1000 meters from the fire polygons,

PAGE 14

3. Is within a time interval that begins 12 hours before the first fire polygon that was detected

from the satellite and ends 12 hours after the last fire polygon that was detected from the

satellite

In the figure below (Figure 11) is demonstrated the clear relation between geotag g508 and other

geotags as well as fire polygons detected from polar-orbiting satellites23.

Figure 11: The event screen showing the result of the more options that are related with a crowd generated event. On the left the event screen showing the geotags that are related with the current

geotag. On the right the event screen showing a fire polygon detected through a polar-orbiting satellite that is related with the current geotag.

Vice versa if the user chooses to view one of the other geotags or the fire event that was generated

from the polar-orbiting satellites will confirm the same relation with the current geotag.

EXAMPLE OF EO GENERATED EVENT

This example will demonstrate how a user can view an EO generated event, but most importantly

its relation with other events either EO or crowd generated.

2 There was not any observation from the SEVIRI instrument of the MSG-2 satellite, so Seviri Raw and Seviri Refined options returned nothing. 3 Of course the user can view at the same time both the relative fire polygons detected from polar-orbiting satellites and the relative geotags sent by other users.

PAGE 15

For this example, a forest fire event detected from the SEVIRI instrument of MSG-2 satellite will be

used. The following figure (Figure 12) shows how this event will appear to a DisasterHub user if she

chooses to view it and what are the more options:

Figure 12: The event screen showing a fire polygon detected from SEVIRI. On the left the event screen and on the right the event with the popover pane showing the more options.

The approach here is the same with the one described in the previous example. DisasterHub will

relate the above fire polygon detected from SEVIRI with any fire polygons detected from polar-

orbiting satellites and geotags sent by the DisasterHub users.

The next figure (Figure 13) exhibits the relation of the current event (forest fire fe2635) with other

events and how is this going to appear in event screen.

PAGE 16

Figure 13: From left to right and from top to bottom the event screen showing relative events with forest fire event fe2635. Top-left the refined SEVIRI fire polygons of event fe2635. Top-right the

refined SEVIRI fire polygons along with fire polygons detected from polar-orbiting satellites. Bottom-left the fire polygons detected from the satellites along with user geotags. Bottom-right the fire

polygons detected from the satellites, the user geotags and the Natura 2000 layer enabled showing that this forest fire threatens a natural habitat.

PAGE 17

Annex A

In this annex are going to be described the datasets that are used from DisasterHub either as layers or not, and are fully available and open

through the URLs provided in the table below.

Νο.

Title URL Description

1 EKXA VLSO http://gis.ktimanet.gr/wms/wmsopen/wmsserver.aspx High Resolution Aerial Images of the Hellenic National Cadaster Services that cover the land surface of Greece.

2 MapQuest sat https://otile{1-4}-s.mqcdn.com/tiles/1.0.0/sat/{z}/{x}/{y}.jpg MapQuest satellites images fully available from the MapQuest tile server.

3 OSM standard https://{a-c}.tile.openstreetmap.org/{z}/{x}/{y}.png OpenStreeMap standard style map fully available from the OSM tile server.

4 Toponyms http://195.251.203.242:8888/v2/admin_over/{z}/{x}/{y}.png Dataset with the toponyms of Greece fully accessible from the tile server of NOA.

5 Corine Land Cover 2000

http://195.251.203.242:8888/v2/clc_00/{z}/{x}/{y}.png The Corine Land Cover 2000 dataset for the region of Greece fully accessible from the tile server of NOA.

6 Natura 2000 http://195.251.203.238:8080/geoserver/firehub/wms?service=WMS&version=1.1.0&request=GetMap&layers=firehub:natura2000_view&styles=&bbox=2154252.83658552,4136560.77103287,3300206.77041457,5123333.5559624&width=768&height=661&srs=EPSG:3857&format=application/openlayers

The Natura 2000 dataset for the region of Greece fully accessible from the GeoServer of NOA.

Notes: This layer is available through the GeoServer that is currently installed in the premises of National Observatory of Athens (NOA). The

output format is application/openlayers but you can change it to whatever format is supported from a WMS service (e.g. GeoTiff, JPEG, PNG,

etc.). You can also access this dataset using a WFS service. For example:

http://195.251.203.238:8080/geoserver/firehub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=firehub:natura2000_view&

maxFeatures=50&outputFormat=application%2Fjson

PAGE 18

7 Urban Atlas http://195.251.203.238:8080/geoserver/firehub/wms?service=

WMS&version=1.1.0&request=GetMap&layers=firehub:urban

atlas_view&styles=&bbox=2286676.1328035,4186107.58361465

,2824998.15496999,5032952.67090845&width=488&height=7

68&srs=EPSG:3857&format=application/openlayers

The Urban Atlas dataset for the region of Greece fully accessible from the GeoServer of NOA.

Notes: This layer is available through the GeoServer that is currently installed in the premises of National Observatory of Athens (NOA). The

output format is application/openlayers but you can change it to whatever format is supported from a WMS service (e.g. GeoTiff, JPEG, PNG,

etc.). You can also access this dataset using a WFS service. For example:

http://195.251.203.238:8080/geoserver/firehub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=firehub:urbanatlas_view&maxFeatures=50&outputFormat=application%2Fjson

8 SEVIRI Raw http://195.251.203.238:8080/geoserver/firehub/wms?service=

WMS&version=1.1.0&request=GetMap&layers=firehub:seviri

&styles=&bbox=2494215.78307072,4151161.02601186,3103932.5

3217261,4787200.69874927&width=736&height=768&srs=EPS

G:3857&format=application/openlayers

Raw Fire Polygons over the region of Greece as

detected from the SEVIRI instrument of the MSG-2

satellite.

Notes: This layer is available through the GeoServer that is currently installed in the premises of National Observatory of Athens (NOA). The

output format is application/openlayers but you can change it to whatever format is supported from a WMS service (e.g. GeoTiff, JPEG, PNG,

etc.). You can also access this dataset using a WFS service. For example:

http://195.251.203.238:8080/geoserver/firehub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=firehub:seviri&maxFeatures=50&outputFormat=application%2Fjson

This dataset is dynamic as it is updated every time that new fire polygons are being detected from the SEVIRI instrument.

It is also a parametrized dataset. If a user wants to view if any fire polygons were detected from the SEVIRI instrument in a specific timestamp, then she has to provide the WMS request with one more parameter, the viewparams that will contain the timestamp. For example, to get any fire polygons detected at 2015-06-08T21:00:15 the WMS request will be as follows:

http://195.251.203.238:8080/geoserver/firehub/wms?service=WMS&version=1.1.0&request=GetMap&layers=firehub:seviri&styles=&bbox=2494215.78307072,4151161.02601186,3103932.53217261,4787200.69874927&width=736&height=768&srs=EPSG:3857&format=application/openlayers&viewparams=this_date:%272015-06-08T21:00:15%27

PAGE 19

If the user does not provide any vieparams parameter in the WMS (or WFS) request, then GeoServer will generate a layer that will

contain the last detected raw fire polygons.

9 SEVIRI Refined http://195.251.203.238:8080/geoserver/firehub/wms?ser

vice=WMS&version=1.1.0&request=GetMap&layers=fire

hub:propagation&styles=&bbox=2494215.78307072,41511

61.02601186,3103932.53217261,4787200.69874927&width

=736&height=768&srs=EPSG:3857&format=application/

openlayers

Refined Fire Polygons over the region of Greece as

generated through the processing chains of the

FireHub service over the Raw fire polygons detected

from the SEVIRI instrument of the MSG-2 satellite

Notes: This layer is available through the GeoServer that is currently installed in the premises of National Observatory of Athens (NOA). The

output format is application/openlayers but you can change it to whatever format is supported from a WMS service (e.g. GeoTiff, JPEG, PNG,

etc.). You can also access this dataset using a WFS service. For example:

http://195.251.203.238:8080/geoserver/firehub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=firehub:propagation&maxFeatures=50&outputFormat=application%2Fjson

This dataset is dynamic as it is updated every time that new fire polygons are being detected from the SEVIRI instrument.

It is also a parametrized dataset. If a user wants to view if any fire polygons were detected from the SEVIRI instrument and refined through the FireHub service in a specific timestamp, then she has to provide the WMS request with one more parameter, the viewparams that will contain the timestamp. For example, to get any fire polygons detected at 2015-06-08T21:00:15 the WMS request will be as follows:

http://195.251.203.238:8080/geoserver/firehub/wms?service=WMS&version=1.1.0&request=GetMap&layers=firehub:propagation&styles=&bbox=2494215.78307072,4151161.02601186,3103932.53217261,4787200.69874927&width=736&height=768&srs=EPSG:3857&format=application/openlayers&viewparams=this_date:%272015-06-08T21:00:15%27

If the user does not provide any vieparams parameter in the WMS (or WFS) request, then GeoServer will generate a layer that will

contain the last generated refined fire polygons.

10 Polar-Orbiting

Refined

http://195.251.203.238:8080/geoserver/firehub/wms?servic

e=WMS&version=1.1.0&request=GetMap&layers=firehub:h

r_sat_refined&styles=&bbox=2494215.78307072,4151161.026

Refined Fire Polygons over the region of Greece as

detected from medium resolution Polar-Orbiting

satellites (EOS Aqua, EOS Terra, Suomi NPP, NOAA 18,

NOAA 19, MetOp-A, Metop-B) and acquired from the

PAGE 20

01186,3103932.53217261,4787200.69874927&width=736&hei

ght=768&srs=EPSG:3857&format=application/openlayers

ground station that is currently installed in the premises

of National Observatory of Athens (NOA).

Notes: This layer is available through the GeoServer that is currently installed in the premises of National Observatory of Athens (NOA). The

output format is application/openlayers but you can change it to whatever format is supported from a WMS service (e.g. GeoTiff, JPEG, PNG,

etc.). You can also access this dataset using a WFS service. For example:

http://195.251.203.238:8080/geoserver/firehub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=firehub:hr_sat_refined&maxFeatures=50&outputFormat=application%2Fjson

This dataset is dynamic as it is updated every time that new fire polygons are being detected from the instruments of the Polar-Orbiting satellites.

It is also a parametrized dataset. If a user wants to view if any fire polygons were detected from one or more satellites during a specific period of time, then she has to provide the WMS request with one more parameter, the viewparams that will contain the start and end dates of that period. For example, to get any fire polygons detected from 2015-06-08T21:00:15 to 2016-08-29T12:12:35 the WMS request will be as follows:

http://195.251.203.238:8080/geoserver/firehub/wms?service=WMS&version=1.1.0&request=GetMap&layers=firehub:hr_sat_refined&styles=&bbox=2494215.78307072,4151161.02601186,3103932.53217261,4787200.69874927&width=736&height=768&srs=EPSG:3857&format=application/openlayers&viewparams=start_date:%272015-06-08T21:00:15%27;end_date:%272016-08-29T12:12:35%27

If the user does not provide any vieparams parameter in the WMS (or WFS) request, then GeoServer will generate a layer that will

contain the last generated fire polygons.

11 Geotags http://195.251.203.238:8080/geoserver/firehub/ows?serv

ice=WFS&version=1.0.0&request=GetFeature&typeNam

e=firehub:geotags_view&maxFeatures=50&outputForm

at=application%2Fjson

Geotags posted from the users of the DisasterHub app

with information about locations stricken from one of the

following hazards: Earthquake, Flood, Forest Fire,

Heatwave and Smoke Plume.

Notes: This layer is available through the GeoServer that is currently installed in the premises of National Observatory of Athens (NOA). The

output format is application/json but you can change it to whatever format is supported from a WFS service (e.g. CSV, GML, etc.).

This dataset is dynamic as it is updated every time that a user posts a new geotag.

It is also a parametrized dataset. If a user wants to view if any geotags were posted through DisasterHub during a specific period of time, then she has to provide the WFS request with one more parameter, the viewparams that will contain the start and end dates of that period. For example, to receive any geotags posted from 2016-06-08T21:00:15 to 2016-06-29T12:12:35 the WFS request will be as follows:

PAGE 21

http://195.251.203.238:8080/geoserver/firehub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=firehub:geotags_view&maxF

eatures=50&outputFormat=application%2Fjson&viewparams=start_date:%272016-06-08T21:00:15%27;stop_date:%272016-06-29T12:12:35%27

12 Fires http://195.251.203.238:8080/geoserver/firehub/ows?serv

ice=WFS&version=1.0.0&request=GetFeature&typeNam

e=firehub:fires_view&maxFeatures=50&outputFormat=

application%2Fjson

Fires as generated through the FireHub service. FireHub

service groups the fire polygons that were detected from

the various satellites into discrete fire events through an

elaborate clustering process

Notes: This layer is available through the GeoServer that is currently installed in the premises of National Observatory of Athens (NOA). The

output format is application/json but you can change it to whatever format is supported from a WFS service (e.g. CSV, GML, etc.).

This dataset is dynamic as it is updated every time the FireHub service is ingesting fire polygons detected from the aforementioned satellites.

It is also a parametrized dataset. If a user wants to view if any fire events were generated from the FireHub service during a specific period of time, then she has to provide the WFS request with one more parameter, the viewparams that will contain the start and end dates of that period. For example, to view forest fires that occurred from 2016-06-08T21:00:15 to 2016-06-29T12:12:35 the WFS request will be as follows: http://195.251.203.238:8080/geoserver/firehub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=firehub:fires_view&maxFeat

ures=50&outputFormat=application%2Fjson&viewparams=start_date:%272016-06-08T21:00:15%27;stop_date:%272016-06-29T12:12:35%27

13 Events http://195.251.203.238:8080/geoserver/firehub/ows?serv

ice=WFS&version=1.0.0&request=GetFeature&typeNam

e=firehub:events_view&maxFeatures=50&outputForma

t=application%2Fjson

The events dataset as generated from the crow-generated

and EO generated data of DisasterHub.

Notes: This dataset is in fact a fusion of the fires_view (no. 12) and the geotags_view (no. 11) datasets. This dataset is not used as a layer in

the applications map. It actually provides the real time feed of events that the user gets in the main screen of DisasterHub, as well as the basic

information of each event; namely the information that every user would like to view instantly.

This dataset is dynamic as it is updated every time the FireHub service is generating a new fire event or a user sends a geotag.

It is also a parametrized dataset. If a user wants to view if any events were generated from the DisasterHub app during a specific period of time, then she has to provide the WFS request with one more parameter, the viewparams that will contain the start and end dates of that period. For example, to view events that generated from 2016-06-08T21:00:15 to 2016-06-29T12:12:35 the WFS request will be as follows:

PAGE 22

http://195.251.203.238:8080/geoserver/firehub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=firehub:events_view&maxFe

atures=50&outputFormat=application%2Fjson&viewparams=start_date:%272016-06-08T21:00:15%27;stop_date:%272016-06-29T12:12:35%27