Amtrak

From OpenStreetMap Wiki
Jump to: navigation, 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: some passenger=suburban (commuter) trains, most passenger=regional (medium-distance: often interstate, sometimes intrastate) 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 kph), nearly half of Amtrak trains operate at top speeds of 100 mph (161 kph) or greater.

In North America, a "bottom level" (infrastructure) route=tracks relation is usually omitted, skipping directly to a "middle level" (infrastructure) route=railway relation. "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 includes accurate name=* and usage=* tags. And, identically named track segments (making up a "named Subdivision") are collected into a middle level route=railway relation (not a bottom level route=tracks relation 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 the underlying middle level route=railway relation(s) (infrastructure which should contain 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!

Amtrak route=train routes are roughly Complete, at least to a rudimentary stage of public_transport:version=1. Underway now are improvements to these relations to public_transport:version=2 (a route_master super-relation, each identically-tracked train in its own route relation, bi-directional route logic and precise locations of a completed set of public_transport=platforms). See the Southwest Chief routes, which serve as a model Amtrak public_transport:version=2 example. For another v2 route with exemplary station and platform members see Relation: Brunswick Line: Frederick => Union Station of the Maryland Transit Administration. A goal is for all Amtrak routes to become public_transport:version=2. Thanks to all who improve OSM!

Such growth from v1 to v2 is what is meant by Map Your Train Ride! Add public_transport=platforms to the route=train relation of your commute. It's easy: add a node or draw a small polygon representing the exact location of the platform, and tag with public_transport=platform, railway=platform and rail=yes. Also add it to the proper route=train relation(s) which should be found around that railway=station. For further guidance, see this diagram of a "simple railway station."

Even-numbered trains travel north and east, while odd-numbered trains travel south and west. Among the exceptions are Pacific Surfliner trains, which use the opposite numbering system inherited from the Santa Fe Railway, some Empire Service trains and Downeaster trains.

