My WebLink
|
Help
|
About
|
Sign Out
Home
2014-10-08_PC_Agenda
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Agendas and Packets
>
2014 Agendas
>
2014-10-08_PC_Agenda
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/22/2016 12:13:02 PM
Creation date
4/22/2016 12:12:56 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.
/
31
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, September 3, 2014 <br />Page 2 <br />Member Boguszewski reviewed subdivision typesfrom section to section on the <br />46 <br />displayed table, noting that it became apparent that each type successively required a <br />47 <br />greater degree of administrative analysis and oversight, with clear distinctions for an <br />48 <br />applicant to follow.Member Boguszewski opined that he found no real distinctions in <br />49 <br />requirements of type 1 or 2 subdivisions unlessburied in the details and therefore <br />50 <br />questioned why the distinction. <br />51 <br />Mr. Lloyd responded that there were no other distinctions buried in the details, and <br />52 <br />Member Boguszewski’s question was reasonable for discussion.Mr. Lloyd advised that <br />53 <br />the main distinction was that type 1 subdivisions are reserved for single-family <br />54 <br />homeowners, and the process less expensive with Ramsey County to seek revised legal <br />55 <br />descriptions and new deeds.However, for type 2 subdivisions, requiring a plat, Mr. Lloyd <br />56 <br />advised that the process was for administrative review and potential approval was not <br />57 <br />much different between the type 1 and type 2 plats beyond documentation requirements <br />58 <br />for recording purpose with Ramsey County.Mr. Lloyd advised that practical ramifications <br />59 <br />over time included the long and confusion metes and bounds legal descriptions versus a <br />60 <br />more simplistic legal description with a plat. <br />61 <br />At same time, Mr. Lloyd noted that the “on ground”impact may not be that different <br />62 <br />betweensubdivision types 1 and2, with a simple understanding of lot and block <br />63 <br />numbers,but not providing property boundaries unless iron monuments can be found <br />64 <br />and verification that those monuments are actually located in the correct place, otherwise <br />65 <br />requiring the services of a land surveyor.Mr. Lloyd advised that the intent of the <br />66 <br />proposed language was to indicate that type 1 subdivisions aresimpler and less <br />67 <br />expensive to accomplish; and whether for multi-familyor business properties, the plat <br />68 <br />process didn’t necessarilyincrease expensesproportionately,but resulted in something <br />69 <br />simpler over time. <br />70 <br />Based on his understanding of the revisions themselves, Member Boguszewski sought <br />71 <br />verification that there were simply a lot of details in current code that were proposed to be <br />72 <br />removed from this section; not lost, but covered in other parts of code, thereby simplifying <br />73 <br />the subdivision code.Member Boguszewski questioned if those changes included any <br />74 <br />changes in the level of burden or cost or administrative oversight; in other words, was the <br />75 <br />revision a simplification and clarification, or did the displayed table also represent a shift <br />76 <br />between what is in various sections and subdivision types. <br />77 <br />Mr. Lloyd responded that the intent was to ease the review and approval process for <br />78 <br />minor subdivisions without the need for aformal public hearing at the Planning <br />79 <br />Commission orCity Council level; but via an administrative hearing and approval process <br />80 <br />due to those simpler and smaller scale applications not involving any deviations from <br />81 <br />standard requirements, and limiting the area of impact versus larger proposals. <br />82 <br />Mr. Lloyd advised that the expectations for applicants in any of the subdivision types <br />83 <br />would be more appropriately addressed as part of the application forms and process, in <br />84 <br />detail, but not changing that process as part of the subdivision code itself.Mr. Lloyd <br />85 <br />advised that is the Planning Division’s goal to work with the Public Works Department to <br />86 <br />move metrics more sensibly into the part of the code to which they apply (e.g. <br />87 <br />engineering or land use); and for those not smaller subdivisions not involving any zoning <br />88 <br />or other code changes or review.Mr. Lloyd clarified that, as usual, plan documents would <br />89 <br />need to be provided for Preliminary and/or Final Plat approvals as part of the application <br />90 <br />process, but without the subdivision code actually dictating the format of the plat <br />91 <br />(compass directions) or how the plats are scales to a certain level.Mr. Lloyd advised that <br />92 <br />those details and requirements would be carried forward to the application forms <br />93 <br />themselves, allowing for periodic changes to the application forms versus the entire <br />94 <br />subdivision code by ordinance. <br />95 <br />At the request of Member Boguszewski, with additional administrative approval or denial, <br />96 <br />Mr. Lloyd confirmed that the standard appeal section would be incorporated intothe <br />97 <br />subdivision code, allowing recourse for the applicant or any other party before the Board <br />98 <br />ofAdjustments (City Council). <br />99 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.