Open-EO / Open-EO/openeo-python-driver
Running UDF on Vector Cube
Open
Nobody has claimed this yet.
vector cubes
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
reported by @mbuchhorn :
- loading vector cube with
connection.vectorcube_from_paths(which usesload_uploaded_filesprocess) - run UDF on that cube
fails with
File ".../openeo_driver/ProcessGraphDeserializer.py", line 1491, in run_udf
data = data.to_legacy_save_result()
File ".../openeo_driver/datacube.py", line 366, in to_legacy_save_result
if cube.dims == (self.DIM_GEOMETRIES, "t"):
AttributeError: 'NoneType' object has no attribute 'dims'
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
Reproduce the vector-cube UDF flow through connection.vectorcube_from_paths and load_uploaded_files. Start in openeo_driver/ProcessGraphDeserializer.py at run_udf and follow the call into openeo_driver/datacube.py at to_legacy_save_result. Done means this flow no longer raises the reported NoneType AttributeError and the UDF result is handled successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100