Opened 9 years ago

Last modified 4 years ago

#1190 new enhancement/feature request

possibility to have navigation_next_turn[1] ... [n]

Reported by: ah be Owned by: KaZeR
Priority: minor Milestone: version 0.6.0
Component: core Version: git master
Severity: trivial Keywords: OSD, routing, directions



osmand has a nice feature to display the second "next turn" as well including the direction arrow and the distance.

the distance is no problem in navit as one can just increment the index from
navigation.item[1].street_name to

so it would be nice to have the same for navigation_next_turn, eg navigation.item[1].navigation_next_turn, navigation.item[2].navigation_next_turn, ...

best regards

Change History (7)

comment:1 Changed 9 years ago by usul

  • Keywords OSD routing directions added
  • Milestone set to version 0.5.1
  • Severity changed from normal to trivial

I guess this is trivial as we seem to have the route data available.

As this will improve consistency in our model, I suggest to schedule it for 0.5.1 release

comment:2 Changed 9 years ago by ah be

maybe #1102 would also be easy to solve in this process?

comment:3 Changed 9 years ago by usul

Sadly I'm not skilled enough to do the coding, so we can just wait till somebody can help :(

comment:4 Changed 8 years ago by jandegr

I just have the impression this is a duplicate of #483, so already possible for a few years

comment:5 Changed 8 years ago by kazer

Agree with Jandegr.

Jan, would you mind sharing a screenshot and the relevant OSD for the navigation you've been working on? It definitely solves this ticket.

Last edited 8 years ago by kazer (previous) (diff)

comment:6 Changed 5 years ago by

  • Milestone changed from version 0.5.1 to version 0.5.2

This ticket was pushed back in order to bring 0.5.1 out soon.

comment:7 Changed 4 years ago by

  • Milestone changed from version 0.5.2 to version 0.6.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.