Laserfiche WebLink
Diagonal Parking <br /> Change the configuration of the parking lot to one-way traffic with diagonal parking <br /> spaces, instead of 90-degree parking stalls, on each side: This concept was reviewed <br /> during the very early design stage, but it was not advanced as it only created 31 <br /> additional parking stalls. This configuration would provide an additional four feet to the <br /> trail area. This is not enough width to add a six-foot multi-use path in addition to the <br /> proposed concrete path as was included as part of the FHAC design, but it would allow <br /> for a wider concrete path. <br /> Mix 90-degree and Parallel Parking (BPTC Suggestion) <br /> Change the parking configuration on the west of the parking lot to parallel parking, while <br /> maintaining the 90-degree parking on the east side: This would require the drive aisle <br /> be designated as one-way southbound and remain 24 feet wide for maneuvering in/out <br /> of the perpendicular spaces. While at first, this seems like it would add significant width <br /> to the area available for trail use, upon a detailed review it only adds a maximum of six <br /> feet. This is because the current design allows vehicles to pull all the way into the <br /> parking spaces and does not accommodate pedestrian traffic between the railing on top <br /> of the retaining wall and the front of the parked vehicle. If parallel parking spaces are <br /> installed, the design will need to provide space for vehicle passenger doors to open into <br /> a walkway area on the passenger side of the vehicle, parallel to the retaining wall. This <br /> is necessary for passenger ingress/egress from vehicles. If the pathway area is <br /> determined to be an Americans with Disabilities Act (ADA) path of travel, there must be <br /> enough sidewalk width for a wheelchair to still pass on the sidewalk with a vehicle <br /> passenger door fully open and swung out over the sidewalk. The amount of width this <br /> gains for the trail area is estimated to be approximately three feet. The impact on <br /> parking is not as significant with this option as compared to the angled parking option. <br /> While the design of this option is not fully developed, this option appears to create a <br /> total of 107 parking spaces, or 48 more spaces than the 59 spaces that currently exist <br /> on this section of the corridor (see Attachment Two). <br /> Eliminate Landscape Buffers <br /> Leave the parking lot as proposed but remove the landscape buffer which is used to <br /> transition from the edge of the path elevation to the varying property line elevation: This <br /> would require a small, varying-height retaining curb wall of six to 15 inches to be <br /> constructed along the property line between the corridor and private properties. Since <br /> the elevations vary, this curb wall would retain the public property in some areas and <br /> retain the private property in others. This would add three feet to the trail width. <br /> However, the additional width could not be fully utilized because in some areas, private <br /> fencing will be immediately adjacent, so there will not be space for body and bicycle <br /> handlebar overhang. There would also be conflict zones created at the building exits as <br /> there are some doors that will swing out in the area. The low retaining wall would <br /> interfere with pedestrian access from the trail to adjacent parking lots, and the removal <br /> of landscaping would not provide the channelization of pedestrians from the trail in the <br /> locations preferred by the adjacent private property owners. In addition, the wall and <br /> fencing on both sides of the trail would make some areas feel more like an alleyway and <br /> take away from the linear park experience. Finally, additional improvements would be <br /> Page 8 of 10 <br />