Nay Development 24A | 24m | 6s | Nay Developments | CTZN

Ahh yes, that is actually a key distinction in this case. Killarney is not the Beltline. Hope this helps!
Beltline also has delivery trucks, garbage collection and emergency access with narrow laneways, and significantly higher density than this area. What about this development specifically causes issues with those services?
 
Last edited:
Not the Beltline, but a very inner city community where we need to intensify and start pushing for more midrise development, especially along major throughfares like 17th. Developments like this also should constrain vehicle access, there's not a lot of room for more cars on the roads, so people need alternatives. Transit is an option, cycling, car pooling anything other than the endless single occupant vehicles that drive past this development every day. I live a similar distance from downtown and I cycle every day, far superior to driving about 90% of the time.
 
There's a choice, larger roads that will need to take over private property to accommodate more cars, or more investment in transit to try and delay or replace the needs for larger roads.

I prefer the latter to the former. Some places we don't really have a choice (Crowchild north of memorial) but most places we do.

What cannot be missed in the "war on cars" debate is that the city is growing and will continue to grow, the consequences for the type of growth we choose need to be understood. The cars or nothing crowd seem to miss the consequences of more cars (mostly because it isn't their home that's going to be expropriated to expand the roads).

Macleod cannot get bigger without expropriating properties; Crowchild cannot get bigger without expropriating properties; Bow Trail cannot get bigger without expropriating properties; Memorial cannot get bigger without expropriating properties, and Deerfoot cannot get bigger beyond undertaking a rebuild of every interchange from Peigan to 64th.

That's the choice, you do those things or you create more dense communities and invest in transit. Answer seems pretty obvious to me.
 
Fully agree with your point. I just feel like pointing out that, ironically, 17th Avenue SW has a 5.182m public realm setback on it, so this project will need to be pushed back from the current property line by 5.182m, to widen the ROW for 17th Avenue. You can see this in the DP drawings. I am being a bit tongue in cheek though, the City has at least started allowing these setbacks to be used for widened sidewalks, street furniture, trees, etc... But, this setback table has existed in the land use bylaw for decades, and for the longest time was meant to preserve land to allow for road widenings as you described.

I guess that is not really ironic, I just felt like pointing out this technical requirement on this project, as it relates to the above post.
 
Site is being cleared, looked like all houses demolished.
1000007276.jpg
 
Fully agree with your point. I just feel like pointing out that, ironically, 17th Avenue SW has a 5.182m public realm setback on it, so this project will need to be pushed back from the current property line by 5.182m, to widen the ROW for 17th Avenue. You can see this in the DP drawings. I am being a bit tongue in cheek though, the City has at least started allowing these setbacks to be used for widened sidewalks, street furniture, trees, etc... But, this setback table has existed in the land use bylaw for decades, and for the longest time was meant to preserve land to allow for road widenings as you described.

I guess that is not really ironic, I just felt like pointing out this technical requirement on this project, as it relates to the above post.
That setback table in the land use bylaw used on 17th Avenue and other places in the bylaw is pretty wild artifact in that it's just there by itself . As you said, these setbacks were for road widening originally but that's not really a thing that seems to be captured anywhere in official reports, strategy or policy. I actually wonder how old those setbacks are?

Without any documentation all that remains is the setback rules themselves. The start of the story is something like 1960s-era engineers and planners got together and said all these corridors are too narrow given future car transportation forecasts that showed infinite volume growth everywhere on all corridors. At the time - just like today - can't just afford to widen 17th Avenue to it's ultimate "final design" right now. So the strategy became to slowly get the corridors ready by using the land use regulations to require a setback on land development so that one day all the land is set aside for their future project once all parcels redevelop.

The benefit to this approach is that it's "painless" - don't need to argue with the community and get into big, messy road expansion battles, all the city has to do is wait for all the lands to turn over naturally, apply the setback rules and then expand the road. It appears cheap too - no costly expropriation, the city will just get the land one day.

However, the problem with this approach should have been immediately obvious - this will take a couple hundred years to accumulate all the land this way. Land parcels are redeveloped at the random whims of land owners, many go their whole lifetimes without ever thinking about redevelopment. It should have been pretty obvious even at that time that this parcel-by-parcel approach won't achieve the stated needs (more land for a road widening to match a travel demand projection), yet they went ahead and implemented the setback anyways.

Fast forward 60+ years, and the result is this: some parcels have turned over, some not. Land use decisions have drifted as interpretation of the setbacks shifted over the years the result is a jagged block pattern with total inconsistency on how to use this setback space but also how to orientate buildings. Developments all choose different paths to use that space that's dedicated to the setback based on the whims of the transportation department and the individual application at the time - sometimes it's a patio space, sometimes a wide sidewalk, sometimes a parking bay. The setback creates inconsistent walking environment for a goal that doesn't even exist.

1772817018221.png

Compare that to a city like Toronto where they never tried the same approach. Notice the consistent parcel boundaries:

1772819343764.png


At no point in our lifetimes - let alone the lifetimes of the planners who can up with this strategy as they are likely all dead by now - will the setback be fully implemented so that dreamed about widening can occur. That widening isn't even contemplated anymore and I don't think has been contemplated in any official way for a few decades. The city's own public transportation modelling assumes 17th Avenue will remain 4 lanes out to 2076.

I am sure in the rooms where developments argue about this stuff today, there's still lots of arguments to keep using the setbacks in the same spirit of future-proofing - "sure we don't want to do widening now, but who knows in 100 years? That's valuable corridor space we could need for any number of reasons." This is why the setbacks haven't gone away even if the reason they were put in at the beginning has long been forgotten.

Future-proofing like this seems prudent and strategic but it has a real downside: inconsistent public realm, more complicated and negotiated developments, risk of some sites becoming less developable etc. It isn't free - these setbacks have real impacts that prevent the street from evolving consistently and becoming more productive. 17th Avenue's hodgepodge of development and weak walkability in this area is a direct byproduct.

By sticking with the setbacks even though the reason we started them no longer exists, we've let the rule become it's own justification. The references have became circular - in effect, the point of the setback rules on main streets is so we can satisfy the needs of the setback rules. We shouldn't have these types of rules unless they are tied to a clear vision, project or strategy of what we want to achieve by enforcing the rule.
 
I have first hand involvement in this table. Your assessment is frightenlingly accurate. I will also add that one some of the corridors we have undertaken "ultimate" designs withour Main STreets program (including 17th Ave SW where this project resides). However, when the Mainstreets team is pushed into whether we still need the setback or not, or if their project considered incorporating it, the repsonse is "outside of our scope". Can we get rid of it then? "no, it could be useful in the future". The reason it was outside of the scope is I have been told it would be too complicated / costly to deal with it. Just because a building is setback doesn't mean the land is dedicated as ROW.

So you are right, huge flaws, we will never see it achieve what the initial intent was (whether for road widening or public realm improvements, The City just won't get the land ever without dedicated funding/expropriation). There are a handful of corridors where we have utlized it, 16th Ave NW for instnace with the widening project 20 years ago.

The lack of desire to resolve this table is so frustrating.
 

Back
Top