<div dir="ltr"><div>Thanks Even.</div><div><br></div><div>In the DB, the operation registered is ETRS89_TO_ETRF2020, so it has to be "inverted". However, I do not see any way to indicate that in the concatenated operation.<br></div><div><br></div><div>For instance, this concatenated operation does not mention that the second step should be "inverted" (if I understood correctly)<br></div><div></div><div><span style="font-family:monospace"> ('NKG', 'ITRF2014_TO_DK', 1, 'EPSG', '8366'), -- ITRF2014 -> ETRF2014<br> ('NKG', 'ITRF2014_TO_DK', 2, 'NKG', 'NKG_ETRF14_TO_ETRF2014'),<br> ('NKG', 'ITRF2014_TO_DK', 3, 'NKG', 'PAR_2020_DK'),<br> ('NKG', 'ITRF2014_TO_DK', 4, 'NKG', 'DK_2020_INTRAPLATE')</span></div><div><br></div><div>Does it mean that PROJ is finding it automatically?</div><div><br></div><div>Thanks.<br></div><div><br></div><div>PS Should I add the concatenated operation (ITRF2020->ETRS89) to PROJ in a PR? There are different "paths" from ITRF2020 to ETRS89. All apparently equivalent, but probably not exactly the same.<br></div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 27 Aug 2024 at 19:55, Even Rouault <<a href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<p>Javier,</p>
<p>I believe that registering a concatenated operation for ITRF2020
-> ETRS89 = ITF2020->ETRF2020+ETRF2020->ETRS89 in the
database should be enough for PROJ to infer the ITRF2020 ->
CH1903+ pipeline</p>
<p>Even<br>
</p>
<div>Le 27/08/2024 à 19:29, Javier Jimenez
Shaw via PROJ a écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi</div>
<div><br>
</div>
<div>I am now facing transformations with ITRF2020 with
time(yes, because Skylark, but I guess more NTRIPs are going
to do (or already doing) the same)</div>
<div><br>
</div>
<div>The point is when the destination CRS does not have a
direct transformation from ITRF2020 (or almost).</div>
<div><br>
</div>
<div>For instance, EPSG:4150, CH1903+ (the geographic of LV95,
in Switzerland) is only connected to ETRS89. See that CH1903+
is in the European tectonic plate, as ETRS89</div>
<div><br>
</div>
<div>A direct transformation is completely ballpark<br>
</div>
<div><span style="font-family:monospace"><br>
</span></div>
<div><span style="font-family:monospace">echo 42 6 0 2024.6 |
./cs2cs EPSG:9989 EPSG:4150 -d 9 --3d <br>
42.000000000 6.000000000 0.000000000 2024.6</span></div>
<div><br>
</div>
<div>However, from ITRF2020 to ETRS89 there is some change due
to the time (the European plate moving at 2.5 cm/a since
2015):<br>
</div>
<div><span style="font-family:monospace">echo 42 6 0 2024.6 |
./cs2cs EPSG:9989 EPSG:4937 -d 9 --3d <br>
41.999994981 5.999991317 -0.001861237 2024.6</span></div>
<div><br>
</div>
<div>and from ETRS89 to CH1903+ due to the datum offset:<br>
<span style="font-family:monospace">echo 42 6 0 2024.6 |
./cs2cs EPSG:4937 EPSG:4150 -d 9 --3d <br>
42.000742733 6.000670188 -60.682799297 2024.6</span></div>
<div><br>
</div>
<div>Looking at the pipelines, the steps would be ITRF2020 ->
ETRF2020 -> ETRS89 -> CH1903+</div>
<div>(btw, only since PROJ 9.4.1, when ETRF2020 was added)<br>
</div>
<div><br>
</div>
<div>I understand that the only way to get the proper
transformation is chaining these two manually. Via ETRS89 ...
because I know it. Right?</div>
<div><br>
</div>
<div>Well, the future does not look so promising to me: in EPSG
I only see transformations from ITRF2020 to ETRF family,
NAD83(2011) family and NAD83(CSRS)v8. That is Europe, USA and
Canada. That's all, folks.<br>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>
<div>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>.___ ._ ..._ .. . ._. .___ .. __ . _. . __.. ...
.... ._ .__</div>
<div>Javier Jimenez Shaw</div>
<div>Mercator str 42.<br>
</div>
<div>Null-Island<br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
PROJ mailing list
<a href="mailto:PROJ@lists.osgeo.org" target="_blank">PROJ@lists.osgeo.org</a>
<a href="https://lists.osgeo.org/mailman/listinfo/proj" target="_blank">https://lists.osgeo.org/mailman/listinfo/proj</a>
</pre>
</blockquote>
<pre cols="72">--
<a href="http://www.spatialys.com" target="_blank">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</div>
</blockquote></div></div>