Laserfiche WebLink
Figure 1: Site Location <br />PLEASANTON MASONIC CENTER <br />The Masonic Center Conditional Use Permit was approved in 1977 (prior to construction of <br />the Masonic Center building) and did not specify or elaborate upon the intended uses or <br />activities of the site other than operation of a Masonic Center. The staff report to the Planning <br />Commission stated that Masonic buildings are commonly rented for non - Masonic affairs such <br />as wedding receptions and parties. The staff report stated that "[w]hile it might be preferable <br />to have the Masonic building farther south on the property, it would be possible to design the <br />structure so as to minimize any noise which is generated from within." As such, Condition <br />No.1 of UP -77 -13 (Attachment 3) required "that buildings be designed so that activities will be <br />focused toward the southern portion of the subject property," and Condition No. 20 required <br />"[t]hat the applicant provide an effective buffer between the development and the single - <br />family residential area surrounding the property." However, no specifications for this buffer <br />(e.g., dimensions, buffering measures, operational standards) were provided in the conditions <br />of approval. Additionally, the original approval of UP -77 -13 did not specify or elaborate upon <br />intended uses or activities other than operation of a Masonic Center. <br />The Masonic Center building was constructed in 1980, after approval by the City Design <br />Review Board. The building was approved to be located 70 feet south of the northern <br />property line. The entrance to the building was approved to be located on the south side, <br />with no windows along the other three elevations. One emergency exit was identified on the <br />east side of the building and one emergency exit was identified on the north side of the <br />building. <br />Site and Building Changes <br />Since construction of the Masonic Center building, the following site and building changes <br />have been undertaken: <br />Page 3 of 13 <br />