[Andy_in_Toronto]

An update on the University Avenue / Queen's Park cycle track upgrades (east side). I inquired with the city about the construction timeline and they've responded. This section is under the most threat of this populistic provincial government. Therefore, let’s read the following statement carefully:

The short version is: there's no firm start date yet, but they expect to have a timeline in a few weeks and plan to start construction this summer.

All official updates will eventually be posted here, under the "University Avenue Upgrades" section: https://www.toronto.ca/services-pay...ing-infrastructure/cycling-upgrades-renewals/

Frankly, I'm concerned about the vagueness of the response. We've seen important projects suffer from indefinite delays before.

What do you all think? Does "expected this summer" give you confidence, or should we be pushing for a more concrete commitment now? @Northern Light is welcome to add his valuable knowledge and background information.

 

[bearcat]

An update on the University Avenue / Queen's Park cycle track upgrades (east side). I inquired with the city about the construction timeline and they've responded. This section is under the most threat of this populistic provincial government. Therefore, let’s read the following statement carefully:

The short version is: there's no firm start date yet, but they expect to have a timeline in a few weeks and plan to start construction this summer.

All official updates will eventually be posted here, under the "University Avenue Upgrades" section: https://www.toronto.ca/services-pay...ing-infrastructure/cycling-upgrades-renewals/

Frankly, I'm concerned about the vagueness of the response. We've seen important projects suffer from indefinite delays before.

What do you all think? Does "expected this summer" give you confidence, or should we be pushing for a more concrete commitment now? @Northern Light is welcome to add his valuable knowledge and background information.

I would be genuinely surprised if this goes ahead......

 

[Northern Light]

An update on the University Avenue / Queen's Park cycle track upgrades (east side). I inquired with the city about the construction timeline and they've responded. This section is under the most threat of this populistic provincial government. Therefore, let’s read the following statement carefully:

The short version is: there's no firm start date yet, but they expect to have a timeline in a few weeks and plan to start construction this summer.

All official updates will eventually be posted here, under the "University Avenue Upgrades" section: https://www.toronto.ca/services-pay...ing-infrastructure/cycling-upgrades-renewals/

Frankly, I'm concerned about the vagueness of the response. We've seen important projects suffer from indefinite delays before.

What do you all think? Does "expected this summer" give you confidence, or should we be pushing for a more concrete commitment now? @Northern Light is welcome to add his valuable knowledge and background information.

I believe this will come forward this year, for implementation in mid to late summer or fall.

However, the design has been modified vs what we achieved in the SB direction. Having said that, there will still be a cycle track and it will still be materially better than the one we have now. Just not quite as good as it could have been.

I would be genuinely surprised if this goes ahead......

I am hopeful that you will be surprised.

 

[Cambry Ardship]

Over the past couple days I've biked on both sides of Eglinton from Mount Dennis to Leslie, 12 km each way. I used the road lanes in all cases where bike lanes weren't available.

My takeaways:

• The biking conditions are currently very poor and felt extremely dangerous in much of the way. The cars were the most unpleasant bit. The worst sections, subjectively, were westbound between Bathurst and the Allen, both ways between Caledonia and Keele, and both ways between Mount Pleasant and Bayview.
• Even the separated bike lane section was shorter than I thought it would be. I found myself thankful for even the brief Metrolinx bike lane stubs that often emptied suddenly right into traffic.
• The centre section around Yonge with the separated bike lanes had by far the most people biking (and had the best, most consistent infrastructure). Other than that section, I encountered very other few people biking.
• It will be a fantastic bike route if separated bike lanes are built throughout, but it is currently too disjointed and inconsistent to recommend as a route other than for people living just west of Yonge.

I worry that the city has made a terrible mistake by pushing back the construction of Eglinton TOday so long.

 

[TwoWheelPoli]

Over the past couple days I've biked on both sides of Eglinton from Mount Dennis to Leslie, 12 km each way. I used the road lanes in all cases where bike lanes weren't available.

My takeaways:

