It's not a problem, unless the logged callsign isn't in the database. When the logged callsign is in the database, if you don't provide the information, the missing data is populated from what's provided in the database by the other operator's license entry (or their logbook operating location if they are logging on QRZ).
There are awards not just for activating and hunting unique parks, but they have their own WAS, there are awards for activating/hunting parks and operators multiple times, park-to-park awards, "late shift" awards for 0000Z to 1200Z contacts (good for the after-work crowd), and more. Activators help the hunters, and hunters help the activators.
qso not confirm Discussion in ' QRZ Site Community Help Center ' started by ZS4AW, .
ON QRZ but will not confirm the contact. Discussion in ' QRZ Site Community Help Center ' started by VK2RK, .
ON QRZ but will not confirm the contact. | Page 2 | QRZ Forums
KF8KI QRZ Staff EngineerQRZ HQ Staff QRZ Page Since you didn't provide the other callsign, I can't help beyond telling you that this is a problem that occurs when the user does not properly have their DX entity set in their operating location, found under settings > logbook properties. It's relatively common for things like DXpeditions and secondary callsigns where the logbook wasn't set up ...
Picture not displayed on my page. Discussion in ' QRZ Site Community Help Center ' started by N3UIH, .
W5AOS Platinum Subscriber Platinum Subscriber QRZ Page Any help anybody. I have not been able to export to LoTW since May 15. Still having this issue.