Re: [gdal-dev] Cloud Optimised GeoTiff format

2017-09-08 Thread daunnc
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

Re: [gdal-dev] Cloud Optimised GeoTiff format

2017-09-08 Thread daunnc
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

[gdal-dev] Cloud Optimised GeoTiff format

2017-09-08 Thread daunnc
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

Re: [gdal-dev] Generating Cloud Optimized GeoTIFFs

2017-08-29 Thread daunnc
> I suspect some issue with your setup Thanks a lot, I agree that probably it's a software issue (breakpoint helped), and my GDAL version is 2010100 (I commented out this version check before as thought that it's not that important). Thanks again, and thanks for your reply, I'll upgrade GDAL and h

Re: [gdal-dev] Generating Cloud Optimized GeoTIFFs

2017-08-29 Thread daunnc
Well I'll post the exact message here, as probably I could use not really correct terms in my messages: python validate_cloud_optimized_geotiff.py in.tiff Traceback (most recent call last): File "validate_cloud_optimized_geotiff.py", line 218, in sys.exit(main()) File "validate_cloud_opt

Re: [gdal-dev] Generating Cloud Optimized GeoTIFFs

2017-08-29 Thread daunnc
Ah sorry reread your message. Yes, my tiff has no IFD_OFFSET /tag/ (line int(main_band.GetMetadataItem('IFD_OFFSET', 'TIFF')) fails), but gdalinfo reads tiff info well and moreover reading tiff manually by bytes I can see that /offset field/ has a correct value. -- View this message in context:

Re: [gdal-dev] Generating Cloud Optimized GeoTIFFs

2017-08-29 Thread daunnc
Cool, thanks! Can you write here when it'll be updated? The error is missing IFD_OFFSET tag. Should it be specified manually or it is fine to have it missing? Is it a COG requirement? -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Generating-Cloud-Optimized-GeoTIFFs-tp53

[gdal-dev] Generating Cloud Optimized GeoTIFFs

2017-08-29 Thread daunnc
Hi everybody! We're implementing COGs support in GeoTrellis, and there is appeared a question related to cloud optimized geotiff definition. Following this page: // in.tif is some random tiff. 1. gdaladdo in.tif 2 4 8 16 32 2. gdal_tr