To better support planning a (cycle) route using the node network, it would be nice if the turn-by-turn instructions could include node network numbers. This is especially useful when routing could be configured to highly prefer (node network) routes (as suggested in #9595).
I can imagine two parts to this:
When a turn happens at a named node, this could be mentioned in the instructions, e.g. "At node 25, turn right"
When a segment of the route is exactly a node route between two numbered nodes, the instructions for this segment could be summarized with just a reference to the rout.
For 2., I can imagine a few ways this could be implemented.
2a. The most generic one would be to be explicit: "At node 25, turn right and follow directions to node 26.". This would repeat each node number twice (i.e. the next instruction would be "At node 26...") but make each instruction indepdently readable.
2b. A slightly more condensed version could be to omit the "from" node when the previous instruction already mentioned it (i.e. "Turn right and follow directions to node 26"). Everytime the route switches from non-node-based to node-based directions, the starting node should probably still be added.
2c. A very condensed version, which could be suitable for a route that consists only of node-to-node transitions, could just list the node numbers and nothing else.
I think 1. could maybe be done unconditionally, 2. should almost certainly be opt-in (either persistently in navigation settings, which could maybe even distinguish between 2a/2c or so, or just ad-hoc with a button above the "turn-by-turn" instructions themselves maybe?).
This would need some careful consideration about what consititutes a node network route exactly. In a lot of cases these routes are clear, point-to-point routes, but in some cases (at least in the Dutch cycle network), nodes are split into multiple subnodes (with the same number, usually within sight distance, e.g. for two very close T-junctions, or when a route is split along two sides of a road). There are a few ways this can be mapped, but in general all parts of the route (including the parts between the different subnodes) will be part of at least one route).
My usecase is for cycling, but I think the same would be useful for walking, horse riding, etc.
To better support planning a (cycle) route using the node network, it would be nice if the turn-by-turn instructions could include node network numbers. This is especially useful when routing could be configured to highly prefer (node network) routes (as suggested in #9595).
I can imagine two parts to this:
For 2., I can imagine a few ways this could be implemented.
I think 1. could maybe be done unconditionally, 2. should almost certainly be opt-in (either persistently in navigation settings, which could maybe even distinguish between 2a/2c or so, or just ad-hoc with a button above the "turn-by-turn" instructions themselves maybe?).
This would need some careful consideration about what consititutes a node network route exactly. In a lot of cases these routes are clear, point-to-point routes, but in some cases (at least in the Dutch cycle network), nodes are split into multiple subnodes (with the same number, usually within sight distance, e.g. for two very close T-junctions, or when a route is split along two sides of a road). There are a few ways this can be mapped, but in general all parts of the route (including the parts between the different subnodes) will be part of at least one route).
My usecase is for cycling, but I think the same would be useful for walking, horse riding, etc.