README.md
May 11, 2026 Β· View on GitHub
Field Tasking Manager (Field-TM)
Coordinated field mapping for Open Mapping campaigns.
| CI/CD |     | |
|---|---|---|
| Tech Stack |      | |
| Code Style |     | |
| Quality |   | |
| Community |   | |
| Other Info |      |
Building on the success of HOT's Tasking Manager, a tool for coordinating remote digitization of map features, the Field-TM was conceived with the purpose of tagging the features with field-verified information.
While there are many excellent applications for tagging map features already, the Field-TM aims to solve the problem of coordinating field mapping campaigns.
How Field-TM Works
- Project is created in an area with three things:
- Data extract: the features you want to map, say building polygons.
- ODK XLSForm: the survey for mappers on the ground to fill out for each feature.
- Task areas divided by feature count and linear features (e.g. rivers, roads).
- Users assign a task area for themselves, then map using ODK Collect, ODK Web Forms, or QField.
- User navigates to the feature and fills out the XLSForm survey, then submits.
- The submissions are collected by ODK Central (or QFieldCloud), which feeds the data back into Field-TM, for cleaning, conflation with existing data, and pushing back to OSM.
Usage of ODK
This project relies heavily on the ODK ecosystem underneath:
- XLSForms are used for the underlying data collection survey. The fields in this survey can be mapped to OpenStreetMap tags.
- ODK Central is used to store the XLSForm and receive data submissions from users.
- ODK Collect is a mobile app that the user submits data from.
Contributing ππ
In the wake of the 2010 Haiti earthquake, volunteer developers created the Tasking Manager after seeing a similar coordination challenge for mapping areas without existing data.
Now with over 500,000 volunteer mappers, the Tasking Manager is a go-to resource for volunteers to map collaboratively.
To aid future disaster response, we would really welcome contributions for:
- Backend Python development (Litestar + HTMX)
- Documentation writers
- UI / UX designers
- Testers!
- XLSForm creators
Please take a look at our documentation and contributor guidance for more details!
Reach out to us if any questions!
Install
Use one of these supported paths:
# Local development
just config generate-dotenv
just start dev
# Production install
just prep machine
just config setup
just start prod
just start prod presents an interactive version selector and checks
out the chosen release tag automatically.
See INSTALL.md for requirements, or the full Production Deployment guide for details.
Roadmap
| Status | Feature | Release |
|---|---|---|
| β | π₯οΈ project area splitting avoiding roads, rivers, railways | Since v2024.4.0 |
| β | π₯οΈ XLSForm survey generation in ODK Central | Since v2024.4.0 |
| β | π± mapping of project via survey in ODK Collect mobile app | Since v2024.4.0 |
| β | π± locking & unlocking of tasks to coordinate mapping | Since v2024.4.0 |
| β | π± download base imagery & geolocation for in the field | Since v2024.4.0 |
| β | π₯οΈ view mapper submissions in the Field-TM dashboard | Since v2024.4.0 |
| β | π’ Beta Release | Since v2024.4.0 |
| β | π₯οΈ & π± basic user tutorials and usage guides | Since v2024.4.0 |
| β | π± open ODK Collect with feature already selected | Since v2024.4.0 |
| β | π± live updates during mapping (if online) | Since v2024.5.0 |
| β | π± features turn green once mapped | Since v2024.5.0 |
| β | π± navigation and capability for routing to map features | Since v2024.5.0 |
| β | π₯οΈ organization creation and management | Since v2024.5.0 |
| β | π± better support for mapping new points, lines, polygons | Since v2025.1.0 |
| β | π± seamless mapping in the same app (Web Forms, no ODK Collect) | Since v2025.2.0 |
| β | π₯οΈ user role management per project | Since v2025.2.0 |
| β | π₯οΈ inviting users to projects via invite link | Since v2025.2.0 |
| β | π₯οΈ optional private projects to restrict access | Since v2025.2.0 |
| β | π± fully translated mapper UI and survey in any language | Since v2025.2.0 |
| β | π± custom Field-TM deployments with updated branding | Since v2025.2.0 |
| β | π± | v2025.3.0, removed |
| β | π₯οΈ integration with QField | v2026.1.0 |
| β | π₯οΈ multiple approaches to task splitting algorithm | v2026.1.0 |
| π | π₯οΈ pre-defined OpenStreetMap forms for easy OSM mapping | β |
| π | π₯οΈ integration with OSM mobile apps: EveryDoor, StreetComplete | β |
| π | π₯οΈ integration with ChatMap | β |
| π | π₯οΈ integration with HeiGIT Sketch Map Tool | β |
| π | π₯οΈ integration with other ODK server types: Ona.io, Kobo | β |
| π | π₯οΈ export (+merge) the final data to OpenStreetMap | β |
| π | π₯οΈ instructions for how to best visualize ODK data within QField | β |
Note
π± for mobile / mappers
π₯οΈ for desktop / managers / validators
Contributors β¨
Here's how you can contribute:
- Open an issue if you believe you've encountered a bug.
- Make a pull request to add new features or fix bugs.
Thanks goes to these wonderful people:
