Humanitarian OpenStreetMap Mapping Party, Brittany France

Beg Meil Mapping Party
Photo by Anna Hodgkinson

An email to the HOT list from Nicholas Chavent earlier this month (March 2011) announced the opportunity to participate in a Mapping Party for the Humanitarian OpenStreetMap Team – yep a “HOT” Mapping Party. Many OpenStreetMap enthusiasts would be familiar with the notion of a Mapping Party. Mapping parties are local social events with a focus on having fun while mapping for OpenStreetMap an open licensed map of the world. But what’s a HOT mapping party? HOT mapping parties are for OSM enthusiasts who are also interested in humanitarian mapping. We all know maps form a critical part of disaster response. But how can HOT and OSM be better prepared for the eventuality of assisting during a disaster? Disaster mapping in contrast to general OSM mapping has some specific requirements.

Disaster response must incorporate good geographic data collection practices:

During disasters mapping serves to allow quick and accurate decision making. But there can be no maps without any data. So good disaster response workflows incorporate good geo data collection practices. The HOT Kit is designed to do just this. Over the last year the HOT team has been working in Haiti and have continued to refine and add to a HOT Kit. HOT Kit merges traditional practices of disaster response coordination with the best that the open source geospatial tool-set has to offer.

In the event of a disaster mapping sits close to the planning, support and coordination units. Map-makers working in these efforts must be ready to answer any number of questions thrown at them by the coordinators of the disaster response. Thus being organized and knowing where everything is, is critical, an important goal of the HOT Kit. The kit is organised as five top-level folders under which sit almost anything a HOT team member supporting an operation would need.

Steps during a response will include data collection, cleaning and merging and product creation. The product creation may involve analysis and summarizing. Supporting the operation means having all the data and analysis at your finger tips. In addition it requires a systematic procedure for collection of geographic data and its inclusion into the map making process.

Hot Kit systematizes the steps of map making during disasters:

So the five root directories of HOT Kit are

00_DATA/         <--- geo data ready for use
01_SURVEYS/      <--- data collection
02_PROJECTS/     <--- desktop GIS projects (QGIS being default)
03_PRODUCTS/     <--- products like pdf, shpfiles, garmin files, kml
04_SUPPORT_DOCS/ <--- a kitchen sink of documentation

OSM community must get to know and help refine the HOT Kit: As the HOT Kit gets used it will continue to change and improve. HOT Kit must be able to handle changing requirements based on the kind of project or disaster its being used in. It also needs to elegantly support users of varying skills. Lastly it needs eyeballs. To help folks quickly getting acquainted with the HOT kit I have just published a ruby gem: https://github.com/sabman/HOT-Kit-Generator

HOT Kit Generator is only a day old gem written during the drive from Brittany to Paris. Its aimed at quickly creating a fresh HOT Kit for a new deployment. It currently only stubs out the folders needed during a HOT deployment. This is done based on a configuration file that defines the directory structure of a HOT Kit. My vision for this generator is to allow pulling distributed web and data resources using a single command to create an up-to-date HOT kit in seconds. Allowing different configurations depending on the disaster type, geographic region or project goals or length.

OpenRouteService.org:Home

Give it a try and feel free to fork to get started on some of the TODO items. I would also appreciate any feedback on the idea itself.

On-ground surveys and OSM tags:

Once a HOT team is in the field and collecting data, they should be making the most of the opportunity. This means collecting details that would only be available to someone in close proximity to the resource being mapped. This is where the HOT tagging and forms come in. Over the last few months a number of HOT team members have been developing forms for the OSM Humanitarian Data Model. This along with the Humanitarian Data Model presets in JOSM can make the task of data entry after a survey go a lot smoother. Nicholas Chavent’s work on HDM is particularly impressive.

Role of remote mappers and tagging:

In an emergency the focus is on saving lives. Depending on the kind of disaster the tagging scheme will vary but the regular tags in OSM aren’t always compatible with the needs of first responders. As the HOT team matures so will their ability to engage with the regular OSM mappers who are willing to help support disaster mappers often using satellite imagery. As an arm-chair mapper, instead of mapping for fun you are mapping to create raw data which will form input into products that can give actionable information to first responders.

So where does Haiti-like remote mapping fit into a disaster response. Mapping a disaster from home can be a very useful activity. Useful to the first responders, provided some common sense is applied to the process. For one thing mappers who want to assist in the work of HOT should look at the current mapping priorities here: Current Humanitarian OSM Team Projects Then its worth noting that the mapping you do from home can give first responders some very useful base data. In the case of Haiti it was location of IDP camps, destroyed buildings, blocked roads and landslides. These are all things that first responders can take and plan their missions. It should however be noted that its possible only if the imagery is of high enough resolution. Haiti was and still is, an exception, where sub-meter post disaster imagery was made public and as a result the first-responders were able to save many lives. But we have yet to see such high resolution and clear images for other disasters. So when mapping from home its better to err at the side of caution and not tag an item if you are unsure. Having said that there is no doubt that some data is better than no data and so getting as much of the base infrastructure such as transports, hydrology, admin and populated areas mapped is a good thing.

