WikiProject U.S. Bicycle Route System
|Part of WikiProject United States.|
An OSM project to map the U.S. Bicycle Route System (USBRS). The USBRS is a developing national network of bicycle routes, which will link urban, suburban, and rural areas using a variety of appropriate cycling facilities. To date, 15 U.S. Bicycle Routes spanning 5847 miles (nearly 10000 km) have been established in 12 states: Alaska, Illinois, Kentucky, Maine, Maryland, Michigan, Minnesota, Missouri, New Hampshire, North Carolina, Tennessee and Virginia. Presently, more than 40 states are working to create U.S. Bicycle Routes. These routes are selected and maintained by State Departments of Transportation (DOTs), and designated and catalogued by the American Association of State Highway and Transportation Officials (AASHTO). Source: Adventure Cycling Association.
By using OSM to create high quality maps of this nascent network (and wonderful national resource), we can promote its development, growth and use. OSM is now a positive tool for geographic communication of existing and developing bicycle routing at local, statewide and national levels in the USA!
| international cycling map created from OSM data is available, provided by Andy Allan. The map rendering is still being improved, the data are updated every few days. It shows National Cycle Network cycle routes, other regional and local routes, and other cycling-specific features, such as:
|Lonvia's Cycling Map by Sarah Hoffman is an overlay which shows marked cycle routes around the world. Updated daily, it renders actual routes without the state=proposed tag. Therefore no proposed routes (or numbering protocols) are displayed.|
Actual USBRs in OSM
As of July 2013, OpenStreetMap in the USA, via the Cycle Map layer, displays the current USBRS (or endeavors to do so as routes are newly approved by AASHTO) as solid red lines badged with red route numbers. The Cycle Map layer also displays USBR proposed routes (ongoing proposal discussions at a state level distinctly moving towards AASHTO application as USBRs) as dashed red lines. The Cycle Map renderer displays both actual and proposed routes, and the http://cycling.waymarkedtrails.org (Lonvia) renderer displays only actual (not proposed) routes.
OSM also displays two significant national bicycle routes which are not strictly part of the USBRS: the East Coast Greenway (ECG, which both shares and diverges from segments of USBR 1) and the Mississippi River Trail (MRT, the Minnesota segments of which are identical to USBR 45 and 45A). Each of these routes (ECG & MRT) traverse several states and each is about 3000 miles (5000 kilometers) long. Hence, these two quasi-private (not government) bicycle routes (ECG & MRT) are determined to be so "national in scope" in the USA that their inclusion in OSM's national cycleway network is asserted (as named, but not numbered ncns). ECG & MRT exist alongside USBRs in OSM's national bicycle route hierarchy, but are not USBRS routes (except for USBR 45 and 45A in Minnesota, which are "both" USBRs and part of MRT).
Additionally, as USBR 25 in Ohio comes closer to becoming the actual USBR 25, the also quasi-private Underground Railroad Bicycle Route (UGRR, traversing several states over 2000 miles) may become a third "national in scope" route displayed in OSM as an ncn. This would occur as UGRR potentially transitions (state by state) to USBR 25, most likely starting with Ohio.
Here are current actual USBRS routes in OSM:
|U.S. Bicycle Route 1||XML, check, manage, JOSM, history, view, gpx )(||Maine, New Hampshire, Virginia, North Carolina|
|U.S. Bicycle Route 1A||XML, check, manage, JOSM, history, view, gpx )(||Maine|
|U.S. Bicycle Route 8||XML, check, manage, JOSM, history, view, gpx )(||Alaska|
|U.S. Bicycle Route 20||XML, check, manage, JOSM, history, view, gpx )(||Michigan|
|U.S. Bicycle Route 23||XML, check, manage, JOSM, history, view, gpx )(||Tennessee|
|U.S. Bicycle Route 35||XML, check, manage, JOSM, history, view, gpx )(||Michigan|
| U.S. Bicycle Route 45
(co-branded as Mississippi River Trail in Minnesota)
|XML, check, manage, JOSM, history, view, gpx )(||Minnesota|
| U.S. Bicycle Route 45A
(co-branded as Mississippi River Trail in Minnesota)
|XML, check, manage, JOSM, history, view, gpx )(||Minnesota|
|U.S. Bicycle Route 50||XML, check, manage, JOSM, history, view, gpx )(||Maryland|
|U.S. Bicycle Route 76||XML, check, manage, JOSM, history, view, gpx )(||Virginia, Kentucky, Illinois, Missouri|
|U.S. Bicycle Route 87||XML, check, manage, JOSM, history, view, gpx )(||Alaska|
|U.S. Bicycle Route 95||XML, check, manage, JOSM, history, view, gpx )(||Alaska|
|U.S. Bicycle Route 97||XML, check, manage, JOSM, history, view, gpx )(||Alaska|
|U.S. Bicycle Route 108||XML, check, manage, JOSM, history, view, gpx )(||Alaska|
|U.S. Bicycle Route 208||XML, check, manage, JOSM, history, view, gpx )(||Alaska|
Proposed USBRs in OSM
It is critically important not to assume that a USBR corridor plus a guess on your part (for example, that there is already a state or regional route through that corridor) "means" that you can or should enter a proposed USBR into OSM. Only do so when you have solid knowledge that there is coordinated statewide activity actively assembling a USBR. This usually happens only as towns and cities along the route, affected counties, and the statewide Department of Transportation are all communicating and exhibit active and involved coordination. As the AASHTO approval process completes twice a year (in the spring and autumn), a rough timeframe of a route first arriving on this list, proceeding to application and gaining approval is approximately six to 24 months.
In addition to type=route + route=bicycle, tag such proposed and numbered statewide relations with network=ncn + cycle_network=US:US + name=USBR# (name of state) + ref=USBR# + state=proposed. It is helpful to add the tag source=Where you learned the route members if you know this information (e.g. "State DOT web site" or "County Bicycle Committee Meeting, January 2014").
In the earliest stages of an existing network=rcn state route becoming a proposed network=ncn USBR route, you may wish to simply add an ncn=proposed tag to the existing state route, which superimposes a red dashed line on top of the existing solid turquoise line (with no red numbered shields, keeping the turquoise numbered shields). If you do this (shortcut), it is correct to eventually update the tags so they include those in the previous paragraph, as this requires changing the ref # from the rcn-numbered (state) route to the ncn-numbered (USBR) route. An intermediate status in this scenario is likely two relations: initially the state relation, then the shortcut of adding ncn=proposed to the state relation, then two relations (one representing the actual state route, another representing the proposed national route/USBR) which stay synced, then back to a single relation after AASHTO approval, assuming the state relation has become subsumed by the USBR.
Creating super-relations (containing multiple relations of network=ncn routes, each relation containing road/cycleway members within a single state) is only appropriate for proposed routes when they are simultaneously proposed in multiple states. In this case, create relations so they contain road/cycleway members within a single state. Then, if at least two states (for a single USBR), have incipient ncn routes proposed, these can be appropriately assembled into a super-relation. A current example of this is proposed USBR 90 in Alabama, Mississippi and Louisiana for a total of three statewide relations in the super-relation for proposed USBR 90.
What follows are not yet actual USBRs, they are only serious proposals, with varying levels of activity. When at least this level (or more) of USBR development activity happens in a state, whether to an existing network=rcn state route or with an as-yet-unmapped-in-OSM route, tag the route as above where it is proposed. As with any route relation, this means initially creating a properly-tagged relation, then adding/editing member roads/cycleways in that relation.
Please keep this table synchronized with state registry wiki pages (for example, Ohio).
|Proposed USBR||Relation(s)||State(s)||Status and notes - usually where coordinated activity is taking place that will lead to a state application to AASHTO|
|USBR 10||Washington XML, check, manage, JOSM, history, view, gpx )(||WA, ID, MT, ND, MN||Incipient in Washington state: seeded as SR 20 east of US 97.|
|USBR 11||Virginia XML, check, manage, JOSM, history, view, gpx )(||MD, VA, NC||Incipient in Virginia. Concurrent with Blue Ridge Parkway from North Carolina northeasterly to a concurrency with USBR 76 continuing to near Waynesboro.|
|USBR 23||No relation yet in Kentucky nor Alabama||KY, TN (done), AL||Possibly/perhaps incipient in Alabama. Potential early emergence in Kentucky suggests Mammoth Caves State Bicycle Route as a connection to USBR 23 in Tennessee.|
|USBR 25||Alabama XML, check, manage, JOSM, history, view, gpx ) Mississippi (XML, check, manage, JOSM, history, view, gpx ) Ohio (XML, check, manage, JOSM, history, view, gpx )(||AL, MS, TN, KY, OH, PA, NY, ON||
An Alabama DOT document from 2009 says on page 12 "it is recommended that the U.S. Bike Route 25 in Alabama be the same as the Underground Railroad Bicycle Route." However, Alabama appears not to be further developing this route nor does it have an active proposal to bring this route to AASHTO.
|USBR 30||XML, check, manage, JOSM, history, view, gpx )(||WI||Incipient in Wisconsin. Presently concurrent with the Elroy-Sparta State Bike Trail.|
|USBR 35||Indiana XML, check, manage, JOSM, history, view, gpx ) Mississippi (XML, check, manage, JOSM, history, view, gpx )(||MI (done), IN, KY, TN, MS|| Active development in Indiana. See http://www.indianatrails.com/content/usbr35. This map is not correct in parts of Indianapolis, though more agreement should emerge soon. A newer route goes through Shelbyville with a possible alternate through Greenwood.|
The Natchez Trace is emerging/incipient as USBR 35 (and possibly part of 25) in Mississippi.
|USBR 50||XML, check, manage, JOSM, history, view, gpx )(||DC, MD (done), PA, OH, IN, IL, MO, KS, NE, CO, UT, NV, CA|| Proposed USBR 50 is pending AASHTO approval in the District of Columbia, three discontiguous segments in Ohio, a still-to-be-corrected route in Indiana and nearly complete in Nevada.|
Still undergoing significant adjustments in Ohio. A more current Ohio routing should be available from Adventure Cycling Association soon. In the meantime, three separate relations are keeping track: one near the Indiana border, another in the Miami Valley (MVRPC counties), and a third in Central Ohio (MORPC counties). These three relations will need to be coalesced into one eventually -- most likely as USBR 50 gets closer to an AASHTO application by Ohio.
|USBR 50 Scenic||Ohio XML, check, manage, JOSM, history, view, gpx )(||OH||Complete, but awaiting completion of its "parent" route 50 in Ohio, and then AASHTO application.|
|USBR 51||Arkansas XML, check, manage, JOSM, history, view, gpx ) (XML, check, manage, JOSM, history, view, gpx )(||LA, AR, MO||In the early stages of development. In OSM it is now two discontiguous relations: one (between Bentonville and Fayetteville) is concurrent with the Razorback Regional Greenway in northwestern Arkansas, another (along US 71) is near Fort Smith. The Fort Smith segment may continue onto US Route 71B (from US Route 71), routing north of here is unclear.|
|USBR 66||XML, check, manage, JOSM, history, view, gpx )(||CA, AZ, NM, TX, OK, KS, MO, IL|| Incipient in California, New Mexico, Oklahoma.|
In California, USBR 66 is described by the document "California Bicycle Route 66 Concept Plan (Draft)" published 8/15/2013 by the Southern California Association of Governments (SCAG). The eastern portion of the route at the Arizona border is initially "seeded" for several miles westward to Parker Junction. Volunteers in California are in early stages of incorporating into OSM additional route segments from this document, including harmonizing with many local jurisdictions which (if any) of the listed occasional alternate routes might be entered.
|USBR 76||Wyoming XML, check, manage, JOSM, history, view, gpx )(||OR, ID, MT, WY, CO, KS||Incipient in Wyoming: specifically, the town of Dubois has dubbed US 287 as a USBR 76 "seed" in Wyoming.|
|USBR 80||Arkansas XML, check, manage, JOSM, history, view, gpx )(||OK, AR, TN, NC||Incipient in Arkansas. It is unclear where the route goes east of Pulaski at SR 5 and South University Avenue: north to SR 10? Or east on what might be SR 5 or might also be US 708?|
|USBR 84||Alabama XML, check, manage, JOSM, history, view, gpx )(||SC, GA, AL, MS, AR, TX||An Alabama DOT document from 2009 says on page 12 "it is recommended that U.S. Bike Route 84 follow the same route as the state bicycle route (EW2)." However, Alabama appears not to be further developing this route nor does it have an active proposal to bring this route to AASHTO. This route is tagged with network=rcn + ref=EW2 + cycle_network=US:AL + ncn=proposed so the first two keys cause Cycle Map to display a solid turquoise line badged with turquoise EW2 shields, and the last key superimposes a dashed red line (with no red 84 shields).|
|USBR 90||XML, check, manage, JOSM, history, view, gpx )(||FL, AL, MS, LA, TX, NM, AZ, CA|| Incipient in Alabama, Mississippi, Louisiana.|
In Alabama, USBR 90 is seeded as SR 188 through bayou La Batre.