Why is SOTA Goat changing your callsign? What is it using to determine the bizarre and weird UK regional secondary locator and getting it so wrong?
If you spot by SMS and use the shorthands for <MYCALL> ! and $ then it will pick the correct RSL for all UK callsigns based on the summit ref you give. It’s smart enough to know how to modify any UK call whether it already has an RSL in the registered call or not and uses only the association code to make the change. i.e. if you say you are in Scotland it knows to put and M in the right place.
I haven;'t used SOTA Goat very much but I assume it uses predictive/autofill text (I have used SotaGoat before whilst operating in in Scotland), so it probably remembers both callsigns (MM6guy and m6gyu/p).
I did notice that on at least one spot I posted in G/NP, S. Goat automatically filled in my callsign as MM6GYU/P which I noticed and corrected before I pressed ‘post’.
Unfortunately it must have done this more than once but I obviously didn’t notice.
Unlike spotting with the SMS service Sota Goat doesn’t appear to link the correct callsign prefix with the correct country.
I think I’ll try using the SMS service next time. I’m pretty sure I registered with it as per Andy’s (?) instructions.
I spotted you on G/NP-010 with your correct callsign so there shouldn’t have been any problems on that summit.
I use SOTA Goat for spotting and you can set the default call before you go out and you can override it at anytime once you are out before sending the spot. I do this regularly when Dave G3TQQ and I go out activating together when we change operators.