Support SOTA #2

New issue

Closed

opened 2025-02-23 14:28:20 +00:00 by ianrenton · 1 comment

ianrenton commented

2025-02-23 14:28:20 +00:00

(Migrated from github.com)

Requested by Nathan 2M0OCC, support SOTA summits.

Summit info with all activations is available similar to POTA's secondary query: https://api-db2.sota.org.uk/api/activations/G/SC-008

Not sure yet how to do the primary query to get the list of references on screen. I don't think its API has a "give me all references in this lat/lon box" so I would need a way of getting "all associations & regions currently on screen" then filtering.

People will probably want to toggle POTA & SOTA on & off individually.

May require a name and URL change!

Requested by Nathan 2M0OCC, support SOTA summits. Summit info with all activations is available similar to POTA's secondary query: https://api-db2.sota.org.uk/api/activations/G/SC-008 Not sure yet how to do the primary query to get the list of references on screen. I don't think its API has a "give me all references in this lat/lon box" so I would need a way of getting "all associations & regions currently on screen" then filtering. People will probably want to toggle POTA & SOTA on & off individually. May require a name and URL change!

ianrenton commented

2025-03-01 09:58:50 +00:00

(Migrated from github.com)

If necessary we could move to having some server-side processing, e.g. every day a script downloads all POTA & SOTA CSVs and converts them to minimal JSON. Then at least the client would have less to download. But it introduces a server-side component so an extra thing to maintain. Could be a cron job and .sh on my server or a GitHub Action at the cost of tying this project to GitHub

An alternative for SOTA data would be downloading the whole CSV and parsing it. However, at 21MB it's probably too big to stick in localstorage, even when converted to JSON and only ref/name/lat/lon preserved, which means the user would have to load it every time they arrive at the site and want to use SOTA data. If necessary we could move to having some server-side processing, e.g. every day a script downloads all POTA & SOTA CSVs and converts them to minimal JSON. Then at least the client would have less to download. But it introduces a server-side component so an extra thing to maintain. Could be a cron job and .sh on my server or a GitHub Action at the cost of tying this project to GitHub