-
Notifications
You must be signed in to change notification settings - Fork 3
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
openEO is not returning all bands after UDF execution #92
Comments
I'm wondering if this is caused by using the
I've also tried the following paths, but without success:
metadata = CollectionMetadata({})
metadata = metadata.add_dimension('var', '', 'bands')\
.rename_labels(dimension='var', target=phenology_bands)
phenology.metadata = metadata
phenology = phenology.add_dimension('bands', phenology_bands[0], 'bands')
phenology = phenology.rename_labels(dimension='bands', target=phenology_bands) |
I've also tried using the size = 125
phenology = base_ndvi.apply_neighborhood(process=lambda x: run_udf(x, udf=load_phenology_udf(), runtime="Python"),
size=[
{'dimension': 'x', 'value': size, 'unit': 'px'},
{'dimension': 'y', 'value': size, 'unit': 'px'}
], overlap=[]) However this results in an error that is also reported in Open-EO/openeo-geopyspark-driver#434 |
It looks like summarizing your experiments really help with resolving the issue 😄 . After looking at the screenshots I noticed that the resulting band from the UDF is called phenology = phenology.add_dimension('var', phenology_bands[0], 'bands')
phenology = phenology.rename_labels(dimension='var', target=phenology_bands) |
On the
openeo-publish
branch we are currently integrating the different FuseTS services into openEO. One of the services we are curently working on is the Phenology service. In the following file, you can find a function that tests the Phenology UDF through openEO:https://github.com/Open-EO/FuseTS/blob/openeo_publish/src/fusets/openeo/services/publish_phenology.py#L34
When the UDF is executed, the result seems to be valid datacube that contains 18 bands (see log entry with
Phenology result
. Each of these bands represent one of the phenology metrics that are calculated.However, after downloading the result, there is only 1 band left. It looks like some of the band information gets lost.
The text was updated successfully, but these errors were encountered: