Wrong summit selected at start of operation - GPS not waiting for accurate position

PoLo - Issues & Ideas
1

Hi Sebastian,

When starting a new operation (for SOTA) very often the wrong summit is selected as PoLo is not waiting for an accurate lock and picks the first coordinates. Those often come from the connected celltower (A-GPS) and not from the GPS of the device.

I see that

Geolocation.getCurrentPosition

has already enableHighAccuracy enabled but that is not enough as it seams?
Any idea how this could be improved? Maybe use the watchPosition() function instead and let is run for some seconds until it does not change anymore? Or put down the maximumAge to 0 ? So that it is forced to get a new location?

Thanks a lot
73 Joe

2

I’ve experienced this problem too. Been meaning to look into how to address it. Your pointers are very helpful.

2 Likes