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
There are some well known and some not so well known, but awesome tools. I think some really fall into the scope of hydrobox and implementing some interfaces to these packages makes them usable with hydrobox.
@MarcusStrobl , this would also make them usable in V-FOR-WaTer, so it might be worth it to scan the list for you as well.?
Besides that, do you have general comments concerning hydrobox (maybe especially on a WPS_toolbox interface), before I dive into work?
Also, I think we could transfer hydrobox to V-FOR-WaTer organization. That can make it more visible in the context it is developed. We could also streamline developments better in GH issues on a project board.
I'm open to any suggestions!
The text was updated successfully, but these errors were encountered:
For the WPS_toolbox interface it would be good to get names and units of parameters. Though, as each tool has its own interface I guess these things can also be set within the interface. And I should document some standards for the wps interface.
Do you want to transfer your project completely, or should we just fork it in V-FOR-WaTer?
I have some plans to start developing into this package again.
My first plan is to check this list raoulcollenteur/Python-Hydrology-Tools
There are some well known and some not so well known, but awesome tools. I think some really fall into the scope of hydrobox and implementing some interfaces to these packages makes them usable with hydrobox.
@MarcusStrobl , this would also make them usable in V-FOR-WaTer, so it might be worth it to scan the list for you as well.?
Besides that, do you have general comments concerning hydrobox (maybe especially on a WPS_toolbox interface), before I dive into work?
Also, I think we could transfer hydrobox to V-FOR-WaTer organization. That can make it more visible in the context it is developed. We could also streamline developments better in GH issues on a project board.
I'm open to any suggestions!
The text was updated successfully, but these errors were encountered: