Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, January 6, 2016 <br />Page 8 <br />At the request of Member Murphy, Mr. Lloyd advised that lighting restrictions would be <br />356 <br />addressed as part of future design standards restricting minimal bleed (e.g. parking lot <br />357 <br />and exterior building lighting) from the property line, at the standard 0.50’ candle. <br />358 <br />At the request of Member Murphy, Mr. Lloyd addressed stormwater runoff for an HDR <br />359 <br />structure occupying the majority of this parcel’s footprint, based on preliminary review at <br />360 <br />this point. Mr. Lloyd noted that stormwater was currently robust in this area and as with <br />361 <br />any development, would be held to current high standards for stormwater mitigation <br />362 <br />before flowing into the public system. As noted by Chair Boguszewski, Mr. Lloyd <br />363 <br />confirmed that the city had not received any detailed plans at this concept point and <br />364 <br />reiterated that they would not be part of this request anyway. Mr. Lloyd noted that he <br />365 <br />would be surprised if the development team hadn’t done some preliminary studies up to <br />366 <br />this point, but none had been submitted to the city at this concept stage. After <br />367 <br />submission, Mr. Lloyd noted that the plans would need approval of the city as well as <br />368 <br />applicable watershed district before proceeding further. <br />369 <br />As previously noted, Chair Boguszewski reminded the commission that that information <br />370 <br />was not part of this application request and any decision was not related to any project <br />371 <br />specifics or effects anyway. <br />372 <br />At the request of Member Murphy, Mr. Lloyd addressed the application process and 60- <br />373 <br />day review period, with the city able to extend that review period if the commission <br />374 <br />determined it needed further information before rendering their judgment (e.g. traffic <br />375 <br />study), ideally completed in time for the February 2016 commission meeting. <br />376 <br />In recognizing the existing Midland Grove access point, Member Stellmach questioned if <br />377 <br />that was the only viable access point for a new development, noting the existing driveway <br />378 <br />shown on the displayed map directly off County Road B and whether a new development <br />379 <br />could utilize that access. <br />380 <br />Mr. Lloyd responded that access onto a county roadway would be under the control of <br />381 <br />Ramsey County, and based on past experience, he anticipated the county would be <br />382 <br />reluctant to allow more driveways coming onto County Road B, especially with the <br />383 <br />proximity to a major intersection, and particularly for anything more than a single-family <br />384 <br />use. <br />385 <br />Mr. Paschke responded that even if a single-family development that had been <br />386 <br />considered by the city at one point in the past, Ramsey County would not be inclined to <br />387 <br />allow another separate access point or public road accessing County Road B, requiring a <br />388 <br />shared access for any future development. <br />389 <br />Mr. Bull opined that grading for a road the drop in that area may be prohibitive for an <br />390 <br />access at that suggested point anyway. <br />391 <br />Chair Boguszewski opined that he suspected Ramsey County would give that potential <br />392 <br />access point no consideration at all. <br />393 <br />In his visit with the City’s Public Works staff earlier today, Member Daire reported that <br />394 <br />they had confirmed that Ramsey County had been adamant regarding any additional <br />395 <br />access onto County Road B and their intent to channel access to avoid vehicles turning <br />396 <br />right and/or left and potentially crossing over traffic lanes and creating traffic issues in <br />397 <br />that area. <br />398 <br />Mr. Lloyd confirmed that staff had hear similar comments back from MnDOT that <br />399 <br />specified no access to their rights-of-way as well. <br />400 <br />Applicant Representatives <br />401 <br />th <br />Dan Paulson UCC Weekly Update, Developer Partner with JAH, LLC, 4941 129 <br />402 <br />Street N, Hugo, MN 55038 <br />403 <br />Chair Boguszewski welcomed the development team and asked that they talk about <br />404 <br />where they were at currently in the development and planning process beyond their <br />405 <br /> <br />