Emergency cartography
@rbanick
Methods / principles / tricks / lessons
They always needed the map yesterday
On the ground mapping: uncomfortable, pragmatic, unpredictable, often ugly
Static mapping
- QGIS: general cartography
- ArcGIS: labeling
- Command line tools (GDAL, ogr2ogr, etc.): geoprocessing
- Adobe Illustrator (AI): core cartography
Interactive mapping
- Leaflet.js
- Tilemill
- D3.js
- Mapbox Studio?
Red cross colors
- White
- Light grey
- Black
- Bright, saturated red
Cartographic and design principles
Thematic content and design
- Desaturated background colors
- Highly saturated symbols and thematic layers
- Semi-transparent callout boxes
- Light drop shadows
- Occasional sidebars of information
- Overall: clean, simple elements
Interactive mapping = A little messier
OSM - currently made by hand
All rules are made to be broken, especially in disaster response
Mashups of multiple thematic layers
Organization and workflows
The team
- GIS lead and developer
- 2 analysts / cartographers / junior developers
- Intern(s)
- Awesome volunteers
Exploiting the time difference
Communications:
Skype chats, Github commits, email
AI templates @ consistent scale
"On the job" CartoCSS training for all comers
Deploying: getting maps on the plane
10:30 AM"We're sending someone to the northern Congo at 5:30 PM. Think you can get them 20 maps of the area?"
Large format reference maps - OSM or outside sources
OSM onto Garmin
Tablets with OSMAnd + country maps
Experimental: Offline interactive maps for dummies
Remote support and coping with connectivity
Export as PDF, then export as PNG
Half the file size, all the fun
Transferring files
"Please stop killing the dropbox"
americanredcross.github.io/haiyan_mapfolio
The map dashboarda.k.a.betraying our principles
Integrating Mapbox Studio
Pushing OSM difs to offline interactive maps
OSM + ODK - linking assessment data to response data