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, linking urban, suburban, and rural areas using a variety of appropriate cycling facilities. To date, 18 U.S. Bicycle Routes spanning 6834 miles (almost 11000 km) have been established in the District of Columbia and 15 states: Alaska, Illinois, Kentucky, Maine, Maryland, Massachusetts, Michigan, Minnesota, Missouri, New Hampshire, North Carolina, Ohio, Tennessee, Virginia and Washington state. 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.|
Approved USBRs in OSM
As of July 2013, OpenStreetMap in the USA, via the Cycle Map layer, displays all approved routes in the current USBRS as solid red lines badged with red route numbers (or endeavors to do so as routes are newly approved by AASHTO). The Cycle Map layer also displays USBRS 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 approved and proposed routes, and the Lonvia renderer displays only approved (not proposed) routes.
OSM also displays two significant national bicycle routes (as solid red named, not numbered ncns) 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 proposals for USBR 25 in Ohio come closer to becoming approved, the also quasi-private Underground Railroad Bicycle Route (UGRR or UGR, traversing several states over 2000 miles) may become a third "national in scope" route displayed in OSM as an ncn. This might occur as UGRR potentially transitions (state by state) to USBR 25, perhaps starting with Ohio.
Here are current approved USBRS routes in OSM:
|United States Bicycle Route 1||Maine, New Hampshire, Massachusetts (a "segment"), Virginia, North Carolina|
|United States Bicycle Route 1A||Maine|
|United States Bicycle Route 8||Alaska|
|United States Bicycle Route 10||Washington|
|United States Bicycle Route 20||Michigan|
|United States Bicycle Route 23||Tennessee|
|United States Bicycle Route 35||Michigan|
|United States Bicycle Route 36||Illinois|
|United States Bicycle Route 37||Illinois|
| United States Bicycle Route 45
(co-branded as Mississippi River Trail in Minnesota)
| United States Bicycle Route 45A
(co-branded as Mississippi River Trail in Minnesota)
|United States Bicycle Route 50||District of Columbia, Maryland, Ohio (about 62% done; being completed in OSM now, see below)|
|United States Bicycle Route 76||Virginia, Kentucky, Illinois, Missouri|
|United States Bicycle Route 87||Alaska|
|United States Bicycle Route 95||Alaska|
|United States Bicycle Route 97||Alaska|
|United States Bicycle Route 108||Alaska|
|United States Bicycle Route 208||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, publishing something more substantial than an incomplete or simple draft map: an "active statewide project." (The so-called "high bar standard" for entering into OSM a proposed USBR). 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 statewide relations with network=ncn + cycle_network=US:US + ref=USBR# + state=proposed. If you know this, add source=Where you learned the route members (e.g. "State DOT web site" or "County Bicycle Committee Meeting, January 2014"). To each route that is a member of a super-relation with other routes sharing the same route number, also add the tag name=USBR# (name of state) to disambiguate each state's route as a super-relation member.
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. In Cycle Map layer, this 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/national) route. An intermediate status in this scenario may be 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 USBR/national route) which stay synced, then (perhaps) back to a single relation after AASHTO approval (assuming the state relation is deleted, having 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 network=ncn routes proposed, these can be assembled into a super-relation. A current example of this is proposed USBR 90 in Alabama, Mississippi and Louisiana which contains exactly three statewide relations in the super-relation for proposed USBR 90.
What follows are not yet approved USBRs, they are only serious proposals, with varying levels of activity. When at least this level 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, consider tagging the route as above where it is proposed. (Such consideration must include knowledge of a DOT's project to distinctly move towards a USBR application, not simply a corridor or vague draft map, but actual turn-by-turn directions of a largely complete route). As with any route relation, this means initially creating a properly-tagged relation, then adding/editing member roads/cycleways to that relation. If you wish to adopt one of the proposed routes below marked VOLUNTEER! please contact Kerry Irons via email using irons54vortex at gmail (dot) com. Also, please do your best to keep this wiki page section updated with your progress, for example, create a BrowseRelation entry for new routes. If you don't or can't update this wiki section, please contact stevea via OSM missive with notes of your progress. Finally, 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||Michigan||WA (done), ID, MT, ND, MN, WI, MI||In Michigan, proposed USBR 10 has partially emerged and is entered into OSM as US-2 from Escanaba to St. Ignace. USBR 10 might be continued west from Escanaba at some future date but there are no plans for that at present.|
|USBR 11||Virginia||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. Proposed to follow the Blue Ridge Parkway to Front Royal and then mostly secondary roads to Harpers Ferry, West Virginia. VOLUNTEER to adopt and enter this route!|
|USBR 21||No relation yet in Ohio||OH||
Identified in ODOT's Access Ohio 2040 transportation plan as that state's highest priority USBR. The draft route map indicates that the route will largely follow the , superseding State Bike Route 1. As that is an existing statewide route, already correctly entered into OSM as an rcn route, we wait on further efforts here until ODOT moves closer to motion on a state USBR 21 project before we might either tag the state route with ncn=proposed, include Ohio rcn=1 into an ncn ref=21 relation, or create an altogether new ncn ref=21 relation (different than rcn=1).
|USBR 23||No relation yet in Kentucky nor Alabama||KY, TN (done), AL|| Potential early emergence in Kentucky suggests Mammoth Caves State Bicycle Route as a connection to USBR 23 in Tennessee.|
Possibly/perhaps incipient in Alabama. As there is no statewide project in either state, there is some discussion that this row entry in this table be deleted.
|USBR 25||AlabamaMississippi Ohio||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||Wisconsin||MT, ND, SD, MN, WI, MI (done), OH, PA, NY, VT, NH||
Incipient in Wisconsin. Presently concurrent with the Elroy-Sparta State Bike Trail, but there is news from Adventure Cycling Association that this route is "nearly fully defined." The route will follow DNR trails nearly across the state except for an on-road portion from roughly Reedsburg to Madison. Two alternates are considered for the on-road portion, one using the ferry to cross the Wisconsin River at Merrimac and the other crossing the river in Sauk City. Possibly two routes will be implemented: one as USBR 30 and one as USBR 30A. The Wisconsin Bike Federation may have a soft-copy map document -- it is believed turn-by-turn directions are available. OSM contact: hobbesvsboyle
|USBR 30A||No relation yet in Ohio||OH:SAN, OH:ERI, OH:LOR||Not mapped yet. Proposed as part of ODOT's Access Ohio 2040 transportation plan. Stalled here (as a "red proposed route") until this gets further momentum from ODOT. (Too vague as a draft route to be considered a serious proposed route).|
|USBR 35||IndianaMississippi||MI (done), IN, KY, TN, MS|| Active development in Indiana. OSM does not display the correct route in parts of Indianapolis, though more agreement should emerge soon. A newer route goes through Shelbyville with a possible alternate through Greenwood. VOLUNTEER!|
The Natchez Trace is emerging/incipient as USBR 35 (and possibly part of 25) in Mississippi.
|USBR 36||Indiana||IL (done), IN||A draft route is emerging in Indiana (Lake Michigan shore): from the Illinois state line at Eggers Wood to New Buffalo, Michigan, as provided by northwest Indiana (NIRPC) counties. This route is mostly on trails though some will be on roads where trails are in development or not suitable for touring bicycles. In OSM, the route is seeded as 112th Street at its very western end to connect to USBR 36 in Illinois at Eggers Wood. VOLUNTEER!|
|USBR 37||MichiganNo relation yet in Wisconsin||IL (done), WI, MI|| Wisconsin appears to be waiting on completion of USBR 30 before progress on USBR 37 continues in that state.|
A route proposal in its entirety has emerged and is fully entered into OSM in Michigan (Upper Peninsula) as Michigan 35 from Menominee to Escanaba (continuing a potential USBR 37 in Wisconsin near or in Marinette).
|USBR 40||No relation yet in Ohio||OH||
In Ohio, ODOT's Access Ohio 2040 transportation plan proposes a route for USBR 40 that follows the Great Ohio Lake-to-River Greenway in eastern Ohio but otherwise follows State Bike Route K, which has not been mapped. Hence, this is stalled here (as a "red proposed route") until further forward motion from ODOT or there is a published Route K map available (in which case it should be entered into OSM as an rcn).
|USBR 40A||No relation yet in Ohio nor Indiana||OH:LUC, OH:FUL, OH:WIL||Not mapped yet. As part of ODOT's Access Ohio 2040 transportation plan, the proposed route would largely follow the and North Coast Inland Trail. The project awaits route data in the form of a map, turn-by-turn directions or a GPX file.|
|USBR 50||DC (done), MD (done), PA, WV, OH, IN, IL, MO, KS, NE, CO, UT, NV, CA|| Emerging in Pennsylvania, entered in West Virginia, AASHTO-approved, fully described and about 62% entered into OSM in Ohio, still-to-be-corrected in Indiana and largely complete in Nevada.|
In Pennsylvania, emergence of this proposed route doesn't yet specify details except that it will include the Panhandle Trail, Montour Trail and some secondary roads. The eastern segment is speculative.
|USBR 50A||Columbus, OH||OH:FRA, OH:DEL, OH:LIC||Completely mapped. Part of Ohio's forthcoming USBR 50 submission to AASHTO. (Huh? USBR 50 was recently approved, but did not include 50A. Might be deleted from this table and the relation suppressed from displaying in OCM).|
|USBR 51||Arkansas||LA, AR, MO||In the early stages of development in Arkansas (only). 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||CA, AZ, NM, TX, OK, KS, MO, IL|| Incipient in California, New Mexico, Oklahoma.|
In California, USBR 66 is described by the "California Bicycle Route 66 Concept Plan (Draft)" document that was published on 8/15/2013 by the Southern California Association of Governments (SCAG). Both the "Preliminary Route Concept" and the "Alternate Route Concepts" are now fully entered into OSM. Volunteers are working to harmonize with many local jurisdictions which (if any) of the alternate routes might become part of a more final route. There remains a gap at MCLBB: the short version is that a formal request is going up the chain of command. Being optimistic, permission to traverse Boll Avenue (daytime only, must have acceptable ID...) has occurred before for a group of interstate bicyclists, so this approval might be considered "pending." ACA says SCAG receiving a MOU as a next intended step seems about right, though of course these things take time. Walt in southern California got more jurisdictions harmonious on the routing, accelerating the 66 effort by at least a year! One volunteer has offered to scout POIs along portions of the proposed route. Are there any geographical suggestions for her trip?
|USBR 76||Wyoming||OR, ID, MT, WY, CO, KS||Incipient in Wyoming. The route will follow US 287 from near Jackson to Rawlins, then US 287 Bypass onto Wyoming 76 onto I-80 at Exit 221 to Exit 235 onto SR 130, then SR 230 to the Colorado state line, where it becomes SR 125 in Colorado. There is a challenge with traffic and road quality inside Yellowstone National Park. A possible routing would go through Jackson onto SR 22 into Idaho. What IS known about this route is entered into OSM (and this is what is meant by "green"), but this omits yet-to-be-determined routing through the northwest part of the state.|
|USBR 80||Arkansas||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||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||FL, AL, MS, LA, TX, NM, AZ, CA|| Florida has issued a policy to develop USBR 90.|
Incipient in Alabama, Mississippi, Louisiana.
In Alabama, USBR 90 is seeded as SR 188 through bayou La Batre. VOLUNTEER to adopt and enter this route!