Please feel free to add folders here for your hacking projects. Do this by forking this repository and wowkring on your forked repository. Add a folder to this folder in your repository and after your work publish your work in your repository and afterwards send a pull request to make your changes available in this central repository.
The following list are proposals for possible features or extensions of openEO. You can either work on your own ideas or on one of the proposals:
- OpenID Connect integration: OpenID Connect is a mechanism to authenticate and authorize users against a service provider. openEO uses this protocol, but hasn't yet implemented it in any back-end or front-end.
- Process Graph Storage on client-side or sserver-side
- GraphQL Wrapper for openEO: GraphQL is an evolving technology that is an alternative for RESTful services. This feature proposal aims to investigate into to the feasibility to provide a GraphQL endpoint for openEO.
- Extending the JavaScript client library
- Implementing a framework for back-end compliance testing
- Implementing Job Management in the openEO Python client
- Adding Authentication to the openEO Python client
- Adding Delete File Feature (API: /users/{user_id}/files/{path} endpoint) to the openEO Python client
- Adding a User class to python client (maybe returned by session.auth()) to the openEO Python client
- Add Exception Handling / Error Handling (e.g. If a process is called, that is not implemented by the backend) to the openEO Python client. See API v0.3 for more information about error handling in the next version of openEO.
- Extend the GEE back-end to support other GEE scripts: Do you have any Google Earth Engine script you want to run with openEO? We may be able to add the required processes to the back-end and run your script via openEO.
- Codegeneration for openEO clients
- GDAL pixel functions
- GraphQL wrapper for openEO
- Web Editor: Visual Process Graph Builder
- OpenSearch implementation for OpenEO WCPS driver
- #101 Datasets with disjoint extents
- #100 Debugging and getting intermediate result and metadata
- #99 xxx_time: Names for aggregate functions are misleading
- #98 ndvi: Name of the process
- #97 Common band names
- #96 Further references / links for data discovery and other parts of the API
- plus contributions to existing issues.
- #20 Better error messages
- #21 Making required packages optional
- #22 Performance of describeCollection across OSs
- #38 Merging session.image() and session.imagecollection()
- #37 Pull Request
- #36 Pull Request
- #35 Improvement of displaying ImageCollection
- #34 Adding possibiliy to visualize the process graph
- #33 Pull Request
- #32 Adding error handling to user file handling
- #31 Pull Request
- #30 Pull Request
- #29 Different approach on building process graph (like Dask)
- #28 Pull Request
- #27 UDF: rename function
- #26 NDVI calculation with UDF gives inconsistent results when image graph is constructed in parts
- #25 Using Python date/datetime
- #24 User feedback on adding a process
- #23 Error Handling: job.download
- #22 Imagery methods: Usabilitiy and User Input
- #21 Confusion: max_time, min_time
- #20 Confusion session.get_collection vs. session.imagecollection()
Further Python Client implementations from the participants:
- Adding metadata to imagecollection
- Adding Unittests for the REST Session class
- Adding some functions to the ImageCollection
- Implementinon of a possible solution for visualizing the process graph