Add message on frontend and allow for missing trip data/frequency data

I agree about the fragility - this is something that I should change before any merge. As for the error message translation, the part (11,20) is meant to capture only the number that is passed.

A more ideal solution (which would not be ready for any kind of demo time) would probably involve a couple more columns on the model to track specific types of error.