February 2017 draft of Long Branch (Toronto) Urban Design Guidelines document available online

As you may know, the Preserved Stories website has a good number of posts devoted to the most recent draft – published in February 2017 – of the Long Branch Urban Design Guidelines project.

The latter project involves input from a broad range of people, expressing a wide range of viewpoints, developed in an environment where it’s understood that respectful discussion is the name of the game.

With regard to the February 2017 draft (and it’s important to underline that this is just a draft) of the Guidelines, here is a typical post:

Pages 12 & 13 (i.e. the set of pages) of Feb. 7, 2017 Long Branch Guidelines Draft focuses on 3.6 Special Features

My personal views about the Guidelines project is not likely to be of interest to very many people, but by way of highlighting some of the typical issues that are involved with such a project, you may (or may not) be interested in the following post:

Input from Jaan Pill of Preserved Stories regarding Feb. 7, 2017 Long Branch Guidelines Draft

A post that deals with the February2017 meeting of the Advisory Group for this project is entitled:

Advisory Group for Long Branch Urban Design Guidelines had a productive meeting on Feb. 7, 2017

Posts that follow in sequence after the above-noted post include:

Pages 2 & 3 of Guidelines Draft: Exmoor Drive above TTC Loop is now included in Long Branch Guidelines project/a>

Pages 4 & 5 of Feb. 7, 2017 Long Branch Guidelines Draft focuses on 3.2 Height & Massing

Pages 6 & 7 of Feb. 7, 2017 Long Branch Guidelines Draft focuses on 3.3 Building Elements

Pages 8 & 9 of Feb. 7, 2017 Long Branch Guidelines Draft focuses on 3.4 Driveways & Garages

Pages 10 & 11 of Feb. 7, 2017 Long Branch Guidelines Draft focuses on 3.5 Setbacks & Landscape

Pages 12 & 13 (i.e. the set of pages) of Feb. 7, 2017 Long Branch Guidelines Draft focuses on 3.6 Special Features

 

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *