Quote from Guido on 14.10.2026, 19:21

Yes. I see, and I know why this is happening. It’s the result of a compromise I had to make, sacrificing precision for performance.

To give unpaved, toll and ferry stretches a different color, Scenic splits up the route in ‘maneuvers’ and gives each maneuver the appropriate color.

A ‘maneuver’ is the piece of route between one navigation instruction and the next. If a maneuever has an unpaved stretch Scenic knows this, but it’s a Boolean value. hasUnpaved true or false. We don’t know if it’s entirely unpaved, partially, let alone which part. So, for the moment, if hasUnpaved = true the whole maneuver is drawn yellow.

The way going and way back might have different maneuvers / different maneuver instructions.

A stop also generates a maneuver instruction.

There is a way to get this more precise but that requires a lot more performance. I.e. route calculations will take a lot longer.

I will investigate other possibilities but for now I’ll leave it like this as route calculations taking a lot longer is not acceptable.

Quote from Old Man Emu on 14.10.2026, 22:43

Thanks the explanation. I've added waypoints along the section to isolate where the offending map data might be as I know that the whole section is paved.

It seems to drill down to this location and my guess is that the service road down to the river which is gravel intersects on the main road by "too far" and is crossed therefore creating an IsUpaved boolean? I've tried to replicate this elsewhere but I cannot get a consistent feel for it?

Perhaps if a section between A and B is unpaved insert Vias?

I for one would much prefer precision as in some parts where we ride this would lead us into unpassable sections of road and doubling back 50km