POTA and SOTA hunting

When you log as hunter a POTA contact which was spotted on https://pota.app/ recently, then it fills automatically the field “Their Park” and “Grid”. This is awesome! Great feature.

I would love it, if the same feature would be realized for SOTA contacts, too.

SOTA spots:

73 Pepe

6 Likes

@HB9EVT Hey Pepe, yes we can add this feature. I’ll add it to our list.

Thanks & 73
Brad K4AZE

5 Likes

Great call out Pepe!

1 Like

I’m seconding Pepe’s request here.

I’ve just hunted a number of SOTA activators today in the Ny Adirondacks.

Being able to add them and their true SOTA location, not just their home QTH, would be wicked great!!

You people ROCK!!

Todd Poole

KC1WZN

2 Likes

@KC1WZN Yes as stated previously we’ve got it on our list and will be implementing this very soon once we release our database upgrade changes.

Thanks & 73
Brad K4AZE

3 Likes

I agree and it would be even better if it auto filled in the frequency.

1 Like

@KE5FAR Yup its on our list. If you are using the spotting tab inside your browser and double click a spot it pulls in the frequency currently as well as the other data.

Did I glean the steps correctly?
From the spotting tab, double click on a spot.
Now go to your logging tab, open a logbook, enter the call sign from memory or compare it to the POTA.APP, and I got a call sign match, no park, no frequency, no band or Mode filled in.

Without using the Spotting tab, it almost always fills in the information on the first contact, then it sticks, doesn’t refresh.

If I got the steps right, in order for it to work you would need to be able to click on something from the list view and increase the refresh rate. We don’t hunt by their location on a map. We sort by frequency and tune through the band.

1 Like

@KE5FAR

No, from inside your logbook (see screenshot below), click the spotting tab. From there you can just double click the spot and it loads the callsign, park info, etc into the logging fields.

If you are entering a callsign manually, it will auto fill the information if that spot is already spotted/listed in the spotting tab.

I hope this makes sense.

Thanks & 73
Brad K4AZE

Hello all. Sorry if this is not the correct place for this question but it kind of goes with the OG question. I am using a Flex 6400 with CAT control enabled. When I click a POTA should it change my radio to the frequency? The app within flex does so it would be nice if your app did as well. Currently I manually tune to the frequency or find the POTA I hear in the list.

Great app and thanks for all you do making logging great again.

Curt AC9HO

P.S. it says I am a free member but I did sign up for the basic this weekend.

1 Like

@AC9HO Yes, you just need to double click the spot in the spotting tab inside your logbook and it will pull the callsign and data into the logging fields.

Thanks & 73
Brad K4AZE

1 Like

Thank you for the reply Brad. I understand double clicking will fill all the log book fields which is very nice. What I am asking is it supposed to use CAT to tune the radio to the frequency the POTA spot I double clicked on? Currently mine is not.

1 Like

@AC9HO Yes it should. what radio are you using it with? Also note, we are going to be pushing an few updates to the cat control app either later today or tomorrow. Make sure to grab the latest update once its released.

Thanks & 73
Brad K4AZE

1 Like

Ok will do the updates asap. Thanks for the heads up. I am using a Flex 6400 with smart SDR for Mac. I also have a Maestro and the CAT feature currently does not work with that as far as I know. At least I have not figured out how to get it to work yet.

Does it do that on WWFF as well?

What happens when you have a POTA and a WWFF logbook set up, how does that work?

It will be my first joint POTA & WWFF park tomorrow.

Secondly, when I complete “Club” POTA activation and D/L the ADIF, I have to open the ADIF file up and change the “Station_Callsign” so I can upload it to POTA on the Club POTA site.

Is there a way to pick that up when creating a new Logbook?

If it isn’t a Club activity then it works as designed with my call in both the “Operator” & Station_Call sign” category.

Joe