Status Update
Comments
br...@google.com <br...@google.com> #2
It doesn't look like this bug has a link to the affected dataset(s) in Earth
Engine. Please reply to this bug with a comment containing a URL of the form
"
If this issue doesn't affect an existing dataset, consider moving in into the "Public Trackers > Earth Engine > Datasets > New Datasets" component. If the dataset is a new or updated version of an existing dataset, you can add the URL of the existing one. And if you cannot add a URL, you can disable future automated messages by adding a comment with "dataset_bug_ranker: disable" on its own line.
Reason: Issue does not contain a dataset URL. dataset_bug_ranker: remind=P7D
Description
I need to code a function that has a consistant behaviour whatever the number of bands of the source image. As reported in https://issuetracker.google.com/issues/327605560 the reducers are not. if the source image is a single band image then the output result is using the reducer name if not it's using the band name. I want to make sure it's always using the band name so I did the following:
and I got the following error:
I initially though it was a parsing error and you were badly interpreting the Computed object so I directly use the raw list and it crashed as well.
So I last resort I came back to the example you gave to me when I opened https://issuetracker.google.com/issues/327605560 : https://code.earthengine.google.com/4de51d4647db94dca1efff20cc7aacac and all the calls to setOuputs with more than 1 band are broken. Can you rapidly investigate, my LDC pipeline are heavily relying on this.