OSM Tasking Manager 3 Project Creation and Administration

If the user interface of the version you use looks different from the one described here then you should consult our version overview

Obsah sekcí

• Přihlášení
• Zahájení nového projektu - definujte oblast zájmu
• Vytvoření úkolu - rozdělte oblast zájmu
• Vytvoření projektu - zadejte, co uživatelé potřebují vědět
  • Popis - první věc, kterou se uživatelé dozvědí o vašem projektu
  • Instrukce - co by uživatelé měli dělat
  • Metadata - kam projekt patří
  • Prioritní oblasti - kde by uživatelé měli začít mapovat
  • Podkladové fotografie - základ pro mapování
  • Oprávnění - kdo může mapovat a ověřovat
  • Užitečné tipy - jak byste měli vyplnit všechna tato pole
  • Publikujte - nezapomeňte na to, nebo nikdy nedokončíte práci

Správce úloh (Tasking Manager) OpenStreetMap je nezbytný pro provádění mapathonu, správu aktivace HOT nebo vytvoření mapovacích úloh pro studentské mapovače. Tasking Manager rozděluje práci na zvládnutelné geografické bloky, což snižuje konflikty při editaci, zejména s velkým počtem distribuovaných mapovačů. Tasking Manager také pomáhá mapovat přesnost a kvalitu dat tím, že poskytuje konzistentní soubor instrukcí pro mapovače (např. ‘Mapovat všechny cesty a budovy’). Stručně řečeno, Tasking Manager je o tom, jak nastavíte a nasměrujete pracovní postup pro dobrovolné mapování. Tento modul popisuje základní správu nástroje OSM Tasking Manager pro úspěšné události mapování.

Tento návod je speciálně napsán pro ty osoby, které potřebují pokyny pro správu Task Manageru OSM, včetně tvorby a úpravy projektů mapování pro události otevřeného mapování, tj. “Mapatony”. Tento návod se konkrétně vztahuje na případy OSM Tasking Manager verze 3 včetně HOT Tasking Manager a TeachOSM Tasking Manager .

Modul Správce úloh HOT nebo OSM verze 3 je často označován jako TM3 jako zkratka pro Tasking Manager verze 3.

Přihlašování a přístupové úrovně

První věc, kterou je potřeba pochopit, je přístupová úroveň. Veškerý přístup k TM je povolen prostřednictvím webových stránek OpenStreetMap. Pro přístup k TM3 budete potřebovat účet OpenStreetMap (OSM). Jakmile budete mít tento účet, navštivte Tasking Manager a klikněte na Login to OpenStreetMap, který vás vrátí zpět na stránku OSM, kde můžete povolit správci Tasking Manager omezený přístup k vašemu účtu OSM.

Access Levels within the OSM Tasking Manager 3

The OSM Tasking Manager 3 has three user access levels:

• Uživatel - Nejzákladnější úroveň. Uživatel se může přihlásit k TM3 a využít jeho funkce k vyhledání a výběru projektu mapování a práci na něm. Tato úroveň využití je plně popsána v příručce Tasking Manager OSM v programu LearnOSM. Všimněte si, že některé projekty, jako například projekty v konceptu (tj. Nepublikované), nejsou pro uživatele viditelné.
• Project Manager - Projektoví manažeři mají přístup k vytváření a aktualizaci projektů v TM3.
• Administrator - Administrátoři mají přístup, který jim umožňuje spravovat přístupové úrovně uživatelů v TM3.

Pro vytvoření nových projektů pomocí TM3 budete potřebovat úroveň přístupu na Project Manager.

Začít nový projekt v TM3

Klikněte na své uživatelské jméno v pravém horním rohu a pak na Create New Project (Vytvořit nový projekt). Můžete si vybrat mezi kreslením vaší oblasti zájmu (AoI) na mapě nebo importováním oblasti zájmu z geojson souboru;

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. The suggested workflow is to create a .osm file of the AoI using JOSM and then use http://geojson.io/ to generate a GeoJSON.

Nakreslete oblast zájmu, kterou chcete mapovat

1. Klikněte na tlačítko Draw v pravém horním rohu.
2. Chcete-li nakreslit polygon představující AoI v rámečku mapy, podržte pravé tlačítko myši a přesuňte mapu bez kliknutí, což přidá uzel. Polygon by měl těsně zaostřit oblast zájmu. To šetří čas na dokončení dlaždic, které nejsou zajímavé (tj. oceán, les)
3. Klepnutím na počáteční bod dokončete polygon
4. Po dokončení polygonu můžete přesunout uzly nebo přidat nové tak, abyste dostali oblast tak, jak ji chcete.

