Amtrak

From OpenStreetMap Wiki
Jump to: navigation, search

Amtrak is the sole operator of most intercity passenger trains in the contiguous United States: some commuter trains, most intrastate and regional trains and all interstate, long distance, overnight, high-speed and international trains (some cross into Canada). 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 of which are included in Amtrak (California), some of which 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.

In North America, a "bottom level" (infrastructure) relation of route=tracks is usually omitted, skipping directly to a "middle level" (infrastructure) relation of route=railway. "Higher level" passenger rail routes like the Amtrak routes linked here are properly a collection of rail segments, stations/stops and platforms. More complete tagging on underlying infrastructure includes accurate name=* and usage=* tags. And, identically named track segments (making up a "named Subdivision") are collected into a route=railway relation (not a route=tracks relation as OpenRailwayMap suggests). You can improve one or more of the route=train relations below without the following suggestion, but please endeavor to include a review/correction/completion of the underlying 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 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 route=railway "named Subdivision" relation. The route=train relations listed below are important to complete, but so are their underlying 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, bi-directional route logic and complete public_transport=platforms). See the San Joaquin route, which can be used as a model Amtrak public_transport:version=2 example (it has stations, but few platforms). For a 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, each identically-tracked train with its own route and precise platform locations.

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, light_rail=yes, subway=yes or tram=yes. You might 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".

Route Trains Service Relation Status
Acela Express 2100–2297 high_speed Relation 4460896 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1. Northeast Corridor needs fixing
Adirondack 68, 69 international Relation 4073816 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1; Station nodes need ordering
Auto Train 52, 53 car Relation 3517701 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Blue Water 364, 365 regional Relation 1687374 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
California Zephyr 5, 6 long_distance Relation 905830 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1.  The relation is said to be so big it is hard to work with.
Capitol Corridor 518-553; 720-751 regional Relation 2845553 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1. Extension to Gilroy (Pajaro, Castroville) and Salinas is expected in 2018.
Capitol Limited 29, 30 long_distance Relation 2794554 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Cardinal 50, 51 long_distance Relation 2807121 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Carl Sandburg 381, 382 regional Relation 4744150 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Carolinian 79, 80 long_distance Relation 1900976 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Cascades 500-517 international Relation 71428 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
City of New Orleans 58, 59 long_distance Relation 1532755 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Essentially complete; public_transport v1; "Last mile" connectivity needed in Chicago
Coast Starlight 11, 14 long_distance Relation 2812900 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1. Underlying infrastructure Seattle Subdivision needs fixing
Crescent 19, 20 long_distance Relation 1809808 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
Downeaster 680-699 regional Relation 4743492 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Empire Builder 7, 8; 27, 28 long_distance Relation 1809794 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
Empire Service 230-288 regional Relation 4234377 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v2
Ethan Allen Express 290-296 regional Relation 4234911 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v2
Heartland Flyer 821, 822 regional Relation 4743154 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
Hiawatha Service 329-342 regional Relation 1638760 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Hoosier State 850, 851 regional Relation 4744182 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Essentially complete; public_transport v1; "Last mile" connectivity needed in Chicago
Illini-Saluki 390-393 regional Relation 1902680 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
Illinois Zephyr 380, 383 regional Relation 4744150 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Keystone Service 600-672 commuter Relation 4748609 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Lake Shore Limited 48, 49; 448, 449 long_distance Relation 1358974 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
Lincoln Service 300-307 regional Relation 4744138 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1; tracks near St. Louis estimated
Maple Leaf 63, 64 international Relation 4467191 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v2
Missouri River Runner 311-316 regional Relation 4743862 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
Northeast Regional (Lynchburg) 66, 67, 78, 82–88, 93–95, 99, 110, 111, 121, 125, 127, 129–131, 133–143, 145–148, 150–199 regional Relation 4799101 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1; Needs substantial work to split this "union" route into v2 routes
Northeast Regional (Norfolk) 66, 67, 78, 82–88, 93–95, 99, 110, 111, 121, 125, 127, 129–131, 133–143, 145–148, 150–199 regional Relation 4799100 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Essentially complete; rough public_transport v1; Gap around Petersburg, Virginia. Needs substantial work to split into v2 routes
Pacific Surfliner 562-597; 763-799 regional Relation 2812898 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
Palmetto 89, 90 long_distance Relation 2648181 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Pennsylvanian 42-44 regional Relation 4044002 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
Pere Marquette 370, 371 regional Relation 2744526 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1
Piedmont 73-76 regional Relation 1901007 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
San Joaquin 701-718 regional Relation 4668744 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not complete if exact platform locations count. Let's agree that now 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!
Shuttle 401-497 commuter Relation 4797181 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Silver Meteor 97, 98 long_distance Relation 1590286 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Silver Star 91, 92 long_distance Relation 1897938 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; public_transport v1
Southwest Chief 3, 4 long_distance Relation 4720714 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v2. Underlying infrastructure Seligman Subdivision needs fixing
Sunset Limited 1, 2 long_distance Relation 297142 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1; Needs track/station node ordering, fixes around Houston
Texas Eagle 21-22; 321-322; 421-422 long_distance Relation 2795760 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1; Needs track split fixes in Arizona; tracks near St. Louis estimated
Vermonter 54-57 long_distance Relation 1359387 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Essentially complete; public_transport v1; Needs rerouting through Connecticut River Line (see [1])
Wolverine 350-355 regional Relation 1665342 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Complete; rough public_transport v1

About the 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 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 colors in the Service column

Thanks to Indy Hurt and Mapzen, here is a rail renderer that displays rail-based passenger routes (route=train, route=subway, route=light_rail, route=tram) with their colour=* (or color=*) tags. As Amtrak does not appear to assign specific colors to its many routes, some routes above experimentally display colors in the Service column where service=long_distance routes = blue (the default Amtrak color of #005480), service=high_speed = red, some service=regional routes = orange, service=car = yellow, service=international = indigo or green and service=commuter = goldenrod. Closer zooms with this renderer display color=* tags of state/regional and local route=trains, as they are assigned in their network=*. A present edge seems to be around orange as regional (California poppy state flower color), commuter as goldenrod (a sort of orange-brown) and "what color now?" for other states' regional routes. Initial "orange/brown" assignment choice as SaddleBrown [Chocolate, Sienna, Tan...one of 16 other web safe brownish colors with names] to other Amtrak regional routes may oversimplify and underscores the "muddiness" of what to discuss or assign next. This may be why Amtrak does not assign colors, but it doesn't mean OSM can't make good choices here, we can. An example is that for Amtrak Cascades service in Washington state, OSM's Amtrak wiki and Mapzen's transit-colours both display a closely matching shade of green, which in turn may better match livery of rolling stock found only on those tracks by that line and class of service. Similar early harmony among Amtrak and California/Railroads is underway, e.g. Pacific Surfliner, Capitol Corridor. A goal is towards more state/national agreement and completion. Color harmony, in motion.