Metroscapes
Active Member
I'm just glad we're far past that ugly pale yellow 1990s MSPaint-looking map.
Monday’s incident in the Union Station Rail Corridor had a significant impact across our network - requiring significant work to bring four platforms back into service.
On top of that, we experienced two separate incidents last night on the Lakeshore lines around 17:30, with two separate trains encountering main engine reservoir failures, delaying roughly 2,300 customers for hours as we sought to fix trains in place to allow for service to continue around these trains.
The “well will run express from Milliken to Union” doesn’t materially change much given the slow order at Finch, crawling through Agincourt, slow order at Progress and crawling through Kennedy before getting into queue to crawl into a platform at Union because we missed our original slot.The 8:09 stoufville train got totally jammed up for a mysterious reason at unionville... they claim it's for a northbound train but there's no scheduled train going north until 940.... it finally started moving 30 min later. See.... this is what happens when they lag on finishing double tracking and trains need to go zig zag across eachother....
Didnt help my cause since I had to get kicked off to the next train for agincourt.....The “well will run express from Milliken to Union” doesn’t materially change much given the slow order at Finch, crawling through Agincourt, slow order at Progress and crawling through Kennedy before getting into queue to crawl into a platform at Union because we missed our original slot.
That said, the nomenclature isn’t always consistent. Many lines aren’t named after their terminal stations at all—Lakeshore East and West, Barrie, Richmond Hill, and Stouffville among them. Kitchener is the main exception. You could argue that Lakeshore West should be the Niagara Line and Lakeshore East the Oshawa Line. The apparent logic seems to be naming lines after what they’re best known for, but the result is uneven.Personally, I am not in favour of abandoning the GO naming scheme where the ref and name reflect where the train goes... I think it would be very boring to do so too
The only reforms I think I would bring onto GO is to change naming from terminal -> corridor (So that if it ever gets extended it doesn't need renaming) and to put different services as part of the naming scheme, as an example, LW-HA for trains that terminate to Hamilton GO, or LW-NI for Niagara, or LW-EX for express. Granted, LW has too many service patterns which really should be coalesced.
The current scheme prevents any potential naming conflicts with local transit, which is good.
I couldn't find anything out about this anywhere, and tough even to find the URL of the paywalled article - which is https://www.thetrillium.ca/insider-...zes-for-overcharging-riders-on-feb-1-11862958Article is paywalled so not sure of the details.
I frequently check what I'm charged, especially when doing something out-of-the-ordinary. I've never noticed an issue of charging the cash vs Presto fare. Is there any information on when and where?The issue, as I understand it, is that Presto has been charging people the cash fare rather than the Presto fare when they tap their cards, in some/all circumstances. (one person's account was this experience on GO)
Mx/Presto have been rather quiet about this........Article is paywalled so not sure of the details.
Michael Lindsay, speaking this morning at the Mx Board meeting very thoroughly went over what happened in the USRC incident last week.
Discussion begins at ~24M in to the video.
Short version, a number of lag screws failed and were sheered off due to fatigue, the rail was out by 1 and 1/8th inches causing the derailment. Lots more detail to be had though, including info on a problematic finding that the number of screws required at some locations to keeps the rails working as they should was 1/2 what it was supposed to be.




