<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=Windows-1252">
<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;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:900753775;
mso-list-type:hybrid;
mso-list-template-ids:1856148818 134807569 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1056205394;
mso-list-template-ids:1281546406;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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-DE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black">Dear IGS Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">In reaction to the idea of doing a “BDS/QZSS campaign” we would like to inform you of the status at ESA and offer our contribution.<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">In our multi-GNSS solutions, which are available from our web side (see<span class="apple-converted-space"> </span><a href="http://navigation-office.esa.int/GNSS_based_products.html" title="http://navigation-office.esa.int/GNSS_based_products.html"><span style="color:#0086F0">http://navigation-office.esa.int/GNSS_based_products.html</span></a>)
we clearly saw an issue with the BeiDou and QZSS solutions once we switched to the ITRF2020 and the corresponding igs20.atx. This was expected as the BeiDou and QZSS PCO values were not adjusted to the significant scale change going from ITRF2014 to ITRF2020.
So we have taken the </span><span lang="EN-US" style="color:black">additional work</span><span style="color:black"> to do a reprocessing to estimate the BeiDou and QZSS PCO values. The results of this effort are available from our web-site in the ANTEX format
(<a href="http://navigation-office.esa.int/products/metadata/" title="http://navigation-office.esa.int/products/metadata/"><span style="color:#0086F0">http://navigation-office.esa.int/products/metadata/</span></a>).<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">A very important feature of the esa23.atx is that it is based on the Galileo PCO/PCV values as they were measured and not on the ITRF2020 scale. This is
</span><span lang="EN-US" style="color:black">fully </span><span style="color:black">in line with
</span><span lang="EN-US" style="color:black">the ESA/ESOC</span><span style="color:black"> current IGS approach</span><span lang="EN-US" style="color:black">,</span><span style="color:black"> where we are also using the measured Galileo PCO/PCV values and
not the igs20.atx values. So in doing the effort of estimating the BeiDou PCOs we have also taken the
</span><span lang="EN-US" style="color:black">effort</span><span style="color:black"> of adjusting the GPS and GLONASS values to get their valus to be consistent with the Galileo PCOs rather then with the igs20.atx. So the esa23.atx is a fully consistent set
of PCOs</span><span lang="EN-US" style="color:black">,</span><span style="color:black"> which are aligned to the
</span><span lang="EN-US" style="color:black">measured </span><span style="color:black">Galileo PCOs rather then to the ITRF2020 scale.<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">A very interesting results we got was that the estimates we derived for the GPS Block III PCO values agreed very well</span><span lang="EN-US" style="mso-fareast-language:EN-US"> (1 to 2 cm)
</span><span style="color:black">with the measured GPS Block III PCO values. And we have therefore taken the GPS Block III measured values and not our estimated ones! For us this is a strong validation for our decision to prefer the Galileo PCOs over the ITRF2020
scale as reference for our GNSS solutions. </span><span lang="EN-US" style="color:black">In conclusion</span><span style="color:black"> we can now say that the scale of our solutions is based on the measured Galileo and GPS Block III PCO values!<span class="apple-converted-space"> </span><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">Since this Galileo</span><span lang="EN-US" style="color:black">-</span><span style="color:black">based alignment may not be what the IGS wants,
</span><span lang="EN-US" style="color:black">however </span><span style="color:black">we are</span><span lang="EN-US" style="color:black"> fully</span><span style="color:black"> convinced this is a completely valid approach</span><span lang="EN-US" style="color:black">.
In this context, ESA/ESOC</span><span lang="EN-US" style="color:black"> </span><span lang="EN-US" style="color:black">is</span><span style="color:black"> also prepared to offer
</span><span lang="EN-US" style="color:black">the</span><span style="color:black"> SINEX solutions from this effort so that the IGS (i.e. Paul and Arturo) can
</span><span lang="EN-US" style="color:black">use them to </span><span style="color:black">generate an official IGS antex that is aligned to the ITRF2020 scale. Our reprocessing covers the period from 2014 until
</span><span lang="EN-US" style="color:black">2023 </span><span style="color:black">and includes GPS, GLONASS, Galileo, BeiDou, and QZSS.<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">We hope that this will help the IGS to speed up the “multi” aspect of the multi-GNSS service.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">We intend to publish these results very soon.<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Please do not hesitate to contact us in case you have any questions related to the subject topic.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">Many greetings,<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">Erik Schoenmann, Francesco Gini, Tim Springer</span><span lang="EN-US" style="color:black">,
</span><span style="color:black">Florian Dilssner</span><span lang="EN-US" style="color:black"> and Werner Enderle<o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">For the </span><span lang="EN-US" style="color:black">ESA/</span><span style="color:black">ESOC IGS AC Team<o:p></o:p></span></p>
</div>
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify
the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</body>
</html>