• The biking conditions are currently very poor and felt extremely dangerous in much of the way. The cars were the most unpleasant bit. The worst sections, subjectively, were westbound between Bathurst and the Allen, both ways between Caledonia and Keele, and both ways between Mount Pleasant and Bayview.
• Even the separated bike lane section was shorter than I thought it would be. I found myself thankful for even the brief Metrolinx bike lane stubs that often emptied suddenly right into traffic.
• The centre section around Yonge with the separated bike lanes had by far the most people biking (and had the best, most consistent infrastructure). Other than that section, I encountered very other few people biking.
• It will be a fantastic bike route if separated bike lanes are built throughout, but it is currently too disjointed and inconsistent to recommend as a route other than for people living just west of Yonge.

I worry that the city has made a terrible mistake by pushing back the construction of Eglinton TOday so long.

It gets even worse. The stretches of Eglinton from Allen to Bathurst and east of Caledonia won't be done this year. The former due to additional congestion mitigation measures needed and the latter due to storm sewer work per the slide below.

https://www.toronto.ca/wp-content/uploads/2025/05/8f32-egltinon-allen-public-meeting-slides-may13.pdf

 

[ThenWhat]

It gets even worse. The stretches of Eglinton from Allen to Bathurst and east of Caledonia won't be done this year. The former due to additional congestion mitigation measures needed and the latter due to storm sewer work per the slide below.

https://www.toronto.ca/wp-content/uploads/2025/05/8f32-egltinon-allen-public-meeting-slides-may13.pdf

View attachment 657356

At least for those two sections there is a detour by the Beltline trail. Which brings us back to the problem of gaps in the latter. Even with gaps, going by the trail is more pleasant, safer and better for our health than the road.

 

[Cambry Ardship]

Sure, but detouring on the Beltline from Caledonia to Chaplin adds about 600 extra metres. That's not nothing. I agree, it's a much more pleasant and safe bike ride currently, but it also means in terms of local cycling missing all the stores and restaurants on Eglinton.

The point of Eglinton TOday is that it's supposed to be safe to bike on Eglinton. The city's years and years of delays on actually building that safe, separated infrastructure is a horrible miss. The little Metrolinx stubs have been in place for years now, and the general plan has been in place for decades. It's horribly offensive that they're continuing to delay due to car traffic, like that's something that just popped up for the first time a few months ago.

I know this isn't new to anyone, but I have to rant a little bit. It was a very dispiriting trip across Eglinton.

 

[Admiral Beez]

I really dislike them in the bike lanes but I can't see this ever being enforced -- and with car drivers constantly stopping/parking in the bike lanes or up on sidewalks because they can, nearly always with impunity -- I can't see a world where an Ebike-but-no-the-bad-kind stop being in bike lanes...

Seven years ago I rented a bicycle in Amsterdam and I was surprised that the usually sensible Dutch allowed full-on Vespas onto their bike paths. See below.

I am glad to see that the government finally banned scooters from the bike lanes in 2019, shortly after my visit there.

Amsterdam is banning scooters from the cycle paths from 2019 | DutchReview

It has been officially decided that the city of Amsterdam is banning scooters from the cycle paths. This plan has been in the making since 2017, but it seems like it's finally going to be implemented starting 2019. The problem with scooters on the cycle paths As Amsterdam continues flooding…

dutchreview.com

But I believe they still allow motorized bikes onto the paths, provided the motor is powered by a battery rather than gasoline. That's not far enough, IMO, and only pedal assist bikes should be allowed to join regular manual bikes.

 

[TwoWheelPoli]

Another public consultation is happening next Monday (6:30 to 8:00 PM) at 816 Logan Avenue (Frankland Community Centre) for the Leaside-Danforth Cycling Connections. Instead of just Logan, the City is revising the bikeway designs to include contraflows on both Logan and Carlaw. Apparently, there were some concerns regarding the traffic diverters with the original design.

Leaside Bridge to Danforth Avenue Cycling Connections

The City of Toronto is proposing a new bikeway - Leaside to Danforth cycling connections.

www.toronto.ca

 

[robmausser]

Sure, but detouring on the Beltline from Caledonia to Chaplin adds about 600 extra metres. That's not nothing. I agree, it's a much more pleasant and safe bike ride currently, but it also means in terms of local cycling missing all the stores and restaurants on Eglinton.

View attachment 657421

