Tag:cycleway=link

This tag like footway=link provides logical gap fills between two adjacent pieces of cycling infrastructure. These typically are physically distinct way center-lines that need routable linking.

Use Scenarios

Here are a few common scenarios that cover scenarios where other cycleway=* tags are not clean fits:

1. Two cyclable portions of infrastructure are near to one another and one or both have 'man made' inferences of a logical/routable transition between them. For instance a multi-use side path ends suddenly and just before there is a curb cut (driveway, ramp, etc.) is present just before the path comes to a dead end. A 'link' can fill the gap between the two infrastructure center-lines for routing. Note: That the dead ending path ideally needs to be marked with noexit=yes.
2. Completing 'partially marked desire paths' for instance if there is a footway=access_aisle that ties partially between a multi-use side path with ramp and a cyclable roadway a cycleway=link might be used to connect the vehicle highway=* to the highway=cycleway via the footway=access_aisle with perhaps a bicycle=permissive added to allow for use of the 'access aisle' as a desire path when not conflicting with accessible use.
3. For cycling especially with cyclist bounced between highway=* + cycleway=lane, cycleway=track, or cycleway=shared_lane of roadways and dedicated highway=cycleway as either cycle exclusive or multi-use in nature direction a highway=cycleway into a vehicle highway=* or traffic intersection at a 90° or 45° angle just to disappear demonstrates these to be more route based logical connections than physically based alignments that benefit from distinction from highway=cycleway. Thus, cycleway=link fills this transition point routing function bridging 'gaps' between separate but soon to be linked, or unlinked cycle infrastructure center-lines.
4. If a bike lane ends with a merge into a "bike box" or Advance Stop Line cycleway=asl then cycleway=link can be used to tag the logical transition to the Advance Stop Line node.

Note: As a general rule of thumb almost every cycleway=link listed should be short at most a half roadway or intersection diagonal in width as all listed scenarios are simply logical gap fills for routability between two nearby infrastructure center-lines.

Possible Improvements

cycleway=link does cover the routable gap for cyclable infrastructure transitions. What this does not cover is how at transition points to navigate from one piece of infrastructure to the next. It might be necessary to have a relationship in a 'restriction' like context (i.e. from way, to way, via node) that can communicate from road-to-trail or visa-versa transitions.

For Road-to-Road Transitions

For transitions between 'shared_lane' and 'lane'/'track' of vehicle lane cross-overs look at using Relationship of type=connectivity and align the lanes. For examples see Draft:United States/Cycling.

Tags used in combination

• cycleway=asl
• surface=*
• lit=*
• wheelchair=*
• barrier=kerb + kerb=*

See also

• footway=link - the pedestrian focused equivalent to this tag
• highway=cycleway - used to map sidewalks
• cycleway=lane - used to map non-physically separated Bike lanes
• cycleway=track - used to map physically separated Bike lanes
• cycleway=crossing - used to map crossings along cycle routes and multi-use paths
• footway=access_aisle - only if between two cyclable pieces of infrastructure
• Proposal:Tag:footway=link - original proposal