Laserfiche WebLink
18.68.130 <br />the PUD zoning district may be initiat- <br />ed by the city council, planning com- <br />mission, property owner, an authorized <br />representative or an option holder pur- <br />suant to the provisions of this chapter. <br />B. The city council, planning <br />commission, applicant or general citi- <br />zen may appeal any decision approving <br />or disapproving a request for PUD <br />zoning, development plan approval, or <br />modification to a development plan <br />pursuant to the provisions of this chap- <br />ter. <br />C. A PUD district zoning request and <br />development plan may be processed <br />concurrently or separately. If they pro- <br />ceed concurrently, only a single ordi- <br />nance shall be required for approval. If <br />they proceed separately, or if the PUD <br />development plan proceeds in phases as <br />provided by this chapter, separate ordi- <br />nances shall be required for each pro- <br />cess and phase of the project. The ordi- <br />nance(s) required by this subsection <br />shall be processed in the same manner <br />as any zoning ordinance. <br />D. No subdivision map shall be pro- <br />cessed concurrently with a PUD zoning <br />request or PUD development plan. <br />E. An applicant shall file a separate <br />application for each noncontiguous <br />parcel upon which consideration of <br />PUD zoning and/or a development plan <br />is desired. For the purposes of this <br />subsection, parcels shall be deemed to <br />be noncontiguous if they are separated <br />by roads, streets, utility easements or <br />railroad rights of way, which, in the <br />opinion of the director of planning, are <br />of such a width as to: <br />1. Destroy the unity of the proposed <br />project or the ability of the parcel to be <br />developed as a cohesive unit; or <br />2. Otherwise create the impression <br />that two (2) separate parcels or projects <br />are being developed. (Prior Code <br />§ 2-8.37) <br />559 (Pleasanton January 2004) <br />