Re: [gdal-dev] OGRCoordinateTransformation Thread Safety

On jeudi 7 novembre 2019 08:49:06 CET Bryant wrote: > Thank you for the response Even! > > >As most C/C++ libraries, an object is not thread-safe unless it is > > explicitly mentioned it is. > > This makes sense. > However, I inferred from one of your previous responses >

Re: [gdal-dev] OGRCoordinateTransformation Thread Safety

Thank you for the response Even! >As most C/C++ libraries, an object is not thread-safe unless it is explicitly mentioned it is. This makes sense. However, I inferred from one of your previous responses

Re: [gdal-dev] OGRCoordinateTransformation Thread Safety

On mercredi 6 novembre 2019 14:51:28 CET Bryant wrote: > Further, manual tests suggest that it is in GDAL 2.4.3 -- 20 threads > performing transformations on the same OGRCoordinateTransformation instance > and ensuring that the result is within 1e-4 of the correct result. As most C/C++ libraries,

Re: [gdal-dev] OGRCoordinateTransformation Thread Safety

Further, manual tests suggest that it is in GDAL 2.4.3 -- 20 threads performing transformations on the same OGRCoordinateTransformation instance and ensuring that the result is within 1e-4 of the correct result. -- Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html ___

[gdal-dev] OGRCoordinateTransformation Thread Safety

Hello All! I know that this question has been asked before, but not recently, and I haven't found a satisfactory explanation. Is OGRCoordinateTransformation threadsafe such that multiple threads can call Transform on the same instance in parallel? If not, why not? If so, where is this documented