My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
R2010-167 RECEIVING AND FILING PROPOSED REDEVELOPMENT AGREEMENT
COD
>
City Clerk
>
RESOLUTIONS
>
2010
>
R2010-167 RECEIVING AND FILING PROPOSED REDEVELOPMENT AGREEMENT
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/6/2015 10:29:40 AM
Creation date
10/6/2015 10:29:37 AM
Metadata
Fields
Template:
Resolution/Ordinance
Res Ord Num
R2010-167
Res Ord Title
RECEIVING AND FILING PROPOSED REDEVELOPMENT AGREEMENT
Approved Date
9/20/2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
36
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
T <br /> r <br /> 1 c <br /> obligations, agreements, conditions, or restrictions, ar deprive or limit the City of or with <br /> respect to any rights or remedies or controls with respect to the Project or the <br /> construction thereof; it being the intent of this, together with other provisions of this <br /> Agreement, that (to the fullest extent permitted by law and equity and excepting only in <br /> the manner and to the extent specifically provided otherwise in this Agreement) no <br /> transfer of the Project, a Phase (or any portion thereofl, or any interest therein, however <br /> consummated or occurring, and whether voluntary or involuntary, shall operate legally or <br /> practically, to deprive or limit the City of any rights or remedies or controls regarding the <br /> Project and the construction thereof that the City would have had, had there been no such <br /> transfer. No such transfer shall be deemed to transfer any rights of the Redeveloper to <br /> the reimbursements set forth under Article IV above, unless such rights are expressly set <br /> forth in the instrument of assignment. <br /> 9.3 Status of Assignee. Any assignee of the Redeveloper prior to Substantial Completion, <br /> who is approved under the terms of 9.1 above, shall be considered the "Redeveloper" for <br /> all purposes of this Agreement as to such portion of the Project that has been assigned. <br /> 9.4 Assignment to Affiliated Entity. Nothing herein shall be construed to prevent the <br /> Redeveloper from assigning its interest in this Agreement to an affiliated entity owned or <br /> controlled by the Redeveloper or a majority of the owners of the Redeveloper, provided <br /> that such entity has the financial capacity to perform the obligations of the Redeveloper <br /> pursuant to this Agreement(though the City may not receive any more financial capacity <br /> than that possessed by the Redeveloper on the date hereo fl and such entity in writing <br /> assumes such obligations and conditions in compliance with the terms and conditions set <br /> forth in Section 9.1.2(a)through (d)of this Agreement. <br /> 9.5 No Release of Redeveloper. Any consent by the City to any total or partial transfer of <br /> the Project or the Project Site shall not be deemed a release of the Redeveloper from any <br /> of its obligations hereunder, or from any conditions or restrictions to which the <br /> Redeveloper is subject, unless the Redeveloper is expressly released in writing by the <br /> City. <br /> ARTICLE X: DEFAULT AND REMEDIES <br /> 10.1 Events of Default. The following shall be events of default (the "Events of Default") <br /> with respect to this Agreement: <br /> 10.1.1 Misrepresentation. lf any material representation made by the Redeveloper or <br /> the City in this Agreement, or in any certificate, notice, demand or request made <br /> by the Redeveloper or the City in writing and delivered to the other party <br /> pursuant to or in connection with any of said documents shall prove to be untrue <br /> or incorrect in any material respect as of the date made; or <br /> 10.1.2 Breach. Breach by the Redeveloper or the City of any material covenant, <br /> warranty or obligation set forth in this Agreement. <br /> 10.2 Remedies Upon Default. In the case of an Event of Default by either party hereto or any <br /> successors to such party, such party or successor shall, upon written notice from the other <br /> party, take immediate action to cure or remedy such Event of Default within sixty (60) <br /> days after receipt of such notice (or within a reasonable time if the Event of Default <br /> City of Decatur/Slumberland Redevelopment Agreement 16 <br />
The URL can be used to link to this page
Your browser does not support the video tag.