My WebLink
|
Help
|
About
|
Sign Out
Home
J. Matlock 48 hours Testimony 05.31.23
PublicDocuments
>
Planning Department
>
Leeward/Windward Planning Commission
>
Board Packets
>
2023
>
2023-06-02 Joint Leeward & Windward
>
Item #1 Proposed Amendments to Planning Commission Rule 8 and 9
>
Additional Info Provided to Joint Commission for Consideration at 6-2-23 Hearing
>
J. Matlock 48 hours Testimony 05.31.23
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/31/2023 1:48:11 PM
Creation date
5/31/2023 1:48:10 PM
Metadata
Fields
Template:
Plan Doc Template
Document Date
5/31/2023
Description
J. Matlock 48 hours Testimony 05.31.23
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
2
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).
Show annotations
View images
View plain text
From: ianet Matlock <br /> To: LPCtestimony;WPCtestimony <br /> Subject: Shoreline Setback and SMA-Oppose <br /> Date: Wednesday, May 31,2023 1:05:47 PM <br /> Aloha Members of the Leeward and Windward Planning Commissions, <br /> First off, mahalo to Commissioner Vitousek for opening discussion on concerns with the first <br /> draft of the Planning Director's proposed amendments to Shoreline Setback and SMA <br /> requirements. Also, mahalo to the Commissions for asking how kuleana lands might receive <br /> appropriate consideration compared to other, often profit-driven, developers. <br /> A surprise addressed in your hearing on April 20 was the insertion of language granting the <br /> Planning Director ability to waive public hearings. Given that the County Council recently <br /> curtailed the Planning Director's authority regarding administrative extensions of project <br /> deadlines, this attempt seemed a little tone-deaf. <br /> Mahalo to the Commissions for recognizing the importance of public input. <br /> There are many concerns with the proposed language, beginning with dilution of the <br /> requirements for archeological review. This is alarming, given the incredible history here that <br /> is so fragile, and so easily destroyed forever. <br /> Should we not take note of O`ahu's decision: "Starting in.Iuly 2024,�shoreline setbacks/ will <br /> increase to between 60 to 130 feet. depending on the coastal erosion rate and location and <br /> size ofthe development." (his://www.hawaiinewsnow.com/2023/02/23/honolulu-city- <br /> council-unanimouslybasses-2-bills-combat-rising-sea-levels/) <br /> I have a question: What is the rush to vote right now? (Is there a development that is <br /> anxious to be approved immediately?If so, surely that can be addressed appropriately.) <br /> Why did the Planning Director not want to take time to discuss each of the items in the <br /> proposed amendments? Why does our County administration want this language reviewed and <br /> approved so quickly, and all in one piece? (See transcript of Joint LPC/WPC meeting 4/20/23 <br /> where Director Kern asked the Commissioners to point out where they were opposed, in order <br /> to "save on time" and efficiency...) <br /> By comparison, Maui County held two years of public meetings <br /> (hUs://www.mauicounty.gov/416/Coastal-Zone-Management-Program) and issued multiple <br /> FAQ updates. <br /> What is the rush? If we're already adhering to State MINIMUM requirements, why not take <br /> time to publicly discuss what is best for the use and preservation of Hawaii Island's unique <br /> and precious shoreline and Special Management Areas? <br /> These are complex and critically important issues. Please defer voting on specific language, <br /> and instruct the Planning Department to initiate more public outreach and hearings. <br /> Please take the time to address changes to our Shoreline Setbacks and SMA language <br /> thoughtfully and thoroughly. <br />
The URL can be used to link to this page
Your browser does not support the video tag.