My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
07-08-15-PC
ArdenHills
>
Administration
>
Commissions, Committees, and Boards
>
Planning Commission
>
Planning Commission Packets
>
2010-2019
>
PC Packets 2015
>
07-08-15-PC
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/13/2015 1:06:58 PM
Creation date
8/13/2015 12:32:19 PM
Metadata
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.
/
419
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 of Arden Hills <br />Planning Commission Meeting for July 8, 2015 <br /> <br />P:\Planning\Planning Cases\2015\PC 15-015 - TCAAP CPA & TRC\Memos_Reports <br />Page 4 of 7 <br /> <br />It should be noted that the proposed Comprehensive Plan Amendment (CPA) will be contingent <br />on final approval from the Metropolitan Council. In this case, the Metropolitan Council will <br />make the final determination on the CPA, though they provide great deference to the City as long <br />as the proposed land use change does not have a negative impact on a regional system (i.e. <br />transportation, sanitary sewer, and regional parks). The designated review period for CPA <br />applications is 60 days. Once the Metropolitan Council completes their review, they will notify <br />the City of their decision. <br /> <br />The City must also allow adjacent governments, affected special districts, and affected school <br />districts up to 60 days to review the proposed amendment. This waiting period allows interested <br />agencies to review and comment on the amendment before the Metropolitan Council review. <br />Given these requirements, the City expects to receive the final determination from the <br />Metropolitan Council for the Comprehensive Plan Amendment in November of 2015. <br /> <br /> <br />TCAAP Property Rezoning <br /> <br />The second component of Planning Case 15-015 is the rezoning of the 427 acre TCAAP parcel, <br />based on the Regulating Plan (Attachment K) that has been included in the TCAAP <br />Redevelopment Code (TRC). The zoning districts depicted on the Regulating Plan for different <br />areas within the TCAAP site will be incorporated within the City’s official Zoning Map. While <br />the Comprehensive Plan Amendment will lay out the proposed future land uses for the TCAAP <br />property, the revised Zoning Map will identify the specific zoning districts through which the <br />land uses and goals for the TCAAP redevelopment will be implemented. <br /> <br />The City is proposing rezoning the property from Mixed Business and Mixed Residential to <br />Campus Commercial, Civic/Open Space, Flex Office, Retail Mixed Use, NR-1 Residential, NR- <br />2 Residential, NR-3 Residential, NR-4 Residential, Neighborhood Transition, Office Mixed Use, <br />Open Space, Town Center, and Water Infrastructure. The proposed rezoning of the TCAAP <br />property is consistent with the land use designations for the site as identified in the proposed <br />Future Land Use Map. <br /> <br /> <br />TCAAP Redevelopment Code (TRC) <br /> <br />The TCAAP Redevelopment Code (TRC) establishes the development and design regulations for <br />the 427 acre TCAAP property owned by Ramsey County (Attachment J). This document will <br />implement the community’s goals and visions for the redevelopment site as outlined in the <br />Comprehensive Plan Amendment. The regulations contained within the TRC are meant to <br />promote functional and attractive development through the use of recognized community design <br />principles. While the TRC prescribes a higher level in detail in building design and form, the <br />code also allows property owners and developers greater flexibility in land use and development <br />parameters.
The URL can be used to link to this page
Your browser does not support the video tag.