I recently manually logged a POTA QSO incorrect for LOTW. The operator's home QTH is Pennsylvania and he was operating in New Jersey. When I uploaded to LOTW it was confirmed as a PA contact instead of NJ which the operator is also investigating.
Where in Log4om am I to log the correct state contacted where the POTA site located outside a operator's home QTH state since it is auto populated?
73,
Cliff-K4HCP
Logging correct state from a POTA QSO
-
G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Logging correct state from a POTA QSO
Info (F2)
For existing QSO's use QSO manager
All in user guide
For existing QSO's use QSO manager
All in user guide
73 Terry G4POP
Re: Logging correct state from a POTA QSO
Cliff,
If his LOTW confirmation came back to you as PA instead of NJ, that means he uploaded it with the incorrect state as his location. He should re-upload it as NJ. Your upload doesn't affect what he uploaded. Of course, you can always change his state in your log and re-upload it, but that won't change his upload.
73,
Jim N6VH
If his LOTW confirmation came back to you as PA instead of NJ, that means he uploaded it with the incorrect state as his location. He should re-upload it as NJ. Your upload doesn't affect what he uploaded. Of course, you can always change his state in your log and re-upload it, but that won't change his upload.
73,
Jim N6VH
Re: Logging correct state from a POTA QSO
Hi Cliff,
In LoTW two QSO records ‘match’ if the pertinent details are identical or close enough to indicate that both parties to the QSO consider it to have taken place.
An LoTW confirmation requires an exact match between the callsign you submit and the callsign your QSO partner submits. Band and mode have to match as well (CW, PHONE, DIGITAL), times must be close.
LoTW was designed to track DXCC, so I don't think the US state is mandatory. Nevertheless, it will take the information from your QSO partner and this will overwrite any details you uploaded (e.g. grid, state, CQZ, ITUZ, oblast, ...). Therefore, in many logging programs, you can define different locations you can assign to a QSO (e.g. for different states, grids, counties, ...) to make sure the information uploaded will match the operating location.
If the other station does not care and the callsign is matching the one in the QSO, most probably you will get some wrong data regarding state, county, ... - but still a valid contact. You only can ask the other station to correct the details and upload the log again.
73,
Claus
In LoTW two QSO records ‘match’ if the pertinent details are identical or close enough to indicate that both parties to the QSO consider it to have taken place.
An LoTW confirmation requires an exact match between the callsign you submit and the callsign your QSO partner submits. Band and mode have to match as well (CW, PHONE, DIGITAL), times must be close.
LoTW was designed to track DXCC, so I don't think the US state is mandatory. Nevertheless, it will take the information from your QSO partner and this will overwrite any details you uploaded (e.g. grid, state, CQZ, ITUZ, oblast, ...). Therefore, in many logging programs, you can define different locations you can assign to a QSO (e.g. for different states, grids, counties, ...) to make sure the information uploaded will match the operating location.
If the other station does not care and the callsign is matching the one in the QSO, most probably you will get some wrong data regarding state, county, ... - but still a valid contact. You only can ask the other station to correct the details and upload the log again.
73,
Claus
Claus, OE6CLD/DJ0DX/EI7JZ
