What a royal mistake.
Actually, when I have gone chasing GO promises that I was sure I remembered from a previous year or more ago, the source documents (such as the reports to the Board meetings, or the power point decks for community consultations) often had qualifiers all along. For instance, that fourth track on the Weston Sub - that everyone assumes is just around the corner - was marked "2031" in many of the consultation meeting drawings. Someone knew better than to let the poetic-waxing go crazy without a bit of fine print.I do hate GOs incremental approach. Numerous vague/ambiguous announcements and non-delivered results.
Exactly. And today, signal issues everywhere. GO takes forever to do anything.I do hate GOs incremental approach. Numerous vague/ambiguous announcements and non-delivered results.
TTC might get be a little late, but when they promise certain capacity after such-and-such a project they usually get pretty close; resignalling not included.
IMO, the resignalling project has all the same issues as GOs incremental approaches. A number of required items for the wanted results are not a part of the project or even funded.
I actually chose today to give the 5:50 West Harbour Express a try! I was pretty irritated when 6:05 came and went, 15 minutes late, no sign of the train. It had been pulled off the departure boards/mobile app at 5:51, and disappeared from the on-platform boards a few minutes later. Finally a sole GO employee came on the platform moving from Bay to York, asking people one by one (yes, seriously) what train they were waiting for, and if they said they were waiting for the 5:50, he redirected us to Platform 13 instead of the original 7/8. Wow. Anyways, headed over, the CSA was making announcements every 30-45 seconds that this train makes no stops before West Harbour, and we departed at 6:15, an incredible 25 minutes late. Had some trouble getting out of Union and GO's reported delay online peaked at 30 minutes. Amusingly, the CSA came by a few minutes after departure and confirmed with me that I was heading to West Harbour--I was far from the accessibility coach, so I have to assume he went through the whole train both ways to get both floors and asked everybody to be safe.twitterverse:
Does this break the all-time record for the fastest Union-to-Hamilton trip time for a 12-car bilevel? (vegata_skyline, you might know) It seemed to be going almost always flat-out at the rail speed limits in most sections. This train made GO Tracker exciting to watch as I've never seen a GOtrain rush that fast to Hamilton; it might portend what is the theoretical limit of speedups we might see from RER electrification, if eventually extra tracks and electric express trains were reliable enough to allow timetabled operation this fast. This is kind of why I was watching GO Tracker -- what does rail speed limits allow, if a GO train was allowed to go flat out safely?
Yes. Would not be surprised if there was a 45 minute express back in the olden days, when there were far fewer grade crossings.47 minutes. I wonder what the record was with steam engines, back when they used to run 1-stop or so expresses frequently. As I noted previously in this thread, it was scheduled to be 55 minutes back in 1950 to Hamilton (now West Harbour) from Union, with a stop at Sunnyside.
Is it a Union to Hamilton record? Absolutely! Then again it's not like the previous records been around for long... I mean we only started stopping at the West Harbour GO Station a couple weeks agoDoes this break the all-time record for the fastest Union-to-Hamilton trip time for a 12-car bilevel? (vegata_skyline, you might know)
This started out as a question of how it compared to historic travel times. Given that the platform for West Harbour GO overlaps (barely) the old platform for the CN Hamilton station, then the travel times are comparable.Is it a Union to Hamilton record? Absolutely! Then again it's not like the previous records been around for long... I mean we only started stopping at the West Harbour GO Station a couple weeks ago