My WebLink
|
Help
|
About
|
Sign Out
Home
CCP 06172024
Roseville
>
City Council
>
City Council Meeting Packets
>
2024
>
CCP 06172024
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/8/2024 9:34:34 AM
Creation date
7/8/2024 9:34:14 AM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Agenda/Packets
Meeting Date
6/17/2024
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.
/
220
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
<br />35 they realized that the fence permit application should not have been approved. This <br />36 determination was based on the fact that the fence was being constructed in the ROW, <br />37 without a ROW permit or an encroachment agreement, and in excess of the submitted site <br />38 plan. Staff issued a stop work order on April 24, 2024. Attachment 5 shows the fence at the <br />39 time the stop work order was issued. Despite the stop work order, work continued on the <br />40 fence, and it was completed the next day. Attachment 6 shows a picture of the fence at the <br />41 time work was stopped. On April 25, 2024, the City sent a letter to Mr. Carrara ordering that <br />42 he remove the fence. (Attachment 7). Mr. Carrara submitted an email to the City Manager <br />43 on May 6, 2024, appealing the revocation of fence permit and order to remove the fence <br />44 from City ROW (Attachment 8). <br />45 <br />46 On May 9, 2024, Staff received a complaint about site visibility for trail users. The <br />47 configuration of the driveway (which slopes down from the street to the lake) and the <br />48 inability to see through the fence created a safety hazard for trail users because they could <br />49 not see cars approaching from the driveway, and cars in the driveway did not have a view <br />50 of trail users. Staff reviewed the complaint and determined the fence was an imminent <br />51 safety issue to trail users due to lack of visibility. On May 10, 2024, Staff notified Mr. <br />52 Carrara that the City planned to remove certain fence panels to mitigate the safety issue. <br />53 Mr. Carrara asked the City to allow the fence panels to remain and, in the alternative, <br />54 agreed to barricade his driveway. Staff agreed and the driveway was barricaded. On May <br />55 18, the Property owner removed fence panels addressing the immediate visibility concerns <br />56 and Staff removed the barricades. <br />57 <br />58 The fence permit application should have been denied. The fence is in City ROW. Private <br />59 improvements such as fences are not typically allowed in City ROW since such structures <br />60 limit the public’s use to the ROW. If Staff had realized that the fence was in the ROW, the <br />61 City would have required that Mr. Carrara apply for a ROW permit and Encroachment <br />62 Agreement prior to issuance of a fence permit. <br />63 <br />64 Secondly, the fence constructed was a six-foot privacy fence. Under the zoning code, six- <br />65 foot fences are not allowed in the front yard. The maximum height allowed is four feet. <br />66 Therefore, Mr. Carrara should have been required to obtain a height variance before <br />67 building a six-foot fence. <br />68 <br />69 Finally, the fence permit allowed Mr. Carrara to remove the City’s split-rail fence. The split- <br />70 rail fence that the City installed along numerous segments of the McCarrons pathway <br />71 serves multiple purposes. It acts as a visual and physical barrier while not obstructing the <br />72 view of the lake or, more importantly in this instance, the view from the Property’s driveway <br />73 of pedestrians and others using the trail. The split-rail fence also allowed for storage of <br />74 snow to ensure snow could be cleared from the path so it could be used all year. <br />75 <br />76 In addition to the permit being issued in error, the fence as-built greatly exceeds what was <br />77 shown in the fence permit application. While the site plan does not contain any <br />78 measurements of the proposed fence, the fence that was built is objectively larger. The <br />79 larger fence, in addition to exceeding what was permitted, created a safety hazard at the <br />80 driveway because the fence obstructed the view from the driveway of people on the <br />81 pathway and vice versa. Finally, part of the larger fence (located east of Mr. Carrara’s <br />82 driveway) enters into property not owned by Mr. Carrara nor is considered ROW. <br />83 <br />Page 2 of 4 <br />Qbhf!9!pg!331 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.