New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
Stormwater Policy Team 2002 - 2003
COE
>
PW
>
POS_PWM
>
Parks
>
Stormwater
>
Stormwater Policy Team 2002 - 2003
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/27/2015 2:55:36 PM
Creation date
8/27/2015 2:55:24 PM
Metadata
Fields
Template:
PW_Operating
PW_Document_Type_ Operating
Correspondence
Fiscal_Year
2016
PW_Division
Parks and Open Space
External_View
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
46
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
Background for the February 22, 2002 Stormwater Policy Team Meeting <br /> I. Headwaters Flow Controls: The group is seeking policy team support for flow controls in <br /> the South Hills (part of the draft ordinance). This issue has the general support from the <br /> original Stormwater DAC and the public, though the level of specificity was not as great as we <br /> have now. <br /> From the Last Meeting: <br /> One issue brought up about this requirement is that a developer might get into a situation <br /> where there is no practical means to do what is required. Where there is no pipe downstream <br /> from a headwaters site, it could require substantial off-site construction. <br /> Request from Policy Team: Would like to see a graphic that shows areas of vacant lands <br /> in proximity to streams above 500 ft. in elevation to see how many sites might be <br /> impacted. We could also use this graphic as a visual for explaining the concept to the <br /> public. Would like to see the graphic and talk more about this at the next meeting <br /> (February 22). <br /> Response: We will provide a map of the headwaters area showing "buildable lands"at <br /> the meeting. In addition, there is adjustment language in the draft code, Section 13, <br /> 9.8030 (16)(c) on page 21, which allows developers to propose alternatives to what is in <br /> the BMP Manual. <br /> II. Exemption for Maintenance or Repair of Streets: The group is seeking policy team <br /> approval for the exemption language that will be part of the draft ordinance amending Chapter <br /> 9 of the City Code, and similar language to be part of the Public Improvement Design Manual. <br /> From the Last Meeting: <br /> Request from Policy Team: Would like to see the specific language that would be used <br /> for the ROW public standards (in the Public Improvement Design Standards Manual). <br /> Also, further define"reconstruct drainage system," providing a new threshold. <br /> Response: Draft language is available — see attachment"PEPIManual.wpd"for the <br /> placement and language proposed for the Public Improvement Design Standards <br /> Manual. "Reconstruct drainage system" is defined there as well. <br /> III. Maintenance of Vegetation: At the October Policy Team meeting, we left this issue <br /> unresolved (whether neighboring property owners to a stormwater BMP would be responsible <br /> for maintaining the vegetation). Here's the policy for which the team is seeking approval: <br /> "The City would maintain the vegetation important to the functioning of the <br /> system or access to the system, and property owners would maintain <br /> landscaping vegetation for the purpose of aesthetics." <br /> I <br /> 2 <br /> II <br /> I <br />
The URL can be used to link to this page
Your browser does not support the video tag.