My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
1998 Planning Commission Packets
MoundsView
>
Commissions
>
Planning & Zoning Commission
>
Agenda Packets
>
1990-1999
>
1998
>
1998 Planning Commission Packets
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2018 10:25:19 AM
Creation date
2/22/2012 8:14:59 AM
Metadata
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.
/
882
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).
Show annotations
View images
View plain text
` � V ..� . � ..� ��' . _ ' � -`'t ._ .. . <br />_ �v . . . .__ __ <br />� • . <br />'- . .:" - ' .._ ._' __ _ _ . <br />' ' . .- _� � .- - I ^ � " _ _ - - _ <br />'� _ _ ' .. -.. ._ ._. .:. _ :. . s-.' _._- _ ..=-.L. ...' ____v �� � _ . . <br />� __ __ _'_ '__ '_-__ -_. _.�_�_z. _. _ �' - . <br />Planning Commission Report <br />Bridges Technology Park Phase II <br />Planning Case 514-98 <br />March 27, 1998 <br />Page 2 <br />Discussion: <br />Prevtouslv. <br />This request was discussed at the Planning commission's last meeting on April 1, 1998. <br />According to the site plan dated 3/6/98, all of the dimensional requirements for this development <br />would be met with the exception of the parking requirements, which will be discussed further <br />below. One of the primary issues that was raised at the last meeting concerned how close the <br />paved area was to the delineated wetland. It was requested that the distance between the wetland <br />and pavement be increased to a minimum of ten feet. The revised plan (date-stamped 4/8/98) <br />submitted by the applicant shows a setback of ten feet while maintaining a minimum 26-foot <br />drive-aisle behind the building, as recommended by the Fire Marshal. <br />.Draina�e. Wetland Gonsiderations and Wetland Alteration Permit• <br />As discussed at the last meeting, because work is being done within 100 feet of the wetland, the <br />applicant will need to have a wetland buffer pernut approved by the City. From the revised site <br />plans, the new parking area and drive-aisles will be a minimum of ten feet from the delineated <br />edge of the wetland. The revised site plan shows the 100-foot wetland buffer, the edge of the <br />easement area, and statistics regarding the area of the buffer and the percent of which is covered <br />in pervious and impervious surface. <br />Parking_ <br />The applicant has provided a master site plan for both lots 2 and 3 showing the parking for the <br />existing and proposed buildings. Altogether, a total of 200 spaces would be required for both <br />buildings, with a total of only 162 stalls being provided. The remaining 38 stalls are indicated as <br />"proof of parking" on the master site plan. The proof of parking can be allowed one of two ways. <br />For the neighboring ZEP manufacturing, the proof of parking was allowed by adjusting the office <br />and warehouse parking ratios on the condition that the spaces be constructed if needed in the <br />future. The Code, in Section 1121.14, requires that a conditional use pernut be obtained for any <br />reduction in parking space requirements. Obviously, a variance to the parking ratios would be the <br />more expedient solution, if that choice is still an option considering the what the Code requires. <br />If a variance to the parking requirements were considered, the following amended ratios would <br />closely match with the number of stalls being provided: <br />Office: 3 spaces plus 1 per 200 square feet of floor area = 3+ 84 = 87 <br />Warehouse: 8 spaces plus 1 per 750 square feet of floor area = 8+ 65 = 73 <br />160 <br />The difference between the number of stalls provided (162) and the number required (200) would <br />need to be shown as future parking (38). <br />
The URL can be used to link to this page
Your browser does not support the video tag.