Closed KubaSzostak closed 1 year ago
It can be defined by exposing swig bindings to C#. Before generating bindings, we can apply a patch to this file.
But it's worth checking whether it can be applied harmlessly before trying and the reason why the API was encapsulated this way. I can't give you any warranty that this will work as expected. It's better to ask the maintainers of the GDAL library why they didn't expose those methods and what can be done in this case.
Is your feature request related to a problem? Please describe.
Currently the library exposes
int Gdal.GetCacheMax()
andGdal.SetCacheMax(int nBytes)
methods. The unit of the cache size is byte. Due to the use of anInt32
type as cache size, the the maximum value is 2GB.Describe the solution you'd like or your ideas here
GDAL has also
GDALSetCacheMax64()
andGDALGetCacheMax64()
methods, but they are note exposed by the library. Would it be possible to to expose those methods in the library?Additional context
Currently calling the
Gdal.GetCacheMax()
method on machine having 64 GB RAM causes warning message to be displayed in console application.Sample code
Output