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.

Sign up for GitHub

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

Jump to bottom

Duration of crow_fly's fails for counterclockwise searches #458

Closed
koch-t opened this issue Jul 26, 2014 · 3 comments
Closed

Duration of crow_fly's fails for counterclockwise searches #458

koch-t opened this issue Jul 26, 2014 · 3 comments

Comments

@koch-t
Copy link
Contributor

koch-t commented Jul 26, 2014

For all requests with counter-clockwise searches a response is given with a very long crow_fly (hours) where 0 seconds is expected.
@koch-t
Copy link
Contributor Author

koch-t commented Jul 26, 2014

Example response for request stop_area:lls to stop_area:asdz

CROW_FLY stop_area:lls 813 minutes
Train stop_area:lls to stop_area:asdz
CROW_FLY stop_area asdz 814 minutes

Clockwise search works fine.

@koch-t
Copy link
Contributor Author

koch-t commented Jul 28, 2014

It is already present in the protobuf received by jormungandr. Looks like there is combination that results in fail, as standalone protobuf output does work

@koch-t
Copy link
Contributor Author

koch-t commented Jul 28, 2014

Fixed with c445422

@koch-t koch-t closed this as completed Jul 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@koch-t