My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 12/07/2017
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2017
>
Agenda - Planning Commission - 12/07/2017
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:29:18 AM
Creation date
12/28/2017 8:47:52 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
12/07/2017
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
271
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
Zoning Bulletin October 10, 2017 I Volume 11 I Issue 19 <br />requires developers to pay impact fees before the City approves a <br />development project. Those impact fees are designed to defray antici- <br />pated increased city expenditures caused by the proposed development, <br />including increased expenditures for roads, water services, police <br />protection, storm water infrastructure, and sewer services. Utah's <br />Impact Fees Act regulates the manner in which cities may assess and <br />spend such impact fees. (See Utah Code §§ 11-36a-101 to -705.) <br />Various developers (the "Developers") paid impact fees to the City <br />between 2003 and 2006. In 2012, the Developers sued the city. They al- <br />leged that the City violated the Impact Fees Act by failing to spend or <br />encumber all of the impact fees within six years of collection (see Utah <br />Code § 11-36a-602(2)(a)), and by spending portions of the impact fees <br />on impermissible uses (see Utah Code § 11-36a-602(1)). The Develop- <br />ers argued that those violations of the Impact Fees Act constituted "a <br />taking of private property for public use without just compensation" in <br />violation of the Fifth and Fourteenth Amendments to the U.S. Constitu- <br />tion because: (1) any violation of the Impact Fees Act by the City also <br />constituted a per se violation of the takings clause; and (2) the City's <br />failure to spend all of the impact fees on statutorily mandated expendi- <br />tures within six years violated the United States Supreme Court's un- <br />constitutional conditions doctrine requiring monetary exactions in <br />exchange for a land use permit have an essential nexus and rough <br />proportionality between the amount of money requested and the social <br />cost of the proposed development. <br />The Developers also asserted that the City's violations of the Impact <br />Fees Act gave the Developers an "equitable" right to reimbursement of <br />the impact fees they had paid. <br />The City filed a motion to dismiss the Developers' claims. The district <br />court denied the City's motion to dismiss. <br />The City appealed. <br />DECISION: Judgment of district court reversed, and matter <br />remanded. <br />The Supreme Court of Utah determined that the Developers' claims <br />failed, and directed that the district court dismiss them on remand. <br />In dismissing the Developers' takings clause claims for "failure to <br />state a takings claim for which relief can be granted," the court first <br />explained that the Fifth Amendment of the United States Constitution <br />provides that "[p]rivate property [shall not] be taken for public use <br />without just compensation." The takings clause is applied against States <br />through the Fourteenth Amendment, and encompasses physical takings <br />and regulatory takings. Next, the court rejected the Developers' argu- <br />ment that any violation of Utah's Impact Fees Act was a per se violation <br />of the takings clause of the United States Constitution, noting that it is <br />the courts and not the legislature that establish "the bounds of protec- <br />© 2017 Thomson Reuters 9 <br />
The URL can be used to link to this page
Your browser does not support the video tag.