Difference between revisions of "User talk:DGrewal"
(→Trip) |
(→Node) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 21: | Line 21: | ||
A run is an atomic piece of work performed by a driver. Only one driver can be assigned to a run. | A run is an atomic piece of work performed by a driver. Only one driver can be assigned to a run. | ||
| − | Hierarchy: Block > Route > Trip > '''''Run''''' | + | Hierarchy: Block > Route > Trip > '''''Run''''' > Stop |
== Stop == | == Stop == | ||
A stop is a dedicated physical location along a block, route, trip, or run. | A stop is a dedicated physical location along a block, route, trip, or run. | ||
| + | |||
| + | Hierarchy: Block > Route > Trip > Run > '''''Stop''''' | ||
| + | |||
| + | == Node == | ||
| + | |||
| + | A node is a dedicated point along a block, route, trip, or run. Although a node can be a stop, not all nodes are necessarily stops. | ||
Latest revision as of 21:44, 31 October 2019
Block
A block is the path traveled by a bus from pull-out (usually from a garage, yard, or depot) to pull-in (usually into a garage, yard, or depot). Each block can only have one bus.
Hierarchy: Block > Route > Trip > Run > Stop
Route
A route is a defined path taken by a bus with a designated start point (stop, node) and a designated end point (stop, node).
Hierarchy: Block > Route > Trip > Run > Stop
Trip
A trip is a unidirectional path of travel on a route.
Hierarchy: Block > Route > Trip > Run > Stop
Run
A run is an atomic piece of work performed by a driver. Only one driver can be assigned to a run.
Hierarchy: Block > Route > Trip > Run > Stop
Stop
A stop is a dedicated physical location along a block, route, trip, or run.
Hierarchy: Block > Route > Trip > Run > Stop
Node
A node is a dedicated point along a block, route, trip, or run. Although a node can be a stop, not all nodes are necessarily stops.