Two weeks of SOTA activations on a 3 week holiday. 35 summits logged across 5 Associations/countries and hundreds of QSOs.
PoLo used very successfully for all of those activations. Thank you again to the team behind this superb tool.
One VERY TINY observation. The “New Operation” “Template for SOTA (nearest)” feature picked the wrong summit initially on around a third of occasions, meaning I had to delete and then re-add the summit ref when the list updated a few seconds later with the correct “nearest summit”. I can guess this is something to do with initial phone location fixes being inaccurate.
Suggestion: don’t add “nearest summit” until phone reports location accuracy is at or below 100m?
It’s not a massive problem at all, but just a low level suggestion for improvement.
Yep…. Only thing I could find “wrong” in 35 activations! It’s why I love it so much.
Now I think about it it was rather silly of me not to think of adding it manually rather than use the template. I suspect because mostly it worked (estimate 2 out of 3 times). I’ll try it manually next few times I’m out.
Further feedback on the issue with automated selection of the nearest SOTA summit when using a template.
As requested I’ve now tested selection of a nearest summit separately by adding it without a template. As expected this does work fine, but I’ve noted there is a short delay before the list populated and sometimes it finds the wrong summit, before correcting itself a few seconds later.
As initially explained, I think this might be because the app is selecting a “nearest” summit, before the location is refined in the phone.
Suggestion: display message “waiting for location accuracy to improve”, before displaying a summit if the error circle is larger than, say, 300 metres.