Welcome Guest!
In order to take advantage of all the great features that Waterloo Region Connected has to offer, including participating in the lively discussions below, you're going to have to register. The good news is that it'll take less than a minute and you can get started enjoying Waterloo Region's best online community right away.
or Create an Account




Thread Rating:
  • 15 Vote(s) - 3.93 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ION - Waterloo Region's Light Rail Transit
(10-17-2016, 12:03 PM)Spokes Wrote: Is that because green lights could cause the trains to get there early and thus get off the schedule?

Yes; exactly!

(10-17-2016, 12:34 PM)Markster Wrote: More like, aggressive signal priority would cause more impact to the perpendicular vehicular traffic than they want.

Smile  Imagine a busy intersection like Erb/Caroline, halting traffic for up to 1 minute in all directions every 3.25 minutes.  That would be a bit of a disaster...
Reply


Apparently the platform issue was caught by GrandLinq's quality assurance program. Let's hope that the program has been able to catch any other issues that have been overlooked.

As for the LRVs keeping their schedule and whether they have signal priority, I can imagine that since we aren't going to have five minute LRV headways that a critical part of the network interconnections will be that every vehicle arrives where it should when it should plus/minus a few minutes. For instance, someone arriving at the station either on a connecting bus or to catch a connecting bus (which might operate say with 15 or even 30 minute frequency) won't appreciate if they arrive only to discover that their connection has already left (in the case of a faster than expected LRV) or that it will a longer wait (also in the case where the LRV arrives before it is planned to arrive).
Reply
The buses will have a more variable arrival time than LRVs, so simultaneous transfers are unlikely. More likely would be a situation where, with 10 minute headways, a bus would be targeted to arrive halfway between two LRVs. That way, if you are trying to go from LRV to bus, you should have 5 minutes of waiting, and if you are trying to do the reverse, going from the bus to an LRV, you should have 5 minutes of waiting. If the bus is ahead or behind schedule, one of those waits becomes shorter, the other longer.

I would think they really should try using the burn-in to confirm/deny the predicted travel times. Do runs with no priority at all, runs with priority only activated for trains running X minutes behind schedule, and priority at every single crossing, and see what kind of travel time you can get. It will be the easiest way to get models for this timing, without having to deal with extra costs/interferences.
Reply
(10-17-2016, 09:34 AM)Canard Wrote: Woo-hoo!

<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Production of roof modules for <a href="https://twitter.com/Metrolinx">@Metrolinx</a> <a href="https://twitter.com/yegvalleyLRT">@yegvalleyLRT</a> and <a href="https://twitter.com/rideIONrt">@rideIONrt</a> LRV projects now underway, as scheduled, in our Kingston site. <a href="https://t.co/CE9nt1zOA7">pic.twitter.com/CE9nt1zOA7</a></p>&mdash; BombardierRail (@BombardierRail) <a href="https://twitter.com/BombardierRail/status/788005412381548545">October 17, 2016</a></blockquote>

That is a little bit revisionist. I think they actually meant, "as per our the revised, twice delayed, schedule."
Everyone move to the back of the bus and we all get home faster.
Reply
(10-17-2016, 10:53 AM)Markster Wrote: And the baseline schedule in the project agreement is not exactly pushing any speed records.  It's got about the same end-to-end time that the iXpress initially launched with. Considering that this now cuts off the King/University corner, has a dedicated lane, and several intersections have been removed from both King and Charles Streets, it's safe to say that it should make the trip in time without any signal priority at all.

Interesting to note that the last schedules for 200 before the detours had its Conestoga-Fairway times at 60 minutes during rush hour, which is substantially slower than the rest of the day.

Much of that delay was built into the Waterloo portion of the route, so much so that a 7C from Conestoga can beat the 200 to uptown by 6-7 minutes despite making frequent stops in traffic during rush hour. I'm expecting great things from ION in this leg. With the rail spur and the cut through the park, I foresee this gap disappearing unless the 7C has light off-rush-hour traffic and few stops.
Reply
   
   
   
Everyone move to the back of the bus and we all get home faster.
Reply
I think they forgot to put an accessible ramp at the end of the GRH platform:
   

I think the forgot to put an accessible ramp across the street from the Willis way platform. See the ramps don't align on both sides of the street at the north end on the platform:
   

