Okay. Here's why adding discontinued routes isn't as easy as pie.
The underlying database doesn't allow for anything other than one set of route data - meaning that the whole application does its matching against a single set of routes, cities, stations, mileage, etc. In order to have more than one set of data, the database and pieces of the application would have to be rewritten to accommodate.
Luckily (for you), a new project is on the horizon that will make use of multiple sets of old data. This data will tie into MileTrak for the addition and tracking of discontinued or older routes. You must realize this is a mammoth task, as everything has to be manually entered from old printed matter.
Once the main database schema for discontinued routes is established, it will be a trivial matter to add another timetable, or another year. At that time I may also solicit some donations of old timetables for purposes of data entry. (I have a good list from the past six or seven years, but nothing prior to that)
I think I did mention some time ago about this year being difficult on time. I am constantly doing schoolwork and college entrance exams as well as worrying about work and other obligations. Sitting at a terminal typing mileage and cities from booklets is not a task I look forward to every day after having just gotten home from class, or after spending four hours programming for work. I guess it is hard for people to understand the demands on my time when things are left to languish for two, three, four months, but I really can't explain it much better.
thanks