My WebLink
|
Help
|
About
|
Sign Out
Home
COM 0964.012 2004-2006
ClerkCouncil
>
Council Records
>
Communications
>
2004-2006
>
COM 0964.012 2004-2006
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/12/2008 12:50:28 AM
Creation date
5/9/2008 12:03:09 AM
Metadata
Fields
Template:
Communications
Communications - Type
COM
Communications - Council Term
2004-2006
Communication
0964
Point
012
Author
Bob Ely
Communications - Referred To
PC
Comments
Presented: PC - 7/31/06
Document Relationships
AGE PC 07/31/2006 2004-2006
(Related)
Path:
\Council Records\Agendas\2004-2006\Planning Committee (PC)
BIL 309 Draft 01 2004-2006
(Related)
Path:
\Council Records\Bills\2004-2006
COM 0964.000 2004-2006
(Related)
Path:
\Council Records\Communications\2004-2006
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
4
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
<br /> <br /> <br /> <br /> <br /> Being a private subdivision, Orchidland is responsible for its own roads - paving, maintenance <br /> and associated liability. We get no help from the county or state. <br /> <br /> Commercial development is planned not only along the two main roads but along the unpaved <br /> side roads as well. Development will obviously induce more traffic onto these unimproved, 12 <br /> foot wide, single lane, gravel side roads. Yes, you can make promises that the Planning <br /> Department will put conditions on any new permits that the developer pick up the tab for the <br /> road improvements, but that has not been our experience to date. For example, recently a <br /> congregation made application to build a large church on an Orchidland side road. The Planning <br /> Department's condition was that the church could improve the first 18% of the side road from <br /> one main road, the remaining 82% or 2/3's of a mile of the side road from the other main road <br /> was left up to Orchidland. <br /> When someone would want to go from a shop in the Ainaloa area to another on the Orchidland <br /> area, they aren't going to wait in a traffic backup and take that death defying risk of merging into <br /> a stream of cars on the highway. They are going to go up the single lane, graveled 341i or 35m <br /> inside Orchidland. And, you know what will happen when there is a fatal accident. I'm willing <br /> to bet that the courts will say that the County is liable because they forced this situation on a <br /> private subdivision without the financial means nor the motivation to improve those roads. <br /> These kinds of issues need to be worked out! <br /> <br /> r. <br /> a <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> 35th near Ainaloa Blvd. 35th near Orchidland Drive <br /> <br /> <br /> Action <br /> The above objections show that these amendments are ill-conceived and not well thought out. <br /> They are good reasons for not rushing into this. Orehidland, the Planning Department and the <br /> Puna Community Development Committee need some time to try to come up with a <br /> comprehensive solution to our region's growth problems. There are alternatives to locating <br /> commercial zones - Hawaiian Paradise Park has blocks set aside for this, Shipman has land and <br /> big plans. <br /> Opposition amongst the 2,200 Orchidland lot owners is very strong as demonstrated by the <br /> resolution passed at the April, 2006 General Membership meeting, in which a vote to curtail <br /> commercial development within Orchidland was almost unanimous. We feel that we would be <br /> completely within our rights to gate certain roads and allow access only to residents and guests. <br /> While we don't want to have to resort to such tactics, feelings in the community on this issue run <br /> so high that it could conceivably happen. <br />
The URL can be used to link to this page
Your browser does not support the video tag.