Like they do on the south end of the platform:
   
Everyone move to the back of the bus and we all get home faster.
Reply


Do the crossings have bells as well or just lights? I can see that getting old really fast for nearby residents.
Reply
In the second and third pic's from Uptown King it seems like there is a very wide swaft for the Northbound track. Is this all for sidewalk or Northbound traffic and sidewalk or am I missing something totally. Tried to find the saved PDF for the plans but can't find this portion
Reply
(10-17-2016, 11:11 PM)white_brian Wrote: In the second and third pic's from Uptown King it seems like there is a very wide swaft for the Northbound track. Is this all for sidewalk or Northbound traffic and sidewalk or am I missing something totally. Tried to find the saved PDF for the plans but can't find this portion

I suspect that will be the utility/bench/trashcan/bike rack/street tree space next to the sidewalk.
Reply
LRT cuts off low-income neighbourhood’s access to shops
Reply
I really like the majority of the local LRT reporting it's good for a laugh.
You read the title and and the first few paragraphs and it sounds like trails were ripped up etc. Then the article stumbles to the heart of the matter, the land surrounding the track is all private property and the need for a crossing wasn't identified during the consultation phase as previously discussed. In fact if a crossing is put in place ( which I think should be done) it will be the first crossings for these residents that was technically not trespassing. Don't get me wrong I definitely understand the need for a crossing and the inconvenience this would cause for the local population.

Ideally the titled should read 'More input from the public requested for future infrastructure projects'.
Reply
@rangersfan. This is exactly right. My position on this is the real problem is that pedestrian access was never designed into that neighbourhood and it is only by coincidence that it kind of worked before. Many other neighbourhoods In the city have this problem already.
Reply


(10-17-2016, 11:13 AM)ijmorlan Wrote:
(10-17-2016, 11:04 AM)Canard Wrote: For what it's worth, I've always wanted full-priority, but it was pointed out to me early on that accuracy in arriving at a scheduled time at a station is more important than just blasting end-to-end as fast as possible. Which, as a train guy first and foremost, is what I wanted. Big Grin But I see the logic in keeping an integrated schedule, especially when it ties in with Bus.

It should get full priority, and the schedule should be planned to use the priority, with a reasonable buffer so that minor problems don’t immediately put the schedule off for the rest of the day. But yes, there should be a schedule and no transit vehicle should ever run “hot” (meaning, leaving a pickup point before the scheduled time).

What I would say is that the schedule should be as fast as possible, subject to being realistic in the face of reasonably foreseeable and reasonably common circumstances.

A early bus/train is no bus/train.
Reply
(10-18-2016, 08:28 AM)kitborn Wrote:
(10-17-2016, 11:13 AM)ijmorlan Wrote: It should get full priority, and the schedule should be planned to use the priority, with a reasonable buffer so that minor problems don’t immediately put the schedule off for the rest of the day. But yes, there should be a schedule and no transit vehicle should ever run “hot” (meaning, leaving a pickup point before the scheduled time).

What I would say is that the schedule should be as fast as possible, subject to being realistic in the face of reasonably foreseeable and reasonably common circumstances.

A early bus/train is no bus/train.

Incidentally, this is why GRT's service standard is asymmetrical: to be within -1 and +3 minutes of schedule. You could take the position that there's no excuse for being even 1 minute early, though I would see that as impractical given the amount of attention this would require from drivers at every stop.

(I've heard complaints over the years about a GRT bus running through stops early, and every time I encourage those people to talk to GRT customer service. While it's possible to be a handful of seconds early with the best of intentions, virtually every driver I've seen makes allowances for people who are almost at the stop. To be more than a minute early is to ignore the schedule, and GRT management will talk to drivers who do that.)
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 32 Guest(s)

About Waterloo Region Connected

Launched in August 2014, Waterloo Region Connected is an online community that brings together all the things that make Waterloo Region great. Waterloo Region Connected provides user-driven content fueled by a lively discussion forum covering topics like urban development, transportation projects, heritage issues, businesses and other issues of interest to those in Kitchener, Waterloo, Cambridge and the four Townships - North Dumfries, Wellesley, Wilmot, and Woolwich.

              User Links