Talk:United States Bicycle Route System

Network tag

Why don't you just use the ncn/rcn/lcn tags for these routes like in the rest of the world? Then the routes can be displayed with the current maps that show cycle routes and you don't need to setup your own renderers. Perhaps create a new tag if it's needed to have a usbrs tag. --Eimai 12:35, 11 March 2009 (UTC)

I agree, and I'm in the US. operator=AASHTO seems more appropriate to distinguish the US bike system from any other national cycle network. --Hawke 16:34, 11 March 2009 (UTC)

Now we do (use ncn routes for USBRS). Also, operator=AASHTO isn't exactly correct as AASHTO simply acts as a coordinating body to "coalesce" USBRs published by each state into the national USBRS network. If you MUST enter an operator, it would either be the state DOT or county, city or private owners of the road/cycleway segment. This can be difficult to determine for any given route segment, though the state DOT should have all of these data available as/when they make the application to AASHTO for the USBR. --Stevea (talk) 18:25, 7 August 2014 (UTC)

Update: OSM now uses cycle_network=US:US as a tag on the route relation to identify USBRS routes. We use cycle_network=US to distinguish most quasi-national routes as distinguished from USBRs. --Stevea (talk) 00:18, 9 August 2016 (UTC)

Update: OSM now uses cycle_network=US:USA as a tag on the route relation to identify the 9/11 Trail route (and other routes that might be designated "national" via federal legislation). The 9/11 Trail was created uniquely unlike any other national bike route in the USA (from unanimous federal legislation) and hence deserves a network membership distinct from cycle_network=US (generic quasi-national routes not a member of any particular route network), cycle_network=US:US (USBRs, numbered in the USA's only official national route network), or even cycle_network=US:NPS (as the National Parks Service's parent Department, Interior, is distinctly specified in the legislation to not be sole administrator of 9/11 Trail). It is believed a non-governmental organization will at least partly administer some aspects of 9/11 Trail. Stevea (talk) 06:43, 8 December 2021 (UTC)

Numbered network vs unnumbered

What is the relationship between the numbered and unnumbered networks? The Adventure Cycling Route Network appears different to the USBRS? I take it that the only difference USBRS is intended to be a signposted network, whereas the Adventure Cycling Association network is unsigned? Is there even an OpenStreetMap project for mapping the ACA network? ChrisB 21:32, 29 September 2011 (BST)

Numbered routes in the national network are USBRs. Named routes in the national network (there are currently only two, East Coast Greenway and Mississippi River Trail) are known as "quasi-national" routes, as they are not strictly part of the USBRS, but are so "national in scope" that they rise to become members of the national level of the hierarchy (as named, not numbered routes). The next level down, "regional/state" contains statewide (DOT) networks, as well as larger-scope regional routes like ACA routes (e.g. Transamerica Trail, Underground Railroad Bicycle Route...). To be clear, regional ACA routes are NOT part of the USBRS. Also, not all ACA routes (known as "private") are in OSM, as they are proprietary/commercial property of ACA. When ACA routes DO get entered into OSM, and traverse multiple states, it seems most useful to enter them state-at-a-time (network=rcn) and bundle these into a named super-relation. This is because it can happen that an ACA route might eventually get "promoted" to a USBR, through a lengthy public process involving first the state where this takes place, then as that state's DOT applies to AASHTO for the route to become a USBR. In fact, exactly this process is taking place with ACA's Transamerica Trail (TA) as it is slowly-but-surely becoming superseded by the super-relation for USBR 76 (generally westwardly, now as far west as Kansas). --Stevea (talk) 18:25, 7 August 2014 (UTC)

