My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Ordinance 2532-01
>
Ordinances
>
Ordinance 2532-01
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/7/2014 2:36:24 PM
Creation date
4/7/2014 2:36:23 PM
Metadata
Fields
Template:
Ordinances
Ordinance Number
2532-01
Date
8/22/2001
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
7
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
participation is allowed, you should read the appropriate sections of this chapter for the <br /> required review process. <br /> 19.42.020 Multiple review processes. <br /> In the event that a proposed use or development requires more than one review process, <br /> the applications shall be reviewed by only one review authority to the extent permitted by <br /> city ordinances. Proposals which this title or other city ordinances require review using <br /> both Review Processes II and III shall be reviewed using only Review Process III; <br /> proposals which this title or other city ordinances require review using both Review <br /> Processes III and V shall be reviewed using only Review Process V; proposals which this <br /> title or other city ordinances require review using both Review Processes II and V shall <br /> be reviewed using only Review Process V. In the event that the proposal may not be <br /> reviewed using a single review process, the applications shall be reviewed concurrently, <br /> as set forth in the pertinent land use regulations (hearing examiner ordinance, subdivision <br /> ordinance, etc.). When review processes are combined, the evaluation criteria required to <br /> be used by the review authority for a single review process shall still be applied by the <br /> higher review authority in evaluating a proposal with combined review processes. <br /> 19.42.030 Applications. <br /> Application forms for developments regulated by this title are available from and shall be <br /> filed with the planning department. Specific instructions will be provided with <br /> application forms. Applications may be filed by a property owner or an agent acting on <br /> his/her behalf if an affidavit of ownership signed by the owner is filed with the <br /> application. Applications submitted to the planning department shall not be considered <br /> complete until all required information has been accurately and fully provided. Any time <br /> frame set forth for review procedures shall not commence until the application is deemed <br /> complete by the planning director. <br /> 19.42.040 Fees. <br /> Fees shall be submitted with applications in accordance with the current fee schedule <br /> adopted by the city council. An application shall not be considered complete until the <br /> required fee has been submitted. <br /> 19.42.050 Compliance with SEPA and other laws. <br /> The State Environmental Policy Act (SEPA) applies to many of the decisions that will be <br /> made using this title. Each application shall be evaluated and, where applicable, comply <br /> with SEPA, with state regulations, federal regulations and city ordinances. The minimum <br /> requirements set forth in the zoning code may be increased based upon the SEPA review <br /> process or requirements contained in other city regulations. <br /> 19.42.060 Preapplication conference. <br /> A. Department Initiated. Prior to submittal of an application for consideration by the city, <br /> the planning department may require that the applicant attend a preapplication <br /> conference. The purpose of the preapplication conference is to allow complex proposals <br /> to be preliminarily evaluated in order to provide an applicant with proposal information, <br /> knowledge of development requirements and other relevant information prior to the filing <br /> 2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.