You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hydrology uses geospatial operations, encompassing tasks such as watershed delineation and extraction of physiographic variables at the watershed scale. PAVICS-Hydro has implemented various functionalities in ravenpy to execute these operations.
It would be interesting to integrate some of these features into xhydro by leveraging the work done in ravenpy while also adding some new functionalities.
Potential Solution
The solution would include the functionalities included in ravenpy plus the followings : Watershed Delineation
Support concurrent delineation of multiple watersheds simultaneously.
Enable access to official watershed polygons (shapefiles/geojson/geoparquet) from authoritative sources (DEH, HYDAT, USGS, HQ, etc.) —implemented collaboratively with xdatasets.
Physiographic Variable (or others) Extraction
Support simultaneous extraction of physiographic variables across multiple watersheds.
Facilitate the extraction of variables present in STAC catalogs (e.g., Planetary Computer).
Accommodate cases where users employ their own rasters for extraction.
Implement extraction considering pixel weighting rather than an "all_touched" approach, as this can significantly impact final results —implemented collaboratively with xdatasets.
Additional context
No response
Contribution
I would be willing/able to open a Pull Request to contribute this feature.
The text was updated successfully, but these errors were encountered:
…ilds (#61)
<!-- Please ensure the PR fulfills the following requirements! -->
<!-- If this is your first PR, make sure to add your details to the
AUTHORS.rst! -->
### Pull Request Checklist:
- [x] This PR addresses an already opened issue (for bug fixes /
features)
- This PR fixes#60
- [x] (If applicable) Documentation has been added / updated (for bug
fixes / features).
- [X] (If applicable) Tests have been added.
- [X] CHANGES.rst has been updated (with summary of main changes).
- [X] Link to issue (:issue:`number`) and pull request (:pull:`number`)
has been added.
### What kind of change does this PR introduce?
This PR adds a GIS module for usual geospatial operations that are
common in hydrology such a watershed delineation, watershed properties
extraction, etc. It adapts the work that's been done in
[ravenpy](https://ravenpy.readthedocs.io/) while also adding some new
functionalities.
**Watershed Delineation**
- [x] Support concurrent delineation of multiple watersheds
simultaneously.
- [X] Enable access to official watershed polygons
(shapefiles/geojson/geoparquet) from authoritative sources (DEH, HYDAT,
USGS, HQ, etc.) —implemented collaboratively with xdatasets.
**Physiographic Variable (or others) Extraction**
- [x] Support simultaneous extraction of physiographic variables across
multiple watersheds.
- [X] Facilitate the extraction of variables present in STAC catalogs
(e.g., Planetary Computer).
- [X] Implement extraction considering pixel weighting rather than an
"all_touched" approach, as this can significantly impact final results
—implemented collaboratively with xdatasets.
### Does this PR introduce a breaking change?
No
### Other information:
This PR also integrates the changes from #65 and #68
Addressing a Problem?
Hydrology uses geospatial operations, encompassing tasks such as watershed delineation and extraction of physiographic variables at the watershed scale. PAVICS-Hydro has implemented various functionalities in ravenpy to execute these operations.
It would be interesting to integrate some of these features into xhydro by leveraging the work done in ravenpy while also adding some new functionalities.
Potential Solution
The solution would include the functionalities included in ravenpy plus the followings :
Watershed Delineation
Physiographic Variable (or others) Extraction
Additional context
No response
Contribution
The text was updated successfully, but these errors were encountered: