For Field Day 2026, when finished with my WRL FD Log i was looking at my stats and contact log map when i noticed when the other operator is located in a different state or section other than their fixed QTH based on their callsign, the logger maps it and shows the operater contact as being in their home location, not the location at time of the QSO also skewing the stats as well for the log. Has anyone else seen this and have a solution?
@KC3QOR Hey Willie,
Since we have no way to know where a user is operating from (unless they are activating from a pota, sota, iota, wwff location and are spotted) there is no way for us to set that location of the other user. Now if you know that they are in a different location and you update that data when logging the contact (or editing the contact) you certainly can update that information, but we can’t always know the exact location of every operator.
If the other person is spotted at a pota park for example, we pull the location of the park and map the user to that location instead of their QTH location because we know that they are activating that particular park, and have the park data available to map them properly.
I hope this makes sense.
Thanks & 73
Brad K4AZE
Yes it does, thank you!
1 Like
Just curious, but since the location (Section) of the contact is in the FD log, why can’t you use that rather than the QRZ location??
Thanks!
@KG5PVP it still wouldn’t be accurate as we don’t have the grid square. We map everything based off grid and lat/lon.
Sure we could determine “A” grid from the state but we would have to map it to the middle of the state because we don’t know the county, zip, or any other info that would allow us to map it correctly and it would be inaccurate, people would complain, etc.
Thanks Brad. I understand. I may have missed the fact that you use grid square.
Appreciate the follow up.
73,