@davidsmavrov, what was the result with the particles from FlexHopper, I wonder?
Not much different from what I get with the other sollutions. The problem with the direction is solvable. It doesn’t really matter all that much which tool I will use. What I am stuck at is the actual amount of water I will get at a certain rain fall. Then I use a solution very similar to your first post to calculate the pipes needed.
Actually at this stage this idea turns out to be pretty clever. No matter which solution one choses to use for the flow paths, their end points tend to collect at the same locations. All one needs to do after that is use Cull Duplicates component, to cull the duplicate points, count the number via the Valance output, then calculate what % of the total amount of points is this. And yeah… pretty neat way to estemate the amount of water you will have at a given collector. Thanks man. For now this works very well
I worked on a project that dealt with this question at the landscape scale. It was called EpiFlow Link to project brief.
The primary metric of concern was peak flow calculated by the “Rational Method” to help size green infrastructure, and predict the impact of development on site hydrology. In that case we spent more time thinking about integrating runoff coefficients and storm size/duration in order to inform storm volumes, but getting the area of the watersheds is a simpler operation.
We aggregated mesh faces that had their flow path terminated in the same location. Using a method like this could tell you drainage area for each of your gutters.
Amazing! Thank you for sharing! Can’t wait till the weekend so I can have a good look at this!