Next instruction problem and request.

[Nick Carthew]

@UltraStar You can edit your post by clicking on the 3 dots.

[UltraStar]

@Nick-Carthew Thanks.

[Corjan Meijerink]

Happy to inform all of you that after some painstaking hours, the issue has been resolved!

Distances are now calculated correctly for the next maneuver

Besides thar, the next maneuver UI has been increased in size.

We haven’t yet changed the displayed distance value, gonna give that another night of sleep.

[Dave J 0]

@Corjan-Meijerink Brilliant job. Look forward to the next update.

[Nick Carthew]

@Corjan-Meijerink said in Next instruction problem and request.:

We haven’t yet changed the displayed distance value, gonna give that another night of sleep.

Great job in fixing the problem

Now I don’t want to influence your nightly sleep but the fixed displayed distance after the next turn does make more sense

Sweet dreams buddy

[RetiredWingMan]

@Nick-Carthew I still think the current display is the correct method.

[Nick Carthew]

@Doug-Robinson said in Next instruction problem and request.:

@Nick-Carthew I still think the current display is the correct method.

I'm sorry but I have to strongly disagree for the reasons that I previously mentioned but I will try and argue the case again:

If the next turn is 9.7 miles away and the turn after that is at 10.3 miles you have to work out in your head that the second turn is at 0.6 miles.
And because both of these numbers are dynamic and constantly changing, again more mental arithmetic is required the next time you look and see that the next turn is at 8.9 miles and the turn after that is at 9.5 miles.

I don't need to be concentrating on this while trying to stay alive.
The most important information for me to have is knowing that after the next turn there is another turn coming after 0.6 miles.
The figure of 0.6 miles is fixed and is easy to interpret.

[Con Hennekens]

@Doug-Robinson said in Next instruction problem and request.:

@Nick-Carthew I still think the current display is the correct method.

I am sorry @Nick-Carthew, but I strongly agree...

You don't have to work out anything, because the real distance is already present, and not some imaginative distance to another point than yourself. I would have to "work out in my head" what the real distance is when it would be fixed to the first upcoming point.

You know, I am not really trying to make a statement about the issue itself anymore. I am merely pointing out that the discussion is equally arguemented both ways, and therefore makes no sense.

[Stefan Hummelink]

@Con-Hennekens Hahaha I feel sorry for i.e. tourists that ask you for directions to the nearest restaurant.

Con is telling the curious tourist to
"In 500m from exactly here turn right, then 900m from exactly here, turn left, then 1.5km from exactly here, take the 3rd exit at the roundabout, then after 1750m from exactly here, you've reached the best steakhouse in the village."

And then there is me, being befriended to Con and standing next to him, noticing the dude being completely oblivious about what just has been told to him, converting the instructions into something understandable:
"Turn right in 500m, then turn left after 400m, then take the third exit at the roundabout after 600m, and then after 250m you're ready to order you're ribeye."

Haha. All joking aside, if I were asking for instructions, which is in fact what each nav is doing, telling us where to go, I definitely want the instructions in the latter format instead of the former.

We'll just have to wait and see if Corjan and Joost are willing to offer us "outsiders" the configuration to change it. Haha.

[Con Hennekens]

@Stefan-Hummelink, Haha, if you want to laugh, the app is not about showing tourists the way, but for you to read where you need to go, and at what distance. I am arguing in favor of you that both ways are are valid. I feel sorry for you that you need to make a joke of it. You are ridiculing your own point at the same time. I will refrain from further arguing, because this flamewar is leading nowhere.

[Stefan Hummelink]

@Con-Hennekens said in Next instruction problem and request.:

but for you to read where you need to go

Wellll, in fact, I would like to be that tourist and be led as described before haha. Anyhow, I agree with quiting the discussion, both sides of the matter are clearly described. Power to Corjan and Joost to come up with the best compromise.

[Dave J 0]

Just to put a final thought for @Corjan-Meijerink. Apple Maps, Google Maps, Sygic and TomTom apps just show the direction of the second turn if it is a short distance after the upcoming direction but with no distance. OsmAnd displays the second turn as a static distance as suggested by some of us here. My Garmin Zumo announces the second turn with no distance and no indication.

As said, down to the Dev Team to decide on how they cater for differing requirements. This is not the first of these kind of issues as the development of the app continues; good that we can discuss these differing needs.

[Con Hennekens]

@Dave-J-0 said in Next instruction problem and request.:

Apple Maps, Google Maps, Sygic and TomTom apps just show the direction of the second turn if it is a short distance after the upcoming direction but with no distance.

This a nice thought!

I think that distance for really short following of instructions is not very meaningful anyway (e.g. turn right and immediately left does not really need a distance at all). For distances of let's say 50 to 500 meters the distance is nice to know in advance, and specifically in that scenario I have absolutely no problem with it being static from the first instruction. For greater distances knowing them that early has no benefit because they will turn into the first instruction anyway after passing the previous one.

People seem to look at those info tiles a lot. For myself I can say that I seldomly look at them at all. The routeline itself is leading for me, and it also tells me if a second turn is close or not.