Option to send new spots up to xOTA providers #95

New issue

Open

opened 2026-01-11 10:32:34 +00:00 by ian · 0 comments

ian commented

2026-01-11 10:32:34 +00:00

Owner

This should be user toggleable (and persisted to local storage). It should replace spotting into the local database when used, so we don't get a duplicate spot back from the provider. It should trigger an immediate refresh of the provider to get the new spot back again (for http providers).

Maybe send to all existing spot providers, have them implement a new method and look at the SIG of the new spot to see if they should send the spot or not? This would allow the user to only have to care about the SIG, not about how we post it to multi-programme sites like GMA and PnP.

Add CAPTCHA or similar to prevent bot abuse from the web UI.

Spotting to POTA is already handled in Field Spotter so should be possible to just copy this approach across.

Spotting to GMA is documented: https://www.cqgma.org/api/doc/apigma_spot.pdf We (or the user) need a GMA account, and to send the password in plaintext(!!)

Spotting to SOTA must be possible (PoLo does it), I think this needs a proper auth flow so might be quite difficult to manage secret storage?

Spotting to HEMA is covered in the original email from the team.

Spotting to WWFF should be possible, need to look up the Spotline docs or copy from PoLo.

Spotting to WWBOTA is possible through its API.

Spotting to Parks N Peaks is possible via POST, see https://www.parksnpeaks.org/api/#Spot - requires an API key.

Spotting to ZLOTA is supported via POST, see https://ontheair.nz/api

Spotting to WOTA TBD. M5TEA wrote a new spotting app recently so he should know how, if he's willing to have it added to Spothole.

Spotting to TOTA/xOTA low priority, should be possible but realistically no-one is making TOTA spots through Spothole.

Spotting to RBN, APRS-IS and UK Packet Net from Spothole doesn't make sense, so these are out of scope.

This should be user toggleable (and persisted to local storage). It should *replace* spotting into the local database when used, so we don't get a duplicate spot back from the provider. It should trigger an immediate refresh of the provider to get the new spot back again (for http providers). Maybe send to all existing spot providers, have them implement a new method and look at the SIG of the new spot to see if they should send the spot or not? This would allow the user to only have to care about the SIG, not about how we post it to multi-programme sites like GMA and PnP. Add CAPTCHA or similar to prevent bot abuse from the web UI. Spotting to POTA is already handled in Field Spotter so should be possible to just copy this approach across. Spotting to GMA is documented: https://www.cqgma.org/api/doc/apigma_spot.pdf We (or the user) need a GMA account, and to send the password in plaintext(!!) Spotting to SOTA must be possible (PoLo does it), I think this needs a proper auth flow so might be quite difficult to manage secret storage? Spotting to HEMA is covered in the original email from the team. Spotting to WWFF should be possible, need to look up the Spotline docs or copy from PoLo. Spotting to WWBOTA is possible through its API. Spotting to Parks N Peaks is possible via POST, see https://www.parksnpeaks.org/api/#Spot - requires an API key. Spotting to ZLOTA is supported via POST, see https://ontheair.nz/api Spotting to WOTA TBD. M5TEA wrote a new spotting app recently so he should know how, if he's willing to have it added to Spothole. Spotting to TOTA/xOTA low priority, should be possible but realistically no-one is making TOTA spots through Spothole. Spotting to RBN, APRS-IS and UK Packet Net from Spothole doesn't make sense, so these are out of scope.