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

Extremely high walking time estimates if no path can be found #548

Closed
jbruechert opened this issue Sep 24, 2024 · 3 comments
Closed

Extremely high walking time estimates if no path can be found #548

jbruechert opened this issue Sep 24, 2024 · 3 comments

Comments

@jbruechert
Copy link
Contributor

jbruechert commented Sep 24, 2024

This is a bit of a special case because there is a border here, but it is also reproducible when starting from a building that is located to far from a street.
I just haven't found another place to reproduce it without doxing myself.

The path that is estimated to take 18h is about 4km long and Graph Hopper estimates 0:46 instead.

Copy pastable coordinate for reproducing: 45.153385;19.177957

image
image

@felixguendling
Copy link
Member

This 18h footpath seems to occur again..
It was already discussed here (where I also explain my reasoning what's going on):
#534 (comment)

I was hoping to fix it here:
193d4c2#diff-8d9c8cd9c89caa1b2f03cc19b9209ab104fe47b2f43b44247ea60926a5a75e19R200-R202

But obviously, I didn't find the right spot.

Should already be fixed with MOTIS 2.0 because there "unreachable" is expressed as std::nullopt.

@jbruechert
Copy link
Contributor Author

Ah nice, then I'll just wait :)

@felixguendling
Copy link
Member

Fixed with v2

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