My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Business Retention and Development Committee Agenda and Packet 2018 04 02
PORTAL
>
BOARDS COMMISSIONS COMMITTEES RECORDS (20.000)
>
BUSINESS RETENTION & DEV COMMITTEE
>
2006-2019 Business Retention and Development Committee Agendas and Packets
>
2018 Business Retention and Development Committee Agendas and Packets
>
Business Retention and Development Committee Agenda and Packet 2018 04 02
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/10/2021 2:09:39 PM
Creation date
4/10/2018 12:33:25 PM
Metadata
Fields
Template:
City Council Records
Doc Type
Boards Commissions Committees Records
Supplemental fields
Test
BRADPKT 2018 04 02
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
26
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
e. Operational compatibility, such as lighting, hours of operation, odors, noise, litter, <br />or glare. <br />Similar to Arvada, in Erie, the applicant notices and facilitates the neighborhood <br />meeting. Staff attendance is not required, but may be required by the Community <br />Development Director "only for the purpose of explaining the application process." <br />Pros and Cons of a Neighborhood Meeting Process <br />Pros: A neighborhood meeting provides the opportunity for the developer to hear the <br />public's concerns before an application is submitted. Ideally, the public comments better <br />shape the proposal. <br />Cons: Unless attended by Planning Staff, the applicant may skew or misrepresent the <br />public comments. Some applicants may not be well versed in the development review <br />process or application of the Code requirements. Thus, the applicant may misrepresent <br />City policy and process to the public. Staff attendance at neighborhood meetings will <br />result in more night meetings for staff. However, if neighborhood meetings are only <br />required for certain, more complex applications, the number of neighborhood meetings <br />may be minimal. <br />Early public engagement in the form of neighborhood meetings could be beneficial for <br />more complex applications, but it is Staff's opinion that these processes should not be <br />required for all development applications. If a neighborhood meeting process is <br />considered by Council, staff suggests that City staff attend these meetings. <br />Sketch Plan <br />A sketch plan could provide for review of a conceptual plan with non-binding comments <br />from the Planning Commission and/or City Council. There are several paths to consider <br />for sketch plans: <br />1. A sketch plan could be required for certain applications (e.g., based on property <br />size, density, or uses) or it could be optional. <br />2. A sketch plan could be reviewed by Planning Commission and City Council. <br />3. A sketch plan could only be reviewed by Planning Commission, with an option for <br />Council to call it up or for the applicant to request Council review. <br />Sketch plans applications typically require a conceptual plan which shows and <br />demonstrates the proposed uses and density, layout of lots, proposed building <br />locations, layout of major access points and an internal street network, and the <br />proposed location of utilities and other infrastructure. The process should outline the <br />specific and limited feedback that the Planning Commission and City Council can <br />provide through the process, since formal public hearings will be held at a later date. <br />Depending on the level of detail required or the complexity of the application, the <br />process could require a traffic study. Considering the elevated concern regarding traffic <br />in the City, staff suggests any sketch plan process include a preliminary traffic impact <br />
The URL can be used to link to this page
Your browser does not support the video tag.