Open tobwen opened 5 years ago
You should ask questions from the gdal-dev mailing and not through the issue tracker.
There may be an issue here if GDAL creates the request automatically with GEOTIFF:TILING=TRUE and the server does support GeoTIFF extension (that appears in GetCapabilities) but does not support tiling. Support for tiling is optional but as far as I know it is not possible to know it beforehand. If server does not support tiling it should send "TilingNotSupported" error as a response for the GetCoverage request. I do not know any geotiff-capable WCS 2.0 server that would not support tiling as well but such may exist.
As an administrator of a WCS server I would say that it is just good if GDAL makes tiled requests and it might well be the default behavior to try always with tiling=true first. If I remember right some servers do not have a default for the tilesize so explicit tileheight=256 and tilewidth=256 might be needed as well.
You should ask questions from the gdal-dev mailing and not through the issue tracker.
It was not actually meant to be a question, I just put it that way. I assumed that it was a mistake. I will reformulate the report accordingly.
Expected behavior and actual behavior.
As a user, I want to create a tiled GeoTIFF using
gdal_translate
using-co TILED=YES
.As you can see, the request for tiles get passed through to the server. This is unexpected, since
-co TILED=YES
is a creation option forof GTiff
and not an open option.Steps to reproduce the problem.
License of this dataset: http://www.ioer-monitor.de/fileadmin/Dokumente/PDFs/Nutzungsbedingungen_IOER-Monitor.pdf
Operating system
Windows 7, 64 bit
GDAL version and provenance
GDAL 2.5.0dev, released 2019/99/99 (latest one from OSGeo4W)