Skip to content
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

Use some padding in wflow forcing #5

Open
Peter9192 opened this issue Jul 8, 2022 · 0 comments
Open

Use some padding in wflow forcing #5

Peter9192 opened this issue Jul 8, 2022 · 0 comments

Comments

@Peter9192
Copy link

Peter9192 commented Jul 8, 2022

Currently, no padding is used when extents are inferred from a shapefile:

https://github.com/eWaterCycle/ewatercycle/blob/50e1fa7afd86c574bf74ae2bdffc34226f4e358b/src/ewatercycle/forcing/_wflow.py#L74

In earlier applications we used to take 1.5 deg padding to make sure the forcing extents exceeded the demfile extents. I believe the 1.5 was chosen such that it was a multiple of the grid spacing for era-interim (0.75 deg).

Without padding, I now see some log messages like

2022-07-08 12:32:31,086 [3163697] WARNING  wflow.py,174 Insufficient data available, input data starts at 3.75 degrees longitude, but should be at least one grid cell larger than the DEM start at 3.570833333333352 degrees longitude.

It would be good to add back some padding in the wflow forcing generator

@BSchilperoort BSchilperoort transferred this issue from eWaterCycle/ewatercycle Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant