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
Pedestrian route not using shorter paths in park #15621
Comments
It may be that c:geo is not using an actual walking profile. As written in #15620 (comment): Can you please go to settings => routing/navigation and check what profiles you have configured for walk / bike / car? |
When checking "use internal routing" I see the following:
|
Note: I have updated over the weekend to 2024.04.18 version. I will try to revisit the place on which this report was based and get back. |
Maybe the park is just not correctly mapped in OSM...? |
Unlikely, using OSMAnd and walk profile I get route through park alleys. |
Interesting. Revisited the place today, tested with both internal routing and with external BRouter app and it worked both ways. |
I'd say it's safe to close this. |
That's indeed strange, we have changed nothing wrt to routing in the last versions... But anyway, thanks for cross-checking and reporting back. |
Describe your problem!
Trying to route to cache using walk profiles doesn't use pedestrian features.
How to reproduce?
I am in a park. There are several paths in the park. There is a cache outside the park and walking, the shortest part is using such paths.
c:geo with internal routing or external BRouter app (tested with both).
Using walk profile.
Actual result after these steps?
I get the same route as if using car profile. The routing doesn't go through the park.
As a comparison, routing using OSMAND does use the paths with walk profile, and it also uses basically the same data.
Expected result after these steps?
Route using the pedestrian paths.
Reproducible
Yes
c:geo Version
2024.04.13
System information
Additional Information
No response
The text was updated successfully, but these errors were encountered: