My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01-23-17 Zoning and Annexation
sbend
>
Public
>
Common Council
>
Minutes
>
Committee Meeting Minutes
>
2017
>
Zoning and Annexation
>
01-23-17 Zoning and Annexation
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/25/2017 10:57:17 AM
Creation date
4/25/2017 10:57:15 AM
Metadata
Fields
Template:
City Council - City Clerk
City Council - Document Type
Committee Mtg Minutes
City Counci - Date
1/23/2017
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
16
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).
Show annotations
View images
View plain text
owner of the project. Mr. Smoke stated, I am pleased to say that we have worked with various <br /> landowners and governments in the pursuit of healthy, sustainable developments within our <br /> region and, specifically, in downtown South Bend. Our projects range from brown field <br /> development sites, like Ignition Park, to rehabbing one-hundred (100) year old buildings, like the <br /> JMS building downtown. We are proud to work with the Waggoner family to help facilitate our <br /> shared and comprehensive vision of a well-designed and attractive park for companies to call <br /> home. The first phase of this project will be home to a global company that has operations in <br /> South Bend, currently. They want to keep their three-hundred(300) employees here and then an <br /> additional one-hundred (100)jobs. Since the APC meeting, we have made several compromises <br /> to move it closer to the highway. This will allow for as much buffering in landscape screening as <br /> possible. In order to address any concerns about traffic we've also heard, we reached out to the <br /> City Engineer. I'm looking forward to working with them. <br /> Committeemember Broden asked, What is the company's current location? <br /> Mr. Smoke responded, They are near the airport. <br /> Committeemember Broden stated, A lot of concerns have been brought up about truck traffic on <br /> Mayflower and Adams. Has anyone actually looked at traffic studies, or conducted traffic <br /> studies—looking at Mayflower and Adams and whether or not the existing businesses to the <br /> south are complying with entering and exiting on Dylan versus Mayflower? In other words, <br /> minimizing the truck traffic. <br /> Mr. Smoke responded, Currently,truck traffic on Adams and Mayflower is not allowed. Our <br /> proposal is to only have truck traffic come south on the Dylan extension—over Adams, down <br /> south through Dylan. <br /> Committeemember Broden asked, So,no studies or tracking of trucks? <br /> Mr. Smoke responded, We have not done that. We have reached out to the City engineer and <br /> they are working with us on addressing that, but no formal study has been done. <br /> Committeemember Voorde asked, Lot B—further to the north: will that be accessible, if and <br /> when it is developed, by an extension of what looks like Dylan Drive? <br /> Mr. Smoke responded, Correct. There would be a plan for it to flow through the rest of the park. <br /> Mr. McMorrow added, The alignment we are showing here is consistent with the alignment that <br /> was in the PUD with one exception: it is fifty(50) feet further to the west than was anticipated <br /> before, so that north-south extension that extends Dylan is fifty (50) feet further west. <br /> Committeemember Davis asked for an update on developer communication with neighbors. <br /> Mr. Smoke responded, I reached out to several of the people who came to the initial meeting. I <br /> had lunch with Mr. Nicholas. We are working with him in either acquiring the parcel or, as an <br /> alternative, adding the extra layer of evergreen trees and a privacy screen going up <br /> 13 <br />
The URL can be used to link to this page
Your browser does not support the video tag.