Google Inc + World Bank = Empowering Citizen Cartographers?

[Cross-posted from Patrick Meier's blog iRevolution]

World Bank Managing Director Caroline Anstey recently announced a new partnership with Google that will apparently empower citizen cartographers in 150 countries worldwide. This has provoked some concern among open source enthusiasts. Under this new agreement, the Bank, UN agencies and developing country governments will be able to “access Google Map Maker’s global mapping platform, allowing the collection, viewing, search and free access to data of geoinformation in over 150 countries and 60 languages.”

So what’s the catch? Google’s licensing agreement for Google Map Maker stipulates the following: Users are not allowed to access Google Map Maker data via any platform other than those designated by Google. Users are not allowed to make any copies of the data, nor can they translate the data, modify it or create a derivative of the data. In addition, users cannot publicly display any Map Maker data for commercial purposes. Finally, users cannot use Map Maker data to create a service that is similar to any already provided by Google.

There’s a saying in the tech world that goes like this: “If the product is free, then you are the product.” I fear this may be the case with the Google-Bank partnership. I worry that Google will organize more crowdsourced mapping projects (like the one they did for Sudan last year), and use people with local knowledge to improve Map Maker data, which will carry all the licensing restrictions described above. Does this really empower citizen cartographers?

Or is this about using citizen cartographers (as free labor?) for commercial purposes? Will Google push Map Maker data to Google Maps & Google Earth products, i.e., expanding market share & commercial interests? Contrast this with the World Bank’s Open Data for Resilience Initiative (OpenDRI), which uses open source software and open data to empower local communities and disaster risk managers. Also, the Google-Bank partnership is specifically with UN agencies and governments, not exactly citizens or NGOs.

Caroline Anstey concludes her announcement with the following:

“In the 17th century, imperial cartographers had an advantage over local communities. They could see the big picture. In the 21st century, the tables have turned: local communities can make the biggest on the ground difference. Crowdsourced citizen cartographers can help make it happen.”

Here’s another version:

“In the 21st century, for-profit companies like Google Inc have an advantage over local communities. They can use big license restrictions. With the Google-Bank partnership, Google can use local communities to collect information for free and make the biggest profit. Crowdsourced citizen cartographers can help make it happen.”

The Google-Bank partnership points to another important issue being ignored in this debate. Let’s not pretend that technology alone determines whether participatory mapping truly empowers local communities. I recently learned of an absolutely disastrous open source “community” mapping project in Africa which should one day should be written up in a blog post entitled “Open Source Community Mapping #FAIL”.

So software developers (whether from the open source or proprietary side) who want to get involved in community mapping and have zero experience in participatory GIS, local development and capacity building should think twice: the “do no harm” principle also applies to them. This is equally true of Google Inc. The entire open source mapping community will be watching every move they make on this new World Bank partnership.

I do hope Google eventually realizes just how much of an opportunity they have to do good with this partnership. I am keeping my fingers crossed that they will draft a separate licensing agreement for the World Bank partnership. In fact, I hope they openly invite the participatory GIS and open source mapping communities to co-draft an elevated licensing agreement that will truly empower citizen cartographers. Google would still get publicity—and more importantly positive publicity—as a result. They’d still get the data and have their brand affiliated with said data. But instead of locking up the Map Maker data behind bars and financially profiting from local communities, they’d allow citizens themselves to use the data in whatever platform they so choose to improve citizen feedback in project planning, implementation and monitoring & evaluation. Now wouldn’t that be empowering?

4 Responses to “Google Inc + World Bank = Empowering Citizen Cartographers?”

  1. Thank you for sharing this perspective on this Googel-Bank project. I think you raise legitimate concerns about the restrictive licensing agreement. I will be watching for further developments in this evolving story. Certainly has implications for the other citizen cartographer projects, would be interested to see creative commons licensing or something similar to foster ongoing collaboration in this field.

  2. Thanks Patrick, I also raised questions about this on Twitter and during “The Curious Case of Whose Data is it Anyway?” event in Bangalore there were really concerns shared about this announcement. I am afraid that hoping is not enough and connecting this collaboration with another announced partnership of Microsoft and British Council to support digital school in Africa I think we should focus more on building and extending our own structures and make those stronger. Therefore I very much welcome the step of Ushadidi to use Open Street Map as their default map.

  3. Meanwhile the Humanitarian OpenStreetMap Team and thousands of OpenStreetMap contributors will continue to map disaster truck regions and release geo-data properly. When people volunteer their time and effort towards gathering and inputting data, it’s only right and proper that the data is released in the same spirit of openness. Google Map Maker – OpenStreetMap comparison. Which will you support?

    There’s a hint within some github comments, that ushahidi will swap to OpenStreetMap by default. That’s a very welcome step! Perhaps you could tell us more on the blog here.