Hi Sean,
> But, there is currently no support for creating a thread-safe
dataset wrapper on on-the-fly datasets returned by some algorithms
(e.g GDALTranslate() or GDALWarp() with VRT as the output driver and
with an empty filename, or custom GDALDataset implementation by
external code).
Are vsimem datasets a kind of on-the-fly dataset that are not
supported? Or can we expect vsimem datasets to be clone-able with
thread-safe wrappers?
The underlying file system of a dataset ( "native", /vsimem/, /vsicurl/,
etc. ) is completely orthogonal to the thread-safety aspect. So a
regular GeoTIFF opened with /vsimem/ can be opened in thread-safe
mode. But the same dataset warped by GDALTranslate() or GDALWarp()
can't, as stated by RFC101 . Does that make sense?
Even
--
http://www.spatialys.com
My software is free, but my time generally not.
LLMs contribute to global warming and brain rot.
Let's guillotine them! "Ah ! ça ira, ça ira, ça ira !"
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
