Clear, great!
Sounds a bit sad though. My dreams faced with reality.
At least it's definitely obvious how COG should be formed in a perfect
world.
Thanks again!
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
___
gdal-dev ma
On vendredi 8 septembre 2017 09:35:33 CEST daunnc wrote:
> Haha, awesome!
>
> A bit more context: I think that it could be a great thing to query TIFFs
> directly (for instance) from AWS landsat bucket, and they already have
> generated .ovr files which can be used, probably an additional extra qu
Haha, awesome!
A bit more context: I think that it could be a great thing to query TIFFs
directly (for instance) from AWS landsat bucket, and they already have
generated .ovr files which can be used, probably an additional extra query
would be not that bad. I didn't check segments ordering yet in
On vendredi 8 septembre 2017 08:50:36 CEST daunnc wrote:
> Hi again!
>
> According to the validate_cloud_optimized_geotiff.py script, overviews can't
> be stored in a separate .ovr files. Are there any reasons why it was done?
Because as the dictator of the cloud optimized geotiff spec, I decided
Hi again!
According to the validate_cloud_optimized_geotiff.py script, overviews can't
be stored in a separate .ovr files. Are there any reasons why it was done?
Can in theory there be any problems related to overviews storage in a
separate .ovr file?
Thanks a lot in advance.
--
Sent from: h
