2001-03-19 Special Called Regular Meeting and Public Hearing

Browse Search

\_llil~-""'"""'''''''''''''''~''.''~ " . e 22 TABLE 2-1 Development Planning Scales e Chap. 2 I Site Planning (i;) Site Scale Corridor Scale 1. Create shared marginal access to simplify highway movement and reduce number of access points. 2. Highway access points must be 400 ft. minimum distance from a channelized intersection. 3. Avoid "dog leg" situation by locating access point directly opposite another access point or at least 150 ft. away. (This applies at every level of scale.) 4. Site access should be shared whenever possible to reduce pavement, avoid duplication of roads, and create efficient cir- culation. 5. Parking lots should be shared to reduce parking area. Adja- cent uses which have different operating hours or peak times should share parking. 6. Separate incompatible uses with buffer zone or screen. 7. Size, shape and orientation of buildings should be designed to make them easily visible from hjghway, at highway speeds. 8. Locate buildings, parking areas, and open space to create strong and varied mass/space relationships when viewed from highway. 9. Site slgnage must be located where It Is easily visible to high- way traffic. 10. Site uses along corridor should be land use types which benefit from highway visibility and complement adjacent corridor uses. 11. Uses should take advantage of vistas and pleasant views where they are available. 12. Uses adjacent to natural fea- tures must not endanger or encroach upon the feature. SOURCE: Frank J. Koepke 11]. Project Scale 1. Parking access system should be clear and simple, form circu- lation loops, and avoid dead ends. 2. Parking modules should be used to break up parking lot expanse, and create simple cir- culation patterns for parking search. 3. If parking is shared by two or more buildings, each should have equally convenient pe- destrian and vehicle links to the parking area. 4. Building forms should be used to define and emphasize entrances, which must be visi- ble and easily accessible' from related parking areas. 5. Provide a continuous pedes- trian system which links build- ing entrances along a direct path, separate from vehicular right-of-ways, and connects to pedestrian routes beyond the project. 6. A system of bicycle routes should also be created, sepa- , rate from auto traffic if possible, and linked to a community- wide bicycle system. Areas for convenient storage of bicycles should be provided. 7. Buildings should be oriented to take advantage of pleasant views and to capture highway visibility. 8. Appropriate screens should be used to hide undesirable views. 9. Some areas of natural open space should be created to pro- vide relief from and contrast to built-up areas. 10. Use "green" space as a buffer zone between less compatible uses. 1. Parking modules should alter- nate with planted areas to break up parking expanse, pro- vide safe pedestrian zones, and help define the vehicular circulation system. 2. Parking module location can facilitate safe pedestrian move- ment if modules are oriented perpendicular to building entrance facades, to minimize the number of traffic aisles a pedestrian must cross. 3. Circulation within modules should be simple and con- tinuous. Avoid situations where driver must leave site and re- enter to repeat parking search. 4. Delivery areas should be sepa- rate from parking area. Service drives should not enter parking modules. '15. Pedestrian walkways should t be separate from vehicular right-of-ways, and should fol- low \direct routes between buildings or from parking area to building. " i i i ); f l