Re: [gdal-dev] Utilities as a library, C API

2016-10-20 Thread Even Rouault
On Thursday 20 October 2016 15:03:03 Ivan Lucena wrote: > Hi Even, > > > OK. It is what it is. I guess. > > > I wrote a little test code: > > > #include > #include > > int main( int argc, char** argv ) > { >char* papszArgv[1024]; >int i = 0; > >const char* pszSrcFilename =

Re: [gdal-dev] Utilities as a library, C API

2016-10-20 Thread Ivan Lucena
Maybe it has something to do with that. The GTIFF create-option BLOCKXSIZE doesn't seems to work. I tries with larger images and it seems like we can only control the number of rows on a block (BLOCKYSIZE), but not the number of columns (BLOCKXSIZE). Thanks again. Best regards, Ivan

Re: [gdal-dev] Utilities as a library, C API

2016-10-19 Thread Even Rouault
Ivan, The fact that GDALTranslateOptions is opaque is a design decision that was the outcome of the discussion phase of RFC 59. It was thought that it would be difficult to have a stable C structure that could be also extented in the future without becoming too messy. For example regarding old

[gdal-dev] Utilities as a library, C API

2016-10-19 Thread Ivan Lucena
Hi there, I am trying to use C API defined in gdal_utils.h. By reading the RFC 59.1 I understand that the SWIG wrappers will have a nice interface to pass the parameters [1], ex.: format --- output format ("GTiff", etc...) outputType --- output type (gdal.GDT_Byte, etc...)