My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CC WORKSESSION PACKET 06152021-JOINT WITH PLANNING COMMISSION
StAnthony
>
City Council
>
City Council Work Session
>
2021
>
CC WORKSESSION PACKET 06152021-JOINT WITH PLANNING COMMISSION
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/10/2021 4:13:28 PM
Creation date
6/10/2021 4:08:10 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
22
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
<br /> <br />(2) The City Council has specified all conditions which the City Council deems necessary to <br />make the use compatible with other uses in the area; <br />(3) The use will not be detrimental to the health, safety, or general welfare of persons <br />residing or working in the vicinity or to the values of property in the vicinity; and <br />(4) The use will provide a service or a facility which is in the interest of public convenience <br />and will contribute to the general welfare. <br /> <br />The subject property was bounded by multi-family residential on one side, and single family on <br />another. The ordinance imposes certain additional setback requirements in such <br />circumstances, but the applicant was able to comply with the specific zoning aspects of the <br />code. It was item (3) from the list above that raised the primary issue, as its requirements are <br />non-specific. The potentially vague nature of these requirements created an avenue for <br />opponents of the project to raise a variety of potential issues. <br />It should be noted that the requirements in item (3) are the general standards applied to most <br />any zoning question – they reflect the powers of local government to ensure that land uses, <br />while utilizing property in a legal manner, minimize infringement on the rights of neighboring <br />landowners – often called “police powers”. <br />In applying these standards, the City is constrained by a long history of legal challenges to <br />decision-making on zoning questions, and specifically on Conditional Use Permit applications. <br />The general rule is that a Conditional Use is one that is presumed to be allowed on land in the <br />zoning district in which the CUP is proposed. Conditional uses are distinguished from Permitted <br />Uses in that Permitted Uses are allowed by right, whereas Conditional Uses are expected to <br />create additional impacts beyond those in the permitted class, and which require specific <br />attention to avoid extraordinary negative impacts. <br />In this regard, the City can add conditions to a proposed CUP to mitigate those anticipated <br />impacts. The conditions are required to be relevant to specific aspects of the use, and cannot <br />be unreasonably or arbitrarily assigned as a pretext in lieu of an out and out denial. <br />If the applicant is able to demonstrate that they can meet those reasonable conditions <br />identified by the City, then the City is usually bound to approve the CUP. <br />The other aspect of CUP review is a burden on the opponents of a project. Opponents may <br />raise questions and objections, but their objections must be based in fact for the City to use <br />them as a basis for denial. They may not be speculative or mere opinion. The City may not <br />base a denial on mere neighbor opposition, no matter how overwhelming. But if the project <br />opponents can enunciate factual conditions that violate the elements of item (3) – and the <br />applicant is unable or unwilling to mitigate those conditions - they may form the basis for a <br />denial. <br />There are a couple of other paths for the City to consider as a part of this discussion. One <br />option is to list more specifically the various types of conditions that a CUP will be held to.
The URL can be used to link to this page
Your browser does not support the video tag.