Re: [Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

Oct 18, 2020, 10:17 by dieterdre...@gmail.com: > > > sent from a phone > >> On 16. Oct 2020, at 09:32, Richard Fairhurst wrote: >> >> generally bicycle=dismount should be used instead, reserving bicycle=no for >> those circumstances where even pushing a bike is not legal (e.g. most public

Re: [Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

sent from a phone > On 16. Oct 2020, at 09:32, Richard Fairhurst wrote: > > generally bicycle=dismount should be used instead, reserving bicycle=no for > those circumstances where even pushing a bike is not legal (e.g. most public > footpaths in England & Wales). most bicycle=no tags out

Re: [Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

On 16/10/2020 09:06, Richard Fairhurst wrote: It does not currently take any account of bicycle=no on a crossing, not least because bicycle=no is a very problematic tag - generally bicycle=dismount should be used instead, reserving bicycle=no for those circumstances where even pushing a bike is

Re: [Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

Oct 18, 2020, 09:44 by tagging@openstreetmap.org: > On 15/10/2020 17:36, Jmapb via Tagging wrote: > >> I've always been surprised to see a footway=crossing/cycleway=crossing >> way with the intersection node tagged as highway=crossing. There's >> only a single physical crossing, so this seems

Re: [Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

sent from a phone > On 18. Oct 2020, at 09:46, Emvee via Tagging > wrote: > > Routers do not need highway=crossing to detect crossings, every node > where 3 or more ways connect is a crossing. sure, but many highway=crossings are tagged on nodes where only 2 ways (or one going through)

Re: [Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

On 15/10/2020 17:36, Jmapb via Tagging wrote: I've always been surprised to see a footway=crossing/cycleway=crossing way with the intersection node tagged as highway=crossing. There's only a single physical crossing, so this seems contra to the one-feature-one-element rule. A highway=crossing

Re: [Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

As someone who renders a driving-focused map of [the most twisty] roadways, I specifically have done exactly what Volker describes (looking at highway=crossing nodes only). To provide an example, my renderer walks down each vehicle-legal way and demotes the

Re: [Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

Volker Schmidt wrote: > I don't know what the routers need, to be honest. > Anyone in the router business listening in on this conversation? cycle.travel will take account of highway=crossing nodes (e.g. where a cycleway crosses a road), and adjust its routing weight accordingly. The adjustment

Re: [Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

I don't know what the routers need, to be honest. I have adopted the approach happily because of the frequent two-stage approach. First the main road is mapped with foot/bicycle crossings as nodes , and at a later stage someone else may add the foot/cycleway details - I did not occur to me that

[Tagging] Crossing tagged on both way and node (was: What does bicycle=no on a node means?)

On 10/13/2020 6:30 PM, Kevin Kenny wrote: On Tue, Oct 13, 2020, 17:41 Volker Schmidt mailto:vosc...@gmail.com>> wrote: I changed the crossing to the way we do it in many parts of Europe, i.e. a crossing node _and_ a crossing way. This was described as an option on the