jfalkowski
Civil/Environmental
- Mar 11, 2020
- 3
Good afternoon, I'm just curious if anyone has any workarounds for the following?
When modeling ponds (detention basins) with exfiltration outlets and constant velocity outfall type, we need a way to exclude a certain square footage of the bottom surface area from exfiltration.
Review agencies are now requiring that we exclude the forebay(pre-treatment) areas from the infiltrating area. Unfortunately, there are work arounds but no good way to accurately model the exfiltration area while still keeping the total bottom area available for volume.
One thought was to simply use constant flow, converted to cfs, instead of velocity (in/hr) because we can calculate the flow based on the reduced bottom footprint. The downfall to that is we don't take advantage of exfiltration on the side slopes. When we use velocity, the flow will continue to increase as the detention pond fills because we are taking advantage exfiltration in the side slopes.
The Discharge multiplier simply reduces the rate. In a perfect world, it would be nice if another multiplier option could be added to control the available exfiltration "area" as a percentage of the bottom surface area of the pond. That way, say 85% of the bottom of the pond could be used for exfiltration but 100% is still used for storage volume.
Some guys here have been modeling the forebays as separate ponds that then link to the main pond but i don't like that. Another option was to set the bottom of the pond 0.01' lower and make that area 85% smaller than the 0.0' elevation. The problem with that is I believe the exfiltration will start in the remaining 15% once the pond elevation raises that 0.1'
I'm open to suggestions but would really love more flexibility added to the software for exfiltration.
Thanks!
Jon Falkowski, P.E.
When modeling ponds (detention basins) with exfiltration outlets and constant velocity outfall type, we need a way to exclude a certain square footage of the bottom surface area from exfiltration.
Review agencies are now requiring that we exclude the forebay(pre-treatment) areas from the infiltrating area. Unfortunately, there are work arounds but no good way to accurately model the exfiltration area while still keeping the total bottom area available for volume.
One thought was to simply use constant flow, converted to cfs, instead of velocity (in/hr) because we can calculate the flow based on the reduced bottom footprint. The downfall to that is we don't take advantage of exfiltration on the side slopes. When we use velocity, the flow will continue to increase as the detention pond fills because we are taking advantage exfiltration in the side slopes.
The Discharge multiplier simply reduces the rate. In a perfect world, it would be nice if another multiplier option could be added to control the available exfiltration "area" as a percentage of the bottom surface area of the pond. That way, say 85% of the bottom of the pond could be used for exfiltration but 100% is still used for storage volume.
Some guys here have been modeling the forebays as separate ponds that then link to the main pond but i don't like that. Another option was to set the bottom of the pond 0.01' lower and make that area 85% smaller than the 0.0' elevation. The problem with that is I believe the exfiltration will start in the remaining 15% once the pond elevation raises that 0.1'
I'm open to suggestions but would really love more flexibility added to the software for exfiltration.
Thanks!
Jon Falkowski, P.E.