<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Le 23/08/2024 à 22:17, Even Rouault via
PROJ a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:2096f9e0-8e82-404e-8b32-0ef7c1f9c0ad@spatialys.com">
<p>Javier,</p>
<p>Regarding intra-ITRF transformations, the EPSG database lacks
the ITRF plate motion models. We do have them (up to ITRF2014)
in the data/ITRFxxxx files (cf the link to a previous thread of
mine that Jack Riley has quoted). I see we don't have yet the
ITRF2020 ones. They are at <a class="moz-txt-link-freetext"
href="https://itrf.ign.fr/docs/solutions/itrf2020/ITRF2020-PMM.dat"
moz-do-not-send="true">https://itrf.ign.fr/docs/solutions/itrf2020/ITRF2020-PMM.dat</a></p>
</blockquote>
I've created the ITRF2020 file in
<a class="moz-txt-link-freetext" href="https://github.com/OSGeo/PROJ/pull/4235">https://github.com/OSGeo/PROJ/pull/4235</a>. I've double checked him,
but triple checking could be useful for the plate motion part, as it
is easy to get an extra or missing decimal, or getting a sign wrong
when porting from the PDF to the file...<br>
<blockquote type="cite"
cite="mid:2096f9e0-8e82-404e-8b32-0ef7c1f9c0ad@spatialys.com">
<p>For a fully automated solution what would be mostly missing in
PROJ is support for non-rectangular area of interest, as the
rectangular model could be very inadequate for parts of the
world</p>
<p>Even<br>
</p>
<div class="moz-cite-prefix">Le 23/08/2024 à 11:28, Javier Jimenez
Shaw via PROJ a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CADRrdKtyZMLVSjY7JFEE6uL0xmhXKpw8tBLKhGhnw+HsQ_b=dQ@mail.gmail.com">
<div dir="ltr">
<div>Hi</div>
<div><br>
</div>
<div>I am a bit confused with the epoch of coordinates. For
instance, if I connect to this NTRIP service <br>
</div>
<div><a
href="https://support.swiftnav.com/support/solutions/articles/44002386941-configuring-your-receiver"
class="moz-txt-link-freetext" moz-do-not-send="true">https://support.swiftnav.com/support/solutions/articles/44002386941-configuring-your-receiver</a></div>
<div>it says explicitly that "Skylark Nx RTK uses ITRF2020
reference frame."</div>
<div>Does it mean that the coordinates that I measure today do
have an epoch of 2024.x (today's epoch), or the epoch of
those measurements is 2015.0 (the epoch of ITRF2020 <a
href="https://epsg.org/datum_1322/International-Terrestrial-Reference-Frame-2020.html"
class="moz-txt-link-freetext" moz-do-not-send="true">https://epsg.org/datum_1322/International-Terrestrial-Reference-Frame-2020.html</a>)</div>
<div><br>
</div>
<div>If I want to transform from that reference system
(ITRF2020) to, let's say, ETRS89 or NAD83(2011), should I
add an epoch? which one? where? what happens if I do not set
any?<br>
</div>
<div><br>
</div>
<span>I have the impression that I could convert from one
epoch to another for the same CRS, something like this</span>
<div><span>PROJ_DATA=data ./bin/projinfo -s EPSG:9989 -t
EPSG:9989 --s_epoch 2015.0 --t_epoch 2020.0 -o proj<br>
Candidate operations found: 1<br>
-------------------------------------<br>
Operation No. 1:<br>
<br>
unknown id, Null geographic offset from ITRF2020 to
ITRF2020, 0 m, World.<br>
<br>
PROJ string:<br>
+proj=noop</span></div>
<div><br>
</div>
<div>... but it does not. Should it do a non noop
transformation?</div>
<div><br>
</div>
<div>Note: s_epoch and t_epoch were added in PROJ 9.4</div>
<div><br>
</div>
<div>Thanks.</div>
<div><br>
</div>
<div><br>
</div>
<div>PS. ITRF2020 to CH1903+ is a complete ballpark :(<br>
</div>
<div>
<div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>.___ ._ ..._ .. . ._. .___ .. __ . _. . __..
... .... ._ .__</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
PROJ mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:PROJ@lists.osgeo.org" moz-do-not-send="true">PROJ@lists.osgeo.org</a>
<a class="moz-txt-link-freetext"
href="https://lists.osgeo.org/mailman/listinfo/proj"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/proj</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com"
moz-do-not-send="true">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
PROJ mailing list
<a class="moz-txt-link-abbreviated" href="mailto:PROJ@lists.osgeo.org">PROJ@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/proj">https://lists.osgeo.org/mailman/listinfo/proj</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</body>
</html>