Thank you @ahblake for sharing all these insights on what’s possible right now!
@Edmonds, it sounds like dynamic default likely does what you need in this case and should work today! You might also be interested in exploration we’re doing around showing existing geometry as context for shape/trace questions!
For those interested in displaying existing geometry as a reference while mapping new ones, we have a few open questions we’re exploring and would love your thoughts. If others have similar challenges, please share the scenarios you’re designing for and any feedback on the questions below.
Scenario examples
-
I'm capturing one of a farmer's fields, it's helpful for me to see the fields that have already been captured, especially if I'm not the one who captured the existing ones, so that I don't accidentally re-visit one or capture a geometry that overlaps.
-
I'm capturing the location of a household I'm visiting, it's helpful for me to see all households that have been visited so that I don't accidentally re-visit one
Open questions to better understand the needs
-
What would help enumerators understand that previously mapped geometry is reference, not something to edit?
-
When viewing a reference geometry, what (if any) additional information would be useful to access in the field?
-
Are there cases where enumerators need to see mbtiles or multiple sources of map context at the same time? If so, what are they and why?
-
How much control do enumerators need over showing or hiding reference geometries while mapping?
-
Are there situations where too much map context could interfere with the task?
-
When a map opens with both new and existing geometries, what should it prioritize showing? What is most helpful for the user to help orient?