-
Notifications
You must be signed in to change notification settings - Fork 313
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
Display exit number in turn banner #337
Comments
mapbox/mapbox-directions-swift#147 has landed, so we’re technically unblocked here, even though it’ll be a little while before we start seeing exit numbers coming through from the Directions API. |
Note: the |
#401 proposes appending the exit number to the destination label, adorning it with a border and arrow (left or right depending on the exit side).
A simpler approach would be to shift the maneuver icon upwards by a few pixels and place the exit number beneath the maneuver icon:
The advantage is that accommodating a destination–exit number combination is easy, and there’s no redundant arrow to worry about. The disadvantage is that longer exit numbers may be difficult to accommodate, especially combined exits like |
@frederoni @mayagao do you have spare cycles to hit this? /cc @miccolis |
Information we may want to show:
I think we can omit the current street, and just show exit + next street + destination in two lines. small turn icon in the exit square can be omitted if we can not get that information right now. |
Regarding the mockup above:
We currently ellide long destinations when necessary, but the design above would put enough horizontal pressure on the label that we may have to display only one destination. That will be problematic for subexits until we address Project-OSRM/osrm-text-instructions#30. |
We've got exits now. |
The turn banner should display the exit number when the instruction is to take a highway off-ramp.
Blocked by mapbox/mapbox-directions-swift#147.
/cc @ericrwolfe @bsudekum @mayagao @willwhite
The text was updated successfully, but these errors were encountered: