Key:routing:bicycle
 routing:bicycle
|
| Description |
|---|
Bicycle access tag specific for routing engines 
|
| Group: restrictions |
| Used on these elements |
    |
| See also |
| Status: in use |
| Tools for this tag |
|
 | This tag was created to assist with private routing tools for research purposes in Quebec, Canada and is (to date) only used by a limited number of users related to that project. Its use is disputed, see the forum discussion for details. |
This is different from the bicycle tag since this should be used for routing only. Example: if there is a cycling path separated from the road, but in the region where this cycling path and road are found, it is permitted to cycle in the street or in the cycling path: there should be a way to specify that routing must use the cycling path. Tags on the road: bicycle=yes, bicycle=discouraged or no bicycle tag, and routing:bicycle=use_sidepath.
Warning: this tag is non-standard and applies to very specific regions like Quebec, Canada, where cycling path usage is not mandatory, but where almost all cyclists would use them. The tag makes sure that routing engines can ignore the bicycle tag because it would unrealistically route cyclists on dangerous roads which are still legal to cycle on. It could be replaced by bicycle=optional_sidepath but the "optional" wording is not powerful enough to explain the local context. While it is possible to use weighing in routing engines, it is not 100% reliable and could cause problems in large-scale simulations of bicycle trips (which have been tested in Quebec).
In most other cases, cycleway=separate means the exact same thing and is more semantically correct so should be preferred.
Common values
- yes
- no
- use_sidepath
- For further description see Bicycle#Bicycle Restrictions
- List of possible values with descriptions: see Key:access
- All used values on Taginfo