The point of Eglinton TOday is that it's supposed to be safe to bike on Eglinton. The city's years and years of delays on actually building that safe, separated infrastructure is a horrible miss. The little Metrolinx stubs have been in place for years now, and the general plan has been in place for decades. It's horribly offensive that they're continuing to delay due to car traffic, like that's something that just popped up for the first time a few months ago.

I know this isn't new to anyone, but I have to rant a little bit. It was a very dispiriting trip across Eglinton.

I agree, but it still nice to have a "bike highway" of sorts to zip across unobstructed.

I really think its due time to pave the Eastern section of the Beltline. I understand that its nice and naturey that its gravel, but many sections constantly get washed out and present a danger to cyclists and pedestrians. Plus its getting so busy a separated walking/bike division painted lines would be very welcome (not that any pedestrian would follow them....but I digress)

I also wish they would put bollard lighting along the whole thing. I understand that the houses backing the beltline didnt want lighting, but low to the ground bollard lights directed just at the ground would not cause any or very little light pollution and mean the beltline could be used later.

 

[Cambry Ardship]

I agree that they should pave the Beltline. There's a few spots (particularly just east of Bathurst) that are badly rutted out with unpacked loose gravel. The lighting question I'm more agnostic about but I feel that both follow the question of 'who exactly is the Beltline for?' There's a tension between supporting the local/non-local recreational constituency vs the commuter groups, who use it as a means to move quickly south-east or north-west across the city. I think there's basically four areas of density, marked in blue, that are a realistic target market, or whatever you want to call it, for using the Beltline as a transportation corridor.

Dufferin, Bathurst, Avenue, and Yonge all can feed cyclists in from the north in to get people southbound very quickly, assisted by downhill geography. And there's a lot of planned density along the Beltline (I'm thinking especially about the planned neighbourhood on the Canada Goose site by Caledonia) that could feed into it. But once you get much east of

People do use it to commute (and should!) but it feels like an non-approved use because particularly because of the unrealistically slow bike speed limit (15 kph). As you mention, there's the issue of lack of lighting and poor maintenance, but beyond that there's a lack of signage to the rest of the road and bike network, the connections between the Beltline and Bayview is currently poor and disjointed, and the major road crossings range from adequate to frankly unsafe.

If the city wants a bike highway into downtown, this is probably a cheap and reasonable place to start that avoids issues with repurposing car lanes, but it feels like something that the city is conceptually uncomfortable with.

 

[duffo]

I agree that they should pave the Beltline. There's a few spots (particularly just east of Bathurst) that are badly rutted out with unpacked loose gravel. The lighting question I'm more agnostic about but I feel that both follow the question of 'who exactly is the Beltline for?' There's a tension between supporting the local/non-local recreational constituency vs the commuter groups, who use it as a means to move quickly south-east or north-west across the city. I think there's basically four areas of density, marked in blue, that are a realistic target market, or whatever you want to call it, for using the Beltline as a transportation corridor.

View attachment 657515

Dufferin, Bathurst, Avenue, and Yonge all can feed cyclists in from the north in to get people southbound very quickly, assisted by downhill geography. And there's a lot of planned density along the Beltline (I'm thinking especially about the planned neighbourhood on the Canada Goose site by Caledonia) that could feed into it. But once you get much east of

People do use it to commute (and should!) but it feels like an non-approved use because particularly because of the unrealistically slow bike speed limit (15 kph). As you mention, there's the issue of lack of lighting and poor maintenance, but beyond that there's a lack of signage to the rest of the road and bike network, the connections between the Beltline and Bayview is currently poor and disjointed, and the major road crossings range from adequate to frankly unsafe.

If the city wants a bike highway into downtown, this is probably a cheap and reasonable place to start that avoids issues with repurposing car lanes, but it feels like something that the city is conceptually uncomfortable with.

There's also the Marlee-Winona-Shaw route which is a major fairly continuous N-S corridor for me that connects to the Beltline. Unfortunate to see the Marlee upgrades get canned.

 

[robmausser]

I agree that they should pave the Beltline. There's a few spots (particularly just east of Bathurst) that are badly rutted out with unpacked loose gravel. The lighting question I'm more agnostic about but I feel that both follow the question of 'who exactly is the Beltline for?' There's a tension between supporting the local/non-local recreational constituency vs the commuter groups, who use it as a means to move quickly south-east or north-west across the city. I think there's basically four areas of density, marked in blue, that are a realistic target market, or whatever you want to call it, for using the Beltline as a transportation corridor.

