XOTA/TOTA support #82

Closed
opened 2025-11-23 14:32:51 +00:00 by ian · 3 comments
Owner

Support spots from the xOTA software, which a generic open source xOTA programme server. This is used for TOTA amongst other things.

Set up my own copy locally to test against: https://github.com/nischu/xOTA/

Spothole config should support start and end dates for the provider, so it only runs during the interval it's active. The options call should include an "active" flag and the UI should require the sources to be both enabled and active to display them as options.

Add TOTA SIG support.

Update about page and readme.

Get a geo location from somewhere - maybe lat/lon in the provider config, or from a SIG lookup based on the URL the provider gives?

Support spots from the xOTA software, which a generic open source xOTA programme server. This is used for TOTA amongst other things. Set up my own copy locally to test against: https://github.com/nischu/xOTA/ Spothole config should support start and end dates for the provider, so it only runs during the interval it's active. The options call should include an "active" flag and the UI should require the sources to be both enabled and active to display them as options. Add TOTA SIG support. Update about page and readme. Get a geo location from somewhere - maybe lat/lon in the provider config, or from a SIG lookup based on the URL the provider gives?
ian self-assigned this 2025-11-24 20:51:08 +00:00
Author
Owner

Done most of this in a branch, still need to do the "active time" bits and test it.

Done most of this in a branch, still need to do the "active time" bits and test it.
ian referenced this issue from a commit 2025-11-24 21:57:34 +00:00
ian added this to the 1.1 milestone 2025-11-25 06:43:22 +00:00
Author
Owner

Not sure really whether the active time bits are worth doing. Given the events are unlikely to repeat with the same URL, and there's very little penalty to just flipping the enable switch in th config and restarting Spothole. It's a lot of altering of the main codebase for what is essentially just a joke!

One thing we should do though is look at xOTA docs and see if there's anything in the API responses that we don't get from TOTA but might from other uses of the software.

Not sure really whether the active time bits are worth doing. Given the events are unlikely to repeat with the same URL, and there's very little penalty to just flipping the enable switch in th config and restarting Spothole. It's a lot of altering of the main codebase for what is essentially just a joke! One thing we should do though is look at xOTA docs and see if there's anything in the API responses that we don't get from TOTA but might from other uses of the software.
Author
Owner

Nope, there's nothing else: https://github.com/nischu/xOTA/blob/main/Sources/App/Models/Spot.swift

This story is basically done then, I'll merge the branch and await the chance to test properly. Need to add support in Field Spotter too.

Nope, there's nothing else: https://github.com/nischu/xOTA/blob/main/Sources/App/Models/Spot.swift This story is basically done then, I'll merge the branch and await the chance to test properly. Need to add support in Field Spotter too.
ian referenced this issue from a commit 2025-11-26 07:40:52 +00:00
ian closed this issue 2025-11-26 20:39:13 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ian/spothole#82
No description provided.