63
The Humanitarian OpenStreetMap Team, Crowdsourcing for Disaster and Humanitarian Response @hotosm

Crowd-sourcing for Disaster Response Through OpenStreetMap

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Crowd-sourcing for Disaster Response Through OpenStreetMap

The  Humanitarian  OpenStreetMap  Team,  Crowdsourcing  for  Disaster  and  Humanitarian  

Response  

@hotosm  

Page 2: Crowd-sourcing for Disaster Response Through OpenStreetMap

What  is  OpenStreetMap?  

A web project to create a free and open map of the entire world  

Page 3: Crowd-sourcing for Disaster Response Through OpenStreetMap

History  

*  Founded  in  the  United  Kingdom  in  2004  by  Steve  Coast  *  Ordnance  Survey  Data  was  Expensive  to  Use  *  July  2005  the  First  Mapping  Party  Takes  Place    

Page 4: Crowd-sourcing for Disaster Response Through OpenStreetMap

Why  do  we  need  a  free  world  map?  

Page 5: Crowd-sourcing for Disaster Response Through OpenStreetMap

Why  do  we  need  a  Humanitarian  OpenStreetMap  Team?  

Page 6: Crowd-sourcing for Disaster Response Through OpenStreetMap

What is the Humanitarian OpenStreetMap Team?

An organization working to promote the use of open data and volunteered geographic information within the humanitarian and development contexts

Page 7: Crowd-sourcing for Disaster Response Through OpenStreetMap

http://vimeo.com/9182869

Port-au-Prince

28 Days Later

Before

OSM and Crisis Response in Haiti

Page 8: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 9: Crowd-sourcing for Disaster Response Through OpenStreetMap

High level imagery timely released under an “attribution only” license

Google//GeoEye  DigitalGlobe  World  Bank  (ImageCAT  GFDRR),  SpotImage  CIA  

Raw imagery processed into tiles to be made available in OSM editors (potlatch, merkator & josm) Hundreds traced 24/7 over base map features, humanitarian features (camps) & also damages Incentive for sharing restricted vector data sets Foster quality of field collection activities

Page 10: Crowd-sourcing for Disaster Response Through OpenStreetMap

Database import compatible with OSM license (CC-SA. OdbL).

PREPAREDNESS : only public domain data from UNJLC/LogCluster deployment Sept/Oct 2008 Cyclone Response- Haiti REPONSE: Base map layers (MINUSTAH/ CNIGS), Health Facility (PAHO), Haiti damage assessment: ITHACA & UNOSAT….

Page 11: Crowd-sourcing for Disaster Response Through OpenStreetMap

Community

640 mappers 24/7 month Capacity building to other VCT through crisis camp; marginal

Page 12: Crowd-sourcing for Disaster Response Through OpenStreetMap

Coordination ** Advise using OSM ** Plan training/ surveys

Page 13: Crowd-sourcing for Disaster Response Through OpenStreetMap

Training-

Page 14: Crowd-sourcing for Disaster Response Through OpenStreetMap

Surveying

Page 15: Crowd-sourcing for Disaster Response Through OpenStreetMap

Editing with JOSM

Page 16: Crowd-sourcing for Disaster Response Through OpenStreetMap

Training/ Surveys and Community Building Haiti - Gonaives

Page 17: Crowd-sourcing for Disaster Response Through OpenStreetMap

Support materials HOT Hardware kit, / OSM Kit / Guides/ Training

Page 18: Crowd-sourcing for Disaster Response Through OpenStreetMap

Communaute OpenStreetMap Haiti (COSMHA)

Page 19: Crowd-sourcing for Disaster Response Through OpenStreetMap

HOT/COSMHA & International Organization of Migration (IOM)

WMS: http://haiti.dbsgeo.com/wms/

Page 20: Crowd-sourcing for Disaster Response Through OpenStreetMap

Hurricane shelter and exposure mapping

Page 21: Crowd-sourcing for Disaster Response Through OpenStreetMap

Baseline mapping and capacity building in Saint Marc

Page 22: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 23: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 24: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 25: Crowd-sourcing for Disaster Response Through OpenStreetMap

Tap Tap Map

Page 26: Crowd-sourcing for Disaster Response Through OpenStreetMap

Soley Leve

Page 27: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 28: Crowd-sourcing for Disaster Response Through OpenStreetMap

hWps://github.com/AIFDR/inasafe  

Page 29: Crowd-sourcing for Disaster Response Through OpenStreetMap

How  to  get  data?    

Page 30: Crowd-sourcing for Disaster Response Through OpenStreetMap

Helping  Groups  Already  Mapping  

Page 31: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 32: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 33: Crowd-sourcing for Disaster Response Through OpenStreetMap

Mapping  2  Villages  in  a  week,    with  and  without  Imagery    

Page 34: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 35: Crowd-sourcing for Disaster Response Through OpenStreetMap

Mapping  with  Imagery  

Page 36: Crowd-sourcing for Disaster Response Through OpenStreetMap

With  GPS  

Page 37: Crowd-sourcing for Disaster Response Through OpenStreetMap

What  if  Some  of  the  Data  Needs  to  be  private  

 CC-­‐BY  Ka^e  Tegtmeyer  

What  if  some  of  the  data  needs  to  be  private?  

Page 38: Crowd-sourcing for Disaster Response Through OpenStreetMap

Each  has  a  Unique  Iden^fier  

Page 39: Crowd-sourcing for Disaster Response Through OpenStreetMap

hWps://github.com/geofabrik/sds-­‐server  

