Key:cycle network

cycle_network
Description
A system of bicycle routes typically maintained or designated by a single agency or organization. Often corresponds to a well-defined route numbering protocol.
Group: Properties
Used on these elements
Documented values: 15
Useful combination
type=route route=bicycle network=*
See also
network=*
Status: unsupported “inuse” status
cycle_network=* More details at taginfo
Tools for this tag
taginfo · AD · AT · BR · BY · CH · CN · CZ · DE · DK · FI · FR · GB · GR · HU · IN · IR · IT · LI · LU · JP · KP · KR · NL · PL · PT · RU · ES · AR · MX · CO · BO · CL · EC · PY · PE · UY · VE · TW · UA · US · VN overpass-turbo OSM Tag History

[[Category:Key descriptions with status "unsupported “inuse” status"|cycle_network]]

Values for this key often parallel network=* values. Cycle routes already use network=* to indicate a route's relative level in a hierarchy of cycleway networks: network=icn = international, network=ncn = national, network=rcn = regional/state/provincial, network=lcn = local. So, cycle_network=* is used to help more precisely identify entities, organization (often government and hierarchical) responsible for assignment of route numbers (or names) and administration of a route numbering protocol of routes in that cycleway network. Ideally, all route relations in a single cycleway network should be tagged with the same cycle_network=* value.

While syntax for values of this tag (colon-separated hierarchical Namespace elements, often two- or three-letter acronyms or abbreviations) is used in other key-value tags, each nation/region of the world creates slightly different values as this key is more widely adopted. Values in a semicolon-separated list should be parsed separately. This wiki documents current tagging strategies for cycle_network=*. Please document here (and improve existing) cycle_network=* tags as more tagging conventions emerge around the world.

While public (often government-published) bicycle routes are generally compatible with OSM's ODbL, use good judgement entering into OSM quasi-private (neither government-sanctioned nor approved, but public, for example, when signed) route data; only enter route data compatible with OSM's license and/or with explicit permission. Public route data can always be entered into OSM, quasi-private route data can usually be entered, but private route data should not be entered. If they are "personally sourced," for example, if you ride a route published under copyright while your GPS captures a GPX file, those GPX data belong to you and as an OSM Contributor you may say you have legal nexus to contribute them. However, you may or may not have a legal right to put a particular route name=* on those data. Be cautious, especially with copyrighted data and names.

Austria

• cycle_network=AT:Vienna:Basisrouten — Bicycle routes in Vienna's Basisrouten system.

Belgium

Cycle networks appear to exist, cycle_network=* tagging is not prevalent.

Canada

