Log4OM

It is my understanding that a new version of LotW supports multiple operating locations, without the need to create separate location objects. See info below. There is a special preference setting within the TSQL top menu.

My questions: If I create an ADIF that includes MY_STATE, MY_CNTY, MY_GRIDSQUARE and import it into Log4OM, will these fields be preserved without the need to mess with Log4OM's configuration for my home shack?

Will the Log4OM upload to LotW procedure preserve these fields and upload them correctly?

Thank you; this would be super useful to me, as I tend to operate portable from many locations and the LotW aspect of that is daunting.

explanation image: https://www.dropbox.com/s/wc4afu7cedudd3n/lotw.jpg?dl=0

KG6NRV wrote: 02 Nov 2020, 17:11

My questions: If I create an ADIF that includes MY_STATE, MY_CNTY, MY_GRIDSQUARE and import it into Log4OM, will these fields be preserved without the need to mess with Log4OM's configuration for my home shack?

They will be preserved in the logbook but will not modify the Log4OM configuration

Will the Log4OM upload to LotW procedure preserve these fields and upload them correctly?

The fields in the ADIF file created for upload will be preserved

Thanks, Terry. Then presumably LOTW will correctly locate the origin these QSOs. Do you know any way of testing that function?

KG6NRV wrote: 12 Nov 2020, 20:11 Thanks, Terry. Then presumably LOTW will correctly locate the origin these QSOs. Do you know any way of testing that function?

Bill,

I would create a test ADIF with one, two or a few calls, and import into Log4OM V2 and then proceed with a test.

"test ADIF" ... select 2-3 of the actual calls, etc..

.