nebo

Nahrajte GeoJSON nebo soubor KML oblasti zájmu, která má být mapována

1. Klikněte na tlačítko Import,
2. Vyhledejte soubor v okně Nahrávání souborů,
3. Klepnutím na název souboru zvýrazněte soubor a klepněte na tlačítko Otevřít.
4. Importované oblasti zájmu nelze upravovat.

Vytvoření úkolu (task)

Oblast zájmu (AoI) pro projekt je rozsáhlá celková oblast, která má být mapována. Tato oblast je pak rozdělena na menší oblasti nazvané Tasks, neboli Úkoly.

AoI definovaná nahraným nebo ručně vykresleným souborem se objeví v rámečku mapy a poté budete požádáni, abyste zvolili, jak je AoI rozdělena na jednotlivé úkoly. Existují dvě možnosti:

1. Čtvercová mřížka - Správce úkolů rovnoměrně rozdělí celou oblast projektu na přesně stejné čtverečky úkolů. To je obvykle velmi dobrý nápad pro obecné projekty zpracovávané dobrovolníky.
2. Libovolné geometrie - Pokud jste nahrali soubor a definovali jeho oblast projektu, může tento soubor obsahovat i tvary jednotlivých úloh. V mapování musí být zvláštní potřeba vytvořit vlastní tvary úkolů. Projekt importu silnic může vyžadovat například vlastní tvary úkolů nebo výstup z procesu redukce AoI.

Rozdělení úkolu pomocí čtvercové mřížky

Chcete-li vytvořit jednotné čtvercové dlaždice, využijte možnost Square Grid.

AoI se automaticky rozdělí na buňky mřížky a každá buňka představuje úkol. Pomocí tlačítek “Větší” a “Menší” určete optimální velikost dlaždice. Menší velikost dlaždice bude mít za následek více úkolů. Optimální velikost dlaždice bude tedy záviset jak na velikosti oblasti (vytvořit menší dlaždice pro velký projekt), tak na počtu objektů, které je potřeba zmapovat v rámci každé dlaždice. Obecně řečeno, jak se velikost AoI a/nebo počet pravděpodobných objektů zvyšuje, velikost dlaždice u projektu by se měla snížit.

Všimněte si prosím, že existuje více mapových vrstev, které lze použít při určování velikosti čtverce úloh. Pod tlačítkem v pravém dolním rohu mapy najdete seznam dostupných mapových vrstev. Volba jedné z vrstev snímků je pravděpodobně nejlepší volbou, protože umožňuje zobrazit aktuální snímky, které mají být mapovány.

If you have custom imagery for the project, you can also load that in by using the button in the upper right of the map and putting in a TMS or WMS url.

You can also create several different task sizes by using the “Split” tools. Task squares can be split multiple times. Again, using an imagery layer will help you decide where tasks need to be split. The “Reset” button will reset all of your split tasks. The Split (Polygon) option will let you draw a polygon over an area to create smaller tasks and the Split (Point) will let you click individual task squares to split. The Reset button will remove all of your custom splitting.

Generally you will want small tiles over dense settlement areas for buildings. The goal should be to create project tasks that can be completed in 10-15 minutes.

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’.
• Nový mapovač také považuje za obtížné vysledovat spoustu funkcí, jako jsou budovy.
• 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.

After finalizing Task sizes, click “Next”.

Arbitrary Geometries

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.

Arbitrary geometries can not be split.

Project Area Trim

After determining the task sizes you will have the option to “Trim” your AoI. You can either trim the AoI to the exact polygon shape you drew or imported (suggested) or you can trim to the nearest task square that includes your AoI.

After finalizing a the AoI trim, click “Next”.

Create the project

Give the project a title (can be edited on the next screen) and click “Create”

This establishes the project in the Tasking 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.

Po vytvoření projektu je nutné upravit všechna jeho přiřazená nastavení:

• Popis - slouží k zobrazení v seznamech a motivačních informacích pro mapovače
• Instructions - Detailed instructions for what and how to map the needed objects/entities/features
• Metadata - Additional information used for categorizing the Project. Often used in filtering the full list of projects.
• Imagery - Place to provide a TMS URL and License required.
• Priority Areas - Allows you to specify parts of the Project that should be mapped first.
• Permissions - Allows you restrict access to the project for mapping and validation.
• Settings - Project due date and JOSM Presets.
• Actions - Send messages to contributors, validate and invalidate the entire project with one click.

Description

