Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seeds file #64

Open
Mogee1 opened this issue Sep 18, 2024 · 4 comments
Open

Seeds file #64

Mogee1 opened this issue Sep 18, 2024 · 4 comments

Comments

@Mogee1
Copy link

Mogee1 commented Sep 18, 2024

Hi thanks for the great code, super useful. Could you help me understand the reason of the seeds file? It seems that all the information can be obtained based on the SpotID alone

@swrobel
Copy link
Owner

swrobel commented Sep 18, 2024

Not sure what you mean here. Spot IDs are arbitrary and assigned by the database. The seeds create the actual list of spots to check for forecast data along with their Surfline & Spitcast IDs

@Mogee1
Copy link
Author

Mogee1 commented Sep 18, 2024

So for example this SpotID 590927576a2e4300134fbed8 Provides me always the data output from the wave endpoint for Venice Breakwater https://services.surfline.com/kbyg/spots/forecasts/wave/?spotId=590927576a2e4300134fbed8 Hence I do not understand why there is a Seed file that requires updating if the SpotID seems to be sufficient to pull the information directly. Maybe it does not work for some other spots which are not in the Seeds file?

@swrobel
Copy link
Owner

swrobel commented Sep 18, 2024

How does the app know that the surfline_id you provided is associated with Venice? That's what the seed file is for.

@Mogee1
Copy link
Author

Mogee1 commented Sep 18, 2024

Ah okay perfect that‘s understood thanks, so it‘s an internal dictionary of the app to link the SpotID from Surfline which is fixed to the Name of the Location

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants