My WebLink
|
Help
|
About
|
Sign Out
11 ATTACHMENTS 9 -16
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2015
>
110315
>
11 ATTACHMENTS 9 -16
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/28/2015 3:38:00 PM
Creation date
10/14/2015 3:54:32 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
11/3/2015
DESTRUCT DATE
15Y
DOCUMENT NO
11 ATTACHMENTS 9-16
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
270
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
Because roads and retaining walls "require° a location on the ground," they are clearly <br /> included within the Pleasanton Municipal Code's definition of "structure." The California <br /> Government Code on planning and land use similarly states: "`structure'includes, but is not <br /> limited to, any building, road, ... ." (Cal. Gov. Code, Chap. 4.5, Review and Approval of <br /> Development Projects,§ 65927.) <br /> Both the Pleasanton and the California formulations appear to have widespread adoption: <br /> • It appears the California state formulation ("structure' includes ... road") is more <br /> popular in coastal communities. Examples of communities adopting the California <br /> Government Code definition into their own municipal regulations include Carmel, <br /> Halfmoon Bay, Huntington Beach, Imperial Beach, Laguna Beach, Long Beach, and <br /> Malibu. Notably, Fremont has also adopted this definition. <br /> • Inland communities appear to typically adopt language like Pleasanton's ("anything <br /> constructed ... which requires a location on the ground"). Examples of <br /> communities defining "structure" in the same way as Pleasanton's Municipal Code <br /> include: Atherton, Benecia, Berkeley, Burlingame, Concord, Lafayette, Menlo Park, <br /> Orinda, Pleasant Hill, Sacramento, San Bruno, San Carlos, San Mateo, Sausalito, <br /> Sonoma, South Lake Tahoe, Vacaville,Walnut Creek, and Watsonville.' <br /> So, there are many, many communities that define roads as structures for purposes of <br /> hillside development planning. Indeed, having reviewed the municipal codes of several <br /> dozen California communities, I have not found any municipal code anywhere that suggests <br /> "structure" does not include "roads." Walking through some specific, nearby examples in <br /> more detail: <br /> • Danville. Danville requires a special permit to build a "structure" on a hillside or <br /> ridgeline. (Danville Municipal Code § 32-69.5.) Similar to Pleasanton, Danville <br /> defines "structure" as "anything constructed or erected on and permanently attached <br /> to land." (§ 32-2.2.) Danville goes on to explicitly carve out a variety of things from <br /> "structure," including "sidewalks." The strong implication of such an exception is <br /> that sidewalks would have otherwise been included in the definition absent the <br /> exclusion. If sidewalks are included in "structure" (absent exception), so are roads. <br /> • Fremont. Like Measure PP, Fremont Municipal Code § 18.130.050 prohibits the <br /> construction of "structures" on "hilltops" or "ridgelines." Fremont defines <br /> "structures" to include"any ... road." (§ 18.25.800.) <br /> • Orinda. Orinda Municipal Code § 17.30.7 subjects any "structure" developed on a <br /> "severely sloped" hillside to special design review. Like the Pleasanton Municipal <br /> Code, Orinda further defines "structure" to mean anything "constructed ... on the <br /> ground." (§ 17.2.3.) <br /> • Lafayette. The city code prohibits "development" within certain distances of <br /> ridgelines. (§ 6-2023.) Lafayette defines "development" to include "structures," then <br /> See Attachment 2 for citations. <br />
The URL can be used to link to this page
Your browser does not support the video tag.