Page 40: Crowd-sourcing for Disaster Response Through OpenStreetMap

Other  results  we  could  not  have  guessed!  

Page 41: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 42: Crowd-sourcing for Disaster Response Through OpenStreetMap

Con^nuing  to  Make  the  Technology  Their  Own  

Page 43: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 44: Crowd-sourcing for Disaster Response Through OpenStreetMap

hWp://kompe^siosm.org/  

Page 45: Crowd-sourcing for Disaster Response Through OpenStreetMap

!

!"#$%#&'()*+,-%$&-*

.&&/'0%&,*!"#$%#&'()*12#-,3*()*+,#$*4(/$3*5()3'&'()6*78(/,*(9*:;:*<,#)-*:8(//,8&:=*

>?,)7&/,,&@#?*A,#&%/,*.&&/'0%&,*

7B#?,*8(<?#/'-()*

Page 46: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 47: Crowd-sourcing for Disaster Response Through OpenStreetMap

Na^onal  Disaster  Management  Agency  (BNPB)  Regional  Disaster  Management  Agency  (BPBD)  United  Na^ons  Office  for  Coordina^on  of  Humanitarian  Affairs  World  Bank  AusAID  –  Australia-­‐Indonesia  Facility  for  Disaster  Reduc^on  Humanitarian  OpenStreetMap  Team  University  of  Indonesia  

Page 48: Crowd-sourcing for Disaster Response Through OpenStreetMap

267  Villages  3  Maps  for  Each  Village  Lots  and  lots  of  prinCng…  Lots  and  lots  of  students  

Page 49: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 50: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 51: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 52: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 53: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 54: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 55: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 56: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 57: Crowd-sourcing for Disaster Response Through OpenStreetMap
Page 58: Crowd-sourcing for Disaster Response Through OpenStreetMap

Impor^ng  of  Data  and  Tracing  of  Satellite  Imagery  for  Somalia  

Page 59: Crowd-sourcing for Disaster Response Through OpenStreetMap

Samoa  Simula^on  

Page 60: Crowd-sourcing for Disaster Response Through OpenStreetMap

Responders  

Page 61: Crowd-sourcing for Disaster Response Through OpenStreetMap

Victory

Page 62: Crowd-sourcing for Disaster Response Through OpenStreetMap

EQ 8.4 in Sumatra @ 1336 GMT!

Humanitarian OpenStreetMap

Team (HOT) requests imagery

from Broker!

LFA requests that HOT create vectors for post-EQ imagery and

damage, IDs key AOIs !

USG requests satellite vendors for imagery

under NextView

license!

DG and GeoEye collect imagery of

affected AOI !

OSM HOT mobilizes volunteers for a

mapping sprint for

30 days.!

or!

Broker and LFA conduct flash review

with OSM and UNOSAT, evalates

percent completion.!

OSM mobilizes volunteers for a

mapping sprint for additional 30 days, focus on key gaps

identified by USG.!

HOT to identify TTPs!

NGA releases raw NextView imagery to UNOSAT and LFA via

storefront !

UNOSAT releases imagery on restricted WMS feed to OSM

and other VTCs !

UNOSAT processes

raw imagery !

Broker ensures

request is valid !

LFA evaluates requests against VTC

criteria!

Broker forwards

request to LFA!

LFA forwards request

to NGA!

NGA evaluates LFA's request against

internal criteria !

OSM releases vectors for AOI as a serivce

with documented API.!

USG exercises option to extend NextView

for 30 days.!

LFA and NGA update USG maps based on

OSM services.!

Broker, NGA and LFA conducts AAR with UNOSAT and OSM, incorporates lessons learned into process, and !

certifies compliance with license terms.!

UNOSAT closes restricted WMS to

disaster AOI.!

Broker creates archive of imagery and

vectors and publishes to LFA, open to

analytic and academic

study by request?!

VTC!Request!Schema!

1. Supported!Operation!

2. Geographic!Bounds!

3. Temporal!Bounds!

4. Reason!for!Use. What analytical problem needs to

be solved?!

5. License!for!derived!

works. Will the data be a

public or orivste good?!

6. Partners. Who will

benefit?!

7. Objective: how will the

data be used to do what!

VTC!Request!Evaluation!

Criteria!

1. Goverment Interest. Is the request in the interest of the

USG?!2. Gap. What information

gap will be filled?!3. Trust. Does the USG trust

this VTC with data?!4. Host nation. Does the host nation have issues with

release of data?!5. ROI on data preparation. What return will the USG have on allocating staff time to preparing the data for

release?!6. Sensitivity and human protection. Does the release of the data have real

potential to cause harm?!7. Licensing. What IP license will the data be under? Will it be a public good or will it primarily benefit a private

entity?!

8. Operational security!

Draft Imagery Release Process from USG Lead Federal Agencies to VTCs under the NEXTVIEW License !

OSM certfies that vectors are available

for all secondary uses, including commercial

use.!

remand!

remand!

remand!

NGA receives imagery from DG and/or

GeoEye!

VTC!Request!Schema!

1. Supported!Operation!

2. Geographic!Bounds!

3. Temporal!Bounds!

4. Reason!for!Use. What analytical problem needs to

be solved?!

5. License!for!derived!

works. Will the data be a

public or orivste good?!

6. Partners. Who will

benefit?!

7. Objective: how will the

data be used to do what!

Draft Workflow for Satellite Imagery and OSM Data

Page 63: Crowd-sourcing for Disaster Response Through OpenStreetMap

Ques^ons?  

@hotosm