Feature Request: get an "Average" coordinate when picking an Annotation

[Cat]

The "Annotate" function to store a coordinate only grabs the coordinate found in the last gps reading (often inaccurate), but it would be nice to get an "Average" coordinate: similar to what a surveyor would do, start gathering multiple coordinates, while the user lets it run in a fixed location as long as they need, and when finished it stores the average of all those gathered points.

We should find a way to implement it in a simple way, maybe something into the Annotation dialog.

Time for ideas, mockups, proposals.

[Rob Barnes]

Hi. I am Rob and I am the original requester of this feature. I just want to add some additional ideas. I use this app to plan development of my homestead, such as documenting natural formations, property line pins, soil test locations, geocaches, future clearing for roads and buildings. I export the data to kml and import to Google MyMaps. I recently used another app to do accurate point averaging to record the corners of two buildings I am planning. That app is named "GPS Average". The good things about that app are: it graphically shows all the stored point locations with respect to the average point, so you can see how much the point collection drifts while collecting, and it gives you a button to 'reset' (delete all previously collected points). What's not good about the app is that it will not export your list of averaged (and labelled) points to a kml file, but you can only 'share' each point individually, which is terrible when you have a collection of many points to export. Check out the app to get some ideas. I think this GPS Logger app can do a better job of point averaging. Thanks!

[Cat]

Hi Rob,
As a first thinking about a possible implementation of the feature, we might add two buttons on the Annotation dialog:

1. Pick a single point (in case the user would re-pick the coordinates of the annotation without close and reopen the dialog)
2. start / stop the averaging of points.

The first click could start the averaging of the FIXes, the second could stop the process. A third click could discard the previous data and restart the averaging process.

About the data stored, I thought that we could save only the averaged result, and not all the points used to obtain it.
Could someone be interested to have all the samples used for obtain the averaged annotation?