fdaley
OBS Chief
Someone claiming in this day and age that maintaining a database for the timetable to too time consuming to do it is merely expressing the high level of incompetence involved I am afraid.
It is sort of like a Restaurant saying that it is too time consuming to keep track of food inventory.... Oh wait Amtrak does have that problem too I suppose
I think it's more like a restaurant not having a printed or displayed menu and instead telling you that, if you feel like chicken, just punch that into our app and we'll show you all the chicken entrees. It works fine if you have a pretty good idea in advance of what you want, but you don't have the ability to survey all the options and perhaps be inspired to try something unexpected.
So the point-to-point offering on the website is OK if I'm going from Albany to New York and back or between some other pair of stations that I do all the time. And no doubt for many customers that's all the information they need, because that's the only kind of train travel they do. But if I'm planning a three-week cross-country trip with several stopovers, I really want to see what's covered in daylight, the connections between LD and corridor services, whether the connecting schedule's different on Friday or Sunday, and all kinds of other details before I'd even know whether it works better for me to take the Zephyr eastbound or westbound, for example. I don't think I'd have the patience to try to dope that out by punching in an endless bunch of city pairs and days of the week. So in a very real way, it becomes a disincentive to attempting that kind of travel.
Last edited: