> The VRT driver is the usual solution to a lot of problem but we cannot > automatize the solution on environment other than C/C++ or command > scripts. But unfortunately, even if we add those two function much of the > VRT magic is still not on the VRT code but in gdal_translate.cpp [0].
Yes, some added value still is in the utilities. An idea that has floated around and could be a potential solution for this would be to put the utility code in the library itself and have it mapped as a C API that could also be used from SWIG bindings. Even -- Geospatial professional services http://even.rouault.free.fr/services.html _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