Update: there are now THREE quasi-national routes. In addition to ECG and MRT there is now also WNEG. --Stevea (talk) 23:57, 8 August 2016 (UTC)
Update: there are now FOUR quasi-national routes; we have added the US portion of ISL. --Stevea (talk) 11:52, 12 November 2016 (UTC)
Update: there are now FIVE quasi-national routes; we have added the 9/11 Trail. In a divergence from all other quasi-national routes, this is not tagged cycle_network=US, but is rather tagged cycle_network=US:USA due to the unique method by which it entered as a national route (federal legislation). This is also distinct from cycle_network=US:NPS, even as the National Park Services's parent US Department of Interior is 9/11 Trail's guiding agency. (But the legislation specifies NPS is neither sole administrator nor is 9/11 Trail a "unit" of its administration). It is believed that a (non-profit?) non-governmental organization will handle at least some administration of the Trail. Stevea (talk) 05:30, 8 December 2021 (UTC)
Update: there are now SIX quasi-national routes; we have added the Natchez Trace. Stevea (talk) 01:29, 3 December 2022 (UTC)

Link to GPX without copyright

There was a link to http://ridewithgps.com/routes/920401, which is a GPX file without any copyright information and which appears to be google-drived. I have removed it. -- unsigned comment added by user:Pnorman 18:34, 31 May 2014

Paragraphs

Some of the entries in the proposals table contain multiple paragraphs separated by line breaks (<br />). It's hard to tell where a paragraph begins and ends. Let's skip a line to create a new paragraph. – Minh Nguyễn (talk, contribs) 10:24, 9 June 2014 (UTC)

Adventure Cycling Association (ACA) routes getting promoted from rcn to ncn or icn

Continuing from "Numbered network vs unnumbered" above, some ACA routes which are or could be entered into OSM might get promoted from rcn to ncn, or even icn if they cross an international border. To wit, six ACA routes (should they be entered into OSM) have been identified as candidates for such promotions: Underground Railroad (UGRR), Northern Tier (NT), Pacific Coast (PCBR), Transamerica Trail (TA), Atlantic Coast (AC), Southern Tier (ST). The first three might be promoted to icn, the last three to ncn (as quasi-national, quasi-private). However, these are not fully entered, nor are they guaranteed to be up-to-date AND, these are proprietary route data belonging to ACA under copyright. This makes determining what to do difficult, as ACA has stated (via Kerry Irons) that ACA management would prefer that these data not be entered into OSM, but "they realize that this is going to happen." A major concern of ACA is that OLD and OBSOLETE data will remain in OSM after entry of ACA's routes (in violation of our ODBL), but will not be corrected as ACA updates them. -- Stevea (talk) 03:21 24 January 2016 (UTC)

Additional note: it appears that GDMBR, TA west of USBR 76 at the Kansas/Colorado border (from Colorado to Oregon) and UGRR (partially) are the only ACA routes entered into OSM. The first two appear to be completely entered. GDMBR is not network=ncn nor network=rcn, which require a route=bicycle tag, rather GDMBR is tagged route=mtb, which does not get a network=* tag. TA is essentially superseded by USBR 76 east of Colorado, and is entered as statewide network=rcn relations in Colorado, Wyoming, Idaho and Oregon. UGRR is substantially, though only partially entered (perhaps 75%?) as statewide network=rcn relations. This is only 3 (2.75?) out of 24 ACA routes. Any or all of these ACA route data now entered into OSM might be obsolete, having been updated by ACA. Finally, it should be noted that while both the state of California and ACA "offer" slightly different routes called Pacific Coast Bicycle Route, it is intended that OSM represent the state of California version, not the ACA version, as the California version is signed on the ground whereas no ACA routes are signed. -- Stevea (talk) 23:50 16 February 2016 (UTC) and 03:48 10 August 2016 (UTC)

Recently, the Colorado-to-Oregon portion of (not-necessarily-authorized-to-enter-into-OSM by ACA) Transamerica Trail (TA) was "artificially promoted" from network=rcn to network=ncn. This was changed back to network=rcn for several reasons:

• While a good argument can be made that TA is a "national route," it truly is being subsumed by USBR 76 and so in reality 76 is the "more" national route

• OCM's rendering of purple/red boundary vividly shows where the boundaries between regional and national route exists

• Until further AASHTO approvals which the remaining four states' DOT might apply for (but haven't yet), such a distinction is important to make, respect and note with something like a level / color change

• OSM identified in 2014 the overloading of network=* hierarchies for route=bicycles in the USA needed to do this to accommodate this relationship between ACA routes and USBRs (in this particular way, following these particular assignments of routes into hierarchy levels).

