Closed clausmichele closed 3 weeks ago
In the meanwhile I applied a workaround, to make sure that the y dimension has decreasing values and therefore negative resolution: https://github.com/SARScripts/openeo_odc_driver/commit/d865cfb177828ad88cc26b75f4de7232b195efeb Now it works fine on our back-end, but maybe we should still address this issue.
Thanks Michele. Can you send me an example file for testing purposes? I assume this is an upstream issue in OL or geotiff.js and I'll need to provide an example if I open an issue with them.
Sure! Not working:
Working:
tiff_samples.zip
@clausmichele I've just tested this in pure OpenLayers and it also doesn't work there so this is an upstream issue. I'm just wondering what does a negative resolution mean? Is that valid? Anyway, this is something to report to the openlayers guys...
In this case the positive resolution for y
is the issue. Anyway, most of the time there is a positive resolution along x
and a negative along y
. However, a geoTIFF can contain theoretically any combination of them.
Okay, I've submitted a bug report: https://github.com/openlayers/openlayers/issues/14238
Looks like a bug in geotiff.js: https://github.com/geotiffjs/geotiff.js/pull/337
I guess this is a bug. When using the Eurac back-end, the result of this graph is showed correctly:
this instead, where the result comes from a different collection, shows just a black box. The difference between the two geotiffs is the resolution, which on the not working one is (10,10) instead of (10,-10).
Fixing the collection resolution solves the issue, but I wonder if it shouldn't cause a problem in the viewer.