SOTA

[alanhargreaves]

Could someone point me at the person working on SOTA?

The SOTA API does not provide long/lat information. I've coded up something in the back end to do a daily pull of the CSV containing all summit information, and implemented a cached lookup for /api/sota/summit/:association/:summit that will up date no more than daily.

I'd like to work with rather than at cross purposes against whoever is working on this.

[alanhargreaves]

The big issue that I'm seeing in SOTA is that the API we are using to pull SOTA spots does not include long/lat and the Summit Name.

I tried pulling the csv of all summits with a 24 hour cache refresh (as it's updated daily), so a pull from localhost:3000/api/sota/{association}/{summit} pulls back the information from the cached values in the server or refreshes the cache and then returns them, but I see two issues with this approach.

1. It makes for a tonne of extra queries on the server, and I believe that we're trying to reduce this load.
2. The asynchronous nature of fetch really works against being able to populate the lat/long/name information for each spot in a timely fashion

I considered holding the cache in the client, but then this is not a small hash.

What would be really nice is if there were an API available to the SOTA spots data that included the latest/long/name information; basically doing an SQL join on the spots vs the summit info.

Anyone know of such a beast?

[alanhargreaves]

Doesn't matter. With the merge earlier of the majority of the SOTA code, I've added teh functionality to flesh out the summit detail into the spots on the server side and submitted a pull request.

[alanhargreaves]

Just waiting on the pull request to be accepted.

[alanhargreaves]

This merged some time back