Skip to content

Support for a FollowTheSignage instruction #3542

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

Open
daniel-j-h opened this issue Jan 9, 2017 · 7 comments
Open

Support for a FollowTheSignage instruction #3542

daniel-j-h opened this issue Jan 9, 2017 · 7 comments
Milestone

Comments

@daniel-j-h
Copy link
Member

daniel-j-h commented Jan 9, 2017

There are situations for which following a sign is the proper hint for users.

For example: the noref=yes sign which represents an exit without further details.

http://taginfo.openstreetmap.org/tags/noref=yes#wiki

We should think of adding a instruction for these situations to the api in v6.

(Another use-case would be: complex situations we just can't handle. Acknowledge this and let make the user aware of it)

@pratikyadav @MoKob

@daniel-j-h daniel-j-h added this to the 6.0 milestone Jan 9, 2017
@willwhite
Copy link
Contributor

What would the difference between this and how we handle destinations?

@daniel-j-h
Copy link
Member Author

@willwhite maybe the description for this ticket wasn't detailed enough. Here is a situations I can think of where a "follow the sign" instruction could help:

We know the situation is too complex to issue tons of instructions every other second for but the user can happily make its way through the situation using signs: think about an airport terminal with multiple ways forking and merging where all you want to say is "follow the sign to terminal 2".

Another situation could be complex roundabouts: for roundabouts we already acknowledge lanes inside them are too complex to handle and country-dependent. We simply remove lanes from roundabouts completely. Similarly crossing roundabout types we do not handle yet could be announced as "follow the signs to cross the roundabout".

@1ec5
Copy link
Member

1ec5 commented Jul 3, 2017

We know the situation is too complex to issue tons of instructions every other second for but the user can happily make its way through the situation using signs: think about an airport terminal with multiple ways forking and merging where all you want to say is "follow the sign to terminal 2".

Project-OSRM/osrm-text-instructions#41 and Project-OSRM/osrm-text-instructions#30 suggest that OSRM Text Instructions or a client navigation SDK has almost enough context to rewrite instructions this way without requiring explicit “follow the sign” instructions from the API.

@1ec5
Copy link
Member

1ec5 commented Jul 12, 2017

Per #3304 (comment), OSRM would need to provide OSRM Text Instructions with the contents of the destination:to and destination:ref:to tags in order to reliably say “follow the signs to” in a complex freeway interchange.

Copy link

github-actions bot commented Jul 8, 2024

This issue seems to be stale. It will be closed in 30 days if no further activity occurs.

@github-actions github-actions bot added the Stale label Jul 8, 2024
@1ec5 1ec5 removed the Stale label Jul 9, 2024
@1ec5
Copy link
Member

1ec5 commented Jul 9, 2024

The destination_sign relation type might also be useful for consolidating instructions: #6554.

Copy link

github-actions bot commented Jan 5, 2025

This issue seems to be stale. It will be closed in 30 days if no further activity occurs.

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

3 participants