This screen allows you set the project priority, its status as Draft, Published, or Archived, a short description used in Project listings and the long description available once a mapper has selected the Project.

Both the short and long description should provide information about why the project exists, who will use the data and the expected the impact the mapping will have. These fields support Markdown text and can include images and videos.

Instructions

Entities to Map - A list of the features you want users to map. Generally the fewer features the better as they are more likely to get completed.

Projects that ask for lots of entities to be mapped are difficult for mappers and difficult to get validated. They take much longer to get a good usable dataset. Task sizes are also difficult to make efficient for different types of mapping, e.g., buildings need small task squares, roads and waterways need larger task squares. Making multiple projects over the same area to get buildings and linear features mapped is a best practice.

Changeset Comment - This is the default changeset comment that will be attached to every data upload to OSM. It usually includes something that identifies the Tasking Manager the project resides on and the features that were mapped. It is often used for “hash tags” to help identify the organization requesting and/or doing the mapping. It can also describe the mapping being done, e.g., “Mapping buildings.”

Users should be instructed to fill in meaningful comments about what they mapped, but helping them out with good default comments is always a good idea.

Detailed Instructions - This is where the majority of your detailed instructions will be placed and what we expect every mapper and validator to read carefully and follow.

See the below notes on creating good instructions.

Per Task Instructions - These will be displayed when a mapper selects a task and also has a special feature that allows Task specific URLs to be crafted based on the typical “slippy map” x, y, z coordinates.

Metadata

All of these fields should be filled out and will become non-optional in future versions of TM3.

Mapper Level - This is an indication of the difficulty of the mapping project. There are 3 options Beginner, Intermediate and Advanced. This setting is an indication to the mapper what experience level they should have to be most successful in mapping the project. It can be used in project list filtering and the suggested level can be required in the Permissions screen.

Type of Mapping - Used in project list filtering and helps mappers find projects they like to map.

**Organization **- Allows you to specify the organization the mapping will be used by. Used in project filtering.

**Campaign **- This allows you to group the project with other projects that are part of larger overall mapping effort. Used in project list filtering.

Priority Areas

Use the provided tools to draw areas that should be mapped first. You can have multiple priority areas for a Project. You can also change priority areas at any time.

During disaster mapping, early in the event, having a large project AoI and using priority areas to focus mapping as new information comes in is a best practice.

Imagery

URL Field - A field that takes a TMS URL that will passed automatically to the OSM Editor the mapper or validator uses. Please follow the example, it is very important it is formatted correctly to work in all editors.

License - Optionally, if there is a specific license required for the mapper to accept in using the imagery, you can select it here. If you need a licese that is not available, you can contact an administrator for the Tasking Manager installation and ask them to add it.

Oprávnění

Mapper Level - Allows you to require that a mapper is at the proper level to map on the project (Metadata screen above). Mapper levels can be set manually, but are automatically applied based on total changesets.

Require Validator Role - This allows you to require that people doing validation have been evaluated to be qualified validators. It is a peer review process to designate someone a Validator, Project Managers and existing Validators can mark any user as a qualified Validator.

Private Project - This restricts access to the Project to a list of Users. Users must have logged into the Tasking Manager at least once before they can be added to a project.

Settings

Default Locale - Allows the setting of default instructions language for a project.

Actions

Message All Contributors - Sends a Tasking Manager message to everyone who has marked a task complete or valid. It can be used to thank contributors and/or guide them to other projects in a portfolio/campaign. It should also be used before using either of the two Validate/Invalidate all Tasks options described below.

Validate all Tasks - This will mark all tasks to “Green” validated status, with the exception of tasks that have been marked as “Bad Imagery”

Invalidate all Tasks - This will mark all tasks to “Red” invalidated status, with the exception of tasks that have been marked as “Bad Imagery”

Delete Project - This will permanently delete the project from the Tasking Manager.

Clone Project - This will create a duplicate of the project except for the AoI which you will need to re-import or re-draw.

Instruction Notes

Please use plain language as your target audience may not consist of native English speakers.

1. 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 )
2. 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.
3. 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.
4. 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.
5. 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.

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:

1. Bing does not provide high-resolution coverage for your AoI.
2. Bing has considerable cloud cover in this area.
3. 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:

1. 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.
2. Make sure that all existing features which are also visible on Bing are aligned with Bing imagery, i.e. realign if necessary.
3. Align the alternative imagery to existing features (and thus to Bing) using the imagery offset function of the editor.
4. 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
• animovaný gif na zarovnání snímků v iD editoru
• the josm imagery alignment chapter in learnOSM

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.