<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:windowtext;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:351106818;
mso-list-type:hybrid;
mso-list-template-ids:519370382 -1106329282 201916419 201916421 201916417 201916419 201916421 201916417 201916419 201916421;}
@list l0:level1
{mso-level-start-at:2019;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Ryan,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Is the primary driver for this proposal to reduce the total number of individual files being stored in
the CDDIS data centre or has there been requests from the user community?</span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal">Yes, the main driver is technical. The number of files for us continues to skyrocket yearly. This negatively affects both distribution and in house actions for CDDIS. The underlying issue is the small file problem. Not going to go into
details but any data center including yours is/will be affected. It simply has to do with the total number of operations that must be conducted for EVERY read or write operation of a file multiplied over millions of files. Even putting SSD into the mix only
serves to delay the issue. You (GA) somewhat mitigate the problem by combining requests for multiple files within a zip file but you still have to deal with the file access latencies for each of all those small files.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Within our data centre we find that the majority of requests for high-rate data files is for a couple
of hours rather than an entire day. </span><o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That is similar to what we see but its’ usually centered around the most recent data (less than 6 months of age). Therefore, the reason we proposed not changing anything for data that was less than 6 months of age.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We see no problems with the proposed name or folder structure. Although as a note should monument name
read as station name?</span><o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Yes, monument name as station name.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We would support CDDIS (or other GDCs) in making such a change, but would request that this not become
a mandatory change.</span><o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We weren’t proposing making it mandatory but what we (CDDIS) were going to go forward with.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D;background:white">I would suggest delaying the change until after 1 Jan as support during this period is generally limited due to Christmas and New Year. I would suggest 1 Feb be a more appropriate date. Noting
that the impact of these change on users would be minimal.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We can probably live with early next year to implement.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">R<br>
Pat<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">IGS-IC <igs-ic-bounces@lists.igs.org> on behalf of Ruddick Ryan <Ryan.Ruddick@ga.gov.au><br>
<b>Date: </b>Thursday, November 14, 2019 at 8:16 PM<br>
<b>To: </b>Nacho Romero <nacho@canaryspaceconsulting.co.uk>, ic IGS List <igs-ic@lists.igs.org>, "igs-dcwg@lists.igs.org" <igs-dcwg@lists.igs.org><br>
<b>Subject: </b>[EXTERNAL] [IGS-IC-847] Re: Infrastructure Committee business [SEC=OFFICIAL]<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Hi Nacho, Carey and Michael.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you for the proposal addressing recommendation 2018-02.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">The team at GA have reviewed the document and have the following points:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Is the primary driver for this proposal to reduce the total number of individual files being stored in
the CDDIS data centre or has there been requests from the user community?</span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Within our data centre we find that the majority of requests for high-rate data files is for a couple
of hours rather than an entire day. </span><o:p></o:p></li></ul>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Within our data centre we do not store files within a directory structure, but essentially a large bucket
that is referenced to a database or index. As such, this proposal does not fit within our design and would not provide us any benefit. We are not constrained by the number of files that we can store and users wanting this data can request multiple files at
once which are automatically zipped together on download.</span><o:p></o:p></li></ul>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We see no problems with the proposed name or folder structure. Although as a note should monument name
read as station name?</span><o:p></o:p></li></ul>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We support the consolidation of multi-GNSS navigation files into a single directory. </span><o:p></o:p></li></ul>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We agree that keeping the most recent set of data in the standard format is a good idea.</span><o:p></o:p></li></ul>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We would support CDDIS (or other GDCs) in making such a change, but would request that this not become
a mandatory change.</span><o:p></o:p></li></ul>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We would support CDDIS (or other GDCs) in making such a change, but would request that this not become
a mandatory change.</span><o:p></o:p></li></ul>
<p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Kind regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333">Ryan Ruddick</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"> </span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#006983">
</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333">Section Leader
</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#006983">|</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"> GNSS Infrastructure and Informatics</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333">National Positioning Infrastructure</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#006983"> |</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333">
Positioning and Community Safety Division</span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:6.0pt;font-family:"Arial",sans-serif;color:#29627D"> </span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#006983">t</span></b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333"> +61 2 6249 9426
</span><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#006983">m</span></b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333"> +61</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif"> (0<span style="color:#333333">)
429 771 069 </span></span><span style="font-size:6.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ga.gov.au_&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=yrgx-xAXo5tjY0kqY8hF4m6wOxj3jNazq_pilwD5MO4&m=l3SpR0nHOeXROADi4Y-ftNmUnYuaDGJn1jxkPuCMNzM&s=DQQWSvdvuxCcNrWfbGGQ9pm4FZo5EzSIcARM0lgvHXU&e="><span style="color:windowtext;text-decoration:none"><span style="color:#1F497D"><img border="0" width="270" height="49" style="width:2.8125in;height:.5104in" id="x_Picture_x0020_15" src="cid:image001.png@01D59DF8.40F33AB0" alt="16-9481 GA Email Signature_social media-04"></span></span></a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:6.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_GeoscienceAus&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=yrgx-xAXo5tjY0kqY8hF4m6wOxj3jNazq_pilwD5MO4&m=l3SpR0nHOeXROADi4Y-ftNmUnYuaDGJn1jxkPuCMNzM&s=9NqOivF_T3D--sYfCUlpX_rdt03KgTuuPZt0Cs4aVFc&e="><span style="color:windowtext;text-decoration:none"><span style="color:#1F497D"><img border="0" width="20" height="18" style="width:.2083in;height:.1875in" id="x_Picture_x0020_14" src="cid:image002.png@01D59DF8.40F33AB0" alt="16-9481 GA Email Signature_social media-v2-01"></span></span></a><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_GeoscienceAustralia&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=yrgx-xAXo5tjY0kqY8hF4m6wOxj3jNazq_pilwD5MO4&m=l3SpR0nHOeXROADi4Y-ftNmUnYuaDGJn1jxkPuCMNzM&s=3DRlLrkFxcqnXAuV715PbY894q4cRs3kjF92spHLDzo&e="><span style="color:windowtext;text-decoration:none"><span style="color:#1F497D"><img border="0" width="20" height="18" style="width:.2083in;height:.1875in" id="x_Picture_x0020_13" src="cid:image003.png@01D59DF8.40F33AB0" alt="16-9481 GA Email Signature_social media-v5"></span></span></a><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_user_GeoscienceAustralia&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=yrgx-xAXo5tjY0kqY8hF4m6wOxj3jNazq_pilwD5MO4&m=l3SpR0nHOeXROADi4Y-ftNmUnYuaDGJn1jxkPuCMNzM&s=7mJR46D3w_R6BAyDGhhcIY3Ou8rwHfzAWOHyMcZmPLM&e="><span style="color:windowtext;text-decoration:none"><span style="color:#1F497D"><img border="0" width="20" height="18" style="width:.2083in;height:.1875in" id="x_Picture_x0020_12" src="cid:image004.png@01D59DF8.40F33AB0" alt="16-9481 GA Email Signature_social media-v2-02"></span></span></a><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_geoscience-2Daustralia&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=yrgx-xAXo5tjY0kqY8hF4m6wOxj3jNazq_pilwD5MO4&m=l3SpR0nHOeXROADi4Y-ftNmUnYuaDGJn1jxkPuCMNzM&s=mgQFXP6VbweL7Glrmsm8wYjFEmBsj7eyorBfFz7jbhA&e="><span style="color:windowtext;text-decoration:none"><span style="color:#1F497D"><img border="0" width="18" height="18" style="width:.1875in;height:.1875in" id="x_Picture_x0020_11" src="cid:image005.png@01D59DF8.40F33AB0" alt="16-9481 GA Email Signature_social media-03"></span></span></a><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:#1F497D">Make flexibility work. If you receive an email from me at a time that is outside of normal business hours, I am sending it at a time that suits me. I am not expecting you to read or reply
until normal business hours.</span></i><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_jsOm_4239565966AE4B9F90D68393E077E0DE"></a><b>From:</b> IGS-IC <igs-ic-bounces@lists.igs.org>
<b>On Behalf Of </b>Nacho Romero<br>
<b>Sent:</b> Wednesday, 13 November 2019 2:18 AM<br>
<b>To:</b> ic IGS List <igs-ic@lists.igs.org>; igs-dcwg@lists.igs.org<br>
<b>Subject:</b> [IGS-IC-846] Infrastructure Committee business<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p>Hello to all of you,<o:p></o:p></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.<o:p></o:p></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.<o:p></o:p></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.<o:p></o:p></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.<o:p></o:p></p>
<p> <o:p></o:p></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.<o:p></o:p></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. <o:p></o:p></p>
<p>Hope all is well at your end, <o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre>Nacho<o:p></o:p></pre>
<pre>_______________________________________________________________<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Ignacio (Nacho) Romero<o:p></o:p></pre>
<pre>Aerospace Engineer, PhD<o:p></o:p></pre>
<pre>CSC Ltd @ ESA/ESOC/OPS-GN<o:p></o:p></pre>
<pre>Satellite Navigation Engineer @ ESOC Navigation Support Office<o:p></o:p></pre>
<pre>IGS Infrastructure Committee Chair<o:p></o:p></pre>
<pre><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.navigation-2Doffice.esa.int&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=yrgx-xAXo5tjY0kqY8hF4m6wOxj3jNazq_pilwD5MO4&m=l3SpR0nHOeXROADi4Y-ftNmUnYuaDGJn1jxkPuCMNzM&s=9gJ03KZm1uwACuREG3cMSxt3swgmBuf2bRuJpOZXZ6s&e=">www.navigation-office.esa.int</a><o:p></o:p></pre>
<pre><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.canaryspaceconsulting.co.uk&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=yrgx-xAXo5tjY0kqY8hF4m6wOxj3jNazq_pilwD5MO4&m=l3SpR0nHOeXROADi4Y-ftNmUnYuaDGJn1jxkPuCMNzM&s=DvbZxS1ni9zt2Cza2yqTdiCOAM46tZprg_F2N43wpxE&e=">www.canaryspaceconsulting.co.uk</a><o:p></o:p></pre>
<pre>_______________________________________________________________<o:p></o:p></pre>
<pre>This message including any attachments may contain confidential<o:p></o:p></pre>
<pre>information, according to our Information Security Management System,<o:p></o:p></pre>
<pre> and intended solely for a specific individual to whom they are addressed.<o:p></o:p></pre>
<pre> Any unauthorised copy, disclosure or distribution of this message<o:p></o:p></pre>
<pre> is strictly forbidden. If you have received this transmission in error,<o:p></o:p></pre>
<pre> please notify the sender immediately and delete it.<o:p></o:p></pre>
<p>Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination,
forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks.<br>
-------------------------------------------------------------------------------------------------------------------------<o:p></o:p></p>
</div>
</body>
</html>