These hierarchy guidelines have been further refined with the modest and controlled growth of quasi-national routes, accommodating growth in the USBRS and documenting ACA routes as expressed in OSM. This is especially true with clarification via cycle_network=US, cycle_network=US:US and cycle_network=US:ACA tags.

OSM-US, ACA (management) and AASHTO have a respectful relationship built with lots of give and take and clear understanding of rules (such as copyright as well as the more informal ones noted here that we crafted in 2014). A bold assertion by a single OSM volunteer mountain bike enthusiast to "artificially promote" from regional to national both confuses our defined semantics for wider map consumers and disrespects the understandings OSM has in place to minimize, de-emphasize and correct data which should not be in OSM (unless with explicit permission, which, for TA and indeed all ACA routes, OSM does not have). Let's continue with a non-disruptive consensus of "keeping it to 2.something, and falling" ACA routes with the understandings in place which have worked for years: keep ACA routes regional (and shrinking, unless explicit permission to enter them is granted), document the growth in the USBRS as we have and do and allow sensible growth into US quasi-national namespace, well-documented with cycle_network=* tagging. If/as ACA were to grant OSM explicit permission to enter ACA route data, OSM has identified sensible tagging strategies for them, but OSM does not have that permission today, so we must respect today's hierarchy guidelines as they now work by informed consensus. I continue to welcome Discussion on these topics here. -- Stevea 03:48 10 August 2016 (UTC)

Routes becoming unidirectional, USBRs as GPX

Late 2017 confirmed BrowseRelation's GPX link is sensitive to the "version 1 methodology" with which many of these routes are expressed (one bidirectional relation per route, with forward roles at dual carriageways, not two separate unidirectional route relations, one in each direction). Until newer unidirectional USBRs are completed (as of 2018-Q2 this is early work), GPX files based on wiki-downloading these routes contain noise at dual-carriageway splits. Instead of the single-relation, bidirectional method by which USBRs are entered now, improvements begin: this WikiProject (going forward) strives to enter USBRs as two unidirectional routes per state application, collected together in a super-relation. This eases GPX translation, eliminating noise now found in the GPX files that result from data entered using the original method (largely prevalent now/2018, call it v1). This conversion of existing (bidirectional) routes to unidirectional routes is ongoing. You are welcome to complete these moderate-difficulty tasks (duplicate existing bidirectional USBR relation, create directionality and fix such issues in each relation, place both properly-tagged relations into a new, properly-tagged super-relation, test with BrowseRelation GPX link). (Moved to Discussion from Page) Stevea (talk) 00:54, 15 May 2018 (UTC)

There is some early work to both create new routes as "unidirectional" (and tied together with a super-relation) as well as make it easy to click a GPX link in the BrowseRelation function of our wiki and download a nice, clean, neat GPX. We are a ways from that, as the GPX link can introduce errors at dual carriageway splits as we have created (bidirectional) USBR relations now (up to early 2018). Going forward, better structure emerges that will allow these "one-click downloads" to proceed in a method that is easy, straightforward for downloaders (USBR GPX consumers) and either becomes automated (or automate-able) and/or a table of single-click-download-a-GPX-file tables. This might take the form of a new page/table to do this (linked here, of course) and/or changes to the existing table. It is likely that this wiki bifurcates along these lines in 2018-Q2, so now begins such a transition. Stevea (talk) 03:44, 7 May 2018 (UTC)

