-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Wrong route instruction #686
Comments
when the way has no name, the way type is passed instead. it looks like the front end does not translate these codes. |
at http://www.ibikecph.dk/ we translate these way types. the code (coffeescript) is at https://github.com/ibikecph/ibikecphsite. |
For all roads in the car profile the server sends an empty string instead of the road type if there is a missing street name. This we handle in the webclient by having an optional part in all directions strings, e.g. "Turn left [on %s]". So you either get "Turn left" for unnamed streets or "Turn left on Mainstreet" for Mainstreet. But I see the point of having instructions like "Turn left on bike lane". |
right, the car profile does not send {highway:<type} as the name for unnamed streets, like the bicycle profile does. |
Okay, this will be in in the next version. Just tested it. That said http://www.ibikecph.dk/ still uses more sophisticated route instructions (e.g. pushing the bike against one-ways). |
With the bicycle profile you get sometimes no instruction, or the instruction to go straight on, but in reality you must turn right or left. Below you will find three examples:
The problematic route instruction is the line with the red text-color. It should be a turn right instruction.
At the next example I miss a route instruction like turn right.
At the last example I miss a route instruction like turn left after the red line.
Feel free to test the bicycle profile at
As a warning to you: It's only an experimental installation, preprocessed with a dataset of Europe and the profile bicycle.lua.
The text was updated successfully, but these errors were encountered: