[gdal-dev] Perforce issue in coordinate transformations with Gdal 2.3.2

[Thomas Knudsen]

Prepare/finalize functions were added to pj_inv & pj_fwd  in PROJ PR #731 (
https://github.com/OSGeo/proj.4/pull/731), in order to resolve ticket #700 (
https://github.com/OSGeo/proj.4/issues/700).
These add some overhead as well but IIRC, more like +15% (much depending on
the actual projection) than +100%.

Den man. 28. jan. 2019 kl. 17.38 skrev Even Rouault <even.rouault at gmail.com
>:

> Stefan,
>
> I bet you also upgraded your PROJ version in the process ? I can't think
> of a reason in GDAL itself for a performance change. But on the PROJ side,
> yes, there might be some explanation
> The main one I can see is that in PROJ 4.9.3, the Extended Transverse
> Mercator is used by default for UTM, which has probably a higher
> computation time. If you define the GDAL configuration option /
> environmenet variable OSR_USE_ETMERC to NO, then the older Transverse
> Mercator method will be used.
> PROJ 5.0 has also undergone major changes that might have increased a bit
> the computation time, but I wouldn't expect them to cause a 2x slowdown.
>
> Even
>
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20190129/30e24a42/attachment.html>