Difference between revisions of "Main Page"
Line 20: | Line 20: | ||
</div> | </div> | ||
<div class="clearfix"></div> | <div class="clearfix"></div> | ||
− | |||
− | |||
<div class="col-md-12"> | <div class="col-md-12"> | ||
Line 60: | Line 58: | ||
</div> | </div> | ||
<div class="col-md-6"> | <div class="col-md-6"> | ||
− | < | + | <h3 Class="title-black"><strong>Welcome to the Low Impact Development Stormwater Management Practice Planning and Design Guide</strong></h3> |
− | <p> | + | <p>This website was developed using Mediawiki, a wiki application that allows for easy editing and that has powerful search abilities. See Introduction to the wiki for more information.</p> |
− | <p> | + | <p>The Low Impact Development Stormwater Management Planning and Design Guide |
− | < | + | (LID SWM Guide) has been developed by Credit Valley Conservation (CVC) and |
+ | Toronto and Region Conservation Authority (TRCA) as a tool to help developers, | ||
+ | consultants, municipalities and landowners understand and implement more sustainable | ||
+ | stormwater management planning and design practices in their watersheds. Many | ||
+ | jurisdictions have defined the term low impact development. For this document, the | ||
+ | following definition, adapted from the United States Environmental Protection Agency | ||
+ | (U.S. EPA, 2007) will be used: | ||
+ | |||
+ | {{TextBox|1=Low impact development (LID) is a stormwater management strategy that seeks to mitigate the impacts of increased runoff and stormwater pollution by managing runoff as close to its source as possible. LID comprises a set of site design strategies that minimize runoff and distributed, small scale structural practices that mimic natural or predevelopment hydrology through the processes of infiltration, evapotranspiration, harvesting, filtration and detention of stormwater. These practices can effectively remove nutrients, pathogens and metals from runoff, and they reduce the volume and intensity of stormwater flows.}}</p> | ||
+ | <btnPrimary>Read more ..</btnPrimary> | ||
</div> | </div> | ||
<div class="col-md-6"> | <div class="col-md-6"> | ||
Line 71: | Line 78: | ||
<div class="subtitle-black"></div> | <div class="subtitle-black"></div> | ||
</div> | </div> | ||
− | <div class="col-md-3"> | + | |
− | <h4Blue> | + | <div class="col-md-12 column sortable ui-sortable pull-right"> |
+ | <div class="portlet"> | ||
+ | <div class="panel panel-primary-light-border"> | ||
+ | <div class="panel-heading clearfix"> | ||
+ | <div class="panel-caption"> | ||
+ | <h3 class="panel-title">Portlet Overview</h3> | ||
+ | </div> | ||
+ | <div class="panel-options dark"> | ||
+ | <div class="panel-collapse"> | ||
+ | <div class="pointer"><i class="fa fa-chevron-up"></i></div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div style="display: block;" class="panel-body"> | ||
+ | <p class="justify">Note the functionality, while not the same as tabs, it allows for large blocks of content in a | ||
+ | small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. | ||
+ | Personally I prefer porlets to tabs.</p> | ||
+ | <p style="text-align:justify">As to portlet functionality note how they can be dragged and dropped to different locations, if | ||
+ | you select the <i class="fa fa-chevron-up"></i> it will close the portlet, selecting the <i class="fa fa-times"></i> will remove a portlet, whereas the <i class="fa fa-chevron-down"></i> will close the porlet. Panels can also be set to the | ||
+ | desired potion, either open or closed on page load.</p> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="portlet"> | ||
+ | <div class="panel panel-primary-light-border"> | ||
+ | <div class="panel-heading clearfix"> | ||
+ | <div class="panel-caption"> | ||
+ | <h3 class="panel-title">Portlet Overview</h3> | ||
+ | </div> | ||
+ | <div class="panel-options dark"> | ||
+ | <div class="panel-collapse"> | ||
+ | <div class="pointer"><i class="fa fa-chevron-up"></i></div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div style="display: block;" class="panel-body"> | ||
+ | <p class="justify">Note the functionality, while not the same as tabs, it allows for large blocks of content in a | ||
+ | small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. | ||
+ | Personally I prefer porlets to tabs.</p> | ||
+ | <p style="text-align:justify">As to portlet functionality note how they can be dragged and dropped to different locations, if | ||
+ | you select the <i class="fa fa-chevron-up"></i> it will close the portlet, selecting the <i class="fa fa-times"></i> will remove a portlet, whereas the <i class="fa fa-chevron-down"></i> will close the porlet. Panels can also be set to the | ||
+ | desired potion, either open or closed on page load.</p> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="portlet"> | ||
+ | <div class="panel panel-primary-light-border"> | ||
+ | <div class="panel-heading clearfix"> | ||
+ | <div class="panel-caption"> | ||
+ | <h3 class="panel-title">Portlet Overview</h3> | ||
+ | </div> | ||
+ | <div class="panel-options dark"> | ||
+ | <div class="panel-collapse"> | ||
+ | <div class="pointer"><i class="fa fa-chevron-up"></i></div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div style="display: block;" class="panel-body"> | ||
+ | <p class="justify">Note the functionality, while not the same as tabs, it allows for large blocks of content in a | ||
+ | small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. | ||
+ | Personally I prefer porlets to tabs.</p> | ||
+ | <p style="text-align:justify">As to portlet functionality note how they can be dragged and dropped to different locations, if | ||
+ | you select the <i class="fa fa-chevron-up"></i> it will close the portlet, selecting the <i class="fa fa-times"></i> will remove a portlet, whereas the <i class="fa fa-chevron-down"></i> will close the porlet. Panels can also be set to the | ||
+ | desired potion, either open or closed on page load.</p> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="portlet"> | ||
+ | <div class="panel panel-primary-light-border"> | ||
+ | <div class="panel-heading clearfix"> | ||
+ | <div class="panel-caption"> | ||
+ | <h3 class="panel-title">Portlet Overview</h3> | ||
+ | </div> | ||
+ | <div class="panel-options dark"> | ||
+ | <div class="panel-collapse"> | ||
+ | <div class="pointer"><i class="fa fa-chevron-up"></i></div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div style="display: block;" class="panel-body"> | ||
+ | <p class="justify">Note the functionality, while not the same as tabs, it allows for large blocks of content in a | ||
+ | small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. | ||
+ | Personally I prefer porlets to tabs.</p> | ||
+ | <p style="text-align:justify">As to portlet functionality note how they can be dragged and dropped to different locations, if | ||
+ | you select the <i class="fa fa-chevron-up"></i> it will close the portlet, selecting the <i class="fa fa-times"></i> will remove a portlet, whereas the <i class="fa fa-chevron-down"></i> will close the porlet. Panels can also be set to the | ||
+ | desired potion, either open or closed on page load.</p> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="portlet"> | ||
+ | <div class="panel panel-primary-light-border"> | ||
+ | <div class="panel-heading clearfix"> | ||
+ | <div class="panel-caption"> | ||
+ | <h3 class="panel-title">Portlet Overview</h3> | ||
+ | </div> | ||
+ | <div class="panel-options dark"> | ||
+ | <div class="panel-collapse"> | ||
+ | <div class="pointer"><i class="fa fa-chevron-up"></i></div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div style="display: block;" class="panel-body"> | ||
+ | <p class="justify">Note the functionality, while not the same as tabs, it allows for large blocks of content in a | ||
+ | small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. | ||
+ | Personally I prefer porlets to tabs.</p> | ||
+ | <p style="text-align:justify">As to portlet functionality note how they can be dragged and dropped to different locations, if | ||
+ | you select the <i class="fa fa-chevron-up"></i> it will close the portlet, selecting the <i class="fa fa-times"></i> will remove a portlet, whereas the <i class="fa fa-chevron-down"></i> will close the porlet. Panels can also be set to the | ||
+ | desired potion, either open or closed on page load.</p> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | |||
+ | <div class="portlet"> | ||
+ | <div class="panel panel-primary-light-border"> | ||
+ | <div class="panel-heading clearfix"> | ||
+ | <div class="panel-caption"> | ||
+ | <h3 class="panel-title">Bootstrap Portlet 2</h3> | ||
+ | </div> | ||
+ | <div class="panel-options dark"> | ||
+ | <div class="panel-expand"> | ||
+ | <div class="pointer"><i class="fa fa-chevron-down"></i></div> | ||
+ | </div> | ||
+ | <div class="panel-remove"> | ||
+ | <div class="pointer"><i class="fa fa-times"></i></div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div style="display: none;" class="panel-body"> | ||
+ | <p class="justify"> | ||
+ | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris ullamcorper | ||
+ | dolor ut urna consectetur, id interdum purus pellentesque. Suspendisse fringilla | ||
+ | nunc erat, nec consectetur nisi tristique nec. Etiam dignissim hendrerit vehicula. | ||
+ | Cras eu dui vel nulla cursus feugiat. Suspendisse sem purus, molestie quis diam ac, | ||
+ | facilisis hendrerit elit. Morbi molestie ligula ut volutpat commodo. Donec ultrices, | ||
+ | metus a adipiscing ultrices, risus nibh rutrum nibh, vel interdum quam justo nec | ||
+ | nibh. Maecenas non orci a metus sollicitudin sollicitudin. | ||
+ | </p> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="portlet"> | ||
+ | <div class="panel panel-primary-light-border"> | ||
+ | <div class="panel-heading clearfix"> | ||
+ | <div class="panel-caption"> | ||
+ | <h3 class="panel-title">Bootstrap Portlet 3</h3> | ||
+ | </div> | ||
+ | <div class="panel-options dark"> | ||
+ | <div class="panel-expand"> | ||
+ | <div class="pointer"><i class="fa fa-chevron-down"></i></div> | ||
+ | </div> | ||
+ | <div class="panel-remove"> | ||
+ | <div class="pointer"><i class="fa fa-times"></i></div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div style="display: none;" class="panel-body"> | ||
+ | <p class="justify"> | ||
+ | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris ullamcorper | ||
+ | dolor ut urna consectetur, id interdum purus pellentesque. Suspendisse fringilla | ||
+ | nunc erat, nec consectetur nisi tristique nec. Etiam dignissim hendrerit vehicula. | ||
+ | Cras eu dui vel nulla cursus feugiat. Suspendisse sem purus, molestie quis diam ac, | ||
+ | facilisis hendrerit elit. Morbi molestie ligula ut volutpat commodo. Donec ultrices, | ||
+ | metus a adipiscing ultrices, risus nibh rutrum nibh, vel interdum quam justo nec | ||
+ | nibh. Maecenas non orci a metus sollicitudin sollicitudin. | ||
+ | </p> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | <div class="col-md-2"> | ||
+ | <h4Blue>Introduction to the LID Planning and Design Guide</h4Blue> | ||
+ | <p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | ||
+ | <btnPrimary>Read more ...</btnPrimary> | ||
+ | </div> | ||
+ | <div class="col-md-2"> | ||
+ | <h4Blue>Integrating Stormwater Management into the Planning Process</h4Blue> | ||
+ | <p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | ||
+ | <btnPrimary>Read more ..</btnPrimary> | ||
+ | </div> | ||
+ | <div class="col-md-2"> | ||
+ | <h4Blue>The LID Approach</h4Blue> | ||
<p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | <p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | ||
− | < | + | <btnPrimary>Read more ..</btnPrimary> |
</div> | </div> | ||
− | <div class="col-md- | + | <div class="col-md-2"> |
− | <h4Blue> | + | <h4Blue>Design of Structural LID Practices for Stormwater Management</h4Blue> |
<p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | <p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | ||
− | < | + | <btnPrimary>Read more ..</btnPrimary> |
</div> | </div> | ||
− | <div class="col-md- | + | <div class="col-md-2"> |
− | <h4Blue> | + | <h4Blue>Monitoring of LID Practices</h4Blue> |
<p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | <p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | ||
<btnPrimary>Read more ..</btnPrimary> | <btnPrimary>Read more ..</btnPrimary> | ||
</div> | </div> | ||
− | <div class="col-md- | + | <div class="col-md-2"> |
− | <h4Blue> | + | <h4Blue>Tools</h4Blue> |
<p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | <p>Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.</p> | ||
− | < | + | <btnPrimary>Read more ..</btnPrimary> |
</div> | </div> | ||
<div class="col-md-12"> | <div class="col-md-12"> | ||
Line 133: | Line 321: | ||
</div> | </div> | ||
<div class="clearfix"></div> | <div class="clearfix"></div> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
The LID SWM Guide provides information and direction to assist engineers, ecologists | The LID SWM Guide provides information and direction to assist engineers, ecologists |
Revision as of 15:29, 15 December 2016
Welcome to the Low Impact Development Stormwater Management Practice Planning and Design Guide
This website was developed using Mediawiki, a wiki application that allows for easy editing and that has powerful search abilities. See Introduction to the wiki for more information.
The Low Impact Development Stormwater Management Planning and Design Guide (LID SWM Guide) has been developed by Credit Valley Conservation (CVC) and Toronto and Region Conservation Authority (TRCA) as a tool to help developers, consultants, municipalities and landowners understand and implement more sustainable stormwater management planning and design practices in their watersheds. Many jurisdictions have defined the term low impact development. For this document, the following definition, adapted from the United States Environmental Protection Agency (U.S. EPA, 2007) will be used:
Low impact development (LID) is a stormwater management strategy that seeks to mitigate the impacts of increased runoff and stormwater pollution by managing runoff as close to its source as possible. LID comprises a set of site design strategies that minimize runoff and distributed, small scale structural practices that mimic natural or predevelopment hydrology through the processes of infiltration, evapotranspiration, harvesting, filtration and detention of stormwater. These practices can effectively remove nutrients, pathogens and metals from runoff, and they reduce the volume and intensity of stormwater flows.
<btnPrimary>Read more ..</btnPrimary>
Note the functionality, while not the same as tabs, it allows for large blocks of content in a small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. Personally I prefer porlets to tabs.
As to portlet functionality note how they can be dragged and dropped to different locations, if you select the it will close the portlet, selecting the will remove a portlet, whereas the will close the porlet. Panels can also be set to the desired potion, either open or closed on page load.
Note the functionality, while not the same as tabs, it allows for large blocks of content in a small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. Personally I prefer porlets to tabs.
As to portlet functionality note how they can be dragged and dropped to different locations, if you select the it will close the portlet, selecting the will remove a portlet, whereas the will close the porlet. Panels can also be set to the desired potion, either open or closed on page load.
Note the functionality, while not the same as tabs, it allows for large blocks of content in a small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. Personally I prefer porlets to tabs.
As to portlet functionality note how they can be dragged and dropped to different locations, if you select the it will close the portlet, selecting the will remove a portlet, whereas the will close the porlet. Panels can also be set to the desired potion, either open or closed on page load.
Note the functionality, while not the same as tabs, it allows for large blocks of content in a small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. Personally I prefer porlets to tabs.
As to portlet functionality note how they can be dragged and dropped to different locations, if you select the it will close the portlet, selecting the will remove a portlet, whereas the will close the porlet. Panels can also be set to the desired potion, either open or closed on page load.
Note the functionality, while not the same as tabs, it allows for large blocks of content in a small space in the same way as tabs, but with additional functionality that would be difficult to accomplish with tabs. Personally I prefer porlets to tabs.
As to portlet functionality note how they can be dragged and dropped to different locations, if you select the it will close the portlet, selecting the will remove a portlet, whereas the will close the porlet. Panels can also be set to the desired potion, either open or closed on page load.
<h4Blue>Introduction to the LID Planning and Design Guide</h4Blue>
Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.
<btnPrimary>Read more ...</btnPrimary>
<h4Blue>Integrating Stormwater Management into the Planning Process</h4Blue>
Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.
<btnPrimary>Read more ..</btnPrimary>
<h4Blue>The LID Approach</h4Blue>
Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.
<btnPrimary>Read more ..</btnPrimary>
<h4Blue>Design of Structural LID Practices for Stormwater Management</h4Blue>
Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.
<btnPrimary>Read more ..</btnPrimary>
<h4Blue>Monitoring of LID Practices</h4Blue>
Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.
<btnPrimary>Read more ..</btnPrimary>
<h4Blue>Tools</h4Blue>
Lorem ipsum dolor sit amet, consectetur adipiscing dolor sit amet e.
<btnPrimary>Read more ..</btnPrimary>
Recent projects
The LID SWM Guide provides information and direction to assist engineers, ecologists
and planners with landscape-based stormwater management planning and the
selection, design, construction and monitoring of sustainable stormwater management
practices. The focus of this guide is on guidance regarding the planning and design of
structural low impact development practices for stormwater management.
The practice of managing stormwater is continuing to evolve as the science of watershed management and understanding of our watersheds grow. Effective management of stormwater is critical to the continued health of our streams, rivers, lakes, fisheries and terrestrial habitats. CVC and TRCA believe that an improved understanding of the municipal and environmental planning process and the requirements for stormwater management will lead to improvements in management practices and an increasingly standardized and streamlined approach to addressing stormwater throughout the CVC and TRCA watersheds.
The LID SWM Guide is intended to augment the Ontario Ministry of the Environment (OMOE) Stormwater Management Planning and Design Manual (2003). The OMOE manual provides design criteria for “conventional” end-of-pipe stormwater management practices such as wet ponds and constructed wetlands but provides only limited information about lot level and conveyance controls. The OMOE manual does, however, emphasize the use of a “treatment train” approach to reduce the impacts of stormwater runoff. A treatment train approach – a combination of lot level, conveyance, and end-ofpipe stormwater management practices – is usually required to meet the multiple objectives of stormwater management, which include maintaining the hydrologic cycle, protecting water quality, and preventing increased erosion and flooding.
This LID SWM Guide focuses on a number of lot level and conveyance stormwater management practices that have been used extensively in Europe, the United States, British Columbia and at demonstration sites in Ontario. These practices have only recently been considered for broad application in Ontario as part of the treatment train approach. These low impact development practices include green roofs, bioretention, permeable pavement, soakaways, perforated pipe systems, enhanced grass swales, dry swales and rainwater harvesting. The LID SWM Guide recommends and supports the use of the treatment train approach for stormwater management. Accordingly, the reader is urged to refer to the OMOE manual (OMOE, 2003), as a guide for incorporating more traditional practices such as wet ponds and wetlands into the overall stormwater management planning and design process.
The LID SWM Guide is not intended to limit innovation or restrict the use of creative solutions for stormwater management. Indeed, the OMOE, CVC, TRCA and partner municipalities encourage the development of innovative designs and technologies.
Related Documents[edit]
This manual is not a stand-alone document. It is intended to augment the Ontario Ministry of the Environment’s 2003 Stormwater Management Planning and Design Manual, which provides design criteria for “conventional” end-of-pipe stormwater management practices such as wet ponds and constructed wetlands. It is also a companion document to other stormwater related guidance documents prepared by CVC and TRCA. Amongst others, these include:
CVC
• Credit River Water Management Guidelines (CRWMG) (2007);
• Credit River Stormwater Management Criteria (currently under development; will be an appendix to the CRWMG;
• Geomorphic and Meander Belt Guidelines (an appendix to the CRWMG); • Floodline Mapping Guidelines (an appendix to the CRWMG);
• Environmental Impact Report Terms of Reference (an appendix to the CRWMG);
• Technical Guidelines for Floodproofing, 1994 (an appendix to the CRWMG);
• Hydrologic/Hydraulic Modeling (an appendix to the CRWMG Guidelines);
• Guidelines for Hydrogeologic Studies (an appendix to the CRWMG);
• Headwater Assessment Guidelines (an appendix to the CRWMG).
TRCA
• Planning and Development Procedural Manual (2007);
• Stormwater Management Criteria (currently under development);
• Floodplain Management Guideline; and
• Stream Crossing Guidelines.
Notice[edit]
The contents of this report do not necessarily represent the policies of the supporting agencies. Although every reasonable effort has been made to ensure the integrity of the report, the supporting agencies do not make any warranty or representation, expressed or implied, with respect to the accuracy or completeness of the information contained herein. Mention of trade names or commercial products does not constitute endorsement or recommendation of those products.
Acknowledgements[edit]
Project Team:
• Toronto and Region Conservation Authority
• Credit Valley Conservation Authority
• Sustainable Technologies Evaluation Program
• Aquafor Beech Limited
• Schollen & Company
• Dougan and Associates
• Kidd Consulting
• Center for Watershed Protection
• Chesapeake Stormwater Network
Funding support for this document was generously provided by:
• Region of Peel
• City of Toronto
• Region of York
• Fisheries and Oceans Canada
• Ontario Ministry of the Environment
• Environment Canada’s Great Lakes Sustainability Fund