This guide describes a legacy version of the Tasking Manager. If the user interface of the version you use looks different from the one described here then you should consult the manual for version 3
OSM Tasking Manager Project Admin
The OpenStreetMap Tasking Manager is essential to conducting a mapathon, managing a HOT activation, or creating mapping tasks for student mappers. The Tasking Manager divides the work into manageable geographic chunks, which reduces editing conflicts, especially with large numbers of distributed mappers. The Tasking Manager also helps mapping accuracy and data quality by providing a consistent set of instructions for your mappers (e.g. ‘map all roads and buildings’). In short, the Tasking Manager is how you set up and direct the workflow for open mapping activities. This module describes the basic administration of the OSM Tasking Manager for successful mapping events.
This guide is specifically written for those persons who need instructions on administration of the OSM Tasking Manager, including the creation and modification of mapping projects for open mapping events, i.e. ‘mapathons’. This guide is applicable to all instances of the OSM Tasking Manager including the HOT Tasking Manager http://tasks.hotosm.org/ and the TeachOSM Tasking Manager http://tasks.teachosm.org/. A list of other instances of the OSM Tasking Manager can be found at the OpenStreetMap wiki
The HOT or OSM Tasking Manager is frequently referred to as TM2, as a shorthand for Tasking Manager, version 2.
Logging in & Access Levels
The first thing to understand is access level. All access to TM2 is authorized through https://www.openstreetmap.org. To access TM2 you will need an OpenStreetMap (OSM) account. Once you have this account visit http://tasks.hotosm.org/ and click Login to OpenStreetMap, which will refer you back to the OSM page where you can authorize the Tasking Manager to have limited access to your OSM account.
Access Levels within the OSM Tasking Manager
The OSM Tasking Manager has three user access levels:
- User - The most basic level. The user is able to login to TM2 and use its functionality to find and select a mapping project and work on it. This level of usage is fully described in The OSM Tasking Manager guide within LearnOSM. Note that some projects, such as those in draft (i.e. unpublished) state are not visible to users.
- Project Manager - Project managers have access to create and update projects within TM2.
- Administrator - Administrators have access that allows them to manage access levels of users within TM2. You will need Project Manager Access level to create new projects using TM2.
Initiate a new Project within TM2
Click your username in the upper right corner, then Create a New Project. You then may choose between drawing your area of interest on the map, or importing a bounding box from a file;
Importing a file with a defined area is always preferable to hand drawing a Tasking Manager project. Tools like JOSM, QGIS, etc can be used to create files for importing into the Tasking Manager.
Draw an area of interest to be mapped
- Click the ‘Draw’ button in the upper right corner.
- To draw a polygon representing the area of interest in the map frame hold the right mouse button down to move the map without clicking, which will add a node. The polygon should tightly frame the area of interest. This saves time for completing tiles that are not of interest (i.e. ocean, forest)
- Click on your starting point to complete the polygon
Upload a GeoJSON or KML file of the area of interest to be mapped
- Click the ‘Import’ button,
- Browse to your file in the File Upload window,
- Click the file name to highlight the file and then click ‘Open’.
The area of interest defined by the file upload or hand drawn will appear in the map frame, and you will then be asked to choose how the area of interest is split into individual tasks. There are two options:
- Square Grid - The Tasking manager will uniformly divide up the overall project area in exactly the same sized task squares. This is usually a very good idea for general crowdmapping projects.
- Arbitrary Geometries - If you uploaded a file to define your project area, that file can also contain the shapes for the individual task. There has to be a special need in the mapping to create custom task shapes. An import of roads project might need custom task shapes for example.
Using the Square Grid for task squares
To create uniform square tiles, select the Square Grid option and click next.
The area of interest is automatically split into grid cells and each cell becomes a task. The larger the project area, the larger the resulting squares will be. Determine the optimal tile size based on the five relative tile size options. As such, a smaller tile size will result in more tasks as shown in the screenshots. The optimal tile size will therefore depend both on the size of the area (create smaller tiles for a large project) and the number of features that will likely need to be mapped within each tile. Generally speaking, as the size of the area of interest and/or the number of likely features increases, the tile size chosen for the project should decrease.
Considerations before deciding on tile sizes
- A brand new mapper at a mapathon will map an area at roughly a quarter of the speed of an experienced mapper (many start off far slower, but soon get faster),.
- A new mapper finds it as hard to search for features in the satellite imagery as they do to actually map them. Finding round huts thatched with natural materials in an area of round bushes is a steep learning curve for a ‘newbie’.
- A new mapper also finds it difficult to trace lots of features such as buildings.
- Later in the process you have the opportunity for a mapper to ‘split’ a square - splitting a square into quarters helps new mappers get a square size they can cope with.
- The most likely part of a square for problems to occur is at the edges and corners. Therefore smaller squares means more corners and edges and will result in duplication of mapping as well as objects being missed. There is a tradeoff in how small you make the square, which may make it easier for the new mapper and an increase in errors because there are more corners and edges.
- A square may be split, but there is no option to join squares together to make them bigger again. So be careful when splitting
- Conclusion Try mapping an area of the project yourself to see how easy it is and what difficulties will be faced. This should help you to decide on an optimum square size. Allow splitting, but not to infinity - some new mappers continually split squares until they are so small that it becomes extremely difficult to map.
It is possible if you uploaded a file to define your project area, it could also contain information about the exact shapes you want your project’s individual tasks to be. If the AOI consists of one polygon, the project will have just one task. This is generally not needed and should only be needed for specific needs.
Considerations concerning Imagery
In most cases we use the “standard” Bing imagery. But there are situations where you might want to choose an alternative source:
- Bing does not provide high-resolution coverage for your area of interest (AOI).
- Bing has considerable cloud cover in this area.
- You need newer imagery for post-disaster evaluation.
If Bing does not prove adequate then Mapbox is the next choice. You should only look for other sources if neither of these two meet your requirements.
In such cases it is not sufficient to choose a license-compatible source and make it available through a WMS or TMS service. Your AOI has probably already been partially mapped using Bing or Mapbox imagery and there might be a noticeable offset between images. You must have a close look at various locations of your AOI and determine the offset between your imagery and previously mapped data. If the existing OSM data are offset with respect to your imagery but fit Bing imagery then we usually assume that Bing is the “gold standard” unless we have GPS traces which prove that this assumption is wrong.
If there is a constant offset between your imagery and Bing across the AOI then this might be corrected on the server so that images from various sources loaded in the editor match. If this is not possible, if the offset varies across the AOI or if existing data are aligned with various sources then it is time for plan B:
The important point is that you must develop a strategy for how to cope with these issues and provide detailed instructions to mappers and validators. We strongly suggest that you declare such a project “for experienced mappers only” and explain that experience in this case does not mean having mapped 200+ buildings but having already dealt with alignment issues and different imagery sources.
One possible strategy could include these steps:
- Clearly state which imagery is to be considered the reference to which anything else should be aligned. In this case let us assume that the reference is Bing.
- Make sure that all existing features which are also visible on Bing are aligned with Bing imagery, i.e. realign if necessary.
- Align the alternative imagery to existing features (and thus to Bing) using the imagery offset function of the editor.
- Add new features from the now correctly aligned alternative imagery.
It is important that step 3 is repeated for every task of the project and the individual task squares should not be too large because imagery offsets can vary considerably across an AOI, particularly if the terrain is not flat. Even imagery discontinuities may occur across a project - look out for them and advise the contributors of such a problem.
Here are some suggested bits of information which you might include in the project instructions:
- general guidelines for various editors
- an animated gif on imagery alignment in iD
- the josm imagery alignment chapter in learnOSM
Create the project & add description
After choosing a tile size, click “Create Project”.
This establishes the project in the task manager and opens a screen where you can provide the descriptions, instructions and other information about the project. Keep in mind that this must not be underestimated. A fair share of mappers (in many cases the majority) will have no previous experience with OpenStreetMap and/or HOT and will thus not be familiar with tagging guidelines. It is very important that the objectives of the project are clear and that all resources which the mappers should take into account are laid out here. It is often advisable to confine one project to one class of objects to be mapped. If you need a basemap of an area better split it in several projects, one for the roads, one for the buildings etc. Now beginners can focus on a small class of objects while learning how to map them correctly. Otherwise you might end up with lots of tiles which contain a bit of everything but nothing really complete.
Please use plain language as your target audience may not consist of native English speakers.
- The title of the project should already reveal what entities should be mapped. Prefer a title such as #1396 - Missing Maps: Niger State (north), Nigeria (project 1: roads and residential areas )
- The most important messages should appear on the instruction tab first to ensure they are read. This would include any special imagery to use instead of Bing. The first sentences could mention that it is not required to map every single house if the project is about roads and residential areas, for example. Or that it is required to map every house if the project is to be used for population density estimates. These are the messages that should also appear on the description tab.
- Other points of clarification: If the project is suitable for mappers with a certain level of experience only. For example, the project uses imports or existing data should be realigned to GPS traces or some other imagery (cf. the previous section). Phrase it so that new mappers will feel invited contributing to other projects but understand that advanced techniques are required in this instance.
- There are guidelines that cover common errors we see while validating. One example is Blake Girardot’s compilation on mapping in West Africa. Use the link in the instructions and explain that adhering to these guidelines is required.
- The definitive resource on tagging is the OpenStreetMap wiki. For many HOT-related tasks the page on tagging highways in Africa is the proper specialization and highly recommended reading for every mapper. If your project must adhere to different tagging standards then write a similar page in the wiki and link it in your instructions.
Proofread and Publish
Proofread the various tabs to ensure wording and formatting are correct, and instructions are clear. If you need to make changes or refinements to your project, click the ‘Edit’ link in the upper right hand corner of the page.
If the project is ready for mapping, click the ‘Publish’ link. Once the project is published, it is available for mapping to anyone with an OSM account, unless a group of users was specified in the ‘Allowed Users’ tab, in which case only the allowed users would be able to work on it. If necessary, edits can still be made to the project after publication by clicking on the ‘Edit’ link.