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.
More details can be found here: overview, timeline, docs page, and the FAQ.
- 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, and generate a QR code that is opened in ODK Collect.
- User navigates to the feature and fills out the XLSForm survey, then submits.
- The submissions are collected by ODK Central, which feeds the data back into Field-TM, for cleaning, conflation with existing data, and pushing back to OSM.
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.
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
- Frontend Typescript development
- Documentation writers
- UI / UX designers
- Testers!
- XLSForm creators
- Mobile developers
Please take a look at our Documentation and contributor guidance for more details!
Reach out to us if any questions!
To install for a quick test, or on a production instance, use the convenience script:
curl --proto '=https' --tlsv1.2 -sSf https://get.fmtm.dev | bash
Alternatively see the docs for various deployment guides.
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) | Expected v2025.2.0 |
β | π₯οΈ user role management per project | Expected v2025.2.0 |
β | π₯οΈ inviting users to projects via invite link | Expected v2025.2.0 |
β | π₯οΈ optional private projects to restrict access | Expected v2025.2.0 |
β | π± fully translated mapper UI and survey in any language | Expected v2025.2.0 |
β | π± custom Field-TM deployments with updated branding | Expected v2025.2.0 |
π | π± fully offline field mapping (local-first design) | β |
π | π₯οΈ simplify project creation with basic / advanced workflows | β |
π | π₯οΈ pre-defined OpenStreetMap forms for easy OSM mapping | β |
π | π₯οΈ integration with other mobile apps: EveryDoor, StreetComplete | β |
π | π₯οΈ integration with other ODK server types: Ona.io, Kobo | β |
π | π₯οΈ multiple approaches to task splitting algorithm | β |
π | π₯οΈ improvements to the validation criteria and workflow | β |
π | π₯οΈ export (+merge) the final data to OpenStreetMap | β |
π | π₯οΈ better data visualisation and export options | β |
π | π₯οΈ Field Admin role | β |
Note
π± for mobile / mappers
π₯οΈ for desktop / managers / validators
A more developer-facing roadmap can be found here.
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: