My WebLink
|
Help
|
About
|
Sign Out
Home
2016-03-02_PC_Agenda_Packet
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Agendas and Packets
>
2016 Agendas
>
2016-03-02_PC_Agenda_Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/8/2016 4:29:30 PM
Creation date
4/8/2016 4:29:16 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Agenda/Packet
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
96
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
Regular Planning CommissionMeeting <br />Minutes –Wednesday, January 6, 2016 <br />Page 10 <br />anticipated staff would generate 44 trips/day to and from the site during a 24 hour period. <br />458 <br />Mr. Paulson displayed and referenced additional studies of such facilities indicated <br />459 <br />frequency of visitorsto residents varying from daily visitors and less frequency, equating <br />460 <br />to approximately 60 total trips in a 24-hour period, including the 44 trips per day by <br />461 <br />employees. <br />462 <br />At the request of Member Daire, Mr. Paulson spoke directly to the facility’s typical <br />463 <br />morning peak hour, opining that their staff turnover time would typically be between half <br />464 <br />of the employees arriving by 6:30 a.m. to serve the first meal of the day for residents, and <br />465 <br />the other five employees arriving at approximately 8:00 p.m. At the request of Member <br />466 <br />Murphy, Mr. Paulson noted that there may be Metro Mobility buses or taxis also <br />467 <br />accessing the site for resident appointments. Member Murphy opined that the daily <br />468 <br />estimated traffic to the site could considerably increase when other transportation needs <br />469 <br />were factored in across a day. <br />470 <br />Mr. Paulson reviewed some of the previous development proposals for this site <br />471 <br />compared to this concept, some higher density and one showing 11 single-family <br />472 <br />residential units, permissible under current zoning code, and based on current zoning <br />473 <br />maximizing the site area, noted that there could be the potential of as many as 16 <br />474 <br />residential units by code on the site.Mr. Paulson reviewed a U. S. Department of <br />475 <br />Transportation study done for this area in 2009, and national household travel survey and <br />476 <br />a summary of trends, indicating an average household generates 10 trips/day. Mr. <br />477 <br />Paulson opined that compared to this proposed use, that could have added 110 trips <br />478 <br />versus this high estimate of potentially 60 trips per day. <br />479 <br />Specific to stormwater issues raised by the commission, Mr. Paulson displayed the <br />480 <br />schematic site plan, advising that stormwater would be and was required to be managed <br />481 <br />on site. Mr. Paulson noted the intended use of a lower portion on the site with natural <br />482 <br />drainage already occurring that would allow for natural stormwater flow in that direction, <br />483 <br />and the developer’s intention to take advantage of that natural topography. <br />484 <br />Regarding trees and landscaping, Mr. Paulson assured the commission that both the <br />485 <br />developer and property owner were very sensitive to the mature trees on the site, <br />486 <br />intending at a minimum to retain those mature trees on the perimeter of the site and <br />487 <br />wherever possible, on the interior as well. Based on traditions of this management firm <br />488 <br />and their other operations, Mr. Paulson advised that their desire was to create homelike <br />489 <br />settings for their facilities, with that same intent to do so on this site and maintain as <br />490 <br />many mature trees as possible. Under city code, Mr. Paulson noted for those needing <br />491 <br />removed for construction and drainage, replacement would be at a 2/1 ratio. However, <br />492 <br />Mr. Paulson recognized the significant number of mature trees and their existing <br />493 <br />canopies, especially those buffering Midland Grove’s parking lot on the north side of the <br />494 <br />subject site, that will remain as part of this proposed development. <br />495 <br />Mr. Paulson addressed some of the concerns raised at the recent community <br />496 <br />informational meeting, specific to the parking lot abutting the north property line, currently <br />497 <br />at 17’ setback. Mr. Paulson advised that the developer intended to take the opportunity <br />498 <br />to create a landscape buffer with decorative fencing or a landscape berm that would <br />499 <br />shield headlights from that property to the north. <br />500 <br />Mr. Paulson displayed comparables with other developments by this firm, including <br />501 <br />Gracewood/White Pine Development in the Highland Park area of St. Paul, having similar <br />502 <br />zoning transitions with those seen in Roseville, with HDR transitioning into LDR, single- <br />503 <br />family residences. Mr. Paulson noted that the developer’s intent would be to create as <br />504 <br />minimal impact to surrounding neighborhoods as possible. Based on their experience <br />505 <br />with their other developments, Mr. Paulson concluded by stating they felt this particular <br />506 <br />Roseville site would also prove successful. <br />507 <br />Mr. Paulson reviewed other benefits to Roseville from this proposed development, <br />508 <br />including a significant increase to its tax base, the value of the services offered by this <br />509 <br />firm for assisted/memory care unmatched throughout the metropolitan area, and the <br />510 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.