View attachment 657515

Dufferin, Bathurst, Avenue, and Yonge all can feed cyclists in from the north in to get people southbound very quickly, assisted by downhill geography. And there's a lot of planned density along the Beltline (I'm thinking especially about the planned neighbourhood on the Canada Goose site by Caledonia) that could feed into it. But once you get much east of

People do use it to commute (and should!) but it feels like an non-approved use because particularly because of the unrealistically slow bike speed limit (15 kph). As you mention, there's the issue of lack of lighting and poor maintenance, but beyond that there's a lack of signage to the rest of the road and bike network, the connections between the Beltline and Bayview is currently poor and disjointed, and the major road crossings range from adequate to frankly unsafe.

If the city wants a bike highway into downtown, this is probably a cheap and reasonable place to start that avoids issues with repurposing car lanes, but it feels like something that the city is conceptually uncomfortable with.

The west end could become even more useful if they extend the planned Davenport Diamond path up to connect with the terminus of the Beltline at Caledonia station.

You'd essentially be recreating the Beltline railway loop with a bikeway.

 

[UntitledCyclist]

Sure, but detouring on the Beltline from Caledonia to Chaplin adds about 600 extra metres. That's not nothing. I agree, it's a much more pleasant and safe bike ride currently, but it also means in terms of local cycling missing all the stores and restaurants on Eglinton.

View attachment 657421

The point of Eglinton TOday is that it's supposed to be safe to bike on Eglinton. The city's years and years of delays on actually building that safe, separated infrastructure is a horrible miss. The little Metrolinx stubs have been in place for years now, and the general plan has been in place for decades. It's horribly offensive that they're continuing to delay due to car traffic, like that's something that just popped up for the first time a few months ago.

I know this isn't new to anyone, but I have to rant a little bit. It was a very dispiriting trip across Eglinton.

Yes, and this red line is very generous, as it skips over the disjointed gap between the York and Gardiner trails around Marlee, where you have to awkwardly dogleg up Marlee to Roselawn and take the road for a 100 m or so to get back on the trail.

I'm totally unsurprised Matlow and Colle and local NIMBYs have blocked the EglintonTOday stretch west of Bathurst. This trend has been building around the city, and Eglinton was a ripe spot for pushback. They seem to be channelling the rage I see and hear on the daily (I live nearby) with drivers gunning overpowered cars and trucks to and from the Allen, or shouting and honking at anyone and everyone.

Despite all this, I really disagree with paving the Beltline, as much as it might help cyclists. It's a rare gem of unpaved path, wonderful for kids and families to walk and explore and for pets and other creatures as well. The loose gravel east of Bathurst can be dealt with without paving the trail.

Despite the challenges posed by Ford's bikelane bill, and the general trend to block and backtrack from bike plans, I don't think we should give up on the sensible and logical plan to offer bikeways on arterials like Eglinton. What we shouldn't want as cyclists is to be relegated to corridors or MUPs that don't take us to or past 99% of the businesses and destinations we need.

 

[UntitledCyclist]

It gets even worse. The stretches of Eglinton from Allen to Bathurst and east of Caledonia won't be done this year. The former due to additional congestion mitigation measures needed and the latter due to storm sewer work per the slide below.

https://www.toronto.ca/wp-content/uploads/2025/05/8f32-egltinon-allen-public-meeting-slides-may13.pdf

View attachment 657356

It's a small thing but it bothers me that the city's graphic here shows various "recommended cycling streets" with zero actual infrastructure as part of the solid lined "existing cycling network." This includes Old Park, which runs north of Eglinton in Upper Village, and Elm Ridge, which runs E-W just above the Belt Line. Those streets are often congested with impatient SUVs trying to get to Eglinton or the Allen, and there is nowhere safe for a cyclist to ride. Even Lascelles just west of Yonge, while a fine quiet street to ride on and part of the city's now defunct numbered cycling routes, has no bike lanes.

It all feels like puffing up the very poor and disjointed network. It's misleading and outdated, at best. Those streets are useful suggestions given the lack of real cycling infra, but they aren't a cycling network.