I was expecting to see all 1240Mhz and above (there are none of those) chases listed.
Instead I only see the chases which were summit to summit. I originally thought that this was down to location information not being implemented until the 2026 challenge. But recently I have worked a few summits on 23cm from home and these were not listed either.
There does seem to be a work around by editing the chaser log and in the comment section plugging in %QRA%IO83QN% as the comment. This has the effect of changing the my location latitude and longitude values
Qso before editing
and after editing (and now showing in the microwave chaser log)
I’m not worried about the loss or gain of a km or so, just its a bit counter intuitive that the system already “knows” my location when at home, and that when activating the comments is normally used for the location of the qso partner rather than my own.
Is it just a function of the fact I enter qso’s manually (or 1 click on sotawatch) rather than uploading?
Now I know to enter the locator in the comments its no big deal either, just an oddity to enter less correct information to overwrite the more correct information.
Not to worry, now I know what to do its not a big issue.
Its not like I needed to do a lot of back tracking to edit the logs as I only started on 23cm late last year.
I’m guessing that once this year’s challenge is done, and the distance calculation code has been stress tested to death there will be a few updates to realign stuff.
I suggest it is not a reliable assumption that a chase occurs from the chaser’s profile-defined home qth. Especially on microwave bands where activity days encourage people to go out to good vantage points where they will make contacts, instead of operating from home where contacts are rare. Introduction of a qth locator for the chaser in a standard format would be useful.
The vk portalog software offers the option of automatically including the chasesr’s location based on the gps receiver in the tablet or phone. This data is then included in a standard ADIF field. The corresponding data field in a csv is not defined so we find we are using the comments field for yet another bit of data that is then unsearchable (readily).
With the introduction in the last decade of more affordable portable equipment for 23, 13 and 9 cm usage of the microwave is climbing so the ability to recognise readily the actual chaser location will become increasingly important.
