Dear GDAL friends, I'm looking for tips & tricks for improving performance when working with WMTS services. As I mentioned in previous mails, I work with GDAL C API. My main task is to generate image for a given extent and defined output image size (WxH). I convert this extent to appropriate offset and source window size. Using GDALDatasetRasterIO and pBuffer I create bitmap in required format. This method is different from what I see in, for example, QGIS, where each tile is paint individually when it is ready (downloaded). My first idea is to create N connections with the WMTS server and divide the desired extent into smaller parts and run process in N threads, but it stink of problems for gdalwmscache manager if independent connections download the same tile and try to save it on a disk.
Is my idea a good direction? I would like to ask more experienced users for some advice on this topic :-) Regards, Michał
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
