|
in response (traffic totals from 1992, extrapolated for 2005) are insufficient. Exhibit 28.
<br />There is no way for the City to determine the frequency of the trips, which roads are
<br />being used, the timing in comparison to peak hour traffic on the effected roads, etc.
<br />Without such information, the City cannot make any determinations as to road capacity,
<br />for example, as required by OAR 660-023-180(5)(b)(B).
<br />The applicant’s representatives testified before the Planning Commissions that the
<br />economy and demand controlled what could be sold, that production had been increasing
<br />by approximately one percent per year, and that traffic on Hunsaker Lane would be the
<br />result of the projects that Delta was involved in. Avon Lee Babbs and George Staples,
<br />Planning Commission minutes January 17, 2006, pages 6, 7. If levels of use increase in
<br />the new excavation area because demand increases, then traffic will increase. This
<br />potential increase in traffic was not analyzed by the applicant.
<br />Without more detailed data establishing the site’s current traffic impacts or future
<br />demand for the excavated product, the assertion that the site will continue to have its
<br />current level of impact has little meaning. It provides no way for the City to assess the
<br />potential conflicts pursuant to OAR 660-023-180(5)(b)(B). Numerous participants raised Deleted:
<br />We find that approval of the
<br />application would not result in any
<br />concerns about current and continued conflicts with traffic to and from the site. See, e.g.
<br />conflicts to local roads used for access
<br />Exhibit 3, 7, 14, 16, 20, 21, 22, 23, 27, 275. In light of such testimony, the City finds that
<br />and egress to the mining site.
<br />the applicant’s response to this approval criterion is an insufficient basis on which to
<br />Deleted:
<br />Approval of the application
<br />would not result in any change in the
<br />determine if the criterion is met. As such, if the site were a significant resource, the
<br />applicant’s current use of local roads used
<br />application would fail based on this criterion.
<br />for access to and egress from its facility.
<br />The proposed expansion area would
<br />
<br />merely be an additional area of land,
<br />adjacent to the applicant’s existing
<br />facility, used by the applicant to provide
<br />(C) Safety conflicts with existing public airports due to bird attractants, i.e.,
<br />the resource that it processes on its
<br />open water impoundments as specified under OAR Chapter 660, Division 013;
<br />existing site into a marketable product.
<br />No change or modification of the
<br />The Eugene Airport is the only existing public airport in the general metropolitan area and is
<br />applicant’s existing aggregate processing
<br />located several miles from the proposed expansion area and outside the impact area. Due to that
<br />methodology or facility or ingress/egress
<br />onto local roads would be required as a
<br />distance separating the airport from the proposed expansion area, we find that any bird attraction
<br />result of the proposed expansion of its
<br />by open water impoundment on the expansion area will be negligible if at all. Furthermore, this
<br />resource extraction site. Approval of the
<br />application would result only in the
<br />provision is no longer applicable since the December 23, 1996 effective date of adoption of
<br />applicant’s use of the proposed expansion
<br />division 13 of OAR Chapter 660, which carries out Chapter 285, Oregon Laws 1985.
<br />area as an additional, continual and
<br />consistent source of aggregate material
<br />needed for the continuation of the
<br />(D) Conflicts with other Goal 5 resource sites within the impact area that are
<br />applicant’s business, at its current level of
<br />shown on an acknowledged list of significant resources and for which the
<br />operation and production, at its current
<br />facility. We find that that use would not
<br />requirements of Goal 5 have been completed at the time the PAPA is initiated;
<br />result in any increase in the number of
<br />A meandering scar of the Willamette River (“East Santa Clara Waterway”) is located on a
<br />vehicles leaving or entering the
<br />applicant’s facility for the purpose of
<br />portion of the northwestern boundary of the expansion area and constitutes a wetland within the
<br />delivering its finished product to market.
<br />impact area. This waterway was added to the City’s and County’s Goal 5 inventories as a
<br />Furthermore, we find that that use would
<br />not result in an increase in the number of
<br />“Category D” stream, which requires a setback of 20 feet. No other Goal 5 resources shown on a
<br />third party vehicles servicing applicant’s
<br />Metro Plan acknowledged list of significant resources exist within the impact area. Lane County
<br />business. No increase in product delivery
<br />or service is associated with the
<br />has authorized a variance that would allow “construction” of the aquaclude inside the DEQ 150-
<br />applicant’s proposed addition to its
<br />foot mandatory setback, which would move the area of disturbance nearer this Goal 5 resource. .
<br />source of aggregate material; therefore,
<br />no conflicts to local roads would result
<br />The variance is to the DEQ setback, not the locally-adopted Goal 5 setback, and would not allow
<br />from approval of the application.
<br />any construction activities within the Goal 5 setback. The locally adopted Goal 5 setback along
<br />Deleted:
<br />Opponents have argued that a
<br />East Santa Clara Waterway of 20 feet would still be met.
<br />meandering scar of the Willamette River
<br />(“East Santa Clara Waterway”) is located
<br />
<br />on a portion of the northwestern
<br />The opponents argue that the existence and operation of the aquaclude (see discussion below
<br />boundary of the expansion area and that it
<br />constitutes a wetland
<br />regarding the aquaclude) will negatively impact the water levels and, consequently, the functions
<br />Deleted:
<br />further
<br />
<br />
|