My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 09/10/2015
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2015
>
Agenda - Planning Commission - 09/10/2015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:23:39 AM
Creation date
12/16/2015 10:48:31 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
09/10/2015
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
253
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
The framework for future COR sign ordinance amendments would consider the following: <br />Development Sign (formerly called community sign): A COR development wide identification sign <br />intended to advertise the COR development (primary purpose) with limited tenant exposure. Signs are <br />installed at key locations at the east side: Hwy 10 and Ramsey Blvd, at transit facility, and west side of <br />Hwy 10 and Armstrong Blvd. These signs, located along Hwy 10, are intended to draw drivers into the <br />COR, broaden name recognition, and place recognition of the COR. <br />Each Development sign can have its own specifics as to height, area and advertising function: <br />• East Side - 50 feet in height and more predominantly COR and less for tenants. <br />• Transit Facility - 50 feet in height. COR with primary tenant (40/60) split. <br />• West Sign - increased height to 75 feet due to intersection improvements. Advertises the COR <br />with primary west end tenants using a 40 (city)/60 (tenant) split. <br />• 300 square feet in area. <br />• Ownership of these signs would need to be determined. <br />Signs area is not included in the total signage permitted for the property on which it is located. <br />Signs must have similar appearance and use of materials. <br />Need to determine tenant distribution on Development Signs either by primary tenants or square footage. <br />Tenant signage is limited to sign band and not replacing advertising on private signs. <br />Gateway Sign: Internal development wide advertising signs for the COR, but also includes tenants. <br />These should be located internal to the development at key intersections: Sunwood and Armstrong, <br />Ramsey Blvd and Sunwood, Bunker and Center, Sunwood and Center, or others. <br />• Signs are similar to Development Signs as they serve a broader purpose to advertise the COR <br />but also tenants. Gateway signs should be shorter and less area than Development Signs as 25 <br />feet in height and 50 square feet. <br />• By including tenant signs they serve to direct drivers to major tenants and provide additional <br />advertising to major tenants. Tenant sign area shall be uniform sign band. This sign does not <br />replace private signs. <br />• Will be located on private property, but at street intersection. <br />• As a COR advertising sign they should be included in the total signage permitted for the property <br />on which the sign is located. <br />• All Gateway Signs shall be uniform in size, height, design, and color. <br />• Ownership would need to be determined. <br />Private Freestanding Signs: Signs for individual site or business (replace current "Project Sign") <br />• Individual business or site: by right up to 25 square feet and 6 feet in height (monument style with <br />landscaping at base). <br />• Up to 100 square feet and 25 feet in height by CUP — still single site/business. <br />Shared Multiple Tenant Sign: Mixed tenant sign by CUP — 50 feet in height and 300 square feet. <br />• Site plan is required. <br />• Signs are privately owned. <br />Others: Menu Board is still allowed in COR 2: 1 per drive through lane at 40 square feet. Wall signs are <br />to stay as is. <br />
The URL can be used to link to this page
Your browser does not support the video tag.