I can’t quite figure out whether, in some cases, WRL is holding and passing an incorrect County or Grid Square to QRZ despite a POTA location, or perhaps it’s not passing that information at all and QRZ is auto-assigning the data corresponding to the individual’s license address. I’ve discovered this by looking through several QSOs that QRZ deems ineligible for awards due to mismatched data. In many cases, the County or Grid Square in “You entered” (which came over from WRL) matches the operator’s home QTH, but the “Other Party Entered” data corresponds to the location of their POTA site. In WRL’s QSO Manager, I can see that the POTA park is properly assigned to the QSO.
@W9TEF We pull all the pota spot data directly from the pota site so if a contact shows up in the spots tab and you log that contact the location (grid, etc) will be based off the park that they are at.
However if you log a contact that isnt’ on the spot page and you do a callsign lookup its probably pulling the users qth tied to their callsign that is provided by QRZ (if you have QRZ callsign lookup enabled) which is most likely where the mismatch is coming from.
One thing im thinking about now that we’re talking about it, is that we could set the location of the QSO based on the ‘Their Park’ data that gets entered when logging a contact, if you enter that information during the QSO and over ride the grid from the call sign lookup.
We’d have to make sure that doesn’t get messy though, let me talk to the team about it and get their thoughts.
Thanks & 73
Brad K4AZE
1 Like
@K4AZE Thanks for looking into this; you might be on to something with it being the ones that I manually enter (since I don’t have this problem with all my POTA QSOs, just some subset. I can’t figure out quite what the subset is, but “manually entered” is a good start–especially since I had several on 10/17 and those *might* have been the Park-to-Park ops that hunted me while I was activating.
I haven’t been using the spots tab (I haven’t gotten the hang of using the tab on my relatively small resolution Surface Pro I use for logging, and I don’t like that I lose my place when the panel refreshes regularly), but I do see the info often get auto-populated when I put in the frequency and call sign.
Seems logical that the “Their Park” data should be the highest authority on where the operator is at the time.
Your comment about “if you have QRZ callsign lookup enabled” also makes sense–because my link to QRZ broke with that bug, a few days ago, and I don’t think I have any errored QSOs from that period, but they resumed when I set QRZ back up.
On a separate note: I tried to reply to this thread a few days ago via email, and I got a response with “Email issue – Unknown To: Address” as the subject line; even though I replied directly to the message I got with your post in it. Should I make that a separate bug report?
Thanks, as always!
1 Like
@W9TEF Nah, you can just reply directly here.
1 Like