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

City bike results include suggestions where the bike station is empty or completely full #114

Open
mhalttu opened this issue Jun 19, 2017 · 2 comments

Comments

@mhalttu
Copy link

mhalttu commented Jun 19, 2017

Currently the results can contain an origin station that has no bikes, or a destination station that is completely full and cannot accept any more bikes. These kind of results are not useful for the user. The API should suggest some other stations instead - or walking if that is faster.

@tuukka
Copy link
Contributor

tuukka commented Jun 20, 2017

The route planning results do take station emptyness into account, but you should still follow the situation in the UI and provide an alert whenever the route doesn't seem to be possible anymore. (When that happens, you can also make a request for new plans.) It can happen that all servers in the API cluster are not fully synchronized, which can cause these inconcistencies.

@mhalttu
Copy link
Author

mhalttu commented Jun 20, 2017

Ok. To be clear, the user made a routing request and that initial first result returned by the API was already invalid. Both the origin station was empty and the destination station was full. Are you saying this was caused by the servers in the API cluster not being fully synchronized?

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