Route Trains Passenger Service Relation Status and Notes
Acela Express® 2100-2222 high speed relation 4460896 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 457 miles (735 km). Amtrak's premier high-speed service between Boston and Washington, with speeds up to 150 mph (241 kph) in parts of Rhode Island and Massachusetts. Underlying Northeast Corridor needs fixing (double/triple/quad tracking, infrastructure harmonization with OSM and ORM conventions).
Adirondack® 68, 69 international relation 4073816 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough 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 relation 3517701 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 855 miles (1,376 km). Tagged both passenger=national and service=car.
Blue Water℠ 364, 365 regional relation 1687374 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 319 miles (513 km). Underlying infrastructure (route=railway) relations need fixing. Part of "Michigan Services."
California Zephyr℠ 5, 6 national relation 905830 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v2. 2438 miles (Chicago - Emeryville, California). Underlying infrastructure (route=railway) relations need fixing.
Capitol Corridor℠ 522, 523, 527, 537, 538, 546, 549, 720, 727, 732, 737, 744, 748, 749 regional relation 2845553 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 168 miles (275 km) (San Jose - Oakland - Sacramento - Auburn). Phase 1 southern extension from San José (Diridon) to Gilroy (+49 km) and Salinas (+60 km) expected in 2020, for a new total length of 238 miles (384) km. New infill stations at Watsonville Junction (Pajaro) and Castroville (to serve Monterey) as Phase 2, no revenue service date specified. The Capitol Corridor is the third busiest Amtrak route in the country, moving 1.4 million passengers annually between San Jose and Auburn. Part of "Amtrak California," though this is less prominent with "more local" CCJPA, SJJPA and LOSSAN joint powers authorities.
Capitol Limited℠ 29, 30 national relation 2794554 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 780 miles (1260 km).
Cardinal® 50, 51 national relation 2807121 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 1146 miles (1844 km).
Carl Sandburg®-Illinois Zephyr® 380-383 regional relation 4744150 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 258 miles (415 km). Part of "Illinois Service."
Carolinian℠ 79, 80 national relation 1900976 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 704 miles (1133 km). No overnight service.
Cascades® 500-519 international relation 71428 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 467 miles (752 km), though no single train covers this entire distance. No overnight service. Underlying infrastructure (route=railway) relations need fixing.
City of New Orleans® 58, 59 national relation 1532755 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v2. 934 miles (1503 km).
Coast Starlight® 11, 14 national relation 2812900 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 1377 miles (Seattle - Los Angeles). Underlying infrastructure Seattle Subdivision needs fixing.
Crescent® 19, 20 national relation 1809808 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 1377 miles (2216 km). Underlying infrastructure (route=railway) relations need fixing.
Downeaster℠ 680-699 regional relation 4743492 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 145 miles (233 km).
Empire Builder® 7, 8, 27, 28 national relation 1809794 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 2206 miles (3550 km) (Chicago - Seattle). Underlying infrastructure (route=railway) relations need fixing.
Empire Service® 230-288 regional relation 4452798 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Somewhat complete; rough public_transport v2. 460 miles (740 km), a "higher-speed" corridor and service, contrasted with Acela, Amtrak's highest speed service. Needs additional Albany to Buffalo routes.
Ethan Allen Express® 290-293, 295, 296 regional relation 4445810 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v2. 241 miles (388 km). Underlying infrastructure (route=railway) relations need fixing.
Heartland Flyer® 821, 822 regional relation 4743154 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 206 miles (332 km). Underlying infrastructure (route=railway) relations need fixing.
Hiawatha Service® 329-343 regional relation 1638760 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 86 miles (138 km).
Hoosier State® 850, 851 regional relation 4744182 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Essentially complete; public_transport v1. 196 miles (315 km). "Last mile" connectivity needed in Chicago.
Illini®-Saluki® 390-393 regional relation 1902680 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v2. 310 miles (499 km). Part of "Illinois Service."
Keystone Service® 600-672 regional relation 4748609 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) 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 national relation 1358974 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 959 miles (1543 km). Underlying infrastructure (route=railway) relations need fixing.
Lincoln® Service 300-307 regional relation 4744138 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) 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 relation 4467191 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v2. 544 miles (875 km). No overnight service. Underlying infrastructure (route=railway) relations need fixing.
Missouri River Runner℠ 311-316 regional relation 4743862 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) 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 relation 4799100 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Essentially complete; rough public_transport v1. 664 miles (1069 km). Amtrak's busiest routes on a "higher-speed" corridor and service (though these routes are "regular speed"), contrasted with Acela, Amtrak's highest speed service. Needs substantial work to split into v2 routes. Underlying Northeast Corridor needs fixing (double/triple/quad tracking, infrastructure harmonization with OSM and ORM conventions).
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 relation 4799101 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 664 miles (1069 km). Amtrak's busiest routes on a "higher-speed" corridor and service (though these routes are "regular speed"), contrasted with Acela, Amtrak's highest speed service. Needs substantial work to split this "union" route into v2 routes. Underlying Northeast Corridor needs fixing (double/triple/quad tracking, infrastructure harmonization with OSM and ORM conventions).
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 relation 2812898 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) 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). The 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," though this is less prominent with "more local" CCJPA, SJJPA and LOSSAN joint powers authorities.
Palmetto® 89, 90 national relation 2648181 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 829 miles (1334 km). No overnight service.
Pennsylvanian℠ 42, 43 regional relation 4044002 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 444 miles (715 km). Underlying infrastructure (route=railway) relations need fixing.
Pere Marquette® 370, 371 regional relation 2744526 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 176 miles (283 km). Underlying infrastructure (route=railway) relations need fixing. Part of "Michigan Services."
Piedmont® 73-76 regional relation 1901007 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 173 miles (278 km).
San Joaquins℠ 701-704, 710-719 regional relation 4668744 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Not complete if exact platform locations count, let's agree they do. Let's improve this relation; rough public_transport v2. Use as a rough model v2 example route in California, other (Maryland) routes have better platform members. Needs better platform members. Map Your Train Ride! 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 the Amtrak California system, linking Los Angeles and the Bay Area. Part of "Amtrak California," though this is less prominent with "more local" CCJPA, SJJPA and LOSSAN joint powers authorities.
Shuttle 401, 405, 407, 432, 450, 460, 463-465, 467, 470, 475, 476, 479, 488, 490, 493-495, 497 suburban/commuter relation 4797181 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. About 62 miles (100 km) serving New Haven and Hartford, Connecticut to Springfield, Massachusetts.
Silver Meteor® 97, 98 national relation 1590286 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 1389 miles (2235 km). Part of "Silver Service®."
Silver Star® 91, 92 national relation 1897938 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 1522 miles (2449 km). Part of "Silver Service®."
Southwest Chief® 3, 4 national relation 4720714 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v2. 2265 miles (Chicago - Los Angeles).
Sunset Limited® 1, 2 national relation 297142 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; public_transport v1. 1995 miles (New Orleans - Los Angeles).
Texas Eagle® 21, 22, 421, 422 national relation 2795760 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough public_transport v1. 2728 miles (Chicago - San Antonio - Los Angeles). Needs track split fixes in Arizona; tracks around Saint Louis are estimated.
Vermonter℠ 54-57 regional relation 1359387 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Essentially complete; public_transport v1. 611 miles (983 km). Needs rerouting through Connecticut River Line (see [1])
Wolverine® 350-355 regional relation 1665342 (iD, JOSM, Potlatch2, history, analyze, manage, GPX, XML) Complete; rough 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 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.
Red means that "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.

About the (branding, livery) colors in the Passenger Service 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, passenger=suburban (commuter) = goldenrod and service=car = yellow. Try clicking the Passenger Service 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. Generally, the longest national routes are the darkest blue.
National routes without overnight service are lighter shades of blue: SkyBlue on Carolinian and DeepSkyBlue on Palmetto. Because of this and their "only 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 mostly brown and orange palettes (smearing a bit into yellowish/mustard/khaki); suburban/commuter route Shuttle is goldenrod. Exceptionally, one major regional route is a lighter 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.
This has minor flaws, for example, Vermonter as a darker brown (Sienna), yet Vermonter is not higher-speed, however it is lengthier, so darker regional now has a double-meaning of higher-speed or lengthier. It is true that "lighter browns" are all "regular speed, shorter-length regional routes" (desaturation=shorter). 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 lighter shade of blue. A goal is better visual color consistency (given the above schema, which changes, bending without breaking) across all passenger=* services. Color harmony, in motion.

Retrieved from "http://wiki.openstreetmap.org/w/index.php?title=Amtrak&oldid=1627346"