[PROJ] New national ETRS89 realisations in EPSG messing things up in PROJ 9.8.0?

[Even Rouault]

> Also thanks for the explanation on how PROJ searches for 
> transformations routes. I thought it built a graph of all 
> transformations and do an accuracy-weighted shortest path search with 
> some penalties to prevent too many transformation steps, but PROJ is a 
> bit more heuristic than that.
>
There are situations where if you use the most complicated SQL requests 
it supports (and PROJ just limits itself to finding a single 
intermediate step...)  you can end up with several hundreds or more 
potential transformation pipelines, with runtime of the order of second. 
While the execution of the pipeline is of the order of the microsecond 
for a coordinate. So before going to that, it checks if the results of 
less costly requests look to be good enough.
>
> Jochem
>
>
>
> Disclaimer:
> De inhoud van deze e-mail is vertrouwelijk en uitsluitend bestemd voor 
> de geadresseerde(n).
> Gebruik, openbaarmaking, vermenigvuldiging, verspreiding en/of 
> verstrekking van deze informatie aan derden is niet toegestaan.
> Op al onze producten en diensten zijn onze algemene 
> leveringsvoorwaarden van toepassing
> [https://www.kadaster.nl/algemene-leveringsvoorwaarden].
>
> Disclaimer:
> This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they 
> are addressed.
> If you are not the intended recipient, you are notified that 
> disclosing, copying, distributing or taking any action in reliance on 
> the contents of this information is strictly prohibited.
> Our general terms and conditions of delivery apply to all our products 
> and services
> [https://www.kadaster.com/general-terms-and-conditions].

-- 
http://www.spatialys.com
My software is free, but my time generally not.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20260312/70372322/attachment.htm>