The few mission feature looks very promising.
The blog post gives some info, but it would be great to get more detail - and I’ll throw a few suggestions for potential improvements in.
- What are the current criteria to highlight an area as a mission? This would be great to document/publish.
For example, here I have filtered for sequences since October 10th (2 months) - and this area shows as a mission.
Same area with all sequences, coloured by age:
- If I capture images in a mission area without going through “Start capture” from the mission view, is that counted towards the mission?
- If multiple users take images in a mission area, what happens?
- When could Android app get this feature?
- Missions in the website view?
- Mission details usually (always?) show street name. Is it connected to the mission in any way, or is it just a “name” for it? Or to put it differently, is the named street preferred / counted differently?
- The mission view shows “nn km road”. Is this all roads inside the mission area? How is this calculated - is it from OSM data? If so, which highway=* types are included, what other tags affect it (perhaps access=* etc)?
- The goals seem to be rather on the high end - the example area above states that 513 new images are required. How is this number determined?
Well, checking several missions, it seems to be one image every 10 metres for all the found roads, that question seems to be answered
- The distance in the mission detail - is this somehow related to the mission contents? As in, any requirement for the covered distance in new uploads?
- Seeing a mission like this. No OSM-mapped roads. How so?
- Currently the mission view is separate from the map view - this does not allow to see existing image captures together with the mission view. Would be neat to have them together as toggles, to see which exact areas would be more useful to capture inside the mission area. And perhaps the existing imagery age cutoff slider could be added…
- If the documentation is expanded to explain the questions above, it would be great to include it in the app (I use some devices where there is no internet connection on the move).
The possibility hinted in the blog, “community to “turn on” mission cells. Possibly via an API or integrating with existing OSM task tools” seems extremely intriguing. I’ve wanted something like that for quite some time from JOSM - exposing that via the API sounds wonderful. Such requests might have to be constrained to smaller areas though, and perhaps even to specific spots and directions (to see some street signs).