[gdal-dev] baseline tiff and rpb file

[Even Rouault]

Le jeudi 16 avril 2015 18:02:21, Ivan Lucena a écrit :
> Hi Even,
> 
> Thank you very much for fixing that. Those options are a little trick. I
> understand.
> 
> So now what is the default to deal with RPC on a baseline tiff (-co
> profile=baseline) is:
> 
> a) Create the RPC on a .tif.aux.xml if there is a "RPB=NO" and when there
> is no RPB.
> 
> - That means that for baseline Tiff files the RPC goes to a RPC by default.
> 
> b) Create the RPC on a .tif.aux.xml only if there is a "RPB=NO".
> 
> - That means that RPC is not the default. That behavior is more compatible
> with other "basic" formats. I guess.

Sorry, I didn't get the above ;-) The examples speak better:

$ gdal_translate -q byte_rpc.tif out.tif; ll out*
-rw-r--r-- 1 even even 1294 2015-04-16 18:23 out.tif

$ gdal_translate -q byte_rpc.tif out.tif -co RPB=YES; ll out*
-rw-r--r-- 1 even even 2367 2015-04-16 18:25 out.RPB
-rw-r--r-- 1 even even 1294 2015-04-16 18:25 out.tif

$ gdal_translate -q byte_rpc.tif out.tif -co profile=baseline; ll out*
-rw-r--r-- 1 even even 2367 2015-04-16 18:21 out.RPB
-rw-r--r-- 1 even even  546 2015-04-16 18:21 out.tif

$ gdal_translate -q byte_rpc.tif out.tif -co profile=baseline -co rpb=yes; ll out*
-rw-r--r-- 1 even even 2367 2015-04-16 18:21 out.RPB
-rw-r--r-- 1 even even  546 2015-04-16 18:21 out.tif

$ gdal_translate -q byte_rpc.tif out.tif -co profile=baseline -co rpb=no; ll out*
-rw-r--r-- 1 even even  546 2015-04-16 18:21 out.tif
-rw-r--r-- 1 even even 2227 2015-04-16 18:21 out.tif.aux.xml

$ gdal_translate -q byte_rpc.tif out.tif -co profile=baseline -co rpctxt=yes; ll out*
-rw-r--r-- 1 even even 3300 2015-04-16 18:23 out_RPC.TXT
-rw-r--r-- 1 even even  546 2015-04-16 18:23 out.tif

$ gdal_translate -q byte_rpc.tif out.tif -co profile=baseline -co rpb=yes -co rpctxt=yes; ll out*
-rw-r--r-- 1 even even 2367 2015-04-16 18:24 out.RPB
-rw-r--r-- 1 even even 3300 2015-04-16 18:24 out_RPC.TXT
-rw-r--r-- 1 even even  546 2015-04-16 18:24 out.tif

> 
> Anyway, can we backport that to 1.11 and 1.10?

I'm not really enthusiastic about that. The fix was not trivial and required a bit of refactoring.

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com