Long live the HOT Mapping party:

Finally one man without whom the HOT mapping party in Beg-Meil would never happened was Roderic Bera. He was behind the smooth running of the weekend, having organized everything ranging from food to accommodation to transport – it was all very well thought out. Thank you Rod. Then of course Nicholas and Fredric worked late into the night on Friday to get everything to do with the mapping ready. Fred’s mock reports of a humanitarian crisis in Brittany and Beg-Meil read like a true forced migration.

Thanks to all who came and made the HOT mapping party possible, in order of appearance:

  • Nicholas Chavent
  • Roderic Bera
  • Frederic Bonifas
  • Manuel Robert
  • Maxime Leguillier
  • Anna Hodgkinson
  • Joseph Reeves
  • Rodolphe Quiedeville

A special thanks to Manuel for letting me hang at his place in Paris on Sunday night. Good luck to him and Maxime in Haiti. Until next time.

Mapping & Planning Support (MAPS) meets OpenStreetMap (OSM)

Mapping and Planning Support (MAPS) is a volunteer group based out of Canberra that provides Geographic Information Systems (GIS) support to emergency services during a “major” disaster. It was started in 2005 by Frank Blanchfield and Ian Batley who foresaw the need for a stand-by volunteer mapping team that could spring into action during a major natural disaster. MAPS was strongly supported by Adam Atkinson (RFS) and Steve Forbes (SES/RFS). By the time I joined MAPS in 2008 the team had already had several dozen deployments for a range of emergency activities: everything from fires, floods and flus. MAPS volunteers come from a multi-talented pool of professionals and they are the Australian equivalent of MapAction. There is a great presentation by Ian Batley on the volunteer technical community model of MAPS.

You can’t really talk about MAPS without making reference to the Black Saturday Bushfires. The Black Saturday firestorm of 13th February 2009 was Australia’s worst natural disaster. The fires were intense and ferocious and led to over a 170 fatalities and damaged over 3000 properties. Some towns were nearly wiped off the earth. Just two days after Black Saturday the first MAPS team was deployed on ground working with Victoria Police and other state and federal agencies to assist. That operation continued for 9 weeks. During the deployment MAPS assisted Victoria Police in the coordination of Search & Rescue efforts. Accomplishments included developing map products for carrying out search of over 3000 property parcels in a period of 2 weeks; developing workflows, data quality control routines and databases for capturing, storing, and analysing data collected by field search and rescue teams; developing mapping products to aid reporting of fatalities. Data captured included spatially referenced photographs, high resolution aerial imagery and real time data from GPS enabled handhelds and cameras. Software used included ArcPAD, ArcGIS, ArcSDE, SQLServer and MS-Access. I also wrote custom scripts (in ruby) to process over 9000 georeferenced photographs.

After the MAPS deployment to Victoria we started a working group to investigate the potential for using Open Source tools along with the proprietary applications that are currently used.

Then in January 2010 another natural disaster caught the world’s attention. I wanted to help. But this time I was several thousand miles away from the disaster. I have never been to Haiti, yet I was able to contribute towards the mapping of a country that had had it’s national mapping agency completely destroyed and sadly most of its staff killed. The work was done sitting in my home office working late at night to digitize aerial photograph, intermittent with some wiki gardening. This time I was not working under any formal organisation but rather with a loose community of open source and mapping enthusiasts. And due to my background of working with MAPS I was acutely aware of the value of mapping to first responders. Thanks to the OSM community this work was being used by responders in Haiti. After Haiti I gave a few presentations on how this data was collected, used and will play a key role in the future of Haiti. That talk is at slideshare.

After Haiti I realised that although MAPS can handle disasters in Australia and the Asia Pacific region – if they had formal links with the OpenStreetMap, CrisisCommons and CrisisMappers communities they could learn a lot from each other and the collaboration would help become much more versatile. As I was thinking about formalising this relationship the time for the MAPS Autumn Training also came along. This provided an ideal opportunity to introduce OSM to MAPS. And as it turned out other MAPS co-ordinators where also thinking the same thing. So last weekend we had a training day at the ACT State Emergency Services HQ and we included OpenStreetMap – a crowd sourced, open and free database of spatial data. AFIK this was the first time in the history of MAPS and Australian volunteer emergency community, in general, that a crowd sourced database was used. This is the first step by MAPS to engage with the OSM community and over the coming weeks the working group will be meeting regularly to start to pull together the tools and expertise needed to make OSM a regular source of data and information. My presentation slides and tutorial videos are below:

Here is a video showing how to print walking papers and collect data.

Walking Papers Tutorial – part 1 from shoaib burq on Vimeo.

Here is the video showing the use of walking papers to add data to OSM.

Walking-Papers Tutorial part 2 from shoaib burq on Vimeo.