I am not sure if it is a bug or not. Every evening I do an expert from WRL to import to Wavelog and I see that does not matter if I do a SOTA, POTA, WWFF, and maybe IOTA activity, that the adif export outputs in the SIG field word POTA and in the sig_info the correct output, see here:
If you are setting your logbook activity as SOTA and then when you export your logbook its putting POTA in the field then that is definitely a bug. Iâll reach out to the team and weâll double check and if its wrong weâll push a fix for it. Thanks for the heads up!
Maybe I explained it not well. Up to now no SOTA or POTA activities done so far, I am doing just QSOs with POTA, SOTA, WWFF activators, so I am a hunter. When I export my QSOs sig is always POTA does not matter if I hunt SOTA, POTA or WWFF activators.
I see, so for POTA/SOTA/WWFF you donât need to export your log to upload to those sites if you are just hunting and not activating however with that said, if the activity is being set to SOTA and a logbook is exported and POTA is in the field, it shouldnât be like that I donât think, so thatâs something weâll need to update.
exactly Brad, the only problem is that to SOTA I have to upload my log into server to do the matching and SIG should be SOTA instead of POTA to all QSOs that I make, but I am not sure about SIG use here.
So it looks like its working as expected. One issue I see is that in your account you just have one logbook âCT1DRBâ and its set to the default WRL logbook template but there is no âSOTAâ or âPOTAâ activity set. So when you export your logbook to an ADIF the only field that shows (without those activities set) is the âSIG_INFOâ field which has data like âDE-0093â, âHB/ZH-017â, etc. To set the activities youâll need to do one of two things. Either use your existing logbook and click the âmy activitiesâ button above the RST Sent field (see screenshot) and then select either POTA or SOTA, or you can create a new logbook and then set the activity. I would recommend leaving your current logbook as it is and then creating two new logbooks. One for SOTA and one for POTA and set those activities separately.
Since you donât upload your hunter logs to either POTA/SOTA, the default âPota Activatorâ and âSOTA Activatorâ logbook templates are geared towards activating vs hunting. As a member of WRL you get access to the custom logbook template creator that will allow you to create a custom logbook template that will give you the option to add/remove fields, rearrange them, add custom fields, changes themes etc.
Iâm going to dig into this a bit more as I think I might be missing something now that I think of it. Additionally Iâve went ahead and created two new logbook templates that Iâve set as âsystem templatesâ that should be able to be used by every user (regardless of member level). One is called âPOTA Hunter Templateâ and the other is âSOTA Hunter Templateâ. These have all the fields needed on the front end, Iâm going to have the team make sure that if a user has their logbook template set to one of these two new ones that when exporting the ADIF, it has the correct MY_SIG, MY_SIG_INFO, MY_SOTA_REF, etc fields in the ADIF.
maybe I am requesting a bit more than possible, but if all identifications are diferente among POTA, SOTA, WWFA, IOTA, etc etc, and WRL at spotting can identify each one if I overview spots here, could not be possible to âswitchâ internally to each activity and then use correct ADIF identifications ?
It seems easy but I know programming is another story.
Anyway, comparing with other logging softwares WRL is a bit better, as far as I know, in terms of operational features (I am an Air Force veteran and worked in communications ).
I have another idea, maybe a crazy one, instead to think about Templates, why not to play with the export option to verify which kind of data is about to update and to choose correct adif fields, to SOTA, POTA, WWFF, IOTA, and to include them into the export adif file ?
Just a non-possible idea but I am a bit crazy time to time.
