Browse
Search
Agenda - 10-04-2011 - 7a
OrangeCountyNC
>
Board of County Commissioners
>
BOCC Agendas
>
2010's
>
2011
>
Agenda - 10-04-2011
>
Agenda - 10-04-2011 - 7a
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/28/2011 2:49:17 PM
Creation date
11/28/2011 2:48:58 PM
Metadata
Fields
Template:
BOCC
Date
10/4/2011
Meeting Type
Regular Meeting
Document Type
Agenda
Agenda Item
7a
Document Relationships
Minutes 10-04-2011
(Linked From)
Path:
\Board of County Commissioners\Minutes - Approved\2010's\2011
S Planning - Habitat for Humanity OC, NC Inc. - Tinnin Woods Project - Special Use Permit
(Message)
Path:
\Board of County Commissioners\Various Documents\2010 - 2019\2014
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
124
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
Staff is satisfied that the 8" line will accommodate the proposed development. <br />Please refer to Attachment 5 for additional detail. <br />B. Water line flow rates. Planning Board members requested the applicant, at a minimum, install <br />a water line supplying no less than 1,000 gallons of water per minute and maintain a static <br />water pressure of no less than 80 pounds per square inch. <br />Applicant Response: <br />i. According to the applicant and OAWS, neither an 8" nor a 12" line will supply the <br />1,000 gallons of water per minute desired. <br />ii. The proposed 8" line will be able to supply 750 gallons of water per minute, which <br />is the State of North Carolina's Department of Environmental Health's minimum <br />requirement, with a residual pressure of 20 pounds per square inch. <br />iii. The proposed 8" line should maintain the desired 80 pounds per square inch static <br />pressure for the system according to OAWS and the applicant. <br />Please refer to Attachment 5 for additional detail. <br />C. Staff has recommended a condition that the water system be tied into an existing water main <br />in Alice Miller Court within the Richmond Hills Subdivision to provide a looped water system. <br />Applicant Response: The applicant has agreed to loop the system as requested. <br />D. Payment of connection fees for existing customers connecting to new utility line(s). A <br />question was raised during the May 23, 2011 Quarterly Public Hearing over who would pay <br />the costs associated with existing customers tapping into the proposed new utility lines. <br />Applicant Response: OAWS has indicated that there will be no re-connection fee for existing <br />utility customers to tie into the proposed 8" line. <br />E. Development of sidewalks. Questions were raised over the installation and maintenance of <br />sidewalks. <br />Applicant Response: <br />i. The applicant has indicated support for the development of sidewalks for this <br />project. <br />ii. The applicant has expressed concern over the proposed local Homeowners <br />Association assuming perpetual maintenance costs. <br />iii. The applicant has suggested the sidewalk be located within the proposed public <br />right-of--way through the granting of a two party encroachment agreement with the <br />North Carolina Department of Transportation (NC DOT). <br />iv. The various questions raised by the applicant include: <br />1. Who is paying to install the sidewalks, <br />2. When should they be installed, <br />3. Who should maintain. <br />The Planning Board has recommended a condition that sidewalks should be an integral part <br />of the project if agreements as to their location (i.e. public right-of--way) and <br />installation/maintenance costs can be resolved. The Board reiterated its position that the <br />applicant should not be required to pay for the installation or perpetual maintenance of the <br />sidewalks. <br />
The URL can be used to link to this page
Your browser does not support the video tag.