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

Route ends inside tunnel #747

Closed
Kalten666 opened this issue Sep 29, 2013 · 7 comments
Closed

Route ends inside tunnel #747

Kalten666 opened this issue Sep 29, 2013 · 7 comments

Comments

@Kalten666
Copy link

I have an example of a route not only including something near to a loop, but also ending inside a tunnel, that happens to be tagged as such.

Using http://osrm.at/ Start at e.g. »Weinitzenstraße 6, Graz« and destination e.g. »Kollerbergweg 35, Graz«. See here for a link zooming out the tunnel-problem itself.
The road is tagged with tunnel=yes—see details.

osrw_weinitzenstr_kollerbergweg_35
ru,
Kalten666

@DennisSchiefer
Copy link

I am not sure if I understand the problem correctly. If you put your end marker inside a tunnel the route will end inside a tunnel. Also the loop is due to the end marker being on a one-way lane that goes from south to north and the start is north of it. So the fastest way seems to be drive on the highway to the next exit, make a u-turn and drive back.

@species
Copy link

species commented Sep 30, 2013

You have to enter the Adresses into “Start:” and “End:”, and the marker will automatically snap to the nearest road (the tunnel).

@Kalten666
Copy link
Author

Yes, species, that is what I ment by writing “Start at” and “destination” (well, perhaps I should have written “End” as that is the term being used at http://osrm.at/).

About “the nearest road”: well. I guess, in most cases using the road near to the target with the same name-tag as the houses addr:street-tag would be a good solution—sadly not allways.
But to let me stopp inside the tunnel is out of the question, I dare say. ;)

@DennisSchiefer
Copy link

Ah alright. Now, I see the problem. But having said that, I think this is something for the geocoder to solve (which is not part of OSRM).
As species said, OSRM will snap to the nearest road according to the lat/lng coordinates it is given. If the coordinates happen to be closer to the highway than to the rural road, it will snap to the highway -which is also intended behaviour if you are dragging the marker, for example. Thus, the mapping from addresses to geo-coordinates should become more accurate to solve this problem automatically.

EDIT:
I just checked with Nominatim and the geo-coordinate is indeed closer to the Kollerbergweg than to the highway. So this is something OSRM would have to investigate. But that part of the Kollerbergweg is not marked as being usable by a car. Thus, the closest road is still the highway.

@Kalten666
Copy link
Author

Let me try to make the real BUG more clear by posing a question:
In which country do you live, that you are allowed to make a full stop insige a tunnel let alone park your car and get out of it inside a tunnel? And how do you drill a whole to reach the house? With your fingernails? SCNR

And second: access=private is not the same as access=no. Iff you want to get to a private house, it is extremely likely that you are allowed to use the private road leading to it. At least the routing system should stop at the entrance of that private road, or even traverse it and tell the user it has done so (only for destination reaching, not in other cases!). access=destination would be usable to, but if there is no sign on private ground stating explicitly that one is allowed to use the road to reach a specific house number, it is private: the editor at http://www.openstreetmap.org/edit#… clearly states, that private means: “Access permitted only with permission of the owner on an individual basis” so it is allowed to be the end of a route to a specific house if there is no other way to reach it (and a tunnel definitly is not an option in my country ;-)).

(aaah! unclose!!)

@Kalten666
Copy link
Author

unclose (sorry!)

@DennisOSRM
Copy link
Collaborator

The feature request that fix this issue are already covered in #665 and #156. Keeping it closed therefore.

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

4 participants