Average a waypoint?

[wwbd 9]

The other day I updated one of my hides with a new location about 50' from the original. Is there a way to average a waypoint with multiple samples? Sometimes just grabbing coordinates from one sample can be off by quite a bit. This of course would be helpful when placing new hides as well. I ended up using my old caching app to average out the waypoint which just keeps taking samples until you tell it to stop. Maybe I missed this somehow in Cachly?

[Nic Hubbard 642]

This isn't a feature yet in Cachly, but we have it on our list.

Were you thinking this should be an option when you create a Waypoint and when you use the Save Location option?

[wwbd 9]

Yes, that sounds about right. On the Add Waypoint screen.

That reminds me, it would also be nice to be able to have the coordinates available in one line somewhere in the waypoint so they can be copied and pasted into a log. That would be helpful in various scenarios like when you find that a coordinate is way off and you want to state an updated coordinate in your log. Similar to how you can copy the coordinate from the Additional Information screen.

[Nic Hubbard 642]

1 minute ago, wwbd said:

That reminds me, it would also be nice to be able to have the coordinates available in one line somewhere in the waypoint so they can be copied and pasted into a log. That would be helpful in various scenarios like when you find that a coordinate is way off and you want to state an updated coordinate in your log. Similar to how you can copy the coordinate from the Additional Information screen.

Great idea. Will get that added!

[wwbd 9]

Is the ability to average a waypoint still on the todo list? Just wondering...

[Nic Hubbard 642]

12 hours ago, wwbd said:

Is the ability to average a waypoint still on the todo list? Just wondering...

Sort of. From much research I have done, averaging waypoints on mobile devices doesn't help all that much.

[rragan 200]

Averaging in Geosphere never gave me any number but the original one displayed no matter how many samples. If I walked away and came back it would change some. Averaging multiple samples taken between walk away and come back might be better. It's almost like once the phone has coords and you are not moving it never bothers to try and see if they have changed. Unlike a GPSr. 

[Nic Hubbard 642]

23 minutes ago, rragan said:

It's almost like once the phone has coords and you are not moving it never bothers to try and see if they have changed. Unlike a GPSr. 

This is correct. If you are not moving at all then iOS likely won't send any more coordinate updates (once a good accuracy is returned). This is to save power.

[rragan 200]

So an iOS averaging feature would look more like collecting multiple location markings with leave/reapproach cycles and then average that set of readings. 

[Kyzabra 22]

While on this topic, can you add this to the "add coords" feature while logging. Whilst caching yesterday, we were trying to add "better" coords to a log for a cache but found the built in feature only allowed for entering of coords we obtained from a second device or app. 

[rragan 200]

Thinking more on averaging, would cycling low resolution back to high over and over make ios retake the location? That would beat manually taking multiple samples. 

[Nic Hubbard 642]

14 hours ago, rragan said:

Thinking more on averaging, would cycling low resolution back to high over and over make ios retake the location? That would beat manually taking multiple samples. 

I am not sure this would help. However I think turning on and off location services and waiting for a location fix would likely do the trick. I have noted this in the feature request in our internal tracker.

[Bolling 99]

14 hours ago, rragan said:

Thinking more on averaging, would cycling low resolution back to high over and over make ios retake the location? That would beat manually taking multiple samples. 

More samples is more work but I personally think it's the better approach when hiding a cache.