My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
11-13-17 Zoning and Annexation
sbend
>
Public
>
Common Council
>
Minutes
>
Committee Meeting Minutes
>
2017
>
Zoning and Annexation
>
11-13-17 Zoning and Annexation
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/23/2018 9:12:15 AM
Creation date
1/23/2018 9:12:13 AM
Metadata
Fields
Template:
City Council - City Clerk
City Council - Document Type
Committee Mtg Minutes
City Counci - Date
11/13/2017
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
6
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
With no other members of the public wishing to speak, Committee Chair Davis then turned the <br /> floor back to the petitioner for a rebuttal. <br /> Ms. Smith replied, The ordinance for outdoor seating actually requires they not interfere with the <br /> sidewalk right of ways. So that is in the ordinance but it sounds like it might be an enforcement <br /> issue. <br /> Committee Chair Davis then turned the floor back to the Committee for further comment or main <br /> motion. <br /> Committeemember Broden made a motion to send Bill No. 17-72 to the full Council with a <br /> favorable recommendation. Committeemember Gavin Ferlic seconded this motion which carried <br /> unanimously by a voice vote of three (3) ayes. <br /> Committeemember Ferlic then made a motion to hear together Bill No. 73-17 and 74-14 for <br /> purposes of presentation and public hearing. Committeemember Broden seconded this motion <br /> which carried unanimously by a voice vote of three (3) ayes. <br /> Bill No. 73-17- Zoning Text Amendment pertaining to Engineering Standard <br /> Bill No. 74-17-Zoning Text Amendment pertaining to Pyramiding Uses <br /> Ms. Smith stated, The first ordinance deals with things related to engineering. This was in <br /> conjunction with the Building Department,the Department of Community Investment,the Area <br /> Plan Commission and the Engineering Department. The first provision deals with the clear sight <br /> triangle. One (1) change exempts the Central Business District. We allow buildings to go all the <br /> way to a zero (0) foot setback and the required site triangle needs to be counter-intuitive. We <br /> have wide sidewalks in downtown and there really isn't an issue. It would also reduce the <br /> twenty-five (25) foot clear sight area at the intersections to ten(10) feet. We recently learned <br /> from the Indiana Department of Transportation(INDOT)that this is the standard they use in <br /> urban areas. Because of reduced road speeds and wider walkways,this makes sense. We also <br /> discovered that many of our private streets and alleys are wider than what we are currently <br /> putting in throughout the Smart Streets efforts. It seems silly to have people over-pave their <br /> areas. Right now we require five (5)waiting spaces for cars behind the drive through, whether it <br /> is a restaurant or bank. The five (5) spaces is way more than most people need. We did add <br /> provisions to make sure it cannot interfere with any other parking or pedestrian ways. <br /> She continued, The other ordinance addresses why we have such explicitly defined uses in South <br /> Bend. There are so many specific zonings and sometimes people have to down-zone in order to <br /> do something with their property. We want to preserve districts and make sure owners aren't <br /> having to change back and forth. This is taking a closer look at, and aligning, the allowed uses as <br /> the zones change. It doesn't include the residential uses and doesn't include the Central Business <br /> District <br /> Committee Chair Davis then opened the floor to questions from the Committee and <br /> Councilmembers. <br /> 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.