While it’s cool that the grid square populates automatically based on call sign, another cool idea would be that if you put in the POTA park ID it would add that to the QSO map.
As a hunter, that would be nice addition. I’ve been adding the park IDs into the field were the grid square is located in hopes that it’d eventually do that.
Is there any plans to do so, or am I doing this wrong?
Maybe? What I was hoping could happen is that if I put in the park ID it’d instead use that for the activation location.
Currently it pulls the grid square from the callsign, which most of the time would be fine — but if that activator lives in California, but does the park activation in Wyoming, wouldn’t it be more accurate to say I worked them in Wyoming?
I think as it stands currently in the logbook it’d say “California” regardless of I put in the park ID or not, since it’s pulling gridsquare data elsewhere.
I think they had a feature with the latest major release that pulled location data from a POTA spot if a current POTA spot for that station was detected. It appears that this may not be working currently. Possibly something went awry when switching HamDB APIs? Is this a planned feature outage @WP3C and @N0WRL?
I understand, it is one thing to have the box when one operates from a POTA and another when one is a POTA hunter using the normal logbook. I will report this to the team. Thanks Chris
Good to know! I figured you all had to either have thought about this scenario, or it was on the roadmap. Love the web app, and the iOS app looks great.
Thank you so much for the support and being a Founding Member! It’s thanks to folks like you that we can even afford to do this and keep putting our time and resources behind it to fix this stuff. We will 1000% make you proud!