My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
AgdaPkt 2010-02-01 clsd and regular
RedwoodCity
>
City Clerk
>
Agenda Packets
>
2010-2019
>
2010
>
AgdaPkt 2010-02-01 clsd and regular
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/9/2010 11:31:04 AM
Creation date
1/28/2010 3:29:46 PM
Metadata
Fields
Template:
CC Index
CC Index - Document Type
Agenda Packet
Meeting Type
Regular
Agency Type
City Council
Date
2/1/2010
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
232
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
<br />7A - ATTACHMENT NO.2 <br />Page 8 <br /> <br />focus then turns from disputing jurisdictional issues to reaching agreement regarding <br />appropriate permit conditions. <br /> <br />On November 12, 2009, DMB submitted to USACE an application for PJD in <br />accordance with RGL 08-02. DMB submitted the PJD Application as a means to "set <br />aside questions regarding CW A RHA jurisdiction" for the "sole and exclusive purpose of <br />processing" the 50/50 Balanced Plan project application. <br /> <br />The US ACE was to respond to this application on or before January 12, 2010. <br />(RGL 08-02, ~ 5(a).) To our knowledge, USACE had not issued a response. Once the <br />PJD is finalized, DMB will submit its Section 404/Section 10 permit application. <br /> <br />By its terms, RGL 08-02 provides permit applicants the ability to "elect to use a <br />preliminary JD to voluntarily waive or set aside questions regarding CW A and RHA <br />jurisdiction" and elect to use a PJD to obtain expeditiously a USACE permit <br />authorization. (RGL 08-02, ~ 4(a).) PJD's can be used "even where initial indications <br />are that the water bodies or wetlands on a site may not be jurisdictionaL.. ", (Id., ~ 4( c), <br />emphasis added.) By definition, a PJD can only be used to determine that wetlands or <br />other waterbodies "may be" jurisdictional "waters of the United States." A PJD cannot <br />be used to "determine either that there are no wetlands or other waterbodies on a site at <br />all, or that there are no jurisdictional wetlands or other waterbodies on a site, or that only <br />a portion of the wetlands or waterbodies on a site are jurisdictional." A definitive, <br />official determination that there are, or are not, jurisdictional waters of the United States <br />on a site can only be made by an approved Jurisdictional Determination. (RGL 08-02, ~ <br />7.) <br /> <br />A PJD makes "no legally binding determination of any type regarding whether <br />CW AlRHA jurisdiction exists over the particular water body or wetland in question." <br />(RGL 08-02, ~ 4(f).) Instead, the wetlands and waters that are identified within the PJD <br />are presumed to meet the requirements of federal jurisdiction under CW A Section 404 <br />and RHA Section 10 for the sole and exclusive purpose of processing the application. <br />(RGL 08-02, ~ 4(d).) <br /> <br />In this case, DMB's November 12 submittal indicates that DMB intends to <br />proceed under RGL 08-02. Thus, DMB has agreed that, for purposes of determining <br />impacts and compensatory mitigation requirements, a permit decision made on the basis <br />of a PJD "will treat all waters and wetlands that would be affected in any way by the <br />permitted activity on the site as if they are jurisdictional waters of the U.S." (Id., ~ 4(d).) <br />Therefore, DMB acknowledges that waters and wetlands, as applicable, will be evaluated <br />in accordance with the Federal agencies' section 404(b)( 1) Guidelines and compensatory <br />mitigation regulations. (40 C.P.R. Part 230; 33 C.P.R. Parts 325, 332; see 73 Pederal <br />Register 19593 (April 10, 2008).) <br /> <br />8 <br />
The URL can be used to link to this page
Your browser does not support the video tag.