Handle last pings in realtime

[Edward-Jackson-ONS]

Last pings before 10am aren't necessarily to be associated with a stop e.g. a ping may indicate that stop 5 is next but this may still be minutes in the future. Do we need to drop the last stop_sequence for each trip_id?

[Edward-Jackson-ONS]

By filtering to all the last pings, we can identify (for the large part) currently active services. Consequently, we can remove these trip_id/time_transpond/current_stop combinations. However, this will also remove those services that have legitimately 'just' arrived at their next stop. These are likely to be few in number but will require further work.