My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01/16/2018 (2)
CBCC
>
Meetings
>
2010's
>
2018
>
01/16/2018 (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/11/2021 12:17:48 PM
Creation date
2/14/2018 2:36:13 PM
Metadata
Fields
Template:
Meetings
Meeting Type
BCC Regular Meeting
Document Type
Agenda Packet
Meeting Date
01/16/2018
Meeting Body
Board of County Commissioners
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.
/
225
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
Mr. Boling said currently, the idea was when the applicant/engineer came out of <br />the pre -app, there was direction; the engineer knew of trouble spots. He continued <br />staff's suggestion was to have a staff -coordination meeting before TRC to iron out any <br />conflicts and to provide solid comments at the TRC meeting. <br />Mr. Chuck Mechling, District 5 Representative voiced his support for staff to have <br />the extra time period before the TRC meeting; however, questioned when the applicant <br />and the engineer would know how to proceed with development. He shared his thought <br />with a residential concept, at the resubmittal time, the applicant would have the Traffic <br />Study to know how many lots were allowable. <br />Chairperson Robinson asked Mr. Rich Szpyrka, Public Works Director, with the <br />understanding the Traffic Study could determine changes in driveway egress, etc., and <br />would there be general direction from Public Works as to whether a Traffic Study was <br />required at the formal submission? <br />Mr. Szpyrka said it depended upon the level of information he was provided to <br />make that decision. For him to make a decision, he would require the detailed <br />information from the developer; however, that decision would be arbitrary and staff tried <br />to stay away from arbitrary. He surmised perhaps the Code needed to be changed to <br />require a traffic study before the post TRC resubmittal. <br />Chairperson Robinson asked Mr. Blum when he thought the Traffic Study should <br />be completed, before the TRC meeting, or before resubmittal. Mr. Blum responded his <br />opinion was to have the Traffic Study before resubmittal. Mr. Wes Mills, District 3 <br />Representative agreed the Traffic Study should be required at the post TRC resubmittal <br />because the Traffic Study would need to match the revised site plans. <br />Mr. Joe Schulke, Schulke Bittle and Stoddard shared his thought the formal <br />traffic study should be able to wait for a resubmittal of the site plan; however, the Code <br />required a traffic study methodology meeting prior to conducting the Traffic Study. He <br />suggested requiring the methodology meeting prior to the formal TRC meeting <br />submittal, providing staff and the applicant information going into the TRC meeting, so <br />when staff held their coordination meeting, both parties had the same information. <br />Chairperson Robinson inquired whether the pre -app and the Traffic Study <br />methodology could be done at the same meeting. Mr. Paladin responded the pre -app <br />and Traffic Study covered different items. <br />Mr. John McCoy, Community Development Chief Planner stated he thought a <br />civil engineer designing the project, whether it was a small subdivision, or a regional <br />mall, would know whether a traffic engineer was needed to attend the pre -app based <br />upon the project. <br />Mr. Mechling surmised the concept would be at the resubmittal, to have the full <br />Traffic Study, making a change to the current Code. He also understood having the <br />4 <br />C:\Users\sjohnson\AppData\Local\Microsoft\Windows\lNetCache\Content.Outlook\SEU7ML71 \1 1.8.17 DRPP Minutes.doc 62 <br />
The URL can be used to link to this page
Your browser does not support the video tag.