<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Dear IC & DC,</p>
<p>After the last few days I think we can all agree that having
stations switch too fast away from Rinex 2 would not be positive
for the IGS+ community. Thus please comment on the following
message we aim to send to the IGSSTATION/IGSMAIl/IGS-AC email
lists (minimum)</p>
<p>The idea with the message is to cover these two ideas; to request
station operators NOT to turn off their dual Rinex 2 files yet, to
wait until the end of 2019 or as long as late as possible during
this year, plus also to request that Rinex 2 files continue to be
generated from raw receiver files (and not converted) .</p>
<p>Additionally Data Centers should institute checks to ensure the
Rinex 2 files conforms to the Rinex2.11 standard so that some of
the recent problems (use of C3/L3 observations, inclusion of C7/L7
in Glonass, inclusion of Beidou and QZSS) are flagged and the
files quarantined and the operators notified.</p>
<p>"Dear IGS members,</p>
<p>From the IGS NC and IC we acknowledge that many stakeholders and
users in the IGS+ community have adapted their tools to process
station Rinex 3 data files preferentially. This is as was intended
in the Rinex 3 transition plan as part of the move of the IGS to a
truly multiGNSS service. On the other hand we have to recognize
that Rinex 2 files remain important and some users have expressed
concern at the disappearance of Rinex 2 from important historical
stations.<br>
</p>
<p>As a data provider could you please continue submitting dual
Rinex 3/Rinex2 data files, if this has been your practice in the
recent past, for as long as possible or until the end of 2019. The
choice to continue to submit dual Rinex files is up to each
station data provider but we request that you are sensitive to the
IGS community since some components have not completed the
transition to dual Rinex3/Rinex2 processing yet. Thanks. <br>
</p>
<p>We would like from the IGS to also ask that Rinex 3 and Rinex 2
files are created from the receiver raw tracking files and not
converted between them. Thanks.</p>
<p>Sincerely,</p>
<p> Infrastructure Committee</p>
<p> Network Coordinator</p>
<p>"<br>
</p>
<pre class="moz-signature" cols="72">--
Best regards,
Nacho
_______________________________________________________________
Ignacio (Nacho) Romero
Aerospace Engineer, PhD
CSC Ltd @ ESA/ESOC/OPS-GN
Satellite Navigation Engineer @ ESOC Navigation Support Office
IGS Infrastructure Committee Chair
<a class="moz-txt-link-abbreviated" href="http://www.navigation-office.esa.int">www.navigation-office.esa.int</a>
<a class="moz-txt-link-abbreviated" href="http://www.canaryspaceconsulting.co.uk">www.canaryspaceconsulting.co.uk</a>
_______________________________________________________________
This message including any attachments may contain confidential
information, according to our Information Security Management System,
and intended solely for a specific individual to whom they are addressed.
Any unauthorised copy, disclosure or distribution of this message
is strictly forbidden. If you have received this transmission in error,
please notify the sender immediately and delete it.</pre>
</body>
</html>