Missed one SOTA spot on the internal SPOTS tab

PoLo - Issues & Ideas
1

Dear all

Just noticed here that one particular SOTA spot was not shown on the SPOTS tab within Polo:

a) from SOTLAS

SOTLAS Clipboard_11-23-2025_01
SOTLAS Clipboard_11-23-2025_011257×815 186 KB

and b) within Polo on the SPOTS tab

Screenshot_20251123_134309_PoLo
Screenshot_20251123_134309_PoLo1080×2340 271 KB

Is there a filter or select preventing that EA2CQ/P’s SOTA spot is shown within Polo?

Screenshot_20251123_134325_PoLo
Screenshot_20251123_134325_PoLo1080×2340 155 KB

The only filter in place here on my Polo installation is to select only Africa and Europe. Summit EA2/SS-055 is a part of continental Spain in Europe.

image
image1271×673 64.4 KB

And a newer spot from EA2CQ/P came in to SOTA only on 1247z what is after the above picture had been taken at 1243z (time stamp in Polo). And the 1234z spot has obviously not been deleted.

Is there a magic in this . . . ? :wink:

Thanks in advance for letting me understand,
and vy 73, Markus

1 Like
2

It does seem that this particular spot is the only one in you screenshots that has “DMR2SOTA” as the “source”.

I wonder if the SOTA website handles spots from sources such as that one in a different way, and it is not shared in the APIs we use?

It will be really hard to debug unless I look into it exactly when one of these spots is live.

If you see this happen again, do ping me on the discord chat server. Email or the forums will be too slow for me to have a chance to take a look before it expires.

3

I suggest that you contact one of the team, e.g. VK3ARR. They have probably a good database and the knowledge to investigate such a question.

Vy 73, Markus

4

Actually, upon review, I think the reason it’s missing it’s because the spot had been marked as QRT.

PoLo only shows active spots.

5

Thanks Sebastián, but I am not really convinced of this reason since the QRT spot for this SOTA reference came in only later (1313z, according SOTAwatch3 screen capture) vs. the earlier Polo screen capture taken at 1343 local HB9 time (= 1243z) where this activation still was active.

image
image1271×673 64.4 KB

IMHO, I always suggest regarding topics of 3rd party systems (like SOTA DB here) to contact the responsible persons of that system.

Vy 73, Markus

6

Then we’ll have to keep looking. Ping me if you see a missing spot again.

7

I’m sorry, but I cannot provide constant “looking”. That doesn’t make sense to me.

Vy 73, Markus

8

Luckily the data is still there. But I can’t see anything obviously wrong with it…

{
    "id": 214660,
    "timeStamp": "2025-11-23T12:34:28.087148Z",
    "activatorCallsign": "EA2CQ/P",
    "activatorName": "Iñigo",
    "callsign": "dmr2sota",
    "comments": "[DAGA]APRS",
    "frequency": 14.255,
    "mode": "SSB",
    "summitCode": "EA2/SS-055",
    "summitName": "Ollagon",
    "AltM": 371,
    "AltFt": 1217,
    "points": 1,
    "userID": 34612,
    "type": "",
    "epoch": "df44a4b1-cf88-46ba-b690-ea0ebe1f1103"
  }
9

Oh, wait.I think see the issue now type should be null, "NORMAL", "QRT" or "TEST". But it’s "", which we aren’t handling. Looks like the handful of dmr2sota spots are all sending that. We’ll look at fixing this.

10

Thanks, Steve - interesting. I suggest to liaise with the guys from the sending database, since it might be an error on their side, what should be corrected on the source.

Right, they had introduced this variation some time ago.

Vy 73, Markus