Laserfiche WebLink
r- <br />SEP <br />w 1992 <br />BOOK 87 PAGE 6'33 <br />SECTION 25: would allow a developer credit for satisfying all <br />county stormwater quality standards if a St. Johns, River Water <br />Management District (SJRWMD) permit is obtained. The proposal, <br />made by the County Engineer, would still require a developer to <br />obtain a county stormwater permit to meet county stormwater <br />quantity standards. <br />SECTION 26: would add new, locally -derived categories and trip <br />rates to the county's trip rate data table. The proposals are <br />being made by the County Traffic Engineer, based upon recently <br />completed local trip rate traffic surveys. The new categories <br />"fill in" some gaps in the current rate table (which is based <br />predominantly on national rates), and provide a specific category <br />for contractors trades uses which are a common type of use in the <br />county. The new categories and rates are considered to be more <br />accurate for Indian River County and are more specific and useful <br />in review of small strip centers and stores, and contractors trades <br />buildings projects. <br />SECTION 27: would establish a formula for equating large truck <br />traf f is volume with passenger vehicle traf f is volume in relation to <br />project turn lane requirements. The formula, proposed by the <br />traffic engineer, would affect only warehousing/manufacturing <br />projects and would require a developer to take into account the <br />impact of large truck maneuvers in relation to maneuvers of <br />passenger vehicles. <br />SECTION 28: would change some traffic impact fee credit <br />requirements and procedures. These requirements and procedures <br />will apply to developments within all participating municipalities <br />as well as the unincorporated area of the county. The intent of <br />the proposed changes is to: <br />1. Require up -front agreements on credit for constructed <br />improvements before the improvements are designed and <br />constructed. Such a requirement would eliminate post - <br />construction credit claims which can present various problems. <br />2. Substitute a precise date for a current requirement tied to <br />"...the effective date of this chapter...". <br />3. Better specify what types of improvements constitute non - <br />creditable, site -related improvements. <br />4. Better specify existing procedures. <br />It should be noted that prior to PSAC consideration of this <br />proposal, a draft of the proposal and an invitation for comments <br />and attendance at the PSAC were sent to every municipality in the <br />county. No comments were received from the municipalities. <br />SECTION 29: would correct a discrepancy between the parking <br />ordinance (954) and the landscape ordinance (926). The change <br />would allow a developer to use less paving at the end of a parking <br />space by permitting a design that allows vehicles to overhang up to <br />3' beyond a bumper stop, over grassed areas. This provision is an <br />incentive to design less paving area and more open space. <br />SECTION 30: would prohibit signs (over four square feet) attached <br />to parked vehicles where the signs are used to attract the <br />attention of adjacent right-of-way travelers, unless the vehicle is <br />parked in a designated parking area and is used in day-to-day <br />operations. The intent of this LDR revision is to "close a loop- <br />hole" and prohibit strategically parked vehicles to be used as on - <br />premise or off -premise signs. <br />10 <br />