New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
Stream Corridor Acquisition Memo
COE
>
PW
>
Admin
>
Execs
>
Executive non-confidential
>
Historical
>
Stream Corridor Acquisition Memo
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/11/2010 9:59:35 AM
Creation date
8/6/2008 10:07:41 AM
Metadata
Fields
Template:
PW_Exec
PW_Division_Exec
Administration
PWA_Project_Area
Policy
PW_Subject
Stream Corridor Acquisition
Document_Date
12/16/2005
External_View
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
3
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
Council rescinded its support for a user fee increase to fund an enhanced acquisition <br /> program. The acquisition program was scaled back to a budget of $150,000 annually. <br /> As of July 2003, 36.3 acres of stream corridor had been acquired for $962,000, and <br /> negotiations were underway on an additional 10.5 acres with an approximate value of <br /> $470,000. An additional 113 acres remained to be acquired, at an estimated value of <br /> approximately $4 million. <br /> Lead responsibility for developing and implementing the stream corridor acquisition plan <br /> resided with PW Engineering though March 2004. With the elimination of the Water <br /> Resources team, lead responsibility for implementing the plan was transferred to <br /> POS/Parks Planning. PWE continues to provide acquisition services (Russ and Lloyd). <br /> October 20.2005 Council Worksession <br /> At the October 20, 2005 worksession on the stormwater permit and program <br /> developments, the City Council expressed approval for the additional stormwater permit <br /> related funding needs identified (the main topic of the worksession). Council had a <br /> lengthy discussion about stream corridor acquisition and requested that staff bring back <br /> "a stream corridor acquisition program analogous to that in effect before cuts." The <br /> intent was expressed by one Councilor as "brushing off' the old study that was approved <br /> by Council and bringing it back to them for consideration again. The follow up stream <br /> corridor acquisition worksession is scheduled for January 23, 2006. Council packet is due <br /> by January 16tH <br /> <br /> - At a minimum, it is staff's opinion that the "priority stream corridors and acquisition <br /> sites" map should be updated to identify sites already acquired under the acquisition <br /> program. Also, the sites no longer available or desirable to acquisition should be <br /> removed from the map. Unit costs and total costs should be updated, and based upon <br /> duration of time for implementation, the impacts to stormwater user fees determined. <br /> This would be the minimum needed to respond to the Council request. <br /> In updating the map to reflect sites already acquired and those no longer available for <br /> acquisition, what will be left on the acquisition map are some specific stream corridors in <br /> the south hills, in the Amazon and Willow Creek basins. These remaining acquisition <br /> sites would be a small subset of the Goa15 sites. These remaining acquisition sites would <br /> also be a small subset of the water quality-protected waterways sites. <br /> .Discussion points for Policy team meeting <br /> Policy team direction is needed at this time to allow adequate time for packet and <br /> meeting preparation. Some questions to consider include: <br /> 1. Who is the appropriate staff person to take the lead on the January worksession? <br /> 2. In the context of the CIP and the stormwater program as a whole, how narrowly <br /> or broadly should we respond to the Council request? Possible options {from <br /> narrow to broad) include: <br /> • Respond to the specific request only, doing only the minimum updating <br /> described above. <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.