I’ve used HAMRS for two POTA activations, it’s excellent software and easy to use.
The ADIF file created by HAMRS correctly shows the location information (grid square) for the park I activated (which is different from my home station grid square). When I import the ADIF file into QRZ.com, the grid square data overrides the information on file for my home station, but nothing else changes. So the QSO record is wrong, because although it shows the correct grid square, it shows the “wrong” county and latitude/longitude coordinates for my activation. (And presumably if I were activating in a different state, it would also have the wrong state information).
QRZ support forum says:
I routinely upload to QRZ a “thin” record ADI file to QRZ having only Callsigns, Mode, Band, DXCC nr, UTC Date, UTC Time. There is no RST, frequency, etc. and it works. If that file had the location based fields in it, it should override the Logbook Properties fields for that record(s). Perhaps try it on a few records.
That seems to work for grid square, but not for other location data.
In the HAMRS community I saw another thread suggesting manually changing the QRZ Logbook Properties to reflect the state county and grid square where the activation took place before uploading the HAMRS ADIF file, and then changing them back to the operator’s home QTH after the upload is complete.
Is this the best available workaround? Since HAMRS is pulling complete geographical data for the park, can’t it insert the state and county into the ADI file as well as the grid square? Then that data should override the QRZ Logbook Properties for that activation.