My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
7/27/1989 CONSERVATION COMMISSION Minutes
>
7/27/1989 CONSERVATION COMMISSION Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/21/2018 5:09:16 PM
Creation date
2/21/2018 1:50:52 PM
Metadata
Fields
Template:
Mashpee_Meeting Documents
Board
CONSERVATION COMMISSION
Meeting Document Type
Minutes
Meeting Date
07/27/1989
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
18
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
July 27, 1989 Page 7. <br /> the most significant break above the i o year flood <br /> elevation. I think in some cases we might be giving up 50, <br /> loo feet; jurisdiction in this particular case. <br /> I appreciate all that 1P, through Stan, has evidenced here <br /> in terms of the functionality of the bank and in teras of the <br /> portion of the bank that is below the 100 year flood <br /> elevation being that portion. of the bank that has function <br /> and I am in complete agreement with understanding and that <br /> position. But, it bathers me to see that we' re now <br /> redefining, in my opinion, past DECUB practice that has been <br /> spelle-d out in superceding orders and also adjudicatory <br /> decisions, standard operating procedure out of the <br /> southeastern office. It bothers me that we' re seemingly <br /> throwing that inf'or-mation by the wayside and trying .to core <br /> up with a new way of adopting or designating the top of the <br /> coastal bank; that being that we should take the 100 year <br /> flood elevation, tack on projected increase for sea rise <br /> level and go with that particular designation. I would urge <br /> he commission to evaluate this information very carefully <br /> because I feel that should this p;articul.ar position prevail <br /> here, that you' re setting a precedent that you may live to <br /> regret. <br /> I �Iave visited the site with CZM. I am confident that c el, <br /> through most of the site here, would not call the topo f the <br /> coastal bank the 100 year flood elevation and I feel strongly <br /> enough in my own mind that this decision has ramifications <br /> far beyond this case and that theomission ought to make a <br /> positive determination at some point. if the applicant, <br /> through their- consultant sticks with the 100 year flood <br /> elevation, I would urge the commisslon to make the positive <br /> determination that there are coastal resources but there is a <br /> boundary dispute and that dispute has not been resolved <br /> through the Request for Determination of Applicability <br /> process and that therefore it would leave -the applicant the <br /> opportunity to appeal this to DEQE, now DEP, so that the <br /> issue could be resolved at a higher ievei and perhaps through <br /> all of this, all of the various consultants will be <br /> enlightened as to how we' re going to define the top of the <br /> coastal bark. Stan, Norman and I are good friends; we have <br /> been kicking around this top of the coastal band issue for 1 <br /> years. Stan's right, people at the State level know there is <br /> a problem but no one seems to be coming down with a solution. <br /> We thought we had a solution in 1985 when Brett Bur is , <br /> former coastal geologist for the southeast regional officeg <br /> issued a document with four case types for coastal banks and <br /> we were guided by that for a number- of years and Stan has <br /> a:llUded 'to that in the report and included some diagrams of <br /> those: case types, but again, i think the co[Tvid,3sion ham to <br /> pr-ocee)d cautiotisiy here. We have been given a ciocupient of <br /> some 16 paqe-:,q with ap endi cel:,F; I have not seen the report <br />
The URL can be used to link to this page
Your browser does not support the video tag.