search

GIScience / openrouteservice

🌍 The open source route planner api with plenty of features.
https://openrouteservice.org
GNU General Public License v3.0
1.43k stars 393 forks source link

Unexpected route via `route=shuttle_train` #1132

Open koebi opened 2 years ago

koebi commented 2 years ago

I played around with a request from an unrelated forum issue and got the following rather weird foot-walking route seemingly using a train track

https://classic-maps.openrouteservice.org/directions?n1=46.263799&n2=7.986546&n3=12&a=46.3125,7.84355,46.314183,7.874279,46.3096,7.91865&b=2&c=1&k1=de&k2=km

Screenshot 2022-02-25 at 16-26-03 Openrouteservice Maps

This is correct, since what happens is the following: There is a route=shuttle_train on the train tracks that has no foot=*-tag. Waypoint 1 is on a way with a non-suitable sac_scale and thus snaps to a point on the route=shuttle_train.

The two question this poses are:

  1. Does it make sense to snap to route=[shuttle_train, ferry]? On the one hand, this could be useful to force usage of such ways, on the other no point on such a route is actually "reachable".
  2. Does the corresponding train allow the transportation of passengers, i.e. should routing go via shuttle trains and ferries that have no explicit foot=* tag?

The related meta-question is how and where we could and whether we should record such tag-based routing decisions.

sfendrich commented 2 years ago

It seems something is wrong here. Using "avoid ferries" to avoid using the shuttle results in a shorter and quicker route.

koebi commented 2 years ago

It doesn't get as close to the waypoint, though, so it wouldn't be an option for the route allowing the shuttle, as that can get closer to the waypoint.