[gdal-dev] Limits on use of VRTs?

[Jose Gomez-Dans]

Hello,

I'm trying to do some python processing, and I thought that using VRTs
would be a great way forward. My process is basically:

1.- Putting several bands together into a single dataset. A couple of bands
have a different dataset (Byte vs Int16), so I'd like to upgrade these Byte
bands to Int16
2.- Reprojecting the result of (1) to match a particular spatial extent and
projection.

The first step I was hoping to accomplish by simply doing gdalbuildvrt
-separate (not in Python, just from the shell), but it appears that I need
an extra gdal_translate to convert all the bands to Int16 (the first band
is Byte, and gdalbuildvrt assumes all following bands will be Byte too).

Part 2 fails with a VRT dataset as input, but works OK with a GeoTIFF.

In the end, I have everything working by external calls to gdalwarp,
gdalbuildvrt and gdal_translate, but this is cumbersome and uses lots of
disk I/O, when this is a situation where doing it using VRTs would be
beautifully simple.

I must be clearly missing limitation on VRTs. I'm using GDAL version 1.11.2
on Linux, and any pointers would be appreciated.

Regards,
Jose
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20150927/60b73990/attachment.html>