<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear DC WG,</p>
<p>Many stations have been submitting both Rinex 2 and Rinex 3 long
name files since 2016 or after. <br>
</p>
<p><br>
</p>
<p>Let me first state clearly that IGS stations will continue to
submit whatever RINEX files they want and the Data Centers will
offer all files as always, this is NOT an imposition or a rule
change from the IGS. It is just a clear indication that if
stations already submit RINEX 3 they can stop Rinex 2 file
submission if they want to.</p>
<p><br>
</p>
<p>Last year we agreed to wait until 2020 to give the clear message
that all stations that want to can stop Rinex 2 file submission,
and keep just RINEX 3 files from now on. Some have already stopped
and others continue to wonder. Sending a clear message now will
be helpful to simplify and streamline station operations for those
that still have to maintain parallel data production systems.</p>
<p><br>
</p>
<p>Is there is any reason that this should be further delayed or
discussed? Please let everyone know through the list. Thanks.<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" moz-do-not-send="true">www.navigation-office.esa.int</a>
<a class="moz-txt-link-abbreviated" href="http://www.canaryspaceconsulting.co.uk" moz-do-not-send="true">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>