Expand SOTA chasing support to look up summit gridsquare

Currently when using the SOTA template, the gridsquare from the lookup provider (QRZ/hamqth) gets populated even when a SOTA activator is on a summit and the summit designator is filled in.

It seems like it would make more sense to populate the SOTA summit gridsquare for the contact, which is accessible from the same API that is pulling in the summit name? That is the same behavior of cloudlog, otherwise your log will have incorrect gridsquares when you can make a pretty safe assumption that the activator is in the summit’s 6-digit gridsquare when you are chasing them.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.