cleaning up after a task manager task
Posted by Johnwhelan on 1 January 2022 in English. Last updated on 3 January 2022.In the ideal world all tasks would be validated to a high standard but unfortunately this doesn’t happen.
I’ve seen HOT projects with nearly two thousand duplicate buildings, I’ve seen some with two or three hundred untagged buildings. Some are well mapped and have no errors.
So this a method to clean up after the event. Basically you load up the area into JOSM and run the duplicate building script and JOSM validator. It won’t catch everything but it’s a lot faster than validating each tile. The todo and Mapathoner plugin are required.
select the errors then add them to the todo list and work your way through them.
The key is aoiBBOX”: [6.473334,5.172193,6.870011,5.730142] which is found here: https://tasking-manager-tm4-production-api.hotosm.org/api/v2/projects/10756 for project 10756. You’ll need to search the text to extract it.
You can either feed these coordinates into JOSM and download the area directly or feed them into an overpass query or extract them from an off line version of the map. https://osm-internal.download.geofabrik.de/ is one source. If you work with the off line version you can locate the errors then just directly redownload the tiny bit to ensure the map is up to date before you correct the error.
An example of a .bat file to extract the area from an offline file is osmconvert64 e:\downloads\nigeria-latest-internal.osm.pbf -b=6.473334,5.172193,6.870011,5.730142 -o=f:\maps\nigeria10756.osm Just load nigeria10756.osm as a local file into JOSM.
Note this is not validation since no feedback is given in task manager to the mapper. It is recommended it is used when there are no active mapping taking place so a month or so after the mapping has petered out is a good time.