• cycle_network=CA:CA — Trans Canada Trail, Canada's premier national bicycle route.
• cycle_network=CA — A Canadian quasi-national bicycle route, not a member of any particular national cycle network. Currently, a single route gets a flavor of this tag: cycle_network=US;CA, on International Selkirk Loop to denote it is partly in Canada. Note that international network=icn routes do not render in OpenCycleMap, but do in WaymarkedTrails' Bike renderer.
• cycle_network=CA:XY:Z — Provincial bicycle routes, where XY is the two-letter provincial postal abbreviation and Z is the name or abbreviation of the network. For example, in FR:Route verte (Québec's "Green Way" bicycle network), each of seven routes is tagged cycle_network=CA:QC:RV. If a province only numbers routes with a ref=* value, not naming its regional cycleway network (network=rcn), simply leave Z empty.
• cycle_network=CA:XY:Locality – Local bicycle routes, where XY is the two-letter provincial postal abbreviation and Locality is the name of the local jurisdiction. Part of a local cycleway network (network=lcn).

France

• cycle_network=FR — The V40 is tagged like this on individual ways; it may be better expressed as a single relation with this tag.
• cycle_network=FR:## — Departmental routes, where ## is the ISO 3166-2 department code. For example, cycle_network=FR:67 is used for cycle routes in the Bas-Rhin department.

Germany

Many existing values can become the same values preceded with DE: or other similar harmonizations. For example, radrevier.ruhr. Try clicking the taginfo link, then values in the leftmost column and finally the Overpass turbo link to display the subsets.

Hungary

Many existing values can become the same values preceded with HU: or other similar harmonizations. For example, Pilisbike. Try clicking the taginfo link, then values in the leftmost column and finally the Overpass turbo link to display the subsets.

Iceland

• cycle_network=IS:Lykilleiðir á Höfuðborgarsvæðinu – Key cycle routes of the Capital Area, signed for the most part.

Italy

Many existing values can become the same values preceded with IT: or other similar harmonizations. For example, Bicitalia and Biciplan - Comune di Cremona. Try clicking the taginfo link, then values in the leftmost column and finally the Overpass turbo link to display the subsets.

Japan

• cycle_network=JP:prefectural — Japan's prefectural-level bicycle routes.

New Zealand

Existing values can become the same values preceded with NZ: or other similar harmonizations. For example, Nga_Haerenga_The_New_Zealand_Cycling_Trail. Try clicking the taginfo link, then values in the leftmost column and finally the Overpass turbo link to display the subsets.

Phillipines

Existing values can become the same values preceded with PH: or other similar harmonizations. For example, Washington_Place_Homeowners'_Association. Try clicking the taginfo link, then values in the leftmost column and finally the Overpass turbo link to display the subsets.

Portugal

Existing values can become the same values preceded with PT: or other similar harmonizations. For example, Pista_Internacional_de_XCO_do_Jamor. Try clicking the taginfo link, then values in the leftmost column and finally the Overpass turbo link to display the subsets.

South Africa

Many existing values can become the same values preceded with ZA: or other similar harmonizations. For example, Bottelary MTB. Try clicking the taginfo link, then values in the leftmost column and finally the Overpass Turbo link to display the subsets.

Spain

Existing values can become the same values preceded with ES: or other similar harmonizations. For example, Zona Zero. Try clicking the taginfo link, then values in the leftmost column and finally the Overpass turbo link to display the subsets.

United Kingdom

The prefix UK: is in use even though the United Kingdom's ISO country code is GB:

• cycle_network=UK:National Cycle Network – Explicitly-numbered (in key ref=*) national cycleway network routes in the UK National Cycle Network (network=ncn), approved by Sustrans. These are often signed; improved signage is ongoing.
• cycle_network=UK:London Cycleways (formerly 'UK:London Cycle Superhighways') - Under construction; please add detail here if you know it.
• cycle_network=UK:London Quietways – Under construction; please add detail here if you know it. This network is expected to become part of London's rebranded 'Cycleways' network in 2019.
• cycle_network=UK:London Cycle Network – Under construction; please add detail here if you know it.

The seven routes with value Liverpool might become UK:Liverpool, or those tagged with value Warrington might become UK:Warrington. There may be additional similar harmonizations possible in the UK.

United States

• cycle_network=US:US – Explicitly-numbered (in key ref=*) national cycleway network routes in the United States Bicycle Route System (network=ncn), approved by AASHTO. USBRs are sometimes signed; improved signage is ongoing.
• cycle_network=US – The USA's four quasi-national (and quasi-private) bicycle routes: East Coast Greenway (ECG), Mississippi River Trail (MRT), Western New England Greenway (WNEG) and International Selkirk Loop (ISL). While each are independent routes "national in scope" in the United States, neither ECG, MRT, WNEG, nor ISL are members of any particular well-established national cycle network (network=ncn), as there is only one, the USBRS, and these are not member routes. Currently, ISL is tagged network=icn and cycle_network=US;CA.
• cycle_network=US:Z – Public (government-published/sanctioned) or quasi-private (neither government-sanctioned nor approved by AASHTO, but public data) wide-area regional cycleway network (network=rcn) routes, where Z is a brief name, standardized acronym or abbreviation of the regional network. For example, US Government's Department of the Interior, National Park Service's routes are in a network tagged cycle_network=US:NPS. There are also private routes characterized as wide-area regional cycleway networks which should not be in OSM as this violates our ODbL, but in some limited cases, are. For example, <3 routes in Adventure Cycling Association's private (commercial, proprietary, copyrighted) network are tagged cycle_network=US:ACA. (Over time, these tend to be replaced by USBRs).
• cycle_network=US:XY:Z – State bicycle routes, where XY is the two-letter state postal abbreviation and Z is the name of the network (if there is a name, otherwise Z is empty). For example, in the state of Georgia's regional cycleway network (network=rcn), each route is tagged cycle_network=US:GA and key ref=* with the value of its state-issued route number.
• cycle_network=US:XY:Locality – Local bicycle routes where XY is the two-letter state postal abbreviation and Locality is the name of the local jurisdiction (county/city/town/local routes). Part of a local cycleway network (network=lcn).