Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, July 9, 2014 <br />Page 6 <br />service them. Mr. Lloyd advised that the difference in Type 1 and Type 2 was that Type 1 <br />246 <br />was similar to today’s minor subdivisions rather than plats, where a Type 2 would result <br />247 <br />in a plat and have more parts to it. <br />248 <br />At the request of Member Stellmach, Mr. Lloyd reviewed the current Public Hearing <br />249 <br />requirements for three or more lots coming first to the Planning Commission before <br />250 <br />proceeding directly to the City Council. For others requiring only a Metes and Bounds <br />251 <br />Subdivision process and how the plat related to surrounding section lines, Mr. Lloyd <br />252 <br />advised that it would require a Public Hearing held by the City Council on the same <br />253 <br />evening that they took action on it. <br />254 <br />Member Cunningham questioned, if someone came forward with a three home <br />255 <br />development under the new system approved administratively by staff and not coming <br />256 <br />before the Planning Commission, would there still be a mechanism in place for <br />257 <br />neighborhood objections or appeal at some level. <br />258 <br />Mr. Lloyd advised that the process would remain for appeals handled through the Board <br />259 <br />of Adjustments, a/k/a as the City Council, and heard in public forum. <br />260 <br />Member Stellmach questioned when, if and how notices would be provided to neighbors. <br />261 <br />Mr. Lloyd advised that for minor variances, proposed to be handled administratively, <br />262 <br />letters were now and would continue to be sent to surrounding properties seeking their <br />263 <br />feedback. While that is not represented in the proposed language for Type 1 or Type 2 <br />264 <br />subdivisions about providing written notification, it was done for other applications, and <br />265 <br />language could be added. <br />266 <br />Mr. Bilotta advised that, if the Planning Commission was more comfortable having that <br />267 <br />language included, it could be added. <br />268 <br />Consensus of the body was to include that language, following general notice <br />269 <br />requirements in place today, allowing for further review of that language as the document <br />270 <br />moves into its next iteration. <br />271 <br />At the request of Mr. Lloyd regarding which subdivisions triggered a Public Hearing at the <br />272 <br />Planning Commission or City Council level, Members concurred that they were not <br />273 <br />looking to have more cases brought before them beyond what was allocated today. <br />274 <br />Specific to general policy direction, Member Daire questioned how the proposed <br />275 <br />language would affect the workload of the Planning Commission and/or staff. <br />276 <br />Mr. Lloyd responded that he didn’t see things changing that much from the current code <br />277 <br />as written today; with the Planning Commission seeing subdivision and plat applications, <br />278 <br />with others going directly to the City Council as is also current practice. Therefore, in <br />279 <br />response to Member Daire, Mr. Lloyd opined that staff saw no substantive change in the <br />280 <br />volume of work. <br />281 <br />Member Keynan stated that he liked the way the new Subdivision Ordinance read, <br />282 <br />opining that it was much clearer to read. However, Member Keynan cautioned the need <br />283 <br />to be consistent with applications if the details were removed from the ordinance itself to <br />284 <br />ensure everything was included in the application across departments to strike a balance. <br />285 <br />In reading the proposed language, Member Keynan advised that he liked the intent, but <br />286 <br />worried about striking that balance to provide continuity and addressing the overall needs <br />287 <br />and intents. <br />288 <br />Mr. Bilotta noted that those things going into the application itself would be more nuts and <br />289 <br />bolts pieces, not policy level things which were addressed in subdivision regulations (e.g. <br />290 <br />how many copies an applicant needed to submit, size of document submittals and their <br />291 <br />format in electronic or paper versions, and number of plan sets needed for submission <br />292 <br />and in which AutoCAD version). Mr. Bilotta advised that by removing those details, it <br />293 <br />would avoid staff having to come back for annual updates to the Subdivision Ordinance. <br />294 <br /> <br />