My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 1995/05/01
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
1990-1999
>
1995
>
Agenda Packets - 1995/05/01
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:47:41 PM
Creation date
7/2/2018 2:19:22 PM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
5/1/1995
Supplemental fields
City Council Document Type
City Council Packets
Date
5/1/1995
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
137
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).
Show annotations
View images
View plain text
MEMORANDUM <br /> TO: Jim Thomson • <br /> FROM: Charlie LeFevere <br /> DATE: March 21, 1995 <br /> RE: City of Mounds View Proposed Assessment Policy Statement <br /> I have reviewed the draft Assessment Policy Statement for the City of Mounds View and offer <br /> the following comments. <br /> The last two sentences of section I, C, second paragraph, state: "It is important to recognize the <br /> actual cost of extending an improvement past a particular parcel is not the sole determining factor <br /> in determining the amount to be assessed. An exception might be a project initiated by a single <br /> property owner/developer where market value increase may not be a relevant factor given the <br /> nature of the improvement." I am not sure what was intended by this language. However, for <br /> special assessments to be constitutionally permissible, they must be supported by an increase in <br /> fair market value which is at least equal to the amount of the assessment. To that extent, <br /> increase in market value is always a relevant factor in special assessments. Therefore, I would <br /> recommend that these sentences be deleted. As an alternative, it may be that this language is <br /> intended to state a principal which I do not fully understand. Therefore, it may be that, following <br /> discussions with city staff about the intent of the language, appropriate modifications could be <br /> made to express that principal without conveying the idea that fair market value increase is not <br /> relevant in projects initiated by a single property owner. <br /> The last sentence of the following paragraph states "For example, the use of a front foot <br /> assessment for some properties and the use of a per lot assessment for other properties of the <br /> same class for a related improvement could result in a non-uniform assessment rate which could <br /> mean the assessment would be set aside or could be thrown out by the courts." I am not sure <br /> what was intended by the words "related improvement". There is no general rule which would <br /> prevent the city from using different assessment formulas for different projects, as long as each <br /> of the formulas was reasonably related to the increase in fair market value resulting from the <br /> improvement. However, I would agree that it would be a problem to use different formulas for <br /> the same class of property for one improvement project. I believe that this language would be <br /> more clear if the words "a related improvement" were changed to "the same improvement". <br /> Section I, D, 1 provides, in the last sentence, that the city must still follow all statutory <br /> provisions related to the local improvement process. This is not altogether accurate. The city <br /> charter, section 8.02, provides that all local improvements shall be carried out exclusively under <br /> the provisions of the charter. Section 8.03 provides that the city council shall adopt ordinances <br /> relating to special assessments and that after the adoption of such ordinances, all procedures shall <br /> CLL85803 1 <br /> MU125-19 <br />
The URL can be used to link to this page
Your browser does not support the video tag.