Indicators for line route and timetable evaluation
The following indicators comprise line data, which are made up of the line route and the timetable. Demand data is not required for calculation.
Indicator |
Description |
Line network length (directed) |
Sum of link lengths of the links traversed by line routes. Traverses a line route a link more than once, it is only counted once. |
Line network length (undirected) |
Compared to the directed line network length, for links which are traversed in both directions, only the undirected values (this means, the mean value from the lengths of both directions) is counted. If the link is only traversed in one direction, the undirected length corresponds to the directed length. |
Network length (directed) |
Total length of links open to transport system. The length of both directions is included in the calculation. |
Network length (undirected) |
Compared to directed network length, for links the average link length (this means the mean value from the lengths of both directions) is counted for both open directions. |
Number of lines |
The meaning of this indicator depends on the network object for which it is calculated.
|
Num lines TSys |
Additionally returns the number of lines for each transport system. Otherwise, the indicator is analog to the number of lines. |
Num line routes |
Number of line routes of a line or number of line routes run by a vehicle combination during a block. |
Number of stop points total |
Number of stop points, which lie within a territory polygon. |
Number of stop points served |
Number of served stop points, which lie within a territory polygon. A stop point is served, when it is traversed by a line route. Thus, a line route item with this stop point is required and for the respective time profile item boarding or alighting has to be possible. It is not necessary that trips serve this stop point. |
Stops served |
The meaning of this indicator depends on the network object for which it is calculated.
|
Earliest departure |
Earliest departure from stop point located inside territory. This is the earliest departure within the analysis period, not necessarily the first departure of the day (for example, departure at 12:20 a.m.). |
Latest arrival |
Latest arrival at stop point located inside territory. This is the latest arrival within analysis period, not necessarily the last departure of the day (for example, arrival at 11:59 p.m.). |
Stop time |
The stop time, which accumulates from stop events at stop points within the territory polygon. The stop time is made up of the input attribute Stop time at the time profile items. |
Number of PuT departures |
The meaning of this indicator depends on the network object for which it is calculated. The indicator is especially interesting for time interval-related analyses, to determine the departures within a certain time interval for example.
|
Number of departures-TSys |
In contrast to Number of PuT departures, the number of departures is returned by transport system. The calculation is otherwise the same. The coupling is taken into account if there is a coupling at the departure at the stop point. |
Number of PuT arrivals |
Number of vehicle journeys, which stop for alighting at the stop or the stop point. Multiple stop events are counted several times for a stop. The coupling is taken into account if there is a coupling on arrival at the stop point. |
Number of arrivals-TSys |
In contrast to Number of PuT arrivals, the number of arrivals is returned by transport system. The calculation is otherwise the same. |
Number of service trips uncoupled |
The meaning of the indicator depends on the network object for which it is calculated:
|
Number of service trips |
In contrast to the indicator Number of service trips uncoupled, coupled vehicle journeys count as one vehicle journey for this indicator. If two vehicle journeys have been coupled in a section, the vehicle journey item attribute has value 0.5 for each service within the particular time slot, and 0.33 if three vehicle journeys have been coupled, etc. Accordingly, coupled departures count as one departure in the stop point attribute, for example. Since a vehicle journey, a time profile and a line route can be coupled by section, this indicator can only be returned for network objects with a unique location reference. For line routes, time profiles and vehicle journeys, it cannot be returned.
|
Number of service trips (vehicle combination) |
For PuT-Detail evaluations this indicator only differs from the Number of service trips uncoupled if there are vehicle journeys with several vehicle journey sections and these differ in terms of the vehicle combination. In contrast to Number of service trips uncoupled the number of service trips is distributed to the vehicle journey sections in this case. If vehicle journey sections differ only in terms of the valid days, the values Number of service trips (vehicle combination) and Number of service trips uncoupled will match. Therefore, the evaluation of this indicator is useful for territory analyses only for levels in combination with xVehComb. |
Number of service trips-TSys |
In contrast to Number of service trips, the number of vehicle journeys is returned by transport system. The calculation is otherwise the same. Especially coupled vehicle journeys only count proportionally. |
Number of section service trips |
In contrast to the skim Number of service trips uncoupled, for this skim, the traverses are added, for which the number of vehicle journey sections is decisive. This allows for an evaluation via double tractions if these are modeled via parallel vehicle journey sections. Skims based on links, line route items and vehicle journey items are available. |
Mean service trip length |
Calculation is dependent on the network object.
|
Number of stop events |
The meaning of the indicator depends on the network object for which it is calculated:
|
Number of stop events |
Unlike the Number of stop events, the number of weighted stop events is calculated by half of the sum of arrivals and departures of vehicle journeys. This indicator therefore also counts stop events, but does not provide integer values. Instead, an arrival at the end of a vehicle journey (a vehicle journey section, etc.) is only half a stop event. |
Number of stop events uncoupled |
Unlike the Number of stop events, couplings are not taken into account. Coupled vehicle journeys are counted individually. The calculation is otherwise the same. |
Number of weighted stop events uncoupled |
In contrast to the Number of weighted stop events, couplings are not taken into account. Coupled vehicle journeys are counted individually. The calculation is otherwise the same. |
Number of stop events per transport system |
In contrast to the Number of stop events, the number of stop events is output per transport system. The calculation is otherwise the same. In contrast to the number of stops, the number of stops is output per transport system. The calculation is otherwise the same. |
Number of section stop events |
In contrast to the Number of stop events, the number of the vehicle journey sections is output. The calculation is otherwise the same. |
Number of weighted start stop events |
In contrast to the Number of weighted stop events, the arrivals and departures of vehicle journey sections are output. The calculation is otherwise the same. |
Number of start stop events |
Number of vehicle journeys that start at a stop in the territory. For passenger trip chains between vehicle journeys, only stop events at the outer ends are accounted for. |
Number of end stop events |
Number of vehicle journeys that end at a stop in the territory. For passenger trip chains between vehicle journeys, only stop events at the outer ends are accounted for. |
Number of passage events |
Number of events at a stop where boarding and alighting are not allowed. Couplings are taken into account. |
Number of passage events uncoupled |
Number of events at a stop where boarding and alighting are not allowed. Couplings are not taken into account. |
Number of section passage events |
In contrast to the Number of passage events, the number of vehicle journey sections is output. The calculation is otherwise the same. |
Mean service time |
Calculation is dependent on the network object.
|
Is coupled |
(Respective) time profile is coupled with another time profile (1) or not coupled (0). |
Effectively coupled |
An effective coupling means the following: a vehicle journey, which is coupled with another vehicle journey via its corresponding time profile, is really carried out (in other words: at least one vehicle journey service is required for each of the coupled time profiles, these vehicle journeys have to be active and require a valid 'valid day'. For a valid valid day, the valid day is within the analysis period and both coupled vehicle journeys are carried out on the same day). |
Relation: Reached departing vehicle journey items |
For an item that allows for alighting, the relation between vehicle journeys consists of all vehicle journey items that fulfill the following conditions:
A relation allows you to perform an analysis that identifies areas within the network where connections were changed due to departure times of individual vehicle journeys being moved back. |
Relation: Missed departing vehicle journey items |
For an item that allows for alighting, the relation between vehicle journeys consists of all vehicle journey items that fulfill the following conditions:
|
Relation: Reaching arriving vehicle journey items |
For an item that allows for alighting, the relation between vehicle journeys consists of all vehicle journey items that fulfill the following conditions:
|
Relation: Missing arriving vehicle journey items |
For an item that allows for alighting, the relation between vehicle journeys consists of all vehicle journey items that fulfill the following conditions:
|
Relation: Number of reached transfers |
These attributes sum up the number of vehicle journey items in the relation "Reached departing vehicle journey items" for all vehicle journey items located at a stop point of the stop. |
Relation: Number of missed transfers |
These attributes sum up the number of vehicle journey items in the relation "Missed departing vehicle journey items" for all vehicle journey items located at a stop point of the stop. |
Table 244: Indicators for line route and timetable evaluation
(*) Prior to Visum 2022, indicators were available as Number of service trips.
Calculation example: Number of departures per transport system
- Number of departures for analysis period = number of vehicle journeys, which depart on Jan 02, 2006
For the bus, the number of departures (AP) = 76 (Trips no. 96 to 172)
For the train, the number of departures (AP) = 38 (Trips no. 58 to 95)
- Number of departures for analysis horizon = Num Departures (AP) • projection factor of valid day
For the bus, the number of departures is calculated (AH) = 38 • 365 + 38 • 260 = 23750
For the train, the number of departures is calculated (AH) = 38 • 365 = 13870
- Number of departures for analysis period TI1 = Number of vehicle journeys, whose departure time lies between 8 a.m. and 9 a.m.
For the bus, the number of departures results from (TI1) = 7 (Trip no. 99, 100, 119, 120, 138, 139, 157)
For the train, the number of departures results from (TI1) = 3 (Trip no. 61, 80, 81)
Calculation example: Number of service trips per transport system
For the analysis period and the analysis horizon, the number of service trips complies with the number of departures in this example. The difference between the two indicators can be seen when looking at the analysis period TI1. Now also vehicle journeys are counted, whose departure does not lie in the time interval between 8:00 a.m. and 9:00 a.m., though they are running in this time slice.
- Number of service trips analysis period TI1 = number of vehicle journeys between 08:00 AM and 09:00 AM.
For the bus, the resulting number of service trips (TI) = 10 (Trip no. 98, 99, 100, 118, 119, 120, 138, 139, 156, 157)
For the train, the resulting number of service trips (TI) = 4 (Trip no. 60, 61, 80, 81)