[gdal-dev] RFC 47 Status.

Tomaka, Jacek jacek.tomaka at hexagongeospatial.com
Thu May 7 05:20:42 PDT 2015


Even, 

I am not sure I understand what you are saying about 2.0 beta. Does it mean that it is too late for inclusion or it did not make it to the beta but can still make it to 2.0?
Given that the functionality is enabled by setting GDAL_DATASET_CACHING=YES it should not be too destabilizing?

I agree that per-dataset block cache is huge improvement. Especially in scenarios when different threads are reading different files/datasets. 

If there is chance for it to still be included in 2.0 please let me know what needs to be done to make it happen.  

Regards.
Jacek Tomaka

-----Original Message-----
From: Even Rouault [mailto:even.rouault at spatialys.com] 
Sent: Thursday, 7 May 2015 8:05 PM
To: gdal-dev at lists.osgeo.org
Cc: Tomaka, Jacek
Subject: Re: [gdal-dev] RFC 47 Status.

Jacek,

> 
> What is the current status of RFC 47?

Pending. IMHO the per-dataset block cache vs global block cache looks good. 
I'm less convinced by the attempts to provide even limited multi-threaded access to a same GDALDataset object.

> Is per dataset caching going to make it to GDAL 2.0?

No, not that we are now in beta phase.

Even

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



More information about the gdal-dev mailing list