My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
04-19-2006
MoundsView
>
Commissions
>
Planning & Zoning Commission
>
Agenda Packets
>
2000-2009
>
2006
>
04-19-2006
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/30/2018 10:15:38 AM
Creation date
8/30/2018 10:02:41 AM
Metadata
Fields
Template:
MV City Council
City Council Document Type
City Council Packets
Date
4/19/2006
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
73
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
ED Report <br />April 19, 2006 <br />Page 2 <br /> <br />1. Maximize the Increment. If no changes are made to TIF policies, the City anticipates <br />collecting approximately $14.6 million in non-obligated TIF increment over the course of the <br />next ten years from the three original TIF districts, which expire in 2013 (District 1), 2015, <br />(District 2) and 2014 (District 3.) These three original districts were set up as 25-year districts. <br />The collected increment from these three districts represent “pooled” increment which can be <br />spent on a variety of TIF eligible items anywhere in the “development district.” The <br />development district, according to the TIF plans, represents the entirety of the City. Thus, the <br />pooled increment (totaling $14.6 million) may be spent anywhere in the City so long as the <br />expenditure is deemed TIF eligible. (Later in this report the Commission will find a list of <br />potential expenditures.) There are presently three TIF obligations remaining in the City, one <br />from each district: The Mermaid TIF note (pays off in 2013) from District 1, the Silver Lake <br />Pointe project (pays off in 2011) from District 2, and the recently authorized SYSCO TIF note <br />(pays off in 2008) from District 3. A fourth obligation from District 1 is inactive, that being the <br />TIF note for Building N, which presently generates no property taxes as it is owned by <br />Bethlehem Baptist Church (BBC) and is tax exempt. <br /> <br />If no changes are made to our existing TIF districts, the amount of Market Value Tax capacity <br />captured in Mounds View TIF districts is 16.29 percent. Factoring in the Medtronic <br />development and its projected $96 million market value, the amount of the City’s tax capacity <br />captured in TIF districts will rise to 22.32 percent. <br /> <br /> <br />2. Reduce the Increment. The City could act to reduce the amount of increment collected <br />by a fixed amount or by a percentage. This could be accomplished in a number of ways, <br />such as: <br /> <br />a. Decertify a district early. District 3 would be the best candidate for this action. If done, <br />the amount of tax capacity captured in TIF districts would decrease from 22.32 percent <br />to 19.51 percent. <br />b. Selectively decertify parcels within districts. The City did this in 2004 when it <br />decertified approximately 81 parcels representing 10% of the captured tax value. <br />c. Change the fiscal disparities election for the existing districts. This option would <br />decrease the amount of tax capacity captured in TIF districts from 22.32 percent to <br />16.52 percent <br />d. Turn back a set amount of non-obligated pooled increment to the appropriate taxing <br />authorities. This option retains flexibility for future increments collected. On an annual <br />basis, the City could elect to “turn back” any budgeted yet unexpended non-obligated <br />increment to the proper taxing jurisdictions. <br /> <br />There may be other mechanisms by which increment may be reduced, however the four <br />noted above are the most obvious. Options A and B would be permanent solutions, while <br />Option C and D could be reversed or scaled back as needed. <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.