Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

> I have run some initial tests on an untiled/uncompressed image basically > skipping step 1 and going straight to adding overviews and translating to > reorder, compress, and tile. The resulting image passes the COG validator > test, meaning it is a "valid" COG, though the overview offset values

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

Hi Even, I have seen pretty much everywhere that COG's are created in 3 steps: 1. compress and tile the image $ gdal_translate -co TILED=YES -co COMPRESS=DEFLATE in.tif tmp.tif 2. add overviews $ gdaladdo -r average 2 4 8 16 tmp.tif 3. reorder overviews $ gdal_translate -co TILED=YES -co

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

Added the delete and validate works now. Thanks! On Wed, Feb 14, 2018 at 11:28 AM, Even Rouault wrote: > On mercredi 14 février 2018 11:00:01 CET Kurt Schwehr wrote: > > > (working from pretty close to head...) > > > > > > A follow up question on how to create cogeo

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

On mercredi 14 février 2018 11:00:01 CET Kurt Schwehr wrote: > (working from pretty close to head...) > > A follow up question on how to create cogeo files... > > I appear to need to do additional work to set BLOCK_OFFSET_?_?. How do I > go about this? > > I'm trying to create a cogeo without

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

(working from pretty close to head...) A follow up question on how to create cogeo files... I appear to need to do additional work to set BLOCK_OFFSET_?_?. How do I go about this? I'm trying to create a cogeo without gdal_translate in java by using create and createcopy like this:

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

Thanks Even for the feedback. There have be a few offline discussions going on and Even added some notes to the document on Trac: https://trac.osgeo.org/gdal/wiki/CloudOptimizedGeoTIFF?action=diff=11

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

On mardi 14 novembre 2017 14:20:58 CET Kurt Schwehr wrote: > Hi Even, > > I have some follow up questions on Cloud Optimized GeoTIFFs: The main constraint of C.O.G is that all the IFD definitions are at the beginning of the file, to avoid seeking at various points in it. Other parameters are

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

Hi Even, I have some follow up questions on Cloud Optimized GeoTIFFs: * Is there a preferred/better INTERLEAVE if there is more than one band? * Is there a preferred tile blocksize? You have 512 in your examples. Are there any major trade offs between using 128, 256, 512, or 1024 for x and y

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

On mercredi 10 mai 2017 14:41:44 CEST Peter Schmitt wrote: > Hi, > > I ran into something confusing when using gdal-2.2.0 to generate Cloud > Optimized GeoTIFFs following the instructions at: > https://trac.osgeo.org/gdal/wiki/CloudOptimizedGeoTIFF > > Here's what I did: > > 1. Fetch an image:

[gdal-dev] Creating Cloud Optimized GeoTIFFs

Hi, I ran into something confusing when using gdal-2.2.0 to generate Cloud Optimized GeoTIFFs following the instructions at: https://trac.osgeo.org/gdal/wiki/CloudOptimizedGeoTIFF Here's what I did: 1. Fetch an image: env CPL_VSIL_CURL_ALLOWED_EXTENSIONS=tif GDAL_DISABLE_READDIR_ON_OPEN=YES