Combine "capture location" and "drop pin" tasks

[gino-m]

The idea is that the capture location and drop pin tasks would be combined into a single "Add a point" task, with an option set by the organizer to "Capture data collector's GPS location" or "Allow data collectors to use their GPS location or to place a point anywhere on the map"

Details:

• The location lock will be on by default when the task is first opened.
• If true, the user can pan the map to disengage location location (current behavior of "Drop pin").
• If false, the location lock will be disabled, and the cannot pan/zoom the map (current behavior of "Capture location").
• The tooltip will be the same as it currently is for "Drop pin", but when location lock is on will also show info shown in "Capture location" task.

Related web FR:
google/ground-platform#2173

[anandwana001]

@gino-m
Can we add more details to this?

I think this also needs a parallel web ticket? Do we need to update proto too?

[gino-m]

[@gino-m](https://github.com/gino-m) Can we add more details to this?

I think this also needs a parallel web ticket? Do we need to update proto too?

Added details to PR description. Please let me know if you have any questions!

[gino-m]

@vittorino and I spoke 🥳

[gino-m]

Notes on discussion:

• @jo-spek reports that the GPS lock behavior is not generally understood by data collectors. @gino-m suggests a text label / CTA to make this clearer. @amegantz @vittorino can you help here. @kenstershiro to create a FR.
• @jo-spek simplifying and allowing multiple geometries per submission would make things easier to understand, ie if there's no special magic "add site" task.
• @jo-spek says ideally we would always capture location in the background as metadata. @gino-m I suggest we automatically capture location when data is submitted. @jo-spek suggests we only capture location automatically on geometry and photo tasks.

[jo-spek]

Overall, people are already successfully geolocating, so the below suggestions are not as pressing as may seem. Regardless, the "Capture location" task keeps getting people confused and oftentimes is considered the same as "Drop a pin" and it would be good for completeness to find a better implementation long-term, potentially post GA.

On the GPS lock: I only recognized that this is a thing in regular Google Maps for the first time today. Ground is quite a different case because it is used for actively mapping plots and not just reading maps. Having a button, e.g., with an actual lock + satellite symbology might go a much longer way for users to understand it.

Here is my idea:

In survey creation, the survey organizer can select between "Drop Pin" and "Draw polygon". Next to it, there is a slider "allow free placement". If that one is ticked, the data collector will be able to freely draw, as is currently the case.

If it is not ticked, the data collector will have to go exactly where the pin shall be located, or walk around the field, registering each corner, respectively.
In both cases, during the geolocation task, the data collector will see the target lock button (actual lock + satellite). However, if free drawing is not permitted, it will be greyed out, signifying that it is activated and cannot be deactivated. If free drawing is permitted, the data collector can activate/deactivate it at liberty. If target lock is activated (either imposed by the survey organizer or by choice of the data collector), the 15m accuracy threshold will apply.

In terms of "Capture location" in the background: Did you ever see what geolocation looks like in Kobo Collect? It tells you to wait and when the accuracy threshold is reached, it will automatically collect the point. A potential implementation in Ground Android could be: When arriving at the geolocation task, the map view is slightly greyed out and there is text saying "Please wait while the GPS location is calculated..." (or similar). Once the accuracy threshold is reached, the current location is captured in the background and the grey-out is lifted so that the data collector can proceed to do the actual geolocation task.

I hope the suggestions are clear @gino-m. Excuse the mediocre graphics :D