My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2008-04-07 Regular Council Session Agenda
Public Access
>
City Council Agenda
>
2008
>
2008-04-07 Regular Council Session Agenda
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/4/2008 10:22:02 AM
Creation date
4/4/2008 10:20:11 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
68
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Text Amendment Proposed for “PD” – Planned Development District: <br />Increased and varied density housing is permitted for new major developments under the “PD-R” <br />– Planned Development Residential and “PD-M” – Planned Development Mixed Use Districts. <br />Both of those districts are supposed to only be used in areas where there is over 2 acres to be <br />developed and would assume that the new districts would be for new subdivisions. Although in <br />most cases Staff proposes that those area restrictions remain in order to protect the current <br />residential character of existing subdivisions but there is also flexibility in the code to allow for <br />smaller developments, if necessary and appropriate. It is Staff’s recommendation that the <br />smaller developments not encompass just one lot, in order to retain the characteristics of <br />surrounding areas. <br />The use of the Planned Development Districts in these areas should be considered the key <br />tool for increased and varied density housing in University City. This would allow <br />higher density lots with multi-family dwellings to be allowed throughout several more <br />areas in University City, either by combining lots or using lots that are larger in area than <br />the surrounding lots. However, there is an obstacle in the current code that must be <br />addressed. The current code only permits density in the same amount in the new district <br />than it had in the underlying original district. It does allow for an increase but only in <br />amounts that go up to 20% which is insufficient if the City is serious about increasing <br />density. <br />In other words, if a Planned Development District is created over a single family <br />residential district, it will only be allowed one dwelling unit per original lot. There is no <br />point in rezoning a property to “PD” (except maybe to shift placement of buildings on <br />those lots). That would not increase density as is the goal. The increase in density is <br />only permitted to be up to 20% in section (3)(c) which does not help much in the pursuit <br />of increased density. Staff finds this restriction to be far too restrictive and counter-active <br />to the whole concept of Planned Developments and increasing density in areas that have <br />been designated as such. Staff suggests that the portion limiting density to the original <br />district be deleted altogether. <br />That restriction eliminates all possibilities of varied and increased density if it occurs where an <br />existing “SR” district is located. Further, it gives no benefit or increase in density for multi- <br />family residential districts. This is especially restrictive in the areas north of Olive in the <br />northeast neighborhood where such density is being discussed. It basically means that any <br />existing areas that are rezoned from “SR” to “PD” cannot have a greater density than the <br />previously zoned area. Staff doesn’t see the point of that restriction. Since the property would <br />have been studied during the rezoning process to have been ripe for increased density, it makes <br />no sense. <br />Staff proposes the following change to the text of the “PD” District density regulations (with <br />bolded <br />additions and deletions stricken): <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.