Storage area polygons
Storage nodes often represent detention basins or other locations with large areas. Pipes enter/leave from opposite sides. With the standard link/node configuration, one or more link will be mis-configured compared to the actual location.
I have long wanted to have a storage area polygon, with links connecting to the nearest edge, rather than the center.
Great ideas! The goal is the simplify the physical location to either measured (as-built) or designed locations of pond outfalls, while either logically enforcing the relationship of outfalls to pond/outlet without forced links that do not represent physical pipes.
Gregory Smith commented
Part of the issue is having to geometrically alter the links flowing into the storage area. Therefore, the links shouldn't necessarily connect to the edge, but somewhere within the storage area (read detention basin) and they should be able to be an outfall that can then link to the actual storage node. this will better represent the model both graphically & possibly hydraulically (since the water flow will change from being with a pipe to flowing across a flat surface (with a different Manning's).
I suppose I could change the outfalls back into a (flat) node and have a wide shallow channel connect it to the storage node, but this is going to report structures that simply don't exist.
Pictures show has it is, and how it has to be be dummied to work.
Since there will be constructed outfalls in the basin, these should be able to be reported in the Grids (not simply ignored as is they don't exist).
Anthony Holder commented
I haven't been back here since I suggested this over a year ago. I thought about it again today. It would only be a visual thing for display. This morning, I thought of another way of handling it that might be easier to program and understand.
It would be to create a 'storage outfall' node that visually would hold the location of the storage area's outfall, but would actually be treated in the model as if it were the storage area. It would be linked to an actual storage node and have a dashed line showing the connection. That would probably be easier to program than having a polygon. When the .dat file is created by the GUI to send to the engine, it would only have the one storage node in it. The 'storage outfall' node wouldn't be included at all.