As a workaround solution: try JOSM, File -> Download Object... of the route (by relation number) then File -> Export to GPX... as some users report more successful GPX translation doing this (compared to the wiki's inline GPX link via BrowseRelation). These may still contain noise and yield less-than-ideal results. Stevea (talk) 23:28, 11 May 2018 (UTC)

The main Page's Approved section now links to ACA's GPX downloads via their "Ride With GPS" partnership. This is a workable solution for those who seek GPX files of USBRs, and these GPX files are unidirectional. Stevea (talk) 16:54, 1 August 2018 (UTC)

The very latest: Additionally, since in 2018 the BrowseRelation function in our wiki markup language was modified so it no longer displays the GPX link (allowing a "noisy" download of GPX data) but now simply displays the relation number, this is much less relevant. Prior to this, noise/bad results came from OSM's wiki's BrowseRelation GPX link for bidirectional routes (this broken functionality was reported as a defect). In short, USBRs in GPX format are best utilized from the curated set of these data published by ACA on their RideWithGPS site (the link on the Page). Stevea (talk) 19:38, 16 January 2019 (UTC)

History of the USBRS, route by route

The U.S. Bicycle Route System (USBRS) began to be established as a national numbered bicycle network in 1978. In 1982, the American Association of State Highway and Transportation Officials (AASHTO) formally inaugurated the USBRS, which originally consisted of two routes:

• USBR 1 in North Carolina and Virginia and
• USBR 76 in Virginia.

The System languished between the mid-1980s and 1990s. A "National Corridor Plan" was developed during the 2000s, allowing each of the fifty states of the USA to harmoniously develop USBRs using a cohesive national numbered grid of planned route corridors and a regularized numbering protocol (east-west routes are even-numbered, north-south routes are odd-numbered, spur/belt/alternate routes are preceded by a hundreds-place digit or suffixed with "A"). May 2011 saw the first major expansion of the nascent system. Five new parent routes, two child routes, and one alternate route were created, along with modifications to the existing routes in Virginia and the establishment of USBR 1 in New England. stevea @ 23:03, 14 September 2016 (UTC)

• U.S. Bicycle Route 1 now has an additional segment through Maine and New Hampshire,
• U.S. Bicycle Route 1A is a sea-side alternate route for USBR 1 in Maine,
• U.S. Bicycle Route 8 runs from Fairbanks, Alaska, along the Alaska Highway, to the Canadian border,
• U.S. Bicycle Route 20 runs from the Saint Clair River through Michigan to Lake Michigan,
• U.S. Bicycle Route 76 was extended westward through Kentucky and Illinois,
• U.S. Bicycle Route 87 follows the Klondike Highway from the Alaska Marine Highway terminal in Skagway to the Canadian border,
• U.S. Bicycle Route 95 follows the Richardson Highway from Delta Junction, Alaska to the Alaska Marine Highway terminal in Valdez,
• U.S. Bicycle Route 97 runs from Fairbanks, through Anchorage, to Seward, Alaska,
• U.S. Bicycle Route 108 runs from its parent route in Tok, Alaska to Anchorage and
• U.S. Bicycle Route 208 follows the Haines Highway from the Alaska Marine Highway terminal in Haines to the Canadian border.

In May 2012 Michigan added:

• U.S. Bicycle Route 35 from the Canadian border at Sault Ste. Marie southerly to the Indiana state line near New Buffalo.

The Mississippi River Trail (MRT) is signed similarly to the USBRS, though MRT is not strictly part of USBRS. However, in May 2013 Minnesota received AASHTO approval for its MRT segments to become:

• U.S. Bicycle Route 45 from the Iowa state line north of New Albin, Iowa north through Minneapolis to Brainerd, then northeasterly to Jacobson, then westerly to Bemidji and southerly to near Lake George, and
• U.S. Bicycle Route 45A from Brainerd northerly to Cass Lake.

Minnesota uses both MRT and 45 designations, keeping the MRT brand while blending in the newer USBR 45. MRT may continue (as it did in Minnesota) to become USBR 45 in other states, though there are currently no active proposals to do so.

In May 2013 Missouri added:

• U.S. Bicycle Route 76 from Claryville westward through St. Mary, Farmington, Pilot Knob, Centerville, Eminence, Houston, Marshfield, Ash Grove and Golden City to Kansas.

In October 2013 Tennessee and Maryland (respectively) added:

• U.S. Bicycle Route 23 from the Kentucky state line at Kentucky's Mammoth Cave state bicycle route, south via Robertson County, White House, Nashville and Franklin to Ardmore, Alabama and
• U.S. Bicycle Route 50 as the Maryland segments of the Chesapeake & Ohio Bicycle Trail and the Great Allegheny Passage Trail.

In May 2014 Massachusetts, Washington (state), Illinois (36 & 37), the District of Columbia and Ohio (respectively) added:

• U.S. Bicycle Route 1 from the Museum of Science in Boston westerly along the Paul Dudley White/Charles River Path to Auburndale Park in Newton, then from West Street in Everett northeasterly along the Northern Strand Community Trail/Bike to the Sea to Lincoln Avenue in Saugus,
• U.S. Bicycle Route 10 from the Idaho state line westerly, primarily along Washington State Route 20 to Anacortes, then via ferry to Friday Harbor and Sidney, British Columbia,
• U.S. Bicycle Route 36 south from Buckingham Fountain in Chicago to Eggers Wood to connect eastward to Indiana,
• U.S. Bicycle Route 37 north from Buckingham Fountain in Chicago to the Wisconsin state line at Robert McClory Trail,
• U.S. Bicycle Route 50 along the C&O Canal path to Maryland and
• U.S. Bicycle Route 50 from Indiana near New Westville easterly through Lewisburg, Brookville, Dayton, Xenia, Cedarville, London, Indian Ridge Area, Columbus, northerly to Westerville, then easterly through New Albany, Scott Corners, Newark and Steubenville into West Virginia.

In December 2014 Florida (1 & 90/90A), Massachusetts, Virginia (1 & 76), Michigan and Maryland (respectively) added, updated or realigned:

• U.S. Bicycle Route 1 from Key West to Jacksonville, ending at the Georgia state line,
• U.S. Bicycle Route 1 with two new segments: a northerly one through Salisbury and Newburyport and a southerly one through Topsfield, Wenham, Danvers and Peabody,
• U.S. Bicycle Route 1 provides a safer and more reliable cyclist route through Fort Belvoir, Mount Vernon and Old Town Alexandria, ending at the 14th Street Bridge in Washington DC,
• U.S. Bicycle Route 10 connects the eastern and central portions of Michigan’s Upper Peninsula: its eastern terminus with USBR 35 in Saint Ignace travels west to Iron Mountain near Wisconsin,
• U.S. Bicycle Route 11 from the Pennsylvania state line northwest of Hagerstown to Harpers Ferry, West Virginia,
• U.S. Bicycle Route 76 north of Lexington to near Vesuvius,
• U.S. Bicycle Route 90 from the Alabama state line to Florida’s Atlantic Coast in Butler Beach, just south of Saint Augustine and
• U.S. Bicycle Route 90A as an alternate to USBR 90 around Pensacola.

In May 2015 Idaho, Minnesota and Utah (respectively) added or realigned:

• U.S. Bicycle Route 10 from Oldtown at the Washington state line eastward through Sandpoint and Clark Fork to Montana,
• U.S. Bicycle Route 10A as various belts offering alternate routes through Idaho,
• U.S. Bicycle Routes 45 and 45A with some minor realignments,
• U.S. Bicycle Route 70 from Colorado on US 491 westerly through Monticello and Blanding, crossing the Colorado River and serving Hanksville, Torrey, Escalante, Henrieville, Cannonville, Tropic Junction, Bryce Canyon Junction and Panguitch to Cedar City and
• U.S. Bicycle Route 79 from Cedar City northerly to Minorsville and Milford then westerly and northwesterly to Garrison and Nevada near Baker and US 6.

In September 2015 Vermont, Georgia, Indiana, Ohio, Kansas and Arizona (respectively) added:

• U.S. Bicycle Route 7 from Canada to Massachusetts via Burlington southward,
• U.S. Bicycle Routes 21, 321 and 521 from Atlanta to Tennessee and as two spurs,
• U.S. Bicycle Routes 35, 35A, 36 and 50 from Kentucky via Clarksville to Michigan via Hesston, in Indiana's Hamilton, Marion, Shelby and Clark counties, Illinois via Highland to Michigan via Town of Pines and Illinois via Terre Haute to Ohio via Richmond,
• U.S. Bicycle Route 50A as an alternate route around Alexandria and Westerville,
• U.S. Bicycle Route 76 from Missouri via Pittsburgh to Colorado via Scott City and
• U.S. Bicycle Route 90 from New Mexico through Tucson and Phoenix to California.

In June 2016 Connecticut, Massachusetts, Idaho, Virginia and Georgia (respectively) added or realigned:

• U.S. Bicycle Route 7 from the junction of East Coast Greenway and Western New England Greenway (Westport) north through Danbury, New Milford, Bulls Bridge, Kent, Cornwall Bridge, West Cornwall, Falls Village and west of Canaan to Massachusetts,
• U.S. Bicycle Route 7 from the Connecticut border northward through Ashley Falls, Sheffield, Great Barrington, Stockbridge, Lenox, around Pittsfield to Cheshire, Adams, North Adams, and Williamstown to Vermont,
• U.S. Bicycle Route 10 with minor route realignments around Sandpoint and Ponderay/Kootenai,
• U.S. Bicycle Route 176 as a belt off of USBR 76 to USBR 1 and
• U.S. Bicycle Route 621 as a spur off of USBR 21.

In November 2016 Idaho, Michigan and Minnesota (respectively) added or realigned:

• U.S. Bicycle Route 10 with minor route realignments, also creating new routes 110, 210, 410 and superseding (deleting) USBR 10A,
• U.S. Bicycle Route 110, an alternate spur route off of USBR 10 at Clark Fork with no river crossing to the Montana boundary,
• U.S. Bicycle Route 210, an alternate belt route south of Lake Pend Oreille,
• U.S. Bicycle Route 410, another alternate belt route south of Lake Pend Oreille following Lakeshore Drive,
• U.S. Bicycle Route 35 is realigned in Ottawa County, Michigan to more bicycle-friendly infrastructure (avoiding Butternut Drive): Lakeshore Avenue, Lakewood Boulevard, Division Avenue and North Shore Drive/Howard Avenue and
• U.S. Bicycle Route 41 from USBR 45/Mississippi River Trail in St. Paul north to the Canadian border near Grand Portage, roughly paralleling Wisconsin and Lake Superior, also serving White Bear Lake, Hinckley, Duluth, Two Harbors, Silver Bay and Grand Marais.

In May 2017 Pennsylvania added:

• U.S. Bicycle Route 50 from the West Virginia boundary eastward along the Panhandle Trail through the southern suburbs of Pittsburg, then Westmoreland, Fayette and Somerset counties to the Maryland boundary largely along the Great Allegheny Passage.

In September 2017 Virginia, Michigan and Washington realigned or added:

• U.S. Bicycle Route 1 with a more direct route through the vicinity of Davison AAF along Richmond Highway (U.S. Route 1) in Northern Virginia,
• U.S. Bicycle Route 76 along the Virginia Capital Trail between Willis Church Road and Colonial Parkway,
• U.S. Bicycle Route 35 in Muskegon County, Michigan along the Fred Meijer Berry Junction Trail,
• U.S. Bicycle Route 87 in Washington from the Canadian border at Sumas joining USBR 95 in Whatcom County, joining USBR 97 in Bellingham, crossing USBR 10 at Washington SR 9 to the Skagit County Line,
• U.S. Bicycle Route 95 in Washington from the Canadian border at Blaine joining USBR 87 in Whatcom County, joining USBR 97 in Bellingham, joining USBR 10 in Burlington, continuing to Mount Vernon, joining USBR 87 at Washington SR 9 to the Skagit County Line and
• U.S. Bicycle Route 97 in Washington from the Canadian border at Blaine joining USBR 87 and USBR 95 in Bellingham, continuing south into Skagit County and joining USBR 10 at Washington SR 20, then through Anacortes to Island County and Coupeville at the Port Townsend Ferry Dock.

In May 2018 Washington, Georgia, Michigan, Pennsylvania, Nevada, Missouri and Kansas realigned, renumbered or added:

• U.S. Bicycle Route 10 in Washington to better harmonize with USBR 10 in Idaho,
• U.S. Bicycle Route 97 through Bellingham,
• U.S. Bicycle Route 310 in Newport,
• U.S. Bicycle Route 610 around Sedro-Woolley,
• U.S. Bicycle Route 15 in Georgia (Phase I), initially northbound from the Florida state line,
• U.S. Bicycle Route 221 in Georgia as a renumbering of 321,
• U.S. Bicycle Route 421 in Georgia as a renumbering of 521,
• U.S. Bicycle Route 30 in Pennsylvania between Ohio and New York, serving Erie,
• U.S. Bicycle Route 35 around Charlevoix, Michigan,
• U.S. Bicycle Route 36 across Pennsylvania,
• U.S. Bicycle Route 50 across Nevada and
• U.S. Bicycle Route 66 across Missouri and in the southeast corner of Kansas.
• U.S. Bicycle Route 76 realigned to include Great Bend.

In September 2018 Florida added:

• U.S. Bicycle Route 15 in Florida starting in Madison (as "Phase 1") north through Pinetta to the Georgia line, meeting USBR 15 in that state.

In June 2019 Massachusetts, Kentucky, Virginia and Georgia added or realigned:

• U.S. Bicycle Route 1 in Georgia, connecting Florida and Effingham County,
• U.S. Bicycle Route 7 in Massachusetts as a slight realignment to include the Ashuwillticook Trail in Adams via Lime and Hoosac Streets,
• U.S. Bicycle Route 21 in Kentucky, connecting Ohio and Tennessee,
• U.S. Bicycle Route 23 in Kentucky, connecting Tennessee,
• U.S. Bicycle Route 76 in Virginia as a slight realignment around Atlee Station Road.

In September 2019 West Virginia and Maine added:

• U.S. Bicycle Route 50 in West Virginia, connecting Pennsylvania's Panhandle Trail over US 22, through Weirton and Weirton Junction to the Market Street Bridge over the Ohio River into Steubenville.
• U.S. Bicycle Route 501 in Maine, from Bangor north to East Millinocket, Houlton, Presque Isle, Caribou, Van Buren, Madawaska, Fort Kent, Allagash Village and Dickey to Frank Mack Road at (but not including) Hafey Road Bridge over the Saint John River.

In July 2020 Wisconsin and California added and Kentucky and Michigan realigned:

• U.S. Bicycle Route 21 in Kentucky, with a realignment through the Cumberland Gap.
• U.S. Bicycle Route 30 in Wisconsin, traversing the state east to west: from Milwaukee to Madison and through to Middleton, Lodi, Merrimac, Baraboo, Reedsburg, Onalaska and Trempealeau to the Minnesota border near Winona.
• U.S. Bicycle Route 35 in Michigan, with a realignment through Suttons Bay onto North Saint Mary's Street / Saint Mary's Avenue North.
• U.S. Bicycle Route 50 in California, connecting Stateline at the Nevada border on South Lake Tahoe through the Sierra Nevada to Sacramento and on to Vallejo and a ferry to San Francisco, then a land segment in The City to the southern edge of the Golden Gate Bridge.
• U.S. Bicycle Route 230 in Wisconsin, as a spur through Sauk City to Rock Springs.

In December 2020 the District of Columbia, West Virginia, North Dakota and Maryland added and Florida realigned:

• U.S. Bicycle Route 1 in Washington, DC, following the lower Potomac River on the Rock Creek Trail and Capital Crescent Trail from Arlington Memorial Bridge northwest to the Maryland line.
• U.S. Bicycle Route 11 in West Virginia, from Harpers Ferry south through Jefferson County and along the Shenandoah River to Virginia's Clarke County.
• U.S. Bicycle Route 30 in North Dakota, consisting of the entirety of route US 12 through the state.
• U.S. Bicycle Route 201 in Maryland from Elkton at the Delaware line westward to Havre de Grace, Bel Air, Jarrettsville and Monkton at the Torrey C. Brown Trail.
• U.S. Bicycle Route 1 in Florida, though no details are known.

In July 2021, Florida and California realigned and Washington, Ohio, California, Utah and Indiana added :

• U.S. Bicycle Route 1 in Florida around Key West.
• U.S. Bicycle Route 20 in Washington.
• U.S. Bicycle Routes 21, 25, 30, 44, 225 and 230 in Ohio.
• U.S. Bicycle Routes 40, 81 and 281 in Washington.
• U.S. Bicycle Routes 50, 66 and 95 in California.
• U.S. Bicycle Routes 77, 79, 677, 679 and 877 in Utah.
• U.S. Bicycle Route 235 in Indiana.

In November 2021, Maryland added and Michigan, Ohio and Florida realigned:

• U.S. Bicycle Route 1 in Maryland.
• U.S. Bicycle Route 20 in Michigan.
• U.S. Bicycle Route 21 in Ohio.
• U.S. Bicycle Routes 90 in Florida.

In June 2022, Minnesota, Oklahoma and Delaware added and Michigan and Indiana realigned:

• U.S. Bicycle Route 20 in Minnesota, as new route.
• U.S. Bicycle Route 20 in Michigan, as minor realignment.
• U.S. Bicycle Route 35 in Indiana, as minor realignments.
• U.S. Bicycle Route 66 in Oklahoma, as new route.
• U.S. Bicycle Routes 201 in Delaware, as new route.

In December 2022, Ohio, Tennessee and Arkansas added, Ohio, Minnesota and New York realigned and Ohio deleted:

• U.S. Bicycle Route 11 in New York, as minor realignments.
• U.S. Bicycle Route 21 in Ohio and Tennessee, as new routes, completing USBR 21 (Cleveland to Atlanta).
• U.S. Bicycle Route 25 in Ohio, as minor realignments.
• U.S. Bicycle Route 30 in Ohio, as minor realignments.
• U.S. Bicycle Route 41 in Minnesota, as minor realignments.
• U.S. Bicycle Route 44 in Ohio, as new route.
• U.S. Bicycle Route 50 in Ohio, as minor realignments.
• U.S. Bicycle Route 80 in Arkansas, as new route.
• U.S. Bicycle Route 225 in Ohio, as a deletion from the System, being absorbed into its parent route.In December 2022, Ohio, Tennessee and Arkansas added, Ohio, Minnesota and New York realigned and Ohio deleted:

In June 2023, Pennsylvania, Idaho and Tennessee added, Minnesota and Kentucky realigned and Alaska renumbered:

• U.S. Bicycle Route 11 in Pennsylvania, as new route extension.
• U.S. Bicycle Route 20 in Minnesota, as extension and minor realignments.
• U.S. Bicycle Route 21 in Kentucky, as realignments.
• U.S. Bicycle Route 121 in Tennessee, as new route.
• U.S. Bicycle Route 45 in Minnesota, as realignments.
• U.S. Bicycle Route 45A in Minnesota, as realignments.
• U.S. Bicycle Route 610 in Idaho, as new route.
• U.S. Bicycle Route 8, 108, 208 in Alaska, as renumberings (to deprecated, 397 and 789, respectively).
• U.S. Bicycle Routes 87, 95, 97 in Alaska, as new route extensions.

Alaska PF&DOT plan to improve USBR 95 between Homer - Seward - Anchorage with projects under construction and WSDOT plan to improve USBRS routing with the introduction of spur routes 187, 195 and 197 to Canada. Lengthy ferry routes are having a minor ripple effect while some use cases (human and machine processes, routers, renderers...) learn that cyclists use ferries, sometimes camping on their decks for days. A number of cycling renderers have parsed these data and display ferry segments where applicable, properly denoted. To clarify, after a System-wide assesement this Round:

• U.S. Bicycle Route 35A in Indiana appears not to have been a USBR brought before AASHTO; its route relation was deleted from OSM; clearing up some misty history.

Declaring version 2.3. Stevea (talk) 23:34, 17 June 2023 (UTC)

In November 2023, Alaska added new routes and Florida, Maine, Ohio and Virginia realigned:

• U.S. Bicycle Routes 187, 387, 587 and 787 in Alaska, as new routes.
• U.S. Bicycle Route 1 in Maine and Florida as moderate and minor realignments.
• U.S. Bicycle Route 25 (Cincinnati, elsewhere) and 30 (Eastlake, Genoa) in Ohio, as moderate and minor realignments.
• U.S. Bicycle Route 76 in Virginia around Palmyra as minor realignments.

The "Round Link" to the state DOT Autumn 2023 AASHTO ballot items is or was here. Our community Discource forum topic is here.

Declaring version 2.3.5. Stevea (talk) 21:44, 10 December 2023 (UTC)

Wikipedia and Wikidata maintain comprehensive catalogs of AASHTO minutes along with links to ballots from some meetings.