Mapillary Integration
Mapillary is a fantastic mapping resource with billions of street-level images and sign / feature detections that can be used for mapping in OSM. The screenshot shows where contributors have collected images while driving, riding a bike, or walking, and where Mapillary has automatically detected storefronts and related signage.
All this information is free to use for OSM contributors to improve the map. To aid with that, there are integrations with (Rap)iD and JOSM, the main editing tools for contributing to OSM. Those integrations are great for casual contributions. A deeper integration with MapRoulette would enable more directed use cases. For example, a local OSM chapter would like to start a mapping campaign to add all crosswalks in the city to OSM. They could start by acquiring fresh Mapillary imagery if needed. They would then create a MapRoulette Challenge by defining the area of interest and the feature type (crosswalks). MapRoulette would create the Challenge and mappers can "divide and conquer". Government agencies or companies who have an interest in OSM having a complete inventory of certain features could employ a similar workflow. Let's look at the steps in more detail.
I'll start on the right.
Mapillary offers a few built-in tools to work together on image collection. You can form an organization and add accounts to it. This lets you filter Mapillary contributions on the map so you can easily see the coverage your team has achieved.
Another feature that can help with targeted collection of imagery is the recently released Mapillary Missions. There is currently no option for end users to create missions, but this is something to keep an eye on nonetheless. It reminds me of the "map cake" tools of yore.
We're mostly concerned with the MapRoulette side of things here, but there are a few possible improvements to Mapillary that would help with this workflow:
- Notifications
The current Challenge paradigm on MapRoulette is that you start out with a known set of tasks that define the Challenge, and when all tasks are complete, the Challenge is done. (You can "refresh" a Challenge under certain conditions, but this is not common practice.) You can see in the diagram above that we're after something more continuous: the real world is always changing, the map is never "done". This should be reflected more centrally in the MapRoulette Challenge paradigm
Mapillary has a free vector tile API for retrieving the locations of images and detections, as well as API endpoints to retrieve metadata for all objects.
I wrote this document with Mapillary integration in mind, but there are many other point-based map hints that could be integrated with MapRoulette in a similar way: Osmose, Keepright, Kartaview.