Laserfiche WebLink
<br />When the Planning Commission granted the SMA permit, they fixed that or attempted to fix that <br />in place forever in saying that’s going to be the shoreline regardless if it’s later certified. The <br />problem arises, is that when you move the shoreline inland, and you provide access based on that <br />inland shoreline, there’s a danger as in this case that it cuts off public access to the actual <br />shoreline so when you define the shoreline as the top of the cliff, you don’t get the shoreline out <br />down at the bottom of the cliff anymore which actually exists. And this was treated as if that did <br />not even exist. So, the area that you saw down there this morning with, with the kayak and the <br />landing and the ramp that goes down, none of that is part of what was termed the certified <br />shoreline in 2002. <br /> <br />So, the amendment is designed to allow public access to that shoreline in a formal way, and to <br />recapture the actual shoreline. And for our purposes, for the setback issues, we would agree to <br />use the 2002 shoreline which you have, which is in a map that was provided to you this morning. <br />As the top of the, along the top of the bluff, sometimes they call a sea cliff or pali, and use that <br />shoreline as the setback area only in areas where the actual shoreline exists below. So, the <br />shoreline at the top of the pali where it is inaccessible below remains in place. The 2010 <br />certification kept that portion of the 2002 certified shoreline in place. The change is the addition <br />of the shoreline down below. <br /> <br />So, that would change the setbacks that the County has sought to enforce, and I have to give you <br />a little history here. There’s been some question about whether the developer knew this or knew <br />that at the time. They’ve already submitted testimony, sworn testimony, that they did, were not <br />aware of SMA No. 450’s setback requirements at the time that they got their Building Permit. <br />Neither was the Building Division, which told them where they could put the, the foundation for <br />the building, and that’s what was permitted. Neither did the Planning Department, which <br />originally tried to impose a 50-foot shoreline setback, and a 50- or 20-foot sideyard setback for a <br />parcel that didn’t exist, and then walked back those positions later on. There’s an agreement <br />dated May 6, 2013, that you have that resolves all prior issues. The County Planning <br />Department is satisfied, and I need to correct something. Other people have given you testimony <br />that there may have been some impact on public access. There was never any violation dealing <br />with public access at all. There was never any cut off of public access. Public access has been <br />provided throughout, and it has been improved, as recognized by the County’s own Agreement <br />which states in the Background Report first on Exhibit 4, the current public access easement has <br />gaps that do not allow for continuity for pedestrians to access the shoreline. And, in Exhibit 8, <br />they expressly state that the current public access actually prevents access to the shoreline. <br />That’s because of the use of the 2002 certified shoreline in a place that ignored the actual <br />shoreline. <br /> <br />Not having impaired any public access, I think you’d be really remiss in holding the developer <br />accountable for something that has not happened. With respect to the public access that is being <br />proposed—Scott, if you would get that—that board behind. Okay, as you saw this morning, <br />there is no existing public access that runs from Beach Road in the subdivision to the shoreline, <br />to the, either the sea bluff or all the way down. This portion exists. This portion does not. This <br />portion exists. This portion does not. And when I say this portion, I am referring, just to make a <br />record for the transcript, I’m talking about the curved portion at the entrance that follows along <br />7 <br />EXHIBIT G <br /> <br /> <br />