Talk:Ohio/Route relations/Bicycle routes

List of state bike routes?

Is there somewhere a list of numbered state bike routes for Ohio, and what trails they consist of? Vid the Kid 06:19, 20 July 2010 (UTC)

This page lists the numbered trails in Southwest Ohio, where the numbering system originated and is widely signed. Note that counties and local parks departments have generally been signing these routes in the style of a "statewide" bike route system. So I'm not sure if numbers are even used in other parts of the state, although ODOT's lettered routes certainly are. – Minh Nguyễn (talk, contribs) 06:33, 22 July 2010 (UTC)

Concurrency shield

Apparently there's a small concurrency between routes 1 and 3 in Xenia, where this shield is used: [1]. – Minh Nguyễn (talk, contribs) 21:27, 4 August 2013 (UTC)

Bicycle Routes

I found a map that lists all of the proposed bicycle routes, both state and national routes. [2]

Should we start adding ref tags to SBR 1 (Ohio-to-Erie Trail)? I edited the relation yesterday, but I don't know how the route numbers will appear on the map. Perhaps we should tag the OET's individual segments as "ref = SBR 1" and overlap it with the appropriate national bicycle routes wherever possible, similar to what OSM Ohio is doing with county roads and state routes.

One last thingː Summit County has an active bicycle network in the works, although they don't sign their bicycle routes using route numbers. [3] Akron has a separate bicycle network, but the routes are named after colors and terminate at the city limits. I have edited the bike routes in Akron.

--Bored (talk) 22:19, 8 January 2017 (UTC)

In addition to the route relations that Steve describes below, you can tag individual ways with refs as well. Since bike routes often travel over roads with their own route numbers, we tag the bike route refs using tags such as lcn_ref=* and rcn_ref=* instead of ref=*. Some renderers recognize these tags on individual ways, while others recognize ref=* and cycle_network=* on route relations – use them all while we're in this state of transition. No prefix is needed on the way tags; we want to encourage renderers to use cycle_network=* to disambiguate.

Specifically regarding the concurrency between SBR 1 and the proposed USBR, there should be an ncn_ref=* alongside the existing rcn_ref=* on each way, and each way should be a member of a new network=ncn cycle_network=US:OH state=proposed if there isn't already one.

It's fine for routes to be identified by names or colors. The way-tagging scheme doesn't cope so well with those identifiers, but you can tag the relation with name=* and color=*, and some renderers such as Waymarked Trails will respect those tags.

 – Minh Nguyễn (talk, contribs) 16:23, 9 January 2017 (UTC)

State bike route tagging

OSM has well established tagging for state bicycle routes: see United_States/Bicycle_Networks. Follow existing route relation tagging which shows network=rcn + ref=1 are correct on Ohio-to-Erie Trail Ohio-to-Erie Trail. The "r" in rcn is for regional, which equates to "statewide" in the USA, so entering "SBR" into a ref=* would be redundant (effectively, SBR = rcn) — simply the numeral 1 will do as the tag value. OpenCycleMap (Cycle Map layer) displays network=ncn (USBRS) as red, network=rcn as purple and network=lcn as dark blue, with shields from the ref=* tag limited to three alphanumeric characters. But, don't tag for the renderer, just tag correctly (and yes, harmoniously with the renderer). --User:Stevea 23:39, 8 January 2017 (UTC)