1. The Presentation…
> The Role of Location in Incident and
Disaster Management
Erik van der Zee
Geodan Amsterdam
Multi-POS Winter School Tuesday
11th Februari 2014 16:30-17:45
2. The Dream Team…
> T2.4 Location integration in crisis management lifecycle
Erik van der Zee
PhD Researcher (part time)
Multi-POS Supervisor
Geodan / VU Amsterdam
e2.vander.zee@vu.nl
Luis Bausá López
PhD Researcher (full time)
VU Amsterdam
luis.bausalopez@vu.nl
3. About Geodan
>
>
>
>
>
>
Geo-IT specialist for more than 25 years
Independent system integrator in GIS and Geo-ICT
Founded by Prof. Dr. Henk Scholten and Dr. Evert Meijer
Highly innovative (large R&D dep.)
130 employees
Offices in
• Amsterdam
• Den Bosch
• Madrid
> OGC member
> Associated partner in Multi-POS
> Website www.geodan.nl
5. The Topics…
1.
2.
3.
4.
5.
6.
7.
8.
Overview of Disaster Types
Spatial aspects of Disasters
Positioning people and objects during Disasters
Disaster Management
• Key players (in the field and in the crisis center)
• ICT Challenges (internet connections)
Common Operational Picture and Situational Awareness
Technology behind a Common Operational Picture
Disaster Management in smart(er) environments
Conclusions
16. Natural Disasters
17. Extreme weather
(cold/warm/wet/dry)
e.g. heavy storm, extreme
(ice) rain or snow or a heat
or cold wave
18. Disasters at
distance
(in neighboring
countries which have
an effect on our
country, e.g. nuclear,
floods, forest fire,
etc.)
18. From Indicent… to Disaster…
> Relation between scale (extent/severity) and involved parties
19. Where are the risks…
> Risk Map of The Netherlands…
• Location of Risk generators (dangerous objects or areas)
• Risk distance zones (10^-6)
• Effect distance zones (m) Lethality
• Locations of Risk receivers (vulnerable objects or areas)
> www.risicokaart.nl
20. Source Area vs Effect Area
> “Gasmal” and “Sector mal” (danger zones)
26. The Challenge…
> Can a position be determined? Indoor and Outdoor
for different disaster types?
> Which positional accuracy is needed and what
can be delivered technically (demand and supply)?
• Sometimes a rough indication of position is enough,
sometimes not (e.g. Prison LBS Use Case… in or out
the geofence, Room A is GO area Room B nextdoor
is NOGO area)
• It really depends on the situation (type of disaster
and use case scenario) and the technology used
51. COW works cross domain
User
Interface
COW client
Service
API
Intranet
API
User
Interface
COW client
Service
API
API
User
Interface
COW client
Service
API
Internet
API
User
Interface
COW client
Service
API
API
52. Demo COW
DEMO COW Luis + Erik
(or be a crisis manager yourself ...
http://research.geodan.nl/sites/foss4g)
(COW on GitHub http://github.com/Geodan/cow)
61. Conclusions
> Disaster happen everywhere, indoor AND outdoor
positioning scenarios
> …And under difficult conditions, special demands on
equipment
> Communication lines and connections can be severely
disturbed in DM situations, alternatives needed (plan B…) or
local caching
> There are mono- and multi-disciplinary disasters
> A Common Operation Picture improves the Situational
Awareness, especially in multi-disciplinary situations
> There are 2 types of IT architectures to create a COP, the
central model and the distributed (P2P) model