If I have learnt anything from managing SOTA IT it’s that if you round things up or down, people complain about the lack of precision ![]()
Enjoy your 64-bit floating point goodness ![]()
If I have learnt anything from managing SOTA IT it’s that if you round things up or down, people complain about the lack of precision ![]()
Enjoy your 64-bit floating point goodness ![]()
For those activators who are less obsessed with activator points, that’s me, and slightly more obsessed with S2S opportunities, can you include the number of repeat activations by summit without a score of activators points. Yep multiple activations in 2025 for 0 points.
Example: VK1AD at summit VK1/AC-043 Mt Stromlo.
73, Andrew VK1AD
I was tempted, but I figured - nah, I’ve got this one ![]()
Fix building now (and also for the hyper precision one from G4TGJ)
Yes an interesting anomaly, basically the data retrieved back from activation information only shows the QSOs per the following band for the endpoint I’m using:
[“QSO160”,“QSO80”,“QSO60”,“QSO40”,“QSO30”,“QSO20”,
“QSO17”,“QSO15”,“QSO12”,“QSO10”,“QSO6”,“QSO4”,“QSO2”,
“QSO70c”,“QSO23c”]
Thought from looking at sotl.as at your activations, they are showing as 13cm as the majority for your logs, which agrees with your DB.
Interestingly the chaser endpoint I used covers a lot more bands.
I’ll look at what other options there are next year if I make another app ![]()
I get a “could not fetch your summ̶i̶t̶s̶ary! 403OK”
73, Martin - PE1EEC