Browse
Search
OCPB agenda 121817
OrangeCountyNC
>
Advisory Boards and Commissions - Active
>
Orange County Planning Board
>
Agendas
>
2017
>
OCPB agenda 121817
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/14/2018 4:06:41 PM
Creation date
3/14/2018 3:58:17 PM
Metadata
Fields
Template:
BOCC
Date
12/18/2017
Meeting Type
Regular Meeting
Document Type
Agenda
Document Relationships
OCPB minutes 121817
(Message)
Path:
\Advisory Boards and Commissions - Active\Orange County Planning Board\Minutes\2017
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.
/
210
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
2 <br />Orange County Planning Department <br />131 West Margaret Lane <br />PO Box 8181 <br />(919) 245‐2597 (phone) <br />(919) 644‐3002 (fax) <br /> <br />Pursuant to North Carolina General Statute 132, correspondence sent and received from this account is <br />a public record and may be disclosed to third parties. <br /> <br />From: Chuck Edwards Contact <br />Sent: Tuesday, November 14, 2017 2:12 PM <br />To: Ed Sirgany <br />Cc: Michael Harvey; Bunting, Clarence B; Sorrell, Charles V; Ishak, Doumit Y; Jones, DeAngelo J <br />Subject: Proposed Settlers Pointe- Revised Access Configuration and Revised Traffic Analysis, <br /> <br />Ed, <br /> <br />I’m writing in follow up to our recent meeting between you and District and Congestion Management <br />staff to discuss alternate access arrangements for the above project. As you recall Congestion <br />Management had previously reviewed the original TIA and had included in their recommendations, a <br />new access road serving the industrial element with a new intersection on Old NC 86 that would provide <br />more appropriate intersection spacing relative to the interstate interchange and adjacent proposed <br />accesses. This would require that the Applicant obtain additional property which may not be feasible or <br />possible. During our meeting we identified alternate access configurations utilizing the frontage <br />currently controlled by the Applicant that would be expected to provide acceptable operation and <br />intersection spacing in accordance NCDOT requirements. District and Congestion Management staff <br />have reviewed your analysis for the revised scenario and, based on the information provided, we find <br />the proposed alternate to be conceptually acceptable. Additional site plan and traffic analysis detail will <br />be necessary prior to NCDOT approval and issuance of the required Driveway Permit as this project <br />proceeds. A conceptual exhibit is attached with remarks provided by Congestion Management Staff and <br />a brief summary is provided below: <br /> <br />Phase I <br /> <br />I‐40 Westbound Ramps and Old NC 86 Intersection: <br />Install a traffic signal at this intersection <br /> <br />I‐40 Eastbound Ramps and Old NC 86 Intersection: <br />Provide dual southbound left turn lanes on Old NC 86 <br />Provide dual northbound approach lanes with one lane terminating as a right turn lane to the I‐40 on <br />ramp <br />Provide a second lane on the on ramp to receive the dual left turn movements <br />Install a traffic signal at this location <br /> <br />Old NC 86 and Service Road Intersection: <br />Convert intersection into a right in‐right out configuration with a northbound directional left‐over on <br />Old NC 86 <br />Provide a southbound exclusive right turn lane on Old NC 86 <br /> <br />Old NC 86 and U‐turn Intersection: <br />Eliminate previously proposed Residential Driveway 1 and provide an unsignalized U‐turn intersection <br />for accommodation for redirected turning movements at this location. Provide an exclusive southbound <br />lane for U‐turns <br /> 42
The URL can be used to link to this page
Your browser does not support the video tag.