Laserfiche WebLink
CC Regular Session 4. 17. <br />Meeting Date: 08/13/2013 <br />Submitted For: Grant Riemer By: MaryJo Warner, EnginceringfPublic Works <br />Information <br />Title: <br />Report from Public Works Committee meeting date July 16, 2013. <br />1) Consideration of Permitting Fence Encroachments across Private Property Lines: Ratify the recommendation of <br />the Public Works Committee to change the City policy allowing fences to be extended across property lines. Full <br />motion/report in case background. <br />2) Consider Partial Vacation of Drainage and Utility Easement at 15069 Helium Street NW: Rath the <br />recommendation of the Public Works Committee to approve Option 1 - Full motion/report in case background. <br />3) Approve Plans and Specifications, and Joint Powers Agreement for the Mississippi River Trail: Rath the <br />recommendation of the Public Works Committee to approve the plans and specifications and the JPA for the <br />Mississippi River Trail. <br />4) Cost Estimate for Pedestrian Crosswalk at Alpine Drive and Zirconium Street: Ratify the recommendation of the <br />Public Works Committee to install standard crosswalk signage 200 feet west of Zirconium Street to include 200 feet <br />ofaggregate trail on the north side of Alpine Drive and 225 feet of aggregate trail on the south side of Alpine Drive <br />at a cost o f .$9, 300. <br />5) Recommend Shelter and Restroom for Riverdale Park — 2013.Capital Improvement: Ratify the recommendation <br />of the Public Works Committee to approve a not -to -exceed amount of $84,000 from the Park Trust Fund for <br />Riverdale Park's shelter, restroom, and drinking. fountain as presented within the 2013 Capital Improvement Plan. <br />Committee/Staff Input: Discuss Request to Mow Portions of an Undeveloped Park — Shawn Acres: ratify the <br />consensus of the Public Works Committee and direct staff to mow the front portions of Shawn Acres Park <br />on as -needed basis. <br />Background: <br />The Public Works Committee held its regular meeting on July 16, 2013 and discussed the following cases. <br />5.01. Consideration of Permitting Fence Encroachments across Private Property Lines <br />City Engineer Westby reviewed the staff report, noting the City's policy requires landowners to install fences a foot <br />or more inside their property line in areas where a potential infrastructure conflict exists. He advised of the City's <br />current policy and displayed pictures depicting this situation. As a result, within the Ramsey Town Center 10th <br />Addition, fences are staggered along rear property lines to avoid damaging an existing underground stone sewer <br />system, resulting in the unintended consequence of creating remnant strips of land two or more feet in width <br />between rear fence lines in which property owners arc not able to easily maintain their properties so there are blight <br />and nuisance issues. It was noted the resident's request is to extend their side lot line fencing across their rear <br />property line to connect to their neighbor's fence, thereby allowing a shared common rear fence line that would <br />eliminate the remnant strips of property between fences. Staffs recommends to change the policy to allow <br />neighbors to extend fences across private property lines to connect to neighbor's fences contingent on language <br />being added to the building fence permit to ensure that: City infrastructure will be protected during fence <br />construction activities; access to City infrastructure will be maintained on an on -going basis; property owners will <br />not lose property rights as related to adverse possession laws; and, property owners are reminded to obtain <br />permission from neighbors via a written agreement. <br />Motion to recommend that the City Council change the City policy allowing fences to be extended across property <br />lines, contingent on the draft (building) fence permit language being reviewed and approved by the City Attorney <br />and subsequently added to all (building) fence permits issued in the future, and to add a requirement for a written <br />