My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Public Works Committee - 04/19/2005
Ramsey
>
Public
>
Agendas
>
Public Works Committee
>
2000 - 2009
>
2005
>
Agenda - Public Works Committee - 04/19/2005
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/13/2025 2:26:21 PM
Creation date
4/18/2005 9:33:10 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Public Works Committee
Document Date
04/19/2005
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
62
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
CASE <br /> <br />CONSIDER AUTHORIZING SIDEWALK REPAIRS <br />IN THE PONDS SUBDIVISION <br /> By: Steven Jankowski, City Engineer <br /> <br />Background: <br /> <br />The City began to install concrete sidewalks in 2002 but at that time had not yet <br />developed standard plates detailing the City's sidewalk requirements. During the <br />construction of The Ponds subdivision the contractor was verbally advised that sidewalks <br />must be six inches thick through driveways. During that period the City relied On <br />MnDOT specifications, and MnDOT standard plate 7035J requires six inch thicknesses <br />of concrete in private driveways and sidewalks crossing private driveways. The <br />developer's contractor informed our inspector that it was their intention to. slip form the <br />entire sidewalk four inches thick and then return to replace the sections through <br />driveways once their locations were determined. <br /> <br />Beginning last September staff had written Royal Oak Realty a series of letters requesting <br />this situation be remedied. Mr. Eibensteiner, of Royal Oak Realty, requested that the <br />replacement of the broken sidewalks be postponed until spring of 2005. Considering the <br />lateness of the season, the City agreed to allow an extension until May 31, 2005 for <br />replacement of the broken sidewalks. In a February 24, 2005 letter staff requested that <br />Royal Oak Realty submit a schedule and additional information concerning the repair of <br />the broken sidewalks by April 1, 2005. Royal Oak Realty has not responded to this letter <br />nor have they renewed their letter of credit as requested by the City on November 22, <br />2004. <br /> <br />A. survey of the situation shows that there are a total of 45 driveways which have been <br />constructed through sidewalks; 27 of these are through single family unit driveways and <br />18 are through townhouse unit driveways. Of this total number of driveways nine have <br />one or more broken pieces of sidewalk; six of these drives are in the single family portion <br />of the development while three are in the townhouse area. In addition, there are 16 <br />additional locations (not in driveways) where the sidewalks have been damaged as a <br />result of construction activity. <br /> <br />Staff proposes that this issue be resolved by removing and replacing all broken sidewalks <br />within the developtnent. In addition where broken sidewalks occur within driveways, the <br />adjacent unbroken but substandard 4 inch sidewalk blocks would also be replaced. The <br />estimated cost of this work is $17,000. Royal Oak Realty currently has various escrow <br />balances in the amount of $38,385 with the City. Staff further proposes that the City <br />authorize the repair and fund the cost through the use of these escrow funds and that the <br />balance of these funds be retained to address the repair needs of any additional repairs <br />that occur within driveways within this subdivision. There would remain .34 four inch <br />thick driveway sidewalks which could be exPected to cost about $1160 each to replace <br />~hould they fail in the future. <br /> <br />11 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.