A convention of right-hand main is assumed, and actual track and platform assignments may differ from what is mapped. ( Another rail renderer displayed rail-based passenger routes with their colour=* or color=* tag, but is no longer functional).Īmtrak route= train routes are complete to public_transport:version= 2 as of. 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. 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). Try OpenPublicTransportMap (OPTM): it displays passenger rail in route= train relations. The higher level route= train relations listed below are important to complete, but so are their underlying middle level infrastructure route= railway relations, too! 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. 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.
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. 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.įor 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. These are collected into middle level route= railway relations, not bottom level route= tracks relations as OpenRailwayMap suggests. More complete tagging on underlying infrastructure (track) segments (making up a "named Subdivision") includes accurate, contiguous railway=* elements, with identical name=* and usage=* tags. "Higher level" passenger rail routes like the Amtrak route relations linked here are properly a collection of rail segments, stations/stops and platforms. In North America, "bottom level" (infrastructure) route= tracks relations are omitted, instead skipping to "middle level" (infrastructure) route= railway relations. In the Passenger column, bold type indicates "higher-speed" service, which include Class 5 (90 MPH) or Class 6 (110 MPH) track.
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. Most of these routes are on Class 4 track (maximum speed 80 MPH). 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.
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).
Many states (California, Virginia, Maryland, Missouri, Illinois, Utah, New Mexico, Connecticut, Massachusetts, Pennsylvania, Florida.) and regional transportation authorities (e.g. 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.