[BUG] Cluster Location Error

[alanmcd]

Describe the Bug

TX5EU is being displayed in Noumea instead of correctly in region below French Polynesia

Environment

• OS: Windows
• Browser: Chrome
• OpenHamClock Version: 15.6.4
• Running As: Web browser

For Raspberry Pi Users

• Pi Model: [e.g., Pi 4 4GB, Pi 3B+]
• Pi OS Version: [e.g., Bookworm 64-bit]
• Display: [e.g., Official 7" touchscreen, HDMI 1080p monitor]
• Running in Kiosk Mode: [Yes/No]

Additional Context

It looks like it has the wrong sign of longitude. It's the mirror across the dateline. So this may be a sign of it happening for other locations as well

---

73!

[alanmcd]

Not sure how it can be in two locations at the same time either

[accius]

issue addressed in next release on Tuesday

[alanmcd]

After the update to 26.1.3, TX5EU is now all over the place and no where near its correct location

[accius]

well this is fun. looking into it

[accius]

okay, i see whats actually happening, these are dxpedition callsigns and since they have no map in my code, they fall back to the spotter locations. I am working on this now and will update.

[accius]

all future tx5eu should show up in the right place, as well as all future dxpeditions.... there will show some in france as its stuck in cache for a bit, but all new ones should show correctly.