[Talk-GB] Cycle lanes and Cycle Tracks - how to map
rob.j.nickerson at gmail.com
rob.j.nickerson at gmail.com
Wed May 16 19:54:42 BST 2012
Haha, I only mean well :-)
The issue came about from trying to improve the guidance provided on the UK
tagging guidelines. Currently I have copied over the guidance that already
existed (to the consultation page), however this was very limited and has
already had cries that foot=no is not correct.
Now I can easily improve this section to draw a distinction about
cycleway=lane when the cycle path is _within_ the carriageway (with some
images). However there are 2 methods for cycle tracks alongside a road but
not within the carriageway. Question to talk-gb is do we in the UK have a
preference? If not then we need to discuss this on the wiki page and stress
that "just map it" regardless of non-consensus.
Note: One thought on left / right is that mappers have to realise that a
road has a direction (as it is drawn as an "arrow"). From my conversations
with new mappers this (and the similar Forward/Backward) is not understood
as we tend to think in terms of northbound / southbound / east / west.
Cheers,
Rob
ps For transparency I am currently thinking that the highway=* &
cycleway=track combination is a good start but we should be aiming to map
the cycle track as separate from the highway using a highway=cycleway (or
path) way.
On , Richard Mann <richard.mann.westoxford at gmail.com> wrote:
> Gosh, you are a glutton for punishment.
> cycleway=track is used extensively in some countries
> highway=cycleway is use extensively in some countries
> cycleway=track was only rendered on OCM relatively recently
> cycleway:left|right=track|lane isn't rendered on OCM
> the Danes had a big argument about which to use and settled on
> cycleway=track, despite it not being rendered on OCM
> cycleway=track gives you more control over the rendering
> highway=cycleway is easier to route, though unpacking cycleway=track
> isn't difficult
> sub-tagging of cycleways is difficult (eg their membership of a route
> relation) if you use cycleway=track
> In essence it comes down to the problem that recombining two parallel
> ways in order to render them neatly is next-to-impossible. Whereas
> putting the tags on a single way loses some micro-geography.
> I'd go for cycleway=track, but I'm not prepared to go round deleting
> highway=cycleway, and thus having lots of stuff disappear in OCM. So
> until OCM can render cycleway:left|right properly, we're probably stuck
> with both.
> Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-gb/attachments/20120516/18f5f83a/attachment.html>
More information about the Talk-GB
mailing list