The distance is incorrect on my recent chases, maybe I have the wrong Lat / Lon but I’ve checked it on a few different sites. A summit around 20km from me is showing at over 200km. Is there anything I can do to resolve this or shall I just wait for updates to the system?
Thanks in advance
73 de Mick M0MDA
You had set your location as somewhere in the middle of the North Sea. That would be OK if you lived on an oil rig/gas platform but ISTR you live near Leeds. I have added the missing -ve sign to your longitude in your home location and in your chase and it’s showing 23km for you now.
Is there no check that the chaser and activator entries for a QSO have the same distance?
I see there is one chaser in England who has worked one summit at 7591km.
That’s brilliant, thanks so much for that. When I added the - it said it was incorrect and wouldn’t save it, 73
In the words of the Grail Night “He chose poorly”.
If you knew it should be -ve and you were having issues entering a -ve number (could be user error, could be software error) and you left it +ve then you knew you were in the wrong place. Yet you failed to tell us of the problem so we could fix it. 
No. But as has been said several times, part of the rational for a challenge involving distances etc. was to give the GIS code a code workout and also to get the scabby location data made much less scabby 
Taking <1sec to render the page for me.
DB CPU load looks OK, the big peak is when we write out an approx 10GB backup file.
There was a burst of many simultaneous connections. The load was sitting around 8 connections per node and shot up to around 50 connections/node for 5 mins. That’s indicative of something bashing the system a little which may have explained why you got no results.
I am getting the same, just shows loading.
Tried earlier this afternoon and just checked now, still the same.
I am using Safari
Edit: chaser results working ok.
Yes, bad clicking and I looked at the chaser page. Now everyone will be checking to see if it’s working for them making whatever is unhappy a lot more unhappy.
EDIT:
There’s nothing locked on the DB engine, it’s working away and doesn’t seem abnormally loaded. The API servers are spinning away serving requests and other DB pages are loading.
Phase of the moon? Putin? Trump? I’ll wait for Andrew to awaken and see what he thinks.
W6 is experiencing the same issue. Did we break it?
At work we used to joke that a cosmic ray shower was the cause of a one-off inexplicable problem that was now working ok. Turns out it wasn’t so far fetched.
SEU is the ‘NASAism’ for them; single-event upsets.
I have had the privilege of programming for hardware designed to operate in neutron, γ-ray and x-ray rich environments. Considering why hardware was designed the way it was and the implications was somewhat chilling and disconcerting.
Someone entered some dodgy maidenhead data that should have been better scrubbed - but it got converted to some far out of range longitudes that the DB function that calculates distance correctly said, “Uh uh, no thank you”.
I’ve corrected the relevant entries (there were three), and I’ve added some code to fix that and will upload once I’ve written all my tests and they all pass.
I’ve just re-read the scoring format in the first post in 2026 SOTA Challenge (Part 1). BTW: is the reflector post the golden definition or has it appeared somewhere on www.sotadata.org ?
As I interpret it, I will get a unique summit multiplier just once (during the year), i.e. on the first activation of a particular summit. However, if I activate that summit again, although I don’t get the summit multiplier, I do get the new chaser-specific distance points for valid QSOs on 2m or 70cm CW or SSB.
Would someone confirm this is correct or not.
For example, I didn’t get any 2m CW QSOs on G/LD-056 today [only 2m SSB ones]. I assume I can return to that summit (multiple times if I wish) in 2026 and get more 2m/70cm chaser-dx points.
I assume the total points awarded associated with multiple activations of a particular summit is the same as though all the QSOs had happened on the first and only activation.
I hope this is true, otherwise there would be no incentive to revisit a summit to do the other band or mode not attempted or achieved on the first activation.
Only with unique callsigns. So once you have worked M4ABC from G/LD-056 you won’t get any new credit for working him again from the same summit. If he is at a different location then you will be credited with the furthest distance.
Indeed, I chased Tom EYP on his favourite hill twice & received no Challenge credit for the second chase. John.
Edited-just realised that’s the reverse of the above situation, but the principle works both ways.
Not a bug but rather a confirmation of the algorithm working as intended:
On 3 Jan I completed a 2m SSB S2S from VK1/AC-008 with @VK1DA who was operating from VK2/ST-053. Distance is 81km.
Yesterday I completed a 2m SSB S2S exchange from VK2/SM-093 with VK1DA again at VK2/ST-053 (his local summit) where the distance between summits is 102km.
For my 2m Chaser Challenge km aggregate the greater of the two S2S distances (102km) is applied and the 81 km S2S distance is removed retrospectively, or is the difference applied? Either way the algorithm is working.
Andrew VK1AD
@VK3ARR can you check serial 2 please. 19360 km is a tad optimistic for a first 2m SSB chase.
Andrew VK1AD