I’m trying to log two contacts I made with SOTA activators. I want to log them in my main (general) log book, but I don’t see any related fields, only POTA fields. Is there something I need to turn on in my settings? To reiterate === I am not the activator; I am a hunter who made two contacts, and I would like to document their SOTA locations (summits) and have those distances logged correctly and dispalyed correctly in the map graphic.
Thanks and have a great day! You folks are building great stuff!!
@KC1WZN First off thank you for the kind words! It REALLY means a lot to us!. To answer your question, It depends on the logbook template you used to create your main logbook with. Most likely its the ‘default WRL’ template (I just checked your account and it looks like all your non-POTA logbook are using the default WRL template) which doesn’t have all those fields by default. You can however change your main logbook to use a different template by clicking on the quick settings above the logging fields (see screenshot below). and then selecting a different template.
I’ve created a custom template for all users geared towards hunting. Its called ‘WRL POTA/SOTA/WWFF/IOTA Hunter Template’ that has all the various fields for hunting any of the activities. It will also export all the relevant/needed data for pota/sota/iota/wwff if ever needed. Since you are a premium member you also can access the custom template creator and create your own logbook templates if you would like. The logbook template creator allows you to added/remove fields, rearrange those fields, add custom fields, change the themes etc etc etc. You can access it via the ‘view templates’ link underneath the logbook template drop down (see second screenshot).
Once you’ve updated your logbook template for your main logbook you can use the ‘QSO Manager’ to move/merge the contacts into the logbook of your choice. I hope this helps! Let me know if you have any questions or need a hand.
Thanks for the help, Brad. I’m now re-configuring things to get the fields I want.
I did have another feature request concerning custom fields. As I see it, right now, the custom fields are text {string} only. What about different data types? For instance, if I create a “Mobile” field to just record if my contact was mobile, I only need a binary field like a check box. Also, this small data type will help you keep your cloud costs down .
@KC1WZN This is something we can look at adding after we’ve pushed our database upgrade. we are finalizing testing with it now. Once those change are released we have LOADS of new features on the board
.