Darwin gives a lot of information. One thing to note is that some of the information is supposed to update information previously given.

Currently our implementation simply shoves all the data into Postgres, but what is needed is actually an up to date database with no outdated information stored.

This milestone has the objective of implementing that infrastructure starting with the Schedule messages, including CallingPoints. This also includes handling lost messages (from the darwin logs and/or non-realtime data that is useful to get the schedules up).

In other words, we aim to have an up to date Schedule model.