My WebLink
|
Help
|
About
|
Sign Out
04
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2012
>
042312 Special Meeting
>
04
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/20/2012 2:41:24 PM
Creation date
4/20/2012 2:41:18 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
4/23/2012
DESTRUCT DATE
15Y
DOCUMENT NO
04
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
28
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
• Compliance with RHNA -- Any growth control measure must be drafted to meet RHNA within the <br /> established Housing Element plan period. <br /> • Infrastructure Constraints -- The City is responsible for taking actions to eliminate constraints. As <br /> an example, if lack of sewer capacity is a constraint, the City would be required to address the <br /> constraint through a financing mechanism, capital upgrade and/or other solution. Regarding traffic <br /> impacts, they would have to be addressed through the development review process. <br /> • School Impacts -- State law establishes a statutory school impact fee to mitigate the impacts of <br /> development. However, nothing limits a school district from exploring other financing measures <br /> through cooperative agreements with developers such as gift fee agreements, school-site <br /> construction, and/or other solutions. <br /> • Residential and Commercial Constraints -- There is a link between constraining housing and <br /> commercial development. That is if residential growth is constrained, commercial growth would also <br /> need to be constrained. <br /> As part of the City's typical residential development review process, matters related to the above <br /> referenced constraints, such as water availability, sewer, traffic, etc., are evaluated and if necessary, <br /> conditions to offset the impacts of the development are included in the conditions of approval. <br /> Notwithstanding this process, an amended growth management program could require the City to assess <br /> these constraints in further detail to assist in determining the timing of construction. <br /> In conclusion, an amended growth management program would most likely continue to take place <br /> following the development review process. Notwithstanding this process, an amended growth <br /> management program could also consider constraints and impacts related to the rate of construction for <br /> approved residential development projects, provided the process does not conflict with RHNA and state <br /> law. <br /> SUGGESTED OBJECTIVES FOR AN AMENDED GROWTH MANAGEMENT PROGRAM <br /> Based on the above parameters, the following objectives should be incorporated into an amended growth <br /> management program: <br /> • Retain the current development review process and continue to incorporate public review and <br /> comment. <br /> • Use the growth management program to determine a process for regulating the pace of residential <br /> unit construction consistent with State law and regulation. One method would be to establish an <br /> annual allocation consistent with the RHNA planning period. As an example, assuming a RHNA of <br /> 3,200 units over the seven year RI-INA period, there would be a 457 annual unit allocation (3,200 <br /> RHNA units divided by 7 years °457). Another option would be to link the annual unit allocation to <br /> population growth such that the RHNA represent a percentage of the City's population. <br /> • Develop a comprehensive program that addresses infrastructure constraints in compliance with State <br /> law and regulations. This can be accomplished through the development of a comprehensive growth <br /> management report updated biannually. <br /> Page 4 of 5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.