Amtrak® operates a nationwide rail network of intercity passenger trains in the contiguous United States, serving more than 500 destinations in 46 states, the District of Columbia and three Canadian provinces on more than 21,400 miles of routes: most of the USA's passenger=regional (medium-distance: intrastate or interstate) trains and all passenger=national (long distance, interstate), overnight, highspeed=* and passenger=international trains. Many states (California, Virginia, Maryland, Missouri, Illinois, Utah, New Mexico, Connecticut, Massachusetts, Pennsylvania, Florida...) and regional transportation authorities (e.g. Northern Indiana Commuter Transportation District) sponsor their own state/regional commuter and intrastate route=trains, some are included in Amtrak (California), some are not (Maryland). Try an OpenPublicTransportMap rendering, which displays route=train relations as train-numbered black lines, including the union of Amtrak routes with state- and regional-sponsored routes. While Acela is the only high-speed route which may reach 150 MPH (241 km/h), nearly half of Amtrak trains operate at top speeds of 100 MPH (161 km/h) or greater. In the Passenger column, bold type indicates "higher-speed" service, which may include Class 5 (90 MPH) or Class 6 (110 MPH) track.
In North America, "bottom level" (infrastructure) route=tracks relations are omitted, instead skipping to "middle level" (infrastructure) route=railway relations. "Higher level" passenger rail routes like the Amtrak route relations linked here are properly a collection of rail segments, stations/stops and platforms. More complete tagging on underlying infrastructure (track) segments (making up a "named Subdivision") includes accurate, contiguous railway=* elements, with identical name=* and usage=* tags. These are collected into middle level route=railway relations, not bottom level route=tracks relations as OpenRailwayMap suggests. You can improve one or more of the higher level route=train relations below without the following suggestion, but please endeavor to create/review/correct/complete underlying middle level route=railway relations (infrastructure which should contain contiguous, identically named track segments) as you do so.
For example, the Hiawatha Service route=train relation contains all track segments that make up that route, so it is correct to mark here as Complete. But examining this relation's members shows that while some tracks are correctly named "C&M Subdivision," others are missing such name=* (and usage=*) tags. Furthermore, track segments which make up the C&M Subdivision are not (yet) collected into a middle level route=railway + name=C&M Subdivision relation. Please endeavor to identify contiguous rail segments with identical name=* and usage=* tags and collect them into a middle level route=railway "named Subdivision" relation. The higher level route=train relations listed below are important to complete, but so are their underlying middle level infrastructure route=railway relations, too!
Try OpenPublicTransportMap (OPTM): it displays passenger rail in route=train relations. At closer zooms, OPTM also displays route=light_rail, route=subway, route=tram, route=monorail, route=funicular, route=bus, route=trolleybus, route=aerialway and route=ferry with colors similar to OpenRailwayMap (ORM). Please compare and contrast ORM (rail infrastructure) and OPTM (passenger routes) with OSM's Transport layer which rather simply displays "any and all rail" (railway=*), though not disused or abandoned rail, and at closer zooms, route=bus. (Another rail renderer displayed rail-based passenger routes with their colour=* or color=* tag, but is no longer functional).
Amtrak route=train routes are roughly Complete, at least to public_transport:version=1 (v1 in the type=route column) as green Route names, yellow indicates minor problems with underlying infrastructure, not the v1 route=train relation. Underway now are improvements to public_transport:version=2 (a route_master super-relation, each tracked train in its own route relation, bi-directional route logic and precise locations of a completed set of public_transport=platforms). Such growth from v1 to v2 is what is meant by Map Your Train Ride! If they are not in OSM, add public_transport=platforms to the route=train relation of your commute. It's easy: add a node, way or draw a small polygon representing the exact location of the platform, tag it public_transport=platform, railway=platform and train=yes. Many platforms already exist! If so, include them in the proper route=train relation(s), found around that railway=station. See this diagram of a "simple railway station." Thanks to all who improve OSM!
Even-numbered Amtrak trains travel north and east, odd-numbered south and west. Among the exceptions are Pacific Surfliner trains, which use the opposite numbering system inherited from Santa Fe Railway, and some Downeaster and Empire Service trains. All routes are network=Amtrak.
|Route name||Trains (ref=*)||passenger=*||type=route_master||type=route||Status and Notes|
|Acela Express®||2100-2222||high speed||WAS-BOS
|Roughly complete; public_transport v2. 457 miles (735 km). Amtrak's premier high-speed service between Boston and Washington, with speeds up to 150 MPH (241 km/h) in parts of Rhode Island and Massachusetts. Underlying infrastructure Northeast Corridor needs track connectivity fixes. Partly due to COVID-19, as of early March, 2020, Acela Express service is suspended "until May" (2020).|
|Adirondack®||68, 69||international||v1||Roughly complete; public_transport v1. 381 miles (613 km), a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service. No overnight service.|
|Auto Train®||52, 53||car||v1||Nearly complete; public_transport v1. 855 miles (1,376 km). Tagged both passenger=national and service=car.|
|Blue Water℠||364, 365||regional||v1||Roughly complete; public_transport v1. 319 miles (513 km). Underlying infrastructure (route=railway) relations need fixing (there is a "track split" on Flint Subdivision east of Battle Creek). Part of "Michigan Services."|
|California Zephyr℠||5, 6||national||EMY-CHI
CHI-EMY Mostly complete; public_transport v2. 2438 miles (Chicago - Emeryville, California). Underlying infrastructure route=railway relations are mostly but not quite completely correct (e.g. Creston Subdivision "track splits"), relation is very large. Platforms, amenities around them need improvement.
|Capitol Corridor℠||522, 523, 527, 537, 538, 546, 549, 720, 727, 732, 737, 744, 748, 749||regional||ARN-OKJ
WB Complete; public_transport v2. 168 miles (275 km) (San Jose - Oakland - Sacramento - Auburn). A Phase 1 extension from San José (Diridon) south to Gilroy (+49 km) and Salinas (+60 km) is expected in the 2020s for a new length of 238 miles (384 km). Infill stations at Pajaro/Watsonville Junction (to serve Santa Cruz) and Castroville (to serve Monterey) are Phase 2, with no revenue service date specified, as Monterey Branch is disused / abandoned and Santa Cruz Branch is Class 1 (or 2?) speed, limiting freight and occasional tourism trains to 25 MPH/40 km/h as it rehabilitates. The Capitol Corridor is the third busiest Amtrak route in the USA, moving 1.4 million passengers annually between San Jose and Auburn. Platform assignments need surveying at Martinez and Sacramento: Map Your Train Ride! Part of "Amtrak California:" partially funded by Caltrans' Division of Rail, this branding is less prominent with "more local" CCJPA joint powers authority.
|Capitol Limited℠||29, 30||national||v1||Roughly complete; public_transport v1. 780 miles (1260 km). Underlying infrastructure (route=railway) relations need fixing (there are numerous "track splits").|
|Cardinal®||50, 51||national||v1||Complete; public_transport v1. 1146 miles (1844 km).|
|Carl Sandburg®-Illinois Zephyr®||380-383||regional||v1||Complete; public_transport v1. 258 miles (415 km). Part of "Illinois Service."|
|Carolinian℠||79, 80||national||v1||Nearly complete; public_transport v1. (Needs minor "track split" fixes). 704 miles (1133 km). No overnight service.|
|Complete; rough public_transport v2. 467 miles (752 km), though no single train covers this entire distance; there is no single route=train going all the way from Eugene to Vancouver. Only trains serving Canada are tagged as international; the rest are regional. No overnight service. Underlying infrastructure (route=railway) relations need fixing.|
|City of New Orleans®||58, 59||national||CHI-NOL
NOL-CHI Complete; public_transport v2. 934 miles (1503 km).
|Coast Starlight®||11, 14||national||v1||Mostly complete; public_transport v1. 1377 miles (2216 km). Los Angeles - San José - Oakland - Sacramento - Portland - Seattle.|
|Crescent®||19, 20||national||v1||Somewhat complete; rough public_transport v1. 1377 miles (2216 km). Underlying infrastructure (route=railway) relations need fixing.|
|Downeaster℠||680-699||regional||v1||Somewhat complete; rough public_transport v1. Underlying infrastructure (route=railway) relations need fixing, for example, double-tracking on line ends suddenly at Massachusetts-New Hampshire boundary. 145 miles (233 km).|
|Empire Builder®||7, 8, 27, 28||national||v1 CHI-SPK
|Somewhat complete; rough public_transport v1. 2206 miles (3550 km) (Chicago - Seattle). At Spokane, trains 7 and 27 decouple westbound and trains 8 and 28 couple eastbound.|
|Empire Service®||230-260, 233-259, 280, 281, 283, 288||regional||NYP-YNY-POU-ALB
ALB-NYP 142 miles (229 km) New York City - Albany
NFL-NYP Complete; public_transport v2. 460 miles (740 km) New York City - Buffalo, a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service.
|Ethan Allen Express®||290-293, 295, 296||regional||RUD-NYP
NB Complete; public_transport v2. 241 miles (388 km).
|Hartford Line||401, 405, 407, 432, 450, 460, 463-465, 467, 470, 475, 476, 479, 490, 493, 497||regional||v1||Complete; public_transport v1. About 62 miles (100 km) serving New Haven and Hartford, Connecticut to Springfield, Massachusetts.|
|Heartland Flyer®||821, 822||regional||OKC-FTW
FTW-OKC Complete; public_transport v2. 206 miles (332 km).
CHI-MKE Complete; public_transport v2. 86 miles (138 km).
CDL-CHI Complete; public_transport v2. 310 miles (499 km). Part of "Illinois Service."
|Keystone Service®||600-672||regional||v1||Mostly complete; public_transport v1. 195 miles (314 km), a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service.|
|Lake Shore Limited®||48, 49, 448, 449||national||v1 CHI-ALB
|Complete; rough public_transport v1. 959 miles (1543 km). At Albany-Rensselaer, trains 48 and 448 decouple eastbound and trains 49 and 449 couple westbound. Underlying infrastructure (route=railway) relations need fixing.|
|Lincoln® Service||300-307||regional||v1||Complete; rough public_transport v1. 284 miles (457 km), a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service. Tracks near St. Louis estimated. Part of "Illinois Service."|
|Maple Leaf℠||63, 64||international||TWO-NYP
NYP-TWO Complete; public_transport v2. 544 miles (875 km). No overnight service. Needs to be separated at Niagara Falls, Ontario into Amtrak- and VIA-operated segments.
|Missouri River Runner℠||311-316||regional||v1||Complete; rough public_transport v1. 283 miles (455 km). Underlying infrastructure (route=railway) relations need fixing. Part of "Illinois Service."|
|Northeast Regional℠ (Norfolk/Newport News)||65-67, 82, 83, 85-87, 88, 93-96, 99, 110, 111, 121, 123, 125-127, 129-141, 143, 146, 148-170, 172-175, 179-190, 192-196, 198, 199||regional||v1||Somewhat complete; rough public_transport v1. Amtrak's busiest routes. 457 miles (735 km), a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service. Underlying infrastructure (route=railway) relations need fixing.|
|Northeast Regional℠ (Roanoke)||65, 67, 82, 83, 85-87, 93, 95, 96, 99, 110, 111, 121, 123, 125-127, 129-141, 143, 145-156, 158-178, 180-190, 192-196, 198, 199||regional||v1||Somewhat complete; rough public_transport v1. Amtrak's busiest routes. 457 miles (735 km), a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service. Underlying infrastructure (route=railway) relations need fixing.|
|Pacific Surfliner®||562, 564-567, 572-575, 579, 580, 583, 584, 590, 591, 595, 761, 763, 768, 769, 774, 777, 782, 785, 792, 796, 1566-1568, 1588, 1761||regional||v1||Largely complete; rough public_transport v1. 350 miles (565 km); (San Diego - Los Angeles - Santa Barbara - San Luis Obispo). Underlying infrastructure (route=railway) relations need fixing. While there are some 90 MPH segments (MCBC Pendleton), the underlying LOSSAN corridor is not "higher-speed" (black text regional). Pacific Surfliner is the second busiest Amtrak route in the country, moving 2.6 million passengers annually between San Diego and San Luis Obispo. Part of "Amtrak California:" partially funded by Caltrans' Division of Rail, this branding is less prominent with the "more local" LOSSAN joint powers authority. Needs better public_transport=platform members: Map Your Train Ride!|
|Palmetto®||89, 90||national||v1||Complete; public_transport v1. 829 miles (1344 km). No overnight service.|
|Pennsylvanian℠||42, 43||regional||v1||Complete; rough public_transport v1. 444 miles (715 km). Underlying infrastructure (route=railway) relations need fixing.|
|Pere Marquette®||370, 371||regional||v1||Complete; rough public_transport v1. 176 miles (283 km). Underlying infrastructure (route=railway) relations need review. Part of "Michigan Services."|
|Piedmont®||73-76||regional||v1||Complete; public_transport v1. 173 miles (278 km).|
|San Joaquins℠||701-704, 710-719||regional||BFD-OKJ
|Complete; public_transport v2. 315 miles (507 km); (Bakersfield - Stockton - Oakland), 282 miles (454 km); (Bakersfield - Stockton - Sacramento). The San Joaquins is the fifth busiest Amtrak route in the country, moving 1.1 million passengers annually. With connecting buses at Bakersfield, the San Joaquin service is the spine of Amtrak California: linking Los Angeles and the Bay Area. Platform assignments need surveying at Bakersfield, Martinez and Sacramento: Map Your Train Ride!'|
|Silver Meteor®||97, 98||national||v1||Complete; public_transport v1. 1522 miles (2449 km). Part of "Silver Service®."|
|Silver Star®||91, 92||national||v1||Complete; public_transport v1. 1377 miles (2216 km). Part of "Silver Service®."|
|Southwest Chief®||3, 4||national||LAX-CHI
LAX-CHI Complete; public_transport v2. 2265 miles (Chicago - Los Angeles).
|Sunset Limited®||1, 2||national||v1 LAX-SAS
|Complete; public_transport v1. 1995 miles (New Orleans - San Antonio - Los Angeles). At San Antonio, train 1 couples with train 421 westbound and train 2 decouples from train 422 eastbound.|
|Texas Eagle®||21, 22, 421, 422||national||v1 CHI-SAS||Complete; rough public_transport v1. 2728 miles (Chicago - San Antonio - Los Angeles). At San Antonio, train 421 couples with train 1 westbound and train 422 decouples from train 2 eastbound. Trains 21 and 22 cover the segment between Chicago and San Antonio on days without Sunset Limited service. Tracks around Saint Louis are estimated.|
|Valley Flyer||400, 478, 488, 494, 461, 471, 495, 499||regional||v1||Complete; public_transport v1.|
|Vermonter℠||54-57||regional||v1||Essentially complete; public_transport v1. 611 miles (983 km). Needs rerouting through Connecticut River Line (see )|
|Wolverine®||350-355||regional||v1||Largely complete; public_transport v1. 304 miles (489 km), a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service. Underlying infrastructure (route=railway) relations need fixing. Part of "Michigan Services."|
About the (status) colors in the Route name column
Green means that the route has achieved a rudimentary level of public_transport:version=1. This implies that other relation attributes are correct, but this isn't always strictly true; see Status and Notes column. Green does not conflict with active v1 -> v2 growth. Go!
Yellow means "only partially complete" ; additional volunteer work is needed to enter or correct additional data (railway and/or train route) into OSM. Yellow may also mean a route has a volunteer entering data, yet route ambiguities persist about what is actually correct.
No Amtrak® routes are Red ("Something, often very little is known about the route, so it is useful to put a row in the table about it as a placeholder, but it is likely too early to create a route relation: route data are unknown, incomplete or route attributes are significantly missing").
Acela Express service is "temporarily supspended until May (2020)." Note its route table entry is not set to red/no but remains yellow/partial to denote the completeness of the route itself.
About the (branding, livery) colors in the passenger=* column
Mapzen made a rail renderer, transit-colours, that displayed passenger route=trains with their colour=* (or color=*) tag value (and at closer zooms, route=subway, route=light_rail, route=tram). Although Amtrak does not assign colors to routes, routes above display colors in a rough schema: passenger=international = a purple or green, passenger=national (interstate, long distance) = blue, highspeed=yes = red, passenger=regional = a brown or orange and service=car = yellow. Try clicking the passenger=* column's sort arrow to see:
- International routes include Cascades green (as below) and purples: Adirondack as DarkViolet (dark, as it is on a "higher-speed" corridor; see below), Maple Leaf as MediumOrchid.
- National routes are blue, most are overnight routes (all Amtrak night routes are passenger=national). Overnight routes are darker shades of blue, such as DarkBlue on California Zephyr and MidnightBlue on Coast Starlight. The longest national routes are darkest blue.
- National routes without overnight service are lighter shades of blue: SkyBlue on Carolinian and DeepSkyBlue on Palmetto. Because of this and their "medium distance" length, an argument can be made that these two routes are more regional, rather than national. No current regional routes have overnight service.
- Regional routes are assigned web safe colors in brown and orange palettes (smearing a bit into beige/yellowish/mustard/khaki). Exceptionally, one major regional route is a medium shade of blue: Pacific Surfliner as OceanBlue.
- Regional routes lighter in color (neither dark nor deeply saturated) are regular-speed routes so that regional routes on "higher-speed" corridors are colored darker (DarkOrange, SaddleBrown...). Bold white text indicates higher-speed corridors, regular black text on (lighter colored) regional routes indicates regular-speed.
- Lighter-shade browns are all "regular speed, shorter-length regional routes" (desaturation=shorter).
This scheme has minor flaws, for example, Vermonter is a darker brown (Sienna), yet it is not higher-speed, however it is lengthier, so darker-shade regional now has a double-meaning of higher-speed or lengthier. Have fun.
Assigning web safe brown or orange colors to each Amtrak regional route underscores the difficulty of this task and may explain why Amtrak does not assign colors, but OSM can make good choices here. For example: on Amtrak Cascades service in Washington state, OSM's Amtrak wiki and Mapzen both display(ed) a closely matching shade of green, which in turn (by intention) better matches livery of rolling stock found only on those tracks by that line and class of service; also, Amtrak and California/Railroads show that passenger=regional Capitol Corridor route = poppy orange, color of California state flower. However, overloading/exceptions do happen with brown/orange on passenger=regional routes: Pacific Surfliner is a non-brown/orange regional route tagged with a medium shade of blue. A goal is better visual color consistency (given the above schema, which attempts to bend without breaking) across all passenger=* services. Color harmony, in motion.
About the colors and symbols in the Status and Notes column
Color and symbol legend: status of each route is indicated by a symbol, which describes the type of feature, and a color, which indicates the completeness of that feature in OSM. For more details, see Wiki Help. Meaning of symbols:
The codes 0-4 are a logical progression, but they do not all have to be used in sequence. It is perfectly acceptable to go from 0 (nothing on map) to 3 (everything done in opinion of one editor). However, there should never be a jump to level 4. r=4 should only appear after r=3, and the same with h=3 & h=4, as this implies the relation has been checked by both the editor who completed it (level 3), and a second editor (level 4). Given these are different people, a jump up to level 4 from anything other than 3 is not possible.
In this wiki, this symbology is used as relations indicate where public_transport:version=1 is becoming version 2. The route_master column will eventually be fully populated with v2 relations as v1 routes upgrade to v2, the type=route_master column data acting as "entry point" into these Amtrak routes, the type=route column linking to "directional" child relations.