My WebLink
|
Help
|
About
|
Sign Out
13
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2012
>
101612
>
13
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/12/2012 2:30:25 PM
Creation date
10/12/2012 2:30:17 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
10/16/2012
DESTRUCT DATE
15Y
DOCUMENT NO
13
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
40
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).
View images
View plain text
Finally, as discussed with the City Council previously, due to the fact that the City was <br /> engaged in litigation and the update to the Housing element, it did not make <br /> adjustments to the existing 350 unit allocation number. As a result, from the this time <br /> until July 2014, the City Council will issue growth management allocations to the degree <br /> that the City meets its RHNA obligation and as such the following language has been <br /> added to Section 17.30.060: <br /> "For the Fifth Regional Housing Needs Allocation cycle that ends July 2014, the annual unit <br /> allocation shall be equal to the number of units required to meet the City's Regional Housing <br /> Needs Allocation for the Fifth cycle." <br /> Language regarding the new unit allocation process is included in Section 17.36.060 (A) <br /> and (B) <br /> Amendment to Suballocations <br /> Assuming the annual unit allocation number is amended, there is an issue with the <br /> suballocations since these are also "hard" numbers that relate directly to the 350 annual <br /> allocation, i.e., the total of the suballocations equal 350 units. As a result, the <br /> Subcommittee looked at a number of options to correct this situation including retaining <br /> the current ratio of suballocations and applying it to the new annual unit allocation <br /> number, developing a new set of ratios that are more aligned with RHNA and/or <br /> anticipated new residential growth, developing new suballocation categories or <br /> eliminating the suballocation. Ultimately, the Subcommittee and staff concurred that the <br /> suballocations create a degree of complexity to the ordinance that make it cumbersome <br /> to administer, that they may not be reflective of the type of residential development that <br /> will occur in the future and that create an impression of the types of development that <br /> may or may not occur in the future. As a result, the Subcommittee and staff are <br /> recommending that the subcategories be eliminated in favor of a single annual <br /> allocation number linked to each RHNA cycle. <br /> It should be noted that while reference to suballocations have been deleted from the <br /> recommended ordinance, it has been drafted to retain the basic provisions related to <br /> growth management approval, processes, transfers, uses, etc. and as such these <br /> provisions remain relatively the same. Attachment C includes a redline version of the <br /> existing GMO ordinance. <br /> Notwithstanding the removal of reference to suballocations, the Subcommittee <br /> anticipates that further continued review of the GMO in the upcoming year will focus on <br /> identifying a mechanism for allocating units in the event the number of applications <br /> potentially exceeds the number of available unit allocations. While the actual <br /> methodology for this has yet to be determined, it may include adoption of a point system <br /> that takes into account infrastructure improvements, development design quality, <br /> amenities, impacts, green building, etc. that would be considered by the City Council as <br /> part of its decision making process when considering development projects for growth <br /> management allocations. As such, the current recommended amendments may be <br /> viewed as interim steps in anticipation of a continued review to address these broader <br /> issues. <br /> Page 4 of 5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.