Laserfiche WebLink
DRAFT September 11, 2014 <br /> TCAAP Redevelopment Code <br />Page | 33 <br /> <br /> <br />Illustration showing requirements <br />along Pedestrian Priority <br />Frontages only <br /> <br />ii. Pedestrian-Friendly Frontages – Pedestrian-Friendly Frontages are also intended to be <br />pedestrian-oriented with a mostly contiguous development context. However, in some <br />locations, where access to a General Frontage street or Alley is not available, <br />Pedestrian-Friendly Frontages may need to accommodate driveways, parking, <br />service/utility functions, and loading and unloading. In such cases, Pedestrian-Friendly <br />Frontages may balance pedestrian orientation with automobile accommodation. <br />Typically, they shall establish a hybrid development context that has a more <br />pedestrian-supportive development context at street intersections and accommodates <br />auto-related functions and surface parking in the middle of the block. Surface parking <br />shall be screened from the roadway with a street wall or evergreen living fence. <br />Pedestrian-Friendly Frontages are designated on the Regulating Plan. <br />iii. General Frontages – General Frontages are intended to accommodate more auto- <br />oriented uses, surface parking and service functions on a site with a more <br />suburban/automobile orientation. The General Frontages shall be building frontages <br />not designated as either a Pedestrian Priority or Pedestrian-Friendly Frontage on the <br />Regulating Plan. <br /> <br />Graphic Illustrating the <br />Application of Street Type <br />Designation Based on the <br />Development Context