My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2012-019
CBCC
>
Ordinances
>
2010's
>
2012
>
2012-019
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/18/2025 3:17:18 PM
Creation date
10/5/2015 9:15:10 AM
Metadata
Fields
Template:
Ordinances
Ordinance Number
2012-019
Adopted Date
07/10/2012
Agenda Item Number
4.A.
Ordinance Type
Impact Fees
State Filed Date
07\18\2012
Entity Name
Transportation Monitoring
Code Number
Chapters 952 and 910
Subject
Traffic Impact Fees
Codified or Exempt
Codified
Supplemental fields
SmeadsoftID
11339
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
28
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
ORDINANCE 2012-019 <br />2. As submitted by the applicant or engineer at the pre -application conference. <br />(c) For each intersection in which the project traffic results in a level of service below <br />the acceptable adopted level of service, the applicant and/or engineer will develop <br />proposed improvements to the intersection that result in the intersection operating at <br />an acceptable level of service with the existing, vested and specific project traffic <br />included in the analysis. <br />(d) The applicant and/or engineer -shall be required to provide the following <br />information relative to each intersection analysis: <br />1. Printouts and worksheets for all highway capacity analysis performed on the <br />intersections or roadway segments; <br />2. Copies of any traffic counts performed or used in the analysis, including the <br />source of count data; <br />3. Copies of any signal warrant studies performed in the analysis of non - <br />signalized intersections; <br />4. Documentation of any assumptions used in the analysis including trip <br />generation data, if not already specified for the analysis; <br />5. Turning movement volumes and documentation of methodology used to <br />project existing, prior vested and project traffic; <br />6. Any other applicable data or information. <br />(20j9) Segment analysis. <br />(a) If a roadway segment is operating at or above ninety (90) eighty (80) percent (for <br />projects generating betweei3 from one hundred (100) and f of 4undr-ed ninety .,:.,o <br />(49-9) to more than one thousand (1000) average daily trips) of the available <br />ILevel-of-sService E "D" peak hour, peak direction FDOT generalized planning <br />capacity with the inclusion of vested development; of A or above seventy (70) <br />pereent (for- pmjeets generating be�weea five 4uadr-ed (500) to one thousand (1, <br />aver -age daily trips) of available eapaeity a4 level of sen4ee "E" based on the F -D <br />generalized level of sefviee tables with the inelusion of prior- vested tr-affie, <br />tfanspet4a4ien and the roadway segment is assigned eight (8) or more project <br />peak season/peak hour/peak direction trips for a two-lane roadway or fifteen <br />(15) or more project peak season/peak hour/peak direction trips for a four -lane <br />(or wider) roadway, then an arterial analysis must shall be performed to <br />determine if the actual roadway segment operating characteristics are such that <br />additional capacity is available. <br />The applicant or engineer wi44-shall submit the methodology and approach of <br />each segment analysis at the pre -application conference. The methodology <br />and approach w41 -shall be subject to review and approval by the director of <br />public works. This review shall be based on currently accepted traffic <br />engineering principles. <br />Bold Underline: Additions to Ordinance 19 <br />S#ike through: Deleted Text from Existing Ordinance <br />C:\Documents and Settings\tlister\Local Settings\Temporary Internet Files\Content.Outlook\QPAZMTU8\2012-019 952 and 910 Traffic.doc <br />
The URL can be used to link to this page
Your browser does not support the video tag.