One of the main long-term goals of the effort to improve geospatial functionality in ODK Collect is to support today's use cases for OMK (OpenMapKit) within ODK Collect and offer a smoother flow for users as well as a simpler setup procedure.
As I understand it, the use cases for OMK are about displaying an existing set of map features and letting the user select a feature to collect data about that feature using an ODK form. For example, one might want to label all the buildings in a given geometry collection as made of "brick", "stone", "wood", or "straw", where this label is selected from an ordinary ODK Collect question.
We're taking the first steps in that direction by supporting offline vector map layers in the geospatial widgets, which lets the user see a geometry collection while collecting data. The next step will be allowing the user to interact with that collection and make selections.
There are some open design questions here about exactly how the UX flow will work and how it will look. To inform our design, we'd like to work through some real-life use cases in detail, and make sure that the new design can support them well.
So, we'd like your help:
Does "launching a form associated with a selected map feature" cover the space of use cases, or are there other use cases beyond this description?
Could you provide us the details of previous OMK collection projects you've done? We'd like to know everything one would need to repeat your project, so we can do the exercise of determining whether our designs would be sufficient to successfully repeat the project. Ideally, that includes a description of the project and its goals, the map data you used and its format, the ODK forms you constructed and used, the resulting data you ended up with, and how that resulting data was used or meant to be used.
Very much appreciated!