130
Mapping a Disaster Anthony Baxter, Google [email protected]

Mapping A Disaster

Embed Size (px)

DESCRIPTION

Mapping A Disaster Anthony Baxter Google during MSC Malaysia Open Source Conference 2009 Monday 1 June 2009

Citation preview

Page 2: Mapping A Disaster

Worst fires in Australian history

February 7, 2009

Page 3: Mapping A Disaster

173 dead

Page 4: Mapping A Disaster
Page 5: Mapping A Disaster

horrific conditions46.4C !

Page 6: Mapping A Disaster

fires started sat 7 feb

Page 7: Mapping A Disaster

fires started sat 7 feb

still danger a week+ later

Page 8: Mapping A Disaster

fires started sat 7 feb

still danger a week+ later

some fires burned a month

Page 9: Mapping A Disaster

4,500 km2 of land burned

Page 10: Mapping A Disaster

many fires, across the state

Page 11: Mapping A Disaster

up to date information

Page 12: Mapping A Disaster

ABC radio

government broadcaster

official emergency response network

24/7 radio coverage

Page 13: Mapping A Disaster

official sources

Page 14: Mapping A Disaster

official sourcesCountry Fire Authority:

private landswww.cfa.vic.gov.au

Page 15: Mapping A Disaster

official sourcesCountry Fire Authority:

private landswww.cfa.vic.gov.au

Dept of Sustainability and Environment:public lands

www.dse.vic.gov.au

Page 16: Mapping A Disaster
Page 17: Mapping A Disaster

problem #1

Page 18: Mapping A Disaster

problem #1

server load

500 Server Error

Page 19: Mapping A Disaster

problem #2

Page 20: Mapping A Disaster

problem #2

locating these places

Page 21: Mapping A Disaster
Page 22: Mapping A Disaster
Page 23: Mapping A Disaster

my brotherlives here

Page 24: Mapping A Disaster

my brotherlives here

friend liveshere

Page 25: Mapping A Disaster

my brotherlives here

friendʼs elderlyparents here

friend liveshere

Page 26: Mapping A Disaster

but where are the fires?

Page 27: Mapping A Disaster

who needs to know?

Page 28: Mapping A Disaster

who needs to know?people in danger

Page 29: Mapping A Disaster

who needs to know?people in danger

friends and family

Page 30: Mapping A Disaster

who needs to know?people in danger

friends and family

people followingthe news

Page 31: Mapping A Disaster

sunday morning

Page 32: Mapping A Disaster

sunday morning

started thinking weshould do something

Page 33: Mapping A Disaster

sunday morning

started thinking weshould do something

Page 34: Mapping A Disaster

version one

scrape CFA RSS

geocode locations

publish as a flash map

Page 35: Mapping A Disaster

mapvisage.appspot.com

Page 36: Mapping A Disaster

6 hours initial

development

Page 37: Mapping A Disaster

6 hours initial

development(2 hours of that onflash/IE debugging)

Page 38: Mapping A Disaster
Page 39: Mapping A Disaster
Page 40: Mapping A Disaster

version two

automate geocoding

auto-refresh the map

georss.orggoogle maps API

search, links to relief agencies

Page 41: Mapping A Disaster

<georss:point> 143.74774 -37.52654</georss:point><georss:featuretypetag> point</georss:featuretypetag>

Page 42: Mapping A Disaster
Page 43: Mapping A Disaster

slight issue

Page 44: Mapping A Disaster

slight issue

Fire service data not always clean

Page 45: Mapping A Disaster

slight issue

Fire service data not always clean

“5KM SE WARBUTON TRK”

Page 46: Mapping A Disaster
Page 47: Mapping A Disaster

step three

Page 48: Mapping A Disaster

step three

satellite imagery

Page 49: Mapping A Disaster

step three

satellite imagery

Page 50: Mapping A Disaster
Page 51: Mapping A Disaster

NASA MODIS

Page 52: Mapping A Disaster

NASA MODIS

TERRA and AQUA

Page 53: Mapping A Disaster

NASA MODIS

TERRA and AQUA

250m resolution

Page 54: Mapping A Disaster

NASA MODIS

TERRA and AQUA

250m resolution

daily coverage

Page 55: Mapping A Disaster

NASA MODIS

TERRA and AQUA

250m resolution

daily coverage

IR detectors

Page 56: Mapping A Disaster

NASA MODIS

TERRA and AQUA

250m resolution

daily coverage

IR detectors

rapidfire.sci.gsfc.nasa.gov

Page 57: Mapping A Disaster

polar orbit

Page 58: Mapping A Disaster

polar orbitonline withina few hours

Page 59: Mapping A Disaster
Page 60: Mapping A Disaster
Page 61: Mapping A Disaster
Page 62: Mapping A Disaster

serving the images

Page 63: Mapping A Disaster

serving the images

geotiff images

Page 64: Mapping A Disaster

serving the images

standard format for map tiles

geotiff images

Page 65: Mapping A Disaster

serving the images

standard format for map tiles

standard file names

geotiff images

Page 66: Mapping A Disaster

serving the images

