-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QGEP SWMM raingages export #646
Comments
@DflGruBoe @kfischerar @urskaufmann What do you think about this. How many raingauges do you need in your projects? |
Till now the problem was, how many raingauges with good data are available in a study area. I have always defined the raindata in the hydraulic program, not in the vsa-dss database. |
Feedback from technical group:
Proposition: |
@tproduit is the proposition added to the documentation? @TriformMoritz do you agree with such strategy? |
Current export of rain gages works like this. It is documented in the PR QGEP_SWMM creates one raingage for each subcatchment. By default:
See |
To be closed as soon as doc PR is merged ! |
I usually use only one rain for the whole area for one typical rain event (with a given retourn time amd a typical curve). So I would leave it as default. So my recommandation:
So if I understand Timothee, this is how it will work! |
I agree with @TriformMoritz. This also treats the bug that two raingages are created for a catchment if it is connected to fresh- and wastewater |
creates one raingage per status instead of one raingage per subchatchment. See QGEP/QGEP#646
Currently one raingage per subcatchment is exported. Then, the user can assign the same rain to each raingages. However, the most common case would a single raingage for the entire study area.
In special cases, if the study area is very hilly and extended the user could then choose to add more raingages manually.
The text was updated successfully, but these errors were encountered: