Skip to content

Integrate yprov4wfs into OpenEO (openeo_pg_parser_networkx) #97

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

Closed
wants to merge 1 commit into from

Conversation

hapix
Copy link
Contributor

@hapix hapix commented Apr 15, 2025

This pull request integrates the yprov4wfs library into the openeo-pg-parser-networkx

Version Compatibility:
This integration work was based specifically on tag 2023.5.1, which is the version referenced in the OpenEO local processing cookbook.

Manual testing performed using the following notebook (TU Wien use case) with the local processing setup:
1_yeoda_dc.ipynb – openeo-flood-mapper-local

Added support for yprov4wfs integration in the OpenEO pg parser networkx
@ValentinaHutter
Copy link
Collaborator

From the email conversation with our EURAC colleagues, I think it can be concluded, that you can continue with the latest version of the openeo-pg-parser-networkx. So, the next step would be to update the PR.

@hapix
Copy link
Contributor Author

hapix commented May 6, 2025

Thanks for the update!

I've already updated this PR to use the latest version of openeo-pg-parser-networkx accordingly.
I’ve also created this PR to openeo-python-client to make it compatible with the new changes introduced in openeo-pg-parser-networkx.

By the way, there's a related discussion in this PR and also here that are related about how the provenance output and file-saving should be handled. It would be great to get your input there as well, since it ties into the behavior we’re finalizing here.

I understand from earlier conversations that you might already have your own approach for saving provenance on the backend — so your perspective would really help ensure we align with that and avoid redundant or conflicting logic.

@rtmiz
Copy link
Member

rtmiz commented May 19, 2025

Closing this because #98 exists.

@rtmiz rtmiz closed this May 19, 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

Successfully merging this pull request may close these issues.

3 participants