CT routes through access=destination

Hi,

Today's route tried to take me down an "access only" road. OSM seems to indicate this with access=destination. That appears correct according to OSM documentation, but does cycle.travel expect some other tag? It normally only uses restricted roads and tracks if I put an explicit waypoint on them.

I've made an simplified example route.

Thanks!

Location (incorrectly) snaps to nearby roads

Hi!

I took cycle.travel (on an iPhone) on tour back in August, and noticed a few times along the way that sometimes it would try to snap my location to a nearby road. In some cases, this snapping behaviour would be so strong that my actual route would end up off screen at my usual zoom level.

The most noticeable location was Milton Keynes, and this is the route I planned.

This is perhaps the clearest example:

Here's an extreme case, in which the cycle path is way off to the left:

Here's another one (near Waddesdon, and I was actually on the red-outlined cycle track):

This wasn't a system-wide problem; I was also recording my route using MapOut, and that was able to locate me accurately. I wonder if there is some iOS API setting? I could see snap-to-roads being useful for vehicular navigation so perhaps it's a default.

Thanks!

"Dim between turns" timing

Hello,

"Dim between turns" seems to be invaluable for conserving battery life, so I use it almost all the time. I have noticed, though, that I generally want to see where I'm going somewhat earlier than it wakes up the screen, so I often have to manually wake it when I see a junction coming. This doesn't take long, but it takes longer than a quick glance.

It's quite useable as it is, but it'd be even better if I could adjust the amount of warning that it gives by default.

Thanks!

Reset view when underway (and related suggestions)

Hi!

When navigating, I've found that:

• I like to cycle with the perspective view, following my location, with the zoom level fairly close (so I can glance down to see junction layouts clearly).
• Every so often, I want to stop and check the wider map, so I'll put it in "centred" mode, zoom out, and probably scroll away from my location. I'll then reset it to perspective view when I set off again.

This exchange requires a few button presses, and inadvertent touch events often disable location following. I generally don't notice until I'm underway, then I have to stop to put it right again. It's all manageable, but a fiddle.

I'd like to propose:

1. An option to automatically return to perspective+follow view after a few minutes of travel.
2. Have each "display mode" remember its last zoom level.
3. Those would greatly improve things for me already, but as a bonus: add some way to quickly toggle between display modes, without using the drop-down menu. For example, the "map style" submenu could be moved to settings, then the button on the main display could cycle through centred / look-ahead / perspective views.

Duplicate place labels

I just noticed that several place names are duplicated. Perhaps a tile generation bug?

I can only reproduce this with "cycle.travel" maps, and only on the web interface (not the app).