My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
09A,B,C - Permits, Correspondences, Potential Violations/Enforcement Actions
Laserfiche
>
Planning & Zoning
>
Agenda Packets
>
2005
>
03-17-2005 Planning and Zoning Meeting
>
09A,B,C - Permits, Correspondences, Potential Violations/Enforcement Actions
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/28/2016 11:07:31 AM
Creation date
7/28/2016 11:07:30 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
16
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
Babinski Site Plan <br /> February 28, 2005 <br /> Page 2 of 4 <br /> such. <br /> ■ An alternate driveway will be constructed to the east or northeast to connect with the <br /> proposed TH 371 service road. <br /> ■ All other areas will be restored to grass turf. <br /> _ With these assumptions, the total impervious area for the site as planned will be just slightly <br /> over 25% of the total lot area,thereby meeting the requirements of the ordinance. <br /> Parking <br /> As we understand the City Ordinances with regard to parking, 1 space is required for every 2 <br /> workers or 1 space is required for every 2,000 square feet of building floor space(whichever is <br /> greater). We do not, at this point, know how many workers are to be employed by the facility. A <br /> number around 200 has been reported which would lead to a parking requirement of 100 spaces. <br /> The total building area of 184,800 square feet as shown on the plan of the proposed facility leads <br /> to a total of 92 parking spaces being required. <br /> In either case(i.e.by number of employees or by floor space),the parking area shown on the site <br /> plans comprises approximately 214,000 square feet. Typically, a parking space requires around <br /> 200 square feet,plus space required for associated driving lanes within the lot. <br /> Depending on the portion of this area that is dedicated to "modular storage", also as indicated on <br /> the site plans, adequate parking space/facilities appear to be available. <br /> Storm Water <br /> What we believe to be finished ground contours are shown surrounding the proposed facilities on <br /> one of the site plan drawings provided. Since these do not match elevations of the existing <br /> i <br /> ground in the area,we have assumed these indicate a substantial amount of site grading is to take <br /> place. <br /> It is worth noting that this proposed grading would probably require a large number of the trees <br /> presently on the site to be removed. One of the plan sheets submitted contained a note stating <br /> "No additional trees to be planted as tree coverage is well over 10 0/o..." In light of the area that <br /> would need to be graded to achieve the contours shown on the plans,this statement indicating <br /> that no additional trees need to be planted may no longer be true. <br /> What we assume are to be storm water infiltration basins are shown both north and south of the <br /> proposed building layout. A depth of 10 ft. is indicated on the north basin; 20 ft. is indicated on <br /> the south basin. If the site is graded to the contours shown, it appears that the vast majority of <br /> the site's storm water runoff will flow to these two basins. <br /> This site-grading plan appears to meet the City's ordinances requiring not directing storm <br /> water runoff onto adjoining property. However, the developer should be required to provide a <br /> better detailed grading map prior to construction (for example: either one-foot or two-foot <br /> contour lines, contour lines connecting to each other and not just ending, and contours of the <br /> J:\130PQLAK\0000-GENERAL\CORR\DAWN B=ER-REVIEW OF BABINSKI SUE PLAN-022805.DOC <br />
The URL can be used to link to this page
Your browser does not support the video tag.