From e5633039e2e429e3d048e14456e74158aff39ceb Mon Sep 17 00:00:00 2001 From: spwoodcock Date: Tue, 12 Nov 2024 12:55:42 +0000 Subject: [PATCH] docs: add extra faq section on why fmtm is unique --- docs/about/faq.md | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/docs/about/faq.md b/docs/about/faq.md index 518a6fc79c..ae24c983b0 100644 --- a/docs/about/faq.md +++ b/docs/about/faq.md @@ -19,9 +19,20 @@ already. FMTM is not aiming to compete with these tools, but instead has two goa when mapping an entire area of interest. It can be difficult to **subdivide tasks** and know **who is working on what tasks.**. FMTM should solve this problem. -2. Allow for coordinated field mapping outside of OpenStreetMap. Sometimes - OpenStreetMap is not an appropriate target for the collected data, so a data - flow outside of this ecosystem should be possible too. +2. Allow for coordinated field mapping **both inside and outside of OpenStreetMap**. + Sometimes OpenStreetMap is not an appropriate target for the collected data, + so a data flow outside of this ecosystem should be possible too. + +--- + +### What makes FMTM unique in this space? + +- Fully open-source. +- Manages both **coordination** and **data collection\*** in one framework. +- Roadmapping input from the rich HOTOSM community. + +- Note that the data collection portion is outsourced to the excellent + ecosystem of ODK tools. ---