Many of the use cases covered by this issue/PR are currently solved with hash
tags (e.g. #surveyme) and tools are currently made to take these into account.
Tools would need to be adapted to support tags as well.
The advantage of having tags implemented like this properly would be that there
could be an efficient API with which to filter notes. (Right now, this is the
_only_ advantage I can think of over hash tags and stuff.) For example:
- search for notes created by StreetComplete for certain quest types, to find
common issues (misunderstandings, missing answer options) with quests
- search for notes created by certain versions of StreetComplete, e.g. to find
notes that where perhaps created in error due to the above
- search specifically for notes that need e.g. survey. (However, this use case
would not be useful for StreetComplete, because StreetComplete downloads all
notes, anyway)
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5344#issuecomment-2491705313
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/5344/c2491705...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev
