Jump to content


  • Posts

  • Joined

Posts posted by Sid

  1. 2 hours ago, smallspy said:

    That is one of the "features" of the new schedule. GO wanted to run hourly West Harbour trains during the day - along with a bunch of additional service elsewhere - but the Minister told them to cool it. They are trying again for many of those same improvements in October.

    I'm glad to hear it's just the Minister now! Hopefully ridership will recover fast enough for October.

    2 hours ago, smallspy said:

    That first Barrie train isn't a deadhead, three trains are capable of being stored at Bradford. This will be one of them. The other two slots will continue to be used for more long-term equipment storage.

    I meant the trains that will (afaict) deadhead from Union to run the first trips from Aurora (9:57) and Mount Joy (9:12), where there seems to be lots of room to run them as revenue trips with all stops. Though since you say the schedule was cut back from GO's original plans, maybe there would have been some conflicts if it hadn't been?

  2. 14 hours ago, Articulated said:

    Now with the new schedule giving 20 minutes at each end, the schedules are consistently timed throughout the day, and operators have enough recovery time to turn the train around and have a necessary break.

    If I'm reading the schedules correctly, it's even more generous, with 35 minutes at either end during half-hourly service, growing to 65 minutes at Oshawa when it's hourly. Another interesting quirk is how one of the evening West Harbour trains turns back east and runs in the same slot it would if it stayed at Aldershot!

    There's also a good number of trains silently cancelled, many being counter-peak ones that can't run because of more frequent peak direction service, but some seem to be reverting from revenue to equipment trips for no apparent reason (the first outbound Barrie and Stouffville trips). The Aldershot to Long Branch express is also gone -- without any intermediate stops at say Oakville or Port Credit it couldn't have been very useful.

    Also three Kitchener trains have the Etobicoke North stop removed, I'm not sure why.

  3. 9 hours ago, TransferCutter said:

    Service changes effective April 27th sign up

    Are the Eglinton changes not happening after all? That'd be sad.

    18 minutes ago, Doppelkupplung said:

    I recall something called the 202 Express...but I never actually saw one. When did that exist?

    2005 to 2011 iirc. 202 was just the old name for the 103 -- the renumbering happened as Brampton introduced Zum on Main, and MT wanted something shiny to show for the occasion.

    • Thanks 1
  4. Installed the app and sniffed packets to find where it gets the data. :‬|

    And yes there's a delay of about a minute compared to what you'd see in the app, since the server checks the feed every 40 seconds at most and the page gets it from there twice a minute.

    • Like 1
  5. 2 hours ago, noahrp24 said:

    I don't know what they are thinking but my morning route 1 schedule doesn't seem to make sense for the next signup. The bus passes by my stop at 7:27am, 7:32am, and 7:36am for this signup but next signup they changed it to 7:24am, 7:34am, and 7:35am.

    The 35 also has a few scheduled bunches since the April 11 signup. It seems that their algorithm for updating runtimes works differently on trippers and interlined trips, always keeping one of the terminal times fixed instead of allowing both to change like on normal runs.

  6. Good news in the long run.

    I'd still like to see at least one train running the reverse direction to get to Kitchener during AM peak.

    These improvements, if the schedule won't be much different than the one in the EA, would actually make two-way peak service a lot harder to run. The current schedule, after the Guelph and Acton sidings are reactivated, would have room for trips from Toronto around 6:10 and Kitchener around 17:40, while the EA schedule wouldn't have any time left for an afternoon peak Kitchener departure.

  7. The Google schedule data is up. A few observations.

    The Dundas redesign was done in an interesting way. In the midday, there is a net increase in service with the new 101, but during the peak there's less trips scheduled (by around 5%) with more local than express trips, while currently the express routes combined are more frequent than the 1. An exception here is westbound in the AM peak where the 20 minute gaps in the express service have been filled. Despite the 201 being converted to blue buses, the 108 is still mostly orange, with only 9 of 22 runs done with blue buses.

    The late night frequency cut on Dundas is practically nonexistent, affecting only the last two headways of the day, however there are a couple of 17-18 minute headways at the shoulders of the midday period.

    The 52 and 55 loops are scheduled with one bus each and timed for transfers to the 51 and 5. The 51 gains two trips in the AM and four trips in the PM, while the 5 loses one trip in the AM and two in the PM. Off peak service sees no changes, apart from a slightly later end of service on the 51.

  8. Two way service with the post-GTS track layout should be perfectly doable, with the compromise that only peak-direction trains would stop at Etobicoke North, so that the other direction can use the same track as the UPX. It looks like 30 minute service would be possible without any meets at Brampton or west of Mount Pleasant, which would keep one track free for CN at all times. The "GO" track from Malton south, with most GO service using the UPX tracks, could also support two-way express service to Kitchener.


  9. That's strange, MiWay's Alerts page lists the road closures for New Year's Eve around Celebration Square. The regular closures apply for events like this: Duke of York from Prince of Wales to Burnhamthorpe, Princess Royal from Living Arts to Duke of York and City Centre from Living Arts to the signalized entrance into Square One (they really should give that road a name, Holts is moving in along that roadway...) all starting at 7PM. Burnhamthorpe between Confederation and Duke of York and Living Arts from Burnhamthorpe to Princess Royal close starting at 11:30PM, probably for the fireworks setup.

    They once experimented with making Rathburn car-free to ensure buses could access the terminal, it was either this or last Canada Day.

    In other news, also on the Alerts page is a notice that the bus-only access to the southbound 427 will be opening on December 16. Initially, the 35/A EGLINTON will be the first route to use the on-ramp. The route and subsequent stops will be changed accordingly based on the notice. Is it just a test run? I'm surprised they didn't have the 109 MEADOWVALE EXPRESS use it as well. It's a week late from all of the other Service Changes. It was scheduled to open for Fall 2013. Technically they've got a week and a half left before Winter officially starts.

    Maybe they didn't mention the 109 because it doesn't stop anywhere between Skymark and the 427. Good news in any case, with Skymark to Islington taking over 25' during the PM rush. It will be interesting to see if they can meet their 34' target for Winston Churchill to Kipling, with the downgrade to mixed traffic on Rathburn and the "priority" signal at Mavis working like it does.

  10. One thing I noticed with the new schedules is that the 108, now officially express, still seems to interline with local routes. Not just the 70 and 201 - quite a lot of trips come off or go onto actual local routes and stay there for hours. Does anyone know how MT will handle this regarding blue/orange buses?

    List of these trips for the curious:


    8:00, off 35

    8:15, off 1

    8:30, off 38/20

    9:00, off 9

    9:15, off 35

    9:30, off 1/201


    3:30, off 10

    4:00, onto 20

    4:30, onto 201/1

    5:20, off 70/20

    5:40, onto 201/26

    6:00, 312->70->76->38->108->201->1

    6:30, off 201/70/20

  11. The schedules are now up on Click-n-Ride. While the 108's AM frequency is indeed 15 minutes (apart from the oddball 5:25am trip), the PM frequency is still mostly 30', with one last 60' headway between 7:00 and 8:00pm.

  12. I'm assuming the Dundas changes are the extra Saturday short turns between Dixie and Hurontario/Confederation. Did we ever figure out where they were looping at either end? They did say it was going to be re-evaluated in the spring when they imlemented it. Nothing was mentioned in the March Service Change, so I had assumed it would have been mentioned in the May Service Change.

    Apart from the short turns, they were also planning to redesign the express routes. The plan was to get rid of the 201 in its current form and introduce midday express service. I don't know what (if any) re-routing they were going to do, but I can't see them going straight to the "express to South Common, local to Ridgeway" design just yet, given the current level of Sunday service and recent weekend service cuts.

    The redesign was supposed to happen as soon as they had enough blue buses, i.e. the 2013 series if going by the winter schedule. But the summer schedule takes away 5 AM/6 PM peak blue buses, and given that there's already 12 spares in the PM peak (16 in the AM), they could easily cover the 201's 5-6 buses in May.

    As for the short turn loops, they use Dundas-Confederation-King-Hurontario in the west and the Summerville Ct cul-de-sac in the east end.

    (Edit: I can't count)

  13. May service changes are up on the ATU1572 site.

    - As usual, the 110 short turns are cancelled for the season and 88 weekend service starts

    - 107 service to Humber College is also suspended and frequencies reduced to 16' AM, 23' midday, 17' PM

    - Timed transfers between the 5 and 23 at Lakeshore/Ogden are back on Sundays (this was cancelled back in July 2011)

    - 22 gets a new Sunday evening round trip

    - Single trip adjustments: GO transfers on 13, 19, 29, 45, 110 and in-system transfers on 7, 16, 20, 24, 109

    - No changes yet to Dundas, maybe they're waiting for the BRT to open?

  14. The bus icons are indeed GO's. All I did was add in the bus requests and prevent it from removing all of the markers with each response. And those little speed/origin/destination boxes.

    The speeds also had me confused for a while. The current map should however distinguish between the two.

  • Create New...