<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello to all of you,</p>
<p>In the end I will not make the trip to the AGU in SF this
December and I cannot host the IC/DC meeting that I had asked you
about a few days ago. On the other hand if there is quorum we
could still hold the meeting if enough people are making the trip
and the others we can join by telecon. Please let me know and I
can get the IGS CB to find a meeting room and setup the webex.</p>
<p>Secondly I would ask you to please read the enclosed document
from the CDDIS on the high-rate data long term archiving. This
corresponds to Recommendation 2018-02 from last year's IGS
Workshop. CDDIS will take the lead but we should have discussion
and agreement that this appears OK to everyone. This way forward
shall not be an imposition for the Data Centers (as far as I
understand) but rather an alternative for storing the 96 high-rate
station files each day in a much more convenient form, so this
alternative shall be informed to the users and documented and
explained on our different websites.</p>
<p>We have a volunteer to start to tackle recommendation 2018-04 and
I am hoping that we have a plan to announce the switch away from
the "compress .Z" to "gzip .gz" for IGS data and products, there
are some issues to work through so if you have ideas or potential
pitfalls please let us know.</p>
<p>This is related to the removal of the need to submit Rinex 2
files , for now we have kindly asked all station operators in the
IGs to retain Rinex 2/ Rinex 3 capabilities for their stations and
many have done so. some have already removed the Rine x2 data
flows as they updated their data handling software and could not
retain the old capabilities. By making a formal announcement soon
that from 01/01/2020 IGS stations do not need to submit Rinex 2
any longer if the Rinex 3 station files are flowing , but that
they can retain dual file submissions if they want, but then I
would like to know if we can request that the Rinex 2 files be
"gzip .gz" compressed so that we can move forward ... please send
your views on this. Thanks.</p>
<p><br>
</p>
<p>Please also look over the enclosed recommendations from the last
two workshops and let us know if you would like to advance any one
of them. Thanks. Otherwise I will keep trying to push for actions
as needed.<br>
</p>
<p>Finally, the next IGS Workshop will be at UCAR in Boulder, CO on
14-18 August, 2020, I hope to see you there! If there is no
objection now (please email me) we will retain the current
Infrastructure Committee composition and organization and bring it
up for discussion next summer. I am open to any suggestions for
changes including my Chairmanship, I have been at this for a while
and enjoy it and would like to continue but if you would like to
be considered we can have an internal IC process to elect a new
Chair ahead of the next workshop. <br>
</p>
<p>Hope all is well at your end, <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>