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

Is there some interest in having an GroundWaterML2 import/export in flopy? #2402

Open
rabbl opened this issue Dec 20, 2024 · 0 comments
Open

Comments

@rabbl
Copy link
Contributor

rabbl commented Dec 20, 2024

GroundWaterML2 (GWML2) is an Open Geospatial Consortium (OGC) standard designed to facilitate the exchange of groundwater model data within institutions and modelling frameworks.

As it's approval is yet some years old, there is not much adoption in the world of groundwater modelling, as far we could do our research.

As we are looking for funds for the standard implementation in Python and JS/TS, we are gathering the most useful use cases. So we ask you: Is there a basic interest within the flopy developer und user community to have GroundWaterML2 as Import/Export format plugin in place?

Why do we think this idea is valid and fundable:

European public institutions are trying to switch to modelling approaches which can deliver the model data in a format which is standardised after finishing the work. With an open source solution like modflow/flopy we could develop this implementing an GWML-export/import and make this software unique in the market. Solution partners could be exchanged over the lifetime of a model. University and community driven modelling of public models becomes viable.
With this unique feature, closed source solutions will have to follow this approach and closed models can be exported, validated, approved and also reused from other parties, when exported to the GWM2 format. This has a big advantage in our opinion to enhance the use of modflow and other open source solutions.

The fund we are focussing on has a deadline which ends 2nd of January 2025. We are two developers which can spend 6 month on this issue. If you see also a valid use case for this feature we will put all our energy and effort to write a very good proposal before the deadline and submit it. If approved we can start full time work on this in mid to end 2025.

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