standard format for map tiles

standard file names

geotiff images

stitch them together

Page 67: Mapping A Disaster

problem

Page 68: Mapping A Disaster

Googleʼs map tile pipeline not

suited to smaller jobs

Page 69: Mapping A Disaster

Googleʼs map tile pipeline not

suited to smaller jobs

or repeated,fast turnaround

jobs

Page 70: Mapping A Disaster

maptiler

Page 71: Mapping A Disaster

maptilergdal2tiles

(summer of code)

Page 72: Mapping A Disaster

maptilergdal2tiles

(summer of code)

geotiff⇓

tile images

Page 73: Mapping A Disaster

appengine not currently good at lots of files

Page 74: Mapping A Disaster

appengine not currently good at lots of files

serve from zip files

Page 75: Mapping A Disaster

appengine not currently good at lots of files

serve from zip files

6 zoom levels~1000 images

Page 76: Mapping A Disaster
Page 77: Mapping A Disaster

HTTP Expiry Headers

Page 78: Mapping A Disaster

Google Front Ends

HTTP Expiry Headers

Page 79: Mapping A Disaster

Google Front Ends

HTTP Expiry Headers

Image tiles cached

Page 80: Mapping A Disaster

Google Front Ends

code open sourced“mapvisage” on

google code

HTTP Expiry Headers

Image tiles cached

Page 81: Mapping A Disaster

Google Front Ends

code open sourced“mapvisage” on

google code

HTTP Expiry Headers

Image tiles cached

warning: code notthe prettiest

Page 82: Mapping A Disaster

Automated tilegeneration

Page 83: Mapping A Disaster

Automated tilegeneration

mostly

Page 84: Mapping A Disaster

Automated tilegeneration

mostly

stupid clouds

Page 85: Mapping A Disaster

made mapembeddable

Page 86: Mapping A Disaster

made mapembeddable

news sites

Page 87: Mapping A Disaster

made mapembeddable

news sitesblog posts

Page 88: Mapping A Disaster

made mapembeddable

news sitesblog postshomepage promo

Page 89: Mapping A Disaster

made mapembeddable

news sites

peak:8M map views/day

sustained:60 hits/sec

blog postshomepage promo

Page 90: Mapping A Disaster

benefits

Page 91: Mapping A Disaster

benefitsreassurance for the worried

Page 92: Mapping A Disaster

benefits

better understanding of the fire scale

reassurance for the worried

Page 93: Mapping A Disaster

benefits

better understanding of the fire scale

took load off fire service websites

reassurance for the worried

Page 94: Mapping A Disaster

enable people to reuseyour data

lesson

Page 95: Mapping A Disaster

geocoded RSS ➙ maps=

map of family/friends

Page 96: Mapping A Disaster

going forward

Page 97: Mapping A Disaster

geocoded RSS

Page 98: Mapping A Disaster

geocoded RSS

Page 99: Mapping A Disaster

geocoded RSS

moreplease

Page 100: Mapping A Disaster

more than fires

Page 101: Mapping A Disaster

geo spatialinformation

conveys vitalinformation

Page 102: Mapping A Disaster
Page 103: Mapping A Disaster

disasters

Page 104: Mapping A Disaster

alertsdisasters

Page 105: Mapping A Disaster

alertsevacuations

disasters

Page 106: Mapping A Disaster

loss of control?

Page 107: Mapping A Disaster

loss of control?

something that frightensagencies

Page 108: Mapping A Disaster

loss of control?

something that frightensagencies

donʼt be scared ☺

Page 109: Mapping A Disaster

create clear license

Page 110: Mapping A Disaster

create clear license

lay out terms for re-use

Page 111: Mapping A Disaster

for instance

Page 112: Mapping A Disaster

attribution

for instance

Page 113: Mapping A Disaster

attribution

links

for instance

Page 114: Mapping A Disaster

timeliness

attribution

links

for instance

Page 115: Mapping A Disaster

timeliness

attribution

links

for instance

Page 116: Mapping A Disaster

structure

Page 117: Mapping A Disaster

structure

RSS/Atom are obvious choices

Page 118: Mapping A Disaster

structure

RSS/Atom are obvious choices

think: how can I expose this data as RSS?

Page 119: Mapping A Disaster

RSS/Atom

Page 120: Mapping A Disaster

RSS/Atom

browsers/readers

Page 121: Mapping A Disaster

RSS/Atom

browsers/readers

services to forward to SMS

Page 122: Mapping A Disaster

structure

Page 123: Mapping A Disaster

structure

attach times to data

Page 124: Mapping A Disaster

structure

attach times to data

attach locations to data

Page 125: Mapping A Disaster

structure

attach times to data

attach locations to data

donʼt make people guess

Page 126: Mapping A Disaster

structure

attach times to data

attach locations to data

use georss

donʼt make people guess

Page 127: Mapping A Disaster

you arenʼt the only one who can find a use for your data

Page 128: Mapping A Disaster

open data

Page 129: Mapping A Disaster

open data

especially when livesmay depend on it

Page 130: Mapping A Disaster

you can make a difference