Hello! While working with infostop for my thesis on large data, I noticed the following things about postprocess:
-
The max time between check sometimes splits a single stop event into 2, resulting in compute_intervals returning more rows than in the stop_events.
If we were to column_stack the 2 arrays we would result in an error
-
The last check, if loc_prev == -1 to add the last entry into the final_trajectory sometimes misses a stop, as data can always end with a stop and not a trip.
Hello! While working with infostop for my thesis on large data, I noticed the following things about postprocess:
The max time between check sometimes splits a single stop event into 2, resulting in compute_intervals returning more rows than in the stop_events.
If we were to column_stack the 2 arrays we would result in an error
The last check, if loc_prev == -1 to add the last entry into the final_trajectory sometimes misses a stop, as data can always end with a stop and not a trip.