Introducing the concept of "halt on link", meaning non-movement events, one per row, derived from successive points_on_link having the same location. The duration of a halt event can be decomposed into doors open time, doors closed time, and doors unknown time. Furthermore, it is of interest whether the halt is located at a stop area or elsewhere.
I'm using a bit weird word "halt" instead of "stop", since "stop" is already in use for transit stop points.
This is also an intermediate step towards aggregating time-spent-stopped to links on journey. However, with this table and related views, the user can analyze individual halt events, their exact locations, durations, count, repetitiveness and so on.
Introducing the concept of "halt on link", meaning non-movement events, one per row, derived from successive
points_on_linkhaving the same location. The duration of a halt event can be decomposed into doors open time, doors closed time, and doors unknown time. Furthermore, it is of interest whether the halt is located at a stop area or elsewhere.I'm using a bit weird word "halt" instead of "stop", since "stop" is already in use for transit stop points.
This is also an intermediate step towards aggregating time-spent-stopped to links on journey. However, with this table and related views, the user can analyze individual halt events, their exact locations, durations, count, repetitiveness and so on.