<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="DA">Correct<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="DA">/Kristian<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DA"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Steve Riddell <sriddell@geocue.com> <br>
<b>Sent:</b> 7. februar 2022 15:54<br>
<b>To:</b> Kristian Evers <kreve@sdfe.dk>; proj@lists.osgeo.org<br>
<b>Subject:</b> RE: Plate motion models<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Kristian. And the user application is responsible for deciding which plate is to be used, right? That is, there is currently no code in PROJ to identify the plate model for a particular point, right?<o:p></o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">steve<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Kristian Evers <<a href="mailto:kreve@sdfe.dk">kreve@sdfe.dk</a>>
<br>
<b>Sent:</b> Monday, February 7, 2022 8:43 AM<br>
<b>To:</b> Steve Riddell <<a href="mailto:sriddell@geocue.com">sriddell@geocue.com</a>>;
<a href="mailto:proj@lists.osgeo.org">proj@lists.osgeo.org</a><br>
<b>Subject:</b> RE: Plate motion models<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Steve,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is the original commit message [0] from when the plate motion models were introduced:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Parameters for the plate motion models (PMM) for ITRF2008 and ITRF2014<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">are added to the ITRF2008/2014 init-files. The PMMs allow coordinates<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">to be moved back and forward in time in plate fixed reference frames<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">such as GR96 in Greenland which is defined as
<a href="mailto:ITRF94@1996.623">ITRF94@1996.623</a>.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Transforming an ITRF2014-coordinate to GR96 is done with:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">+proj=pipeline +step +init=ITRF2014:NOAM +t_epoch=1996.623 +t_obs=2017.584<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> +step +init=ITRF2014:ITRF94 +t_obs=1996.623<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">where the first step transforms the coordinate back in time to<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><a href="mailto:ITRF2014@1996.632">ITRF2014@1996.632</a> by using the ITRF2014 PMM. The second step transforms<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">the ITRF2014 coordinate to ITRF94.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And here’s a concrete example using cct:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="text-indent:36.0pt">echo 3496746.5664 743256.4272 5264477.0556 2014.0 | cct +init=ITRF2014:EURA +t_epoch=2022.0<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My memory fails me regarding how to set +t_epoch and the coordinate epoch but if you play around with them you should quickly be able to figure out how to set them. Check to see if your output coordinate moves in the direction you expect.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">/Kristian<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[0] <a href="https://github.com/OSGeo/PROJ/commit/403f930355926aced5caba5bfbcc230ad152cf86">
https://github.com/OSGeo/PROJ/commit/403f930355926aced5caba5bfbcc230ad152cf86</a>
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> PROJ <<a href="mailto:proj-bounces@lists.osgeo.org">proj-bounces@lists.osgeo.org</a>>
<b>On Behalf Of </b>Steve Riddell<br>
<b>Sent:</b> 7. februar 2022 14:49<br>
<b>To:</b> <a href="mailto:proj@lists.osgeo.org">proj@lists.osgeo.org</a><br>
<b>Subject:</b> [PROJ] Plate motion models<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The data for the ITFR2008 & ITRF2014 plate motion models are delivered with PROJ as init files. From the documentation, 8.7, I think I see how an +init proj string can be used for changing epochs between ITFR frames (e.g. ITRF2000 to ITRF2005),
but can someone please give an example of using the plate models? For example, if I have a point in ITRF2000 epoch 2022.1 and I want to use the NOAM plate model to move it to 2010.0, what would be the +init string? I’m assuming cct would be an appropriate
application for processing this string?<o:p></o:p></p>
<p class="MsoNormal">Thanks for any assistance!<o:p></o:p></p>
<p class="MsoNormal">Steve<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>