Amtrak

From OpenStreetMap Wiki
Jump to navigation Jump to search

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. Most of these routes are on Class 4 track (maximum speed 80 MPH). While Acela, on Class 5, 6, 7 or 8 track (90, 110, 125, 160 MPH, respectively) 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 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 complete to public_transport:version=2 as of 2021-01-16. A convention of right-hand main is assumed, and actual track and platform assignments may differ from what is mapped. Map Your Train Ride! Do you ride a train regularly or work at a train station? If you're sure that a train consistently serves a platform different from what is mapped, feel free to reroute the route=train relation and add the matching public_transport=stop_positions and public_transport=platforms. Alternatively, leave a note on the map or on this page, and someone will help you out.

Even-numbered Amtrak trains generally 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, except in cases where service is provided jointly by Amtrak and another operator, such as the Maple Leaf train (operated by Canada's VIA Rail west of Niagara Falls), and the Hartford Line (along which Amtrak and ConnDOT coordinate service).

type=route_master passenger=* Origin-Destination, ref=* as Train #, type=route Status and Notes
Acela Express®
relation 9796393
high speed WAS→BOS:
2158;2248;2250;2252;2254;2256 relation 9796293
2154 relation 11961674
2164 relation 11961673
2170 relation 11961672
WAS→NYP:
2218;2224 relation 11961666
2126 relation 11961667
NYP→BOS:
2168 relation 11961675
BOS→WAS:
2155;2163;2249;2251;2253;2255;2257;2259 relation 9796352
2165 relation 11961671
2167 relation 11961670
NYP→WAS:
2203;2205 relation 11961668
2109 relation 11961669
BOS→NYP:
2173 relation 11961676
Routing (3/4)Stops (3/4) 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.
Adirondack®
relation 10322765
international MTR→NYP:
68 relation 11922066
NYP→MTR:
69 relation 4073816
Routing (3/4)Stops (3/4) Complete; public_transport v2. 381 miles (613 km), a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service. No overnight service.
Auto Train®
relation 10322764
car SFA→LOR:
52 relation 12009935
LOR→SFA:
53 relation 3517701
Routing (3/4)Stops (3/4) Complete; public_transport v2. 855 miles (1,376 km). Tagged both passenger=national and service=car.
Blue Water℠
relation 10322763
regional CHI→PTH:
364 relation 1687374
PTH→CHI:
365 relation 11879713
Routing (3/4)Stops (3/4) 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℠
relation 905830
national EMY→CHI:
6 relation 8440301
CHI→EMY:
5 relation 8440320
EMY-CHI Routing (3/4)Stops (3/4)
CHI-EMY Routing (3/4)Stops (3/4) 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℠
relation 2845553
regional SJC→SAC:
524;528;532;538;542;546;548;724;728;732;738;744;748 relation 9601565
OAC→SAC:
550 relation 9601559
OKJ→SAC:
520;522;530;534;540;544;720;734;736;746 relation 9601564
SJC→ARN:
742 relation 8472909
OKJ→ARN:
536 relation 9601563
SAC→SJC:
521;523;525;527;537;543;547;723;727;737;741;743;747 relation 9601566
SAC→OAC:
531;535;549;733 relation 9601560
SAC→OKJ:
541;545;551;553;745;749;751 relation 9601562
ARN→SJC:
729 relation 8472908
ARN→OKJ:
529 relation 9601561
EB Routing (3/4)Stops (3/4)
WB Routing (3/4)Stops (3/4) 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℠
relation 10563425
national CHI→WAS:
30 relation 12022605
WAS→CHI:
29 relation 2794554
Routing (3/4)Stops (3/4) Complete; public_transport v2. 780 miles (1260 km). Underlying infrastructure (route=railway) relations need fixing.
Cardinal®
relation 10322762
national CHI→NYP:
50 relation 2807121
NYP→CHI:
51 relation 12037189
Routing (3/4)Stops (3/4) Complete; public_transport v2. 1146 miles (1844 km).
Carl Sandburg®-Illinois Zephyr®
relation 10322761
regional QCY→CHI:
380;382 relation 11891956
CHI→QCY:
381;383 relation 4744150
Routing (3/4)Stops (3/4) Complete; public_transport v2. 258 miles (415 km). Part of "Illinois Service."
Carolinian℠
relation 10322760
national CLT→NYP:
80 relation 11996020
NYP→CLT:
79 relation 1900976
Routing (3/4)Stops (3/4) Complete; public_transport v2. (Needs minor "track split" fixes). 704 miles (1133 km). No overnight service.
Cascades ®
relation 10322759
international
regional
PDX→VAC:
518 relation 10571796
SEA→VAC:
516 relation 10945392
EUG→SEA:
500;508 relation 10945393
506 relation 11845490
PDX→SEA:
502 relation 11845489
504 relation 10945389
VAC→PDX:
517 relation 71428
VAC→SEA:
519 relation 10945391
SEA→EUG:
505 relation 10945394
SEA→PDX:
501 relation 10945390
507 relation 11845488
PDX→EUG:
511;513 relation 10945388
Routing (3/4)Stops (3/4) 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®
relation 1532755
national NOL→CHI:
58 relation 8436201
CHI→NOL:
59 relation 8436202
CHI-NOL Routing (3/4)Stops (3/4)
NOL-CHI Routing (3/4)Stops (3/4) Complete; public_transport v2. 934 miles (1503 km).
Coast Starlight®
relation 10322757
national LAX→SEA:
14 relation 12074397
SEA→LAX:
11 relation 2812900
Routing (3/4)Stops (3/4) Complete; public_transport v2. 1377 miles (2216 km). Los Angeles - San José - Oakland - Sacramento - Portland - Seattle.
Crescent®
relation 10322758
national NOL→NYP:
20 relation 1809808
NYP→NOL:
19 relation 12041225
Routing (3/4)Stops (3/4) Complete; public_transport v2. 1377 miles (2216 km). Underlying infrastructure (route=railway) relations need fixing.
Downeaster℠
relation 10322756
regional BRK→BON:
680;682;684;688 relation 11889370
690;692;694;698 relation 11889368
BON→BRK:
681;683;685;689 relation 4743492
691;693;695;699 relation 11889369
Routing (3/4)Stops (3/4) Complete; public_transport v2. 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®
relation 10322755
national SEA→CHI:
8 relation 10946021
PDX→CHI:
28 relation 10946020
CHI→SEA:
7 relation 1809794
CHI→PDX:
27 relation 12089100
Routing (3/4)Stops (3/4) Complete; public_transport v2. 2206 miles (3550 km) (Chicago - Seattle). At Spokane, trains 7 and 27 decouple westbound and trains 8 and 28 couple eastbound.
Empire Service®
relation 4452798
regional ALB→NYP:
236;238;242;250;252;256;260 relation 4452779
244;254 relation 10322903
230;232 relation 10322902
234 relation 10322901
NFL→NYP:
280;288 relation 10322904
284 relation 9155838
NYP→ALB:
233;235;241;243;253;255;259 relation 4234377
239;245;261 relation 10322899
237 relation 10322898
NYP→NFL:
281 relation 10322900
283 relation 9155839
NYP-ALB Routing (3/4)Stops (3/4)
ALB-NYP Routing (3/4)Stops (3/4) 142 miles (229 km) New York City - Albany
NYP-NFL Routing (3/4)Stops (3/4)
NFL-NYP Routing (3/4)Stops (3/4) 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®
relation 4445810
regional RUD→NYP:
290;292;296 relation 4445771
NYP→RUD:
291;295 relation 4234911
293 relation 10322921
SB Routing (3/4)Stops (3/4)
NB Routing (3/4)Stops (3/4) Complete; public_transport v2. 241 miles (388 km).
Hartford Line
relation 10530881
regional NHV→SPG:
450;460;464;470;474;476;4404;4406;4466;6400;6402;6410;6454 relation 9704911
NHV→HFD:
4452;4458;4462;6456;6458 relation 11921113
SPG→NHV:
409;417;463;465;467;473;475;4405;4407;4467;6401;6403;6411;6455 relation 11921114
HFD→NHV:
4453;4461;4463;6457;6459 relation 11921112
Routing (3/4)Stops (3/4) Complete; public_transport v2. About 62 miles (100 km) serving New Haven and Hartford, Connecticut to Springfield, Massachusetts. ConnDOT's CTrail-branded trains are included here, as Amtrak and ConnDOT coordinate service, run trains with identical stopping patterns and honor each other's tickets. Three-digit refs represent Amtrak trains, and four-digit refs represent CTrail trains.
Heartland Flyer®
relation 4743154
regional FTW→OKC:
822 relation 9161444
OKC→FTW:
821 relation 9161443
OKC-FTW Routing (3/4)Stops (3/4)
FTW-OKC Routing (3/4)Stops (3/4) Complete; public_transport v2. 206 miles (332 km).
Hiawatha Service®
relation 9161615
regional MKE→CHI:
330;332;334;336;338;340;342 relation 9161614
CHI→MKE:
329;331;333;335;337;339;341;343 relation 1638760
MKE-CHI Routing (3/4)Stops (3/4)
CHI-MKE Routing (3/4)Stops (3/4) Complete; public_transport v2. 86 miles (138 km).
Illini®-Saluki®
relation 1902680
regional CDL→CHI:
390;392 relation 8438427
CHI→CDL:
391;393 relation 8438428
CHI-CDL Routing (3/4)Stops (3/4)
CDL-CHI Routing (3/4)Stops (3/4) Complete; public_transport v2. 310 miles (499 km). Part of "Illinois Service."
Keystone Service®
relation 10322752
regional HAR→PHL:
610;612;654;656;662;666;670;674 relation 11914036
600;642;646;664 relation 11914032
618;658 relation 11914033
620;622 relation 11914031
644;648 relation 11914029
650 relation 11914034
HAR→NYP:
640 relation 4748609
652 relation 11914037
660 relation 11914038
672 relation 11914039
PHL→HAR:
601;605;611;619;649;651;655;661;665;667;671 relation 11914028
609;615;643;645 relation 11914026
607 relation 11914027
647 relation 11914025
NYP→HAR:
641 relation 11914040
653 relation 11914041
663 relation 11960995
669 relation 11960996
Routing (3/4)Stops (3/4) Complete; public_transport v2. 195 miles (314 km), a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service.
Lake Shore Limited®
relation 10322753
national CHI→NYP:
48 relation 1358974
CHI→BOS:
448 relation 12015551
NYP→CHI:
49 relation 10946018
BOS→CHI:
449 relation 10946019
Routing (3/4)Stops (3/4) Complete; public_transport v2. 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
relation 10322754
regional STL→CHI:
300;302;304;306 relation 4744138
CHI→STL:
301 relation 12192445
303;305;307 relation 11893734
Routing (3/4)Stops (3/4) Complete; public_transport v2. 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℠
relation 4467191
international TWO→NFS:
97 (VIA Rail) relation 11980837
NFS→NYP:
64 relation 4467190
NYP→NFS:
63 relation 4467189
NFS→TWO:
98 (VIA Rail) relation 11980838
TWO-NYP Routing (3/4)Stops (3/4)
NYP-TWO Routing (3/4)Stops (3/4) Complete; public_transport v2. 544 miles (875 km). No overnight service.
Missouri River Runner℠
relation 10322748
regional KCY→STL:
314;316 relation 11896405
STL→KCY:
311;313 relation 4743862
Routing (3/4)Stops (3/4) Complete; public_transport v2. 283 miles (455 km). Underlying infrastructure (route=railway) relations need fixing. Part of "Illinois Service."
Northeast Regional℠
relation 10322749
regional NFK→BOS:
88 relation 11977194
94 relation 11977193
NFK→NYP:
84 relation 11977192
NPN→BOS:
96;194 relation 11977190
66 relation 11977189
174 relation 11977191
RNK→BOS:
176 relation 11977188
RNK→NYP:
156 relation 11977187
WAS→BOS:
86 relation 11977838
162 relation 11977837
164 relation 11977836
166 relation 11977835
168 relation 11977834
170 relation 11977833
172 relation 11977832
178 relation 11977831
WAS→SPG:
140 relation 11976781
146 relation 11976780
148 relation 11976779
WAS→NYP:
82;192 relation 11977961
138;158 relation 11977962
126 relation 11977959
134 relation 11977958
198 relation 11977960
NYP→BOS:
150 relation 11977945
160 relation 11977947
190 relation 11977946
BOS→NFK:
93 relation 11977201
95 relation 4799100
BOS→NPN:
65;67 relation 11977198
99 relation 11977199
BOS→RNK:
171 relation 11977196
BOS→WAS:
135 relation 11977847
137 relation 11977846
139 relation 11977845
161 relation 11977844
165 relation 11977843
167 relation 11977842
173 relation 11977841
175 relation 11977840
195 relation 11977839
BOS→NYP:
169 relation 11977948
179 relation 11977949
SPG→NFK:
157 relation 11976782
SPG→RNK:
147 relation 4799101
SPG→WAS:
141;143 relation 11976783
NYP→NFK:
87 relation 11977200
NYP→NPN:
125 relation 11977197
NYP→RNK:
145 relation 11977195
NYP→WAS:
133 relation 11977954
155 relation 11977955
181 relation 11977957
189 relation 11977956
193 relation 11977953
Routing (3/4)Stops (3/4) Complete; public_transport v2. 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®
relation 10322750
regional SLO→SAN:
774 relation 11897311
GTA→SAN:
768 relation 11897309
796 relation 11897307
LAX→SAN:
564;580;584;1564;1584 relation 11897306
SAN→SLO:
777 relation 2812898
SAN→GTA:
763 relation 11897308
785 relation 11897310
SAN→LAX:
579;593;767;1767 relation 11897305
Routing (3/4)Stops (3/4) Complete; public_transport v2. 350 miles (565 km); (San Diego - Los Angeles - Santa Barbara - San Luis Obispo). 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.
Palmetto®
relation 10322751
national SAV→NYP:
90 relation 12006219
NYP→SAV:
89 relation 2648181
Routing (3/4)Stops (3/4) Complete; public_transport v2. 829 miles (1344 km). No overnight service.
Pennsylvanian℠
relation 10322745
regional PGH→NYP:
42 relation 4044002
NYP→PGH:
43 relation 11913832
Routing (3/4)Stops (3/4) Complete; public_transport v2. 444 miles (715 km). Underlying infrastructure (route=railway) relations need fixing.
Pere Marquette®
relation 10322746
regional CHI→GRR:
370 relation 2744526
GRR→CHI:
371 relation 11851451
Routing (3/4)Stops (3/4) Complete; public_transport v2. 176 miles (283 km). Underlying infrastructure (route=railway) relations need review. Part of "Michigan Services."
Piedmont®
relation 10322747
regional CLT→RGH:
74;76;78 relation 11904123
RGH→CLT:
73;75;77 relation 1901007
Routing (3/4)Stops (3/4) Complete; public_transport v2. 173 miles (278 km).
San Joaquins℠
relation 4668744
regional OKJ→BFD:
710;712;714;716;718 relation 4668743
SAC→BFD:
702;704 relation 4713797
BFD→OKJ:
711;713;715;717;719 relation 4668742
BFD→SAC:
701;703 relation 2856113
Routing (3/4)Stops (3/4) 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®
relation 10322741
national MIA→NYP:
98 relation 12009839
NYP→MIA:
97 relation 1590286
Routing (3/4)Stops (3/4) Complete; public_transport v2. 1522 miles (2449 km). Part of "Silver Service®."
Silver Star®
relation 10322742
national MIA→NYP:
92 relation 12011066
NYP→MIA:
91 relation 1897938
Routing (3/4)Stops (3/4) Complete; public_transport v2. 1377 miles (2216 km). Part of "Silver Service®."
Southwest Chief®
relation 4720714
national LAX→CHI:
4 relation 904839
CHI→LAX:
3 relation 4720713
CHI-LAX Routing (3/4)Stops (3/4)
LAX-CHI Routing (3/4)Stops (3/4) Complete; public_transport v2. 2265 miles (Chicago - Los Angeles).
Sunset Limited®
relation 10322739
national LAX→NOL:
2 relation 10946017
NOL→LAX:
1 relation 297142
Routing (3/4)Stops (3/4) Complete; public_transport v2. 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®
relation 10322739
national SAS→CHI:
22 relation 12180535
LAX→CHI:
422 relation 12180533
CHI→SAS:
21 relation 2795760
CHI→LAX:
421 relation 12180534
Routing (3/4)Stops (3/4) Complete; public_transport v2. 2728 miles (Chicago - San Antonio - Los Angeles). At San Antonio, train 421 decouples from train 21 to couple with train 1 westbound and train 422 decouples from train 2 to couple with train 22 eastbound. Tracks around Saint Louis are estimated.
Valley Flyer
relation 10322743
regional NHV→GFD:
488;494 relation 4797181
SPG→GFD:
400 relation 11961041
GFD→NHV:
461;471 relation 11921097
GFD→SPG:
499 relation 11961042
Routing (3/4)Stops (3/4) Complete; public_transport v2.
Vermonter℠
relation 10322744
regional WAS→SAB:
54 relation 11961030
56 relation 1359387
SAB→WAS:
55 relation 11921087
57 relation 11961031
Routing (3/4)Stops (3/4) Complete; public_transport v2. 611 miles (983 km).
Wolverine®
relation 10322740
regional CHI→PNT:
350 relation 1665342
352 relation 12044090
354 relation 12044091
PNT→CHI:
351 relation 11879712
353 relation 12044088
355 relation 12044089
Routing (3/4)Stops (3/4) Complete; public_transport v2. 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 (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/Passenger 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:

Symbol Meaning
Routing Route status
Stops Stops status
Base Code NA 0 1 2 3 4 X
{{State Route|r=...|h=}} Routing - implies status unknown Routing (0/4) - no part of route added Routing (1/4) - route partly added (as relation) Routing (2/4) - route mainly added, needs completing Routing (3/4) - route relation complete (in view of 1 editor). Should be verified. Routing (4/4) - route complete & verified by second editor. Please date. Routing (X/4) - route does not exist in real world.
{{State Route|r=|h=...}} Stops - implies status unknown Stops (0/4) - no stops added to relation Stops (1/4) - some stops added Stops (2/4) - most stops added, needs completing Stops (3/4) - all stops added to relation (in view of 1 editor). Should be verified. Stops (4/4) - route complete & verified by second editor. Please date. Stops (X/4) - no stops in real world. Unlikely to be used without r=X as well.

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.