My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
09-19-1988 Planning Minutes
Orono
>
Agendas, Minutes & Packets
>
Planning Commission
>
Minutes
>
1980-1989
>
1988
>
09-19-1988 Planning Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/20/2023 8:46:04 AM
Creation date
9/14/2023 4:13:27 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
27
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
MimiTBS OF THE PLAHHIIIG CONHISSIOH TING SEPTEMBER 19, 1988 <br />IJ.-OZONING PILE 81333-REBERS C0NTIN1 <br />Mr. John Shardlow. Indicated that he was not an advocate for <br />the Rebers* proposal. His purpose for attending the meeting was <br />to review the proposal as a Consultant for the City of Orono. <br />This process started with the assumption that the City would look <br />at whether or not the comprehensive plan should be amended first. <br />After the comprehensive plan was in place, it would act on <br />specific requests for rezoning, based upon the conditions and <br />standards established. The Rebers' proposal is consistent with <br />the comprehensive plan. Mr. Shard low said that statement is not <br />an opinion on his part, it is a fact. He was aware of the fact <br />that there were members of the Planning Commission that disagreed <br />with the comprehensive plan. Therefore, if there is opposition <br />to Mr. Rebers* proposed subdivision, it is actually opposition to <br />the comprehensive plan. The "plan” was in place first and Mr. <br />Rebers* developers tailored their proposal to the comprehensive <br />plan. <br />Mr. John Rick, a resident at 730 Dickey Lake Drive, stated <br />that his concern was similar to Mrs. Roderick's in that if the <br />the subdivision were to create a thoroughfare of Dickey Lake <br />Drive, Pine Ridge and the proposed cul-de-sac, there would be a <br />significant public safety issue to be addressed. <br />Mr. Gerald Pettis, another resident of Dickey Lake Drive, <br />stated that he was suspicious of what could potentially happen <br />should Pine Ridge Lane be opened for a firelane. He was <br />concerned about the City going through Dickey Lake Drive for the <br />purpose of installing sewer lines. Mr. Pettis said that he did <br />not have the property to give for the purposes of a sewer line. <br />Chairman Kelley said that was a good point in that was the next <br />logical step should the sewer be expanded to the west. Mr. <br />Pettis also wanted to know if there were proposed covenants for <br />the development. Kelley answered that a letter had been sent <br />setting forth those covenants. Mr. Pettis asked if they were <br />anything like the covenants for Morningside? If so, he would be <br />very concerned about his property if homes of that calibur were <br />to be put in his area. <br />Mr. Robbin Sentell, residing at 736 Dickey Lake Drive, <br />agreed with concerns raised by his neighbors. His main concern <br />was whether any form of traffic regulation had been proposed for <br />Brown Road and Highway 12, should the Rebers* development be <br />approved. Mr. Shardlow responded to Mr. Sentell*s question by <br />stating that one of the mainstays of the xighway 12 Corridor <br />Study is to preclude any direct access from the frontage of Mr. <br />Rebers* property that is currently zoned commercial. There would <br />be an opportunity for local traffic to get across that location <br />without having to go onto Highway 12. The present plan requires <br />the installation of a frontage road before the southern portion <br />of the Rebers* property is developed. Mr. Sentell asked for <br />further Information regarding specific proposed traffic <br />regulations for Brown Road and Highway 12. Mr. Shardlow replied
The URL can be used to link to this page
Your browser does not support the video tag.