Open-EO / Open-EO/openeo-python-client
Parameter factories: add nullable "temporal_extent"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
Parameter.spatial_extent has a schema allowing the parameter to be null. Note that this is based on spatial_extent parameter of load_collection process: https://github.com/Open-EO/openeo-processes/blob/6141771129d58d2a292db3b91d80c812c49f4e52/load_collection.json#L20-L110
Parameter.temporal_interval is based on a predefined schema https://github.com/Open-EO/openeo-processes/blob/6141771129d58d2a292db3b91d80c812c49f4e52/meta/subtype-schemas.json#L281-L293 and can only be an array of two items.
I think we also need a factory for a temporal extent that can be null, like the temporal_extent parameter of load_collection: https://github.com/Open-EO/openeo-processes/blob/6141771129d58d2a292db3b91d80c812c49f4e52/load_collection.json#L114-L140
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Parameter.spatial_extent and Parameter.temporal_interval factory implementations. Compare them with the linked load_collection.json temporal_extent schema and the referenced subtype-schemas.json definition. Done means a temporal-extent factory exists that permits null in the same way as load_collection, with behavior covered by the project's existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100