My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 02/04/1997
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
1997
>
Agenda - Planning Commission - 02/04/1997
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 9:05:36 AM
Creation date
9/23/2003 10:24:21 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
02/04/1997
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
80
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
CAS #-3 <br /> <br />REVIEW PROPOSED ORDINANCE TO ESTABLISH <br />REGULATIONS FOR TOWERS AND ANTENNAS <br />By: Planning Intern Kirk Skoog <br /> <br />Background: <br /> <br />On November 12, 1996, the Ramsey City Council approved a 180 day moratorium that <br />prohibits construction, erection, placement, reconstruction, enlargement, or expansion of <br />towers within the City and on the development and use of property for such purposes. <br />This moratorium took effect on January 6, 1997. The moratorium was established in order <br />to allow Staff.the necessary time to research the development of Personal Communication <br />Services (PCS) and the need for towers and antennas to facilitate the provision of these <br />services. <br /> <br />Observations: <br /> <br />At the January 7, 1997 Planning Commission meeting, the law fzrm of Larkin, Hoffman, <br />Daly & Lindgren, Ltd. (hereafter referred to as "the furn") presented a letter to the <br />Commission that listed its concerns with the proposed towers ordinance. Since this time <br />the finn has sent a letter to the City that lists its requested revisions to the proposed towers <br />ordinance. These requested revisions are summarized below and are accompanied by City <br />Staff's positions on these issues. (The ordinace draft is enclosed for your reference). The <br />firrn has indicated to Staff that a representative will attend the February 4, 1997 meeting to <br />answer questions or provide further explanation. <br /> <br /> Section 9.15.03 (b) (1). The fh'm requests that the word "camouflaged" be <br />replaced with "integrated with or designed" and that the design must meet Federal Aviation <br />Administration (FAA) standards. Staff is comfortable with this suggestion. <br /> <br /> Section 9.15.04 (b) (6). The f'u-m requests that this section be eliminated. Staff <br />believes that the reason for this suggestion is that the finn believes that requirements such <br />as these should be specified in the contract between a firm and the City, not in the Code that <br />applies to all firms that may erect a tower in the City. Staff is comfortable with this <br />provision but notes that some language to the effect of this section should be considered in <br />a contract between the City and a finn that proposes a tower on City owned property. <br /> <br /> Section 9.15.04 (c) (1) (iv). The f'm-n requests that the phrase "will not be harmful <br />to the health of workers" be replaced with "will not unreasonably interfere with". Staff is <br />comfortable with this suggestion. <br /> <br /> Section 9.15.04 (c) (2) (i). The firm requests that the phrase "of a sufficient scale <br />and character" be deleted. Staff believes that the inclusion of this phrase, although <br />ambiguous, allows the Park and Recreation Commission to determine which parks are <br />compatible with communication towers. <br /> <br /> Section 9.15.04 (e) and (f). The firm requests that these sections be eliminated. <br />Staff believes that the same reasoning by the f'rrrn was used to arrive at this request as was <br />used in previously stated Section 9.15.04 (b) (6). Staff opinion is the same as in that <br />section as well. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.