My WebLink
|
Help
|
About
|
Sign Out
20
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2008
>
052008
>
20
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/15/2008 3:14:09 PM
Creation date
5/15/2008 3:14:08 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
STAFF REPORTS
DOCUMENT DATE
5/20/2008
DESTRUCT DATE
15 Y
DOCUMENT NO
20
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
9
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
Should Floor Area Ratio be adjusted for highly sloped sites? Review of <br />recent hillside projects has indicated a concern regarding the size of homes on <br />visible hillsides. The argument has been made that a home on a flat one acre site <br />is less visually prominent than the same size home on a highly sloped site of the <br />same size. Therefore, when floor area ratios (FARs) are adopted for <br />developments, these should be adjusted to account for slope. This could be <br />accomplished through hillside protection regulations by eliminating or discounting <br />land area over a certain slope for the purposes of calculating FAR. A further <br />option could require the designation of a development envelope for each site <br />which would be a less environmentally sensitive area within which all built <br />structures and some amount of level yard area would be contained. An FAR <br />based on the development envelope rather than the entire lot has been another <br />strategy for controlling visible building size. <br />Options: Calculate allowable house size based on the entire parcel, eliminate <br />highly sloped areas from the FAR calculation, or base the FAR on the <br />development envelope rather than the entire parcel. <br />How would slope be calculated? Calculating slope can depend on the specific <br />formula used and the two points selected from which to measure slope. For <br />example, selecting points at the base and top of a hillside may result in an overall <br />average slope of 25 percent between the base and top, but there may be limited <br />areas in between those points that would exceed 25 percent. Furthermore, there <br />could be uncertainties and disagreements as to what constitutes the base or toe <br />of slope on a hillside. The City's geographical information system (GIS) uses a <br />grid system overlaid on a topographical map that calculates and identifies the <br />slope within each grid. (The grid size used on the attached maps is 20 ft. by 20 <br />ft.) The Initiative does not define how slope would be calculated, but this could be <br />accomplished through hillside protection regulations, either by adopting the City's <br />GIS slope maps as the official slope maps or by adopting a specific slope <br />calculation methodology. <br />Options: Calculate slope in a way defined through the adoption of hillside <br />protection regulations, or by adopting the City's GIS slope maps. <br />Process Options: <br />The discussion of hillside regulations is related to the next item on the agenda <br />concerning Council options for proceeding with the Hillside Initiative. Staff is aware that <br />the issues presented above are complex and require study and discussion with Initiative <br />proponents, stakeholders, decision makers, and others. In the short run, the Council <br />may wish to request afollow-up staff report providing more information on potential <br />hillside issues and their impacts on the community. If so, the Council may wish to direct <br />staff to prepare such a report for a future agenda. If the Council decides that further <br />hillside regulations are necessary to implement, clarify, or expand upon a potential <br />Hillside Initiative, then it may wish to consider the public process to accomplish this <br />Page8of9 <br />
The URL can be used to link to this page
Your browser does not support the video tag.