My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2014-00540 - addn/remodel/repair
Orono
>
Property Files
>
Street Address
>
S
>
Shoreline Drive
>
3384 Shoreline Drive - Narrows
>
Permits/Inspections
>
2014-00540 - addn/remodel/repair
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/15/2023 7:19:49 AM
Creation date
12/11/2018 11:48:20 AM
Metadata
Fields
ProcessedPID
True
Tags
No PIN
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
17
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
#13-3615 <br /> November 21,2013 <br /> Page 5 <br /> The applicant's architect has calculated that the shared restroom facilities would meet <br /> building code requirements for the occupant load of the building. This has been confirmed <br /> by Building Official Lyle Oman. One comment received from the public indicated that <br /> restroom use at the Narrows can be difficult between sets. Lyle notes that the codes do not <br /> intend to account for such peak demands. <br /> Applicant has noted that ADA accessibility codes will require the installation of an elevator <br /> for use of the basement area. PC memo Exhibit I depicts three possible locations applicant <br /> is considering for elevator installation. <br /> D. Restaurant Operation. Applicant has indicated that the restaurant is planned to be open <br /> daily from 3:00 pm to 11:00 pm, but is requesting the ability for 8:00 am to 1:00 am in the <br /> event that breakfast/lunch is added on the weekends. Planning Commission discussed <br /> whether limiting hours of the outdoor restaurant seating would be appropriate, but did not <br /> make a specific recommendation. Applicant noted that currently food service stops at 10 <br /> pm on weekdays and 11 pm on weekends. <br /> The applicant noted that he has no intent to pipe live music from the Saloon operation to <br /> the outside seating areas, although he would potentially like to have speakers for soft <br /> dinner background music. It is worth noting that the double door system at the rear of the <br /> building should, if managed properly, avoid excessive Saloon music exiting the building. <br /> E. Potential Impacts on Surrounding Area. Planning Commission had asked that staff confer <br /> with the Police Department for an overview of any past noise and parking issues related to <br /> the current use of the site. Exhibit N of the 10/17 PC memo indicates no complaints have <br /> been received since 2006 specifically regarding noise or parking. <br /> The applicant notes that both outdoor seating areas are intended to have food service (and <br /> presumably alcoholic beverage service). The outdoor seating areas will need aggressive <br /> management to ensure they don't become problematic. <br /> F. Liquor Licensing. The applicant will be required obtain a separate liquar license for the <br /> Steak House restaurant use. Expansion of the Saloon to include outdoar food service <br /> seating may require a review of the existing Saloon liquor license. <br /> Staff Recommendation <br /> Staff recommends approval of the proposed restaurant use, noting that public input received <br /> formally and informally to date has been supportive. Appropriate conditions need to be placed <br /> on the additional use to ensure there are no negative impacts on the surrounding neighborhood <br /> and adjacent businesses. The two most significant apparent concerns that need to be managed <br /> are parking availability and potential noise/light/activity impacts to the neighborhood to the north <br /> across the parking lot. Council should address these concerns with the applicant and if Council <br /> determines they can be reasonably managed, then approval with conditions would be <br /> appropriate. <br />
The URL can be used to link to this page
Your browser does not support the video tag.