Suggestion - Distance and State to Operator

Feature Requests
1

It would be nice that if when we are logging a station to use a logic like this:

IF Operator is at a POTA Park, Then, Set State and Distance to POTA Park, IF NOT in POTA, Set State and Distance to Standard address.

This would improve accuracy of log significantly.

mac

3 Likes
2

@KE8RRG This is how the logic currently set. The distance and mapping is based off of if the other user is at a park or not which is determined by the ā€œTheir Parkā€ field. Additionally if you are doing a pota activation (or sota, iota, etc) and have that activity set and your activity reference added (ie pota park) to your logbook it will use that location instead of your ā€˜saved locationā€™ or qth location.

Here is a screen recording showing this: Location and distance based on Park Data | Loom

Thanks & 73
Brad K4AZE

3 Likes
3

Thatā€™s fantastic. Just one more question: does that apply for Hunters? Not just activators. It would be great if it is the same for a Hunter. I contacted W1IP who was in FL in a park and the log logged him in CT. I see in my log now that he didnā€™t have a park registered. Just would like to confirm the same logic applys for Hunters.

4

Thank you Brad! Perfect! You guys think of everything!

5

@KE8RRG Yes the same logic applies for hunter. As long as you add in the park the other person is at in the ā€˜Their Parkā€™ field it will map it and log it correctly.

Thanks & 73
Brad K4AZE