My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
08-08-05
ArdenHills
>
Administration
>
City Council
>
City Council Packets
>
2000-2009
>
2005
>
08-08-05
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/17/2012 10:46:46 AM
Creation date
11/14/2006 4:25:15 PM
Metadata
Fields
Template:
General
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.
/
292
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 />City Hall/Public Works Site Purchase Agreement Discussion <br />August 1,2005 <br />Page 2 of2 <br /> <br />. <br /> <br />. <br /> <br />I) Do Nothing Option: <br />This is always an option but appears to be against the Council's objective of <br />liquidating the property. The City has spent a considerable amount of money in <br />enviromnental analysis of the property, wetland delineation, establishment of building <br />demolition issues and an appraisal of the property. In addition, because of the past <br />planning action, the site and design issues have been specifically identified, albeit no <br />final resolution to the issues were completed. <br /> <br />2) Renegotiate with Roval Oaks: <br />This appears to be the most straight forward option and one that could be acted on <br />and completed by the spring of 2006. If the Council desires to proceed with this <br />option, direction should be agreed upon as to whether a new appraisal should be <br />ordered and the level of specificity within a new agreement. Most purchase <br />agreements are written with the end use of the property generally described. Since <br />the City has undergone hours of public testimony, had Planning Commission review <br />and in-depth technical review of the site, one option would be to write into the <br />purchase agreement specifics such as allowable street access, signage, square footage <br />of buildings and other considerations. This may appear to take away from the <br />planning process, but as stated previously, all issues have bcen raised and discussed. <br />The last comment is iflesser building square footage is allowed, the developer will be <br />asking for a lower purchase price. <br /> <br />3) Start a New Sale Process: <br />If the Council seeks this direction, a key question will be the acceptable uses for the <br />property. Based on the past planning application there was an agreement not to allow <br />retail or restaurants. If this perspective remains, the list of acceptable uses that the <br />City could submit, with a request for proposal to the dcvelopment/broker community, <br />will be very limited. The other major question on request for proposals is whether the <br />City will allow a company to submit a proposal "to act" as a broker on the property <br />for a period of time. Most developers/brokers do not have a project "in hand" that <br />could immediately be built on the property, so they will seek timc to put a project <br />together. The results could mean a sale and dcvelopment in 2007. <br /> <br />Conclusion <br /> <br />. <br /> <br />If the Council's objective is to have a sale and development occur in 2006, staffrecommends <br />that the purchase agreement for Royal Oaks be renegotiated. The end land use appears to be <br />acceptable and the kcy issues will be renegotiation of a sales price if lesser square footage is <br />mandated, and finalizing site and design issues. The alternative, and potentially longer process, <br />appears to be a general request for proposal, or simple advertisement to the developer/broker <br />community, for a period of time to see what proposals could come forth. <br /> <br />l\EarthIPlanninglMisc FileslCily Hall-PW Sitelcouncil-purchase agreement discussion-August 8 200S.doc <br />
The URL can be used to link to this page
Your browser does not support the video tag.