My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
5.4. SR 05-17-2010
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2000 - 2010
>
2010
>
05-17-2010
>
5.4. SR 05-17-2010
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/26/2010 3:05:21 PM
Creation date
5/14/2010 2:29:55 PM
Metadata
Fields
Template:
City Government
type
SR
date
5/17/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.
/
622
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
an area where landfilling could not lawfully take place, and did not in the alternative seek an <br />amendment restricted to 13.4 areas of its existing property, this Court should not grant such an <br />amendment now. (emphasis added). <br />B. ERL's letter: ERL's March 9 letter states on pages 2-3 that, "if the amendments are adopted <br />by the City Council, then City will no longer be able to maintain, as it did earlier, that ERL's <br />requested 13-acre expansion within the existing 137.4-acre landfill property could and should <br />instead be pursued through either (1) ERL's annual renewal process or (2) a new 13-acre <br />CUP/License amendment application before City." (emphasis added).I <br />The City's filings: In its January 21, 2010, brief in opposition to ERL's motion for summary <br />judgment, the City wrote: <br />In the alternative, the Landfill claims that it is "entitled to its CUP and <br />License amendments as it relates to the 13.4 acre portion of the 73.4 acre MSW <br />landfill expansion which is within the existing 137.4 acre property." (Op. Br. at 2). <br />However, that argument does not describe an actual amendment that the Landfill <br />requested the City to grant, but describes a fraction of the much larger CUP <br />amendment that it requested and that was properly denied. That fallback argument is <br />all about where those 13.4 acres supposedly fall - on property already within the <br />SWF district. However, a CUP is not just about "where," but is also about "what," <br />and the only "what" described in the Application was a proposed expanded landfill <br />that went well beyond the SWF District and the Landfill's property. The idea of <br />granting an amended CUP for a fraction of a proposed expansion, when that <br />proposed expansion presumed the availability of the SDA, is misguided. The <br />Landfill's Application did not seek, in the alternative, such an amendment, and the <br />Landfill cannot ask this Court to compel its approval. <br />Denial of a CUP amendment to landfill on the 109-acre SDA effectively <br />prevents the Landfill from going forward with its design for an expanded landfill, <br />even for that portion of the proposed expansion that is on property the Landfill <br />already owned and is already within the SWF district. The design of the Landfill's <br />proposed expansion presumes that the Landfill does not need to use its existing <br />property for a southern slope to the Landfill and buffer area. To the contrary, the <br />1 The Landfill's March 9 letter also attaches its amendment application, where ERL argues on <br />page 3-17 that "the City even scoffed at the notion that `the Landfill truly believes that the scope of <br />its current CUP prevents it from using as part of a landfilling facility part of its property in the area <br />within the current SWF District,' and it suggests that the ERL `resolve that uncertainty as part of .. . <br />the [parties'] process of discussing conditions for renewal of the Landfill's current CUP and <br />License.' But, when the ERL submitted just such a request as part of the renewal process, the City <br />determined that a separate CUP/License amendment application was required." <br />2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.