We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
now it’s wind directions always because that happened to match for Ghent, other stations will need that check to be different.
We should get the closest of the directions (which is a point), and that should work.
Now we just literally check the direction with latitude > gent.latitude ...
The text was updated successfully, but these errors were encountered:
proposal: there should be a new key “directions” in the config.json
"directions": [ { "longitude": 3.710675, "latitude": 51.035896, "name": "Antwerpen" }, { "longitude": 3.710675, "latitude": 51.035896, "name": "Brugge" }, { "longitude": 3.710675, "latitude": 51.035896, "name": "Kortrijk" } ]
Sorry, something went wrong.
Those coordinates should be a point on the real railway track separating the directions.
No branches or pull requests
now it’s wind directions always because that happened to match for Ghent, other stations will need that check to be different.
We should get the closest of the directions (which is a point), and that should work.
Now we just literally check the direction with latitude > gent.latitude ...
The text was updated successfully, but these errors were encountered: