<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)">
<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;}
@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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
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:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
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-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
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.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:1326324791;
mso-list-type:hybrid;
mso-list-template-ids:-191436356 269025297 269025305 269025307 269025295 269025305 269025307 269025295 269025305 269025307;}
@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;}
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 bgcolor="white" lang="EN-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hi Nacho,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Here are some thoughts from NRCan’s perspective.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I missed the discussion at the workshop so does this mean starting June 1<sup>st</sup> any files submitted need to be gzip
format or does it mean that any files containing data or products from June 1<sup>st</sup> onwards need to be in gzip format? Either way we are in agreement with the date although if it means the latter for the switch of products it may make sense to pick
the start of a GPS week (June 2<sup>nd</sup>?). We think that the data providers should make an effort to transition but for any files that continue to come in as UNIX compressed the DCs should convert them to gzip before posting.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">We think that the historical files should also be converted to gzip by the DCs. We would do this for our historic archive
but maybe not right away.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Nothing that we are aware of.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I think there will be a lot of work on our side (both as data/product providers and users) so it’s probably important that a date is
picked and communicated asap.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Brian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> IGS-IC <igs-ic-bounces@lists.igs.org>
<b>On Behalf Of </b>Nacho Romero<br>
<b>Sent:</b> January 8, 2019 5:28 AM<br>
<b>To:</b> igs-dcwg@lists.igs.org; ic IGS List <igs-ic@lists.igs.org>; Lou Estey <lou@unavco.org>; David Maggert <dmaggert@unavco.org>; MacLeod, Ken (NRCan/RNCan) <ken.macleod@canada.ca><br>
<b>Cc:</b> gsfc-cddis-ops@lists.nasa.gov; Limbacher, Rebecca Irene. (GSFC-690.1)[SCIENCE SYSTEMS AND APPLICATIONS INC] <rebecca.i.limbacher@nasa.gov>; mark.van.kints-esa.int <mark.van.kints@esa.int><br>
<b>Subject:</b> [IGS-IC-814] compression file changes ...<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Dear all,<o:p></o:p></p>
<p>At the last IGS workshop at the IC+DC splinter meeting we approved the recommendation ...
<o:p></o:p></p>
<p><b><span style="font-family:"Calibri",sans-serif">2018-4. </span></b><span style="font-family:"Calibri",sans-serif">To coordinate DC, IC and NC so as to move away from Z compression for all IGS files (data and products) and into using gzip (.gz)</span><o:p></o:p></p>
<p><o:p> </o:p></p>
<p>Please provide us comments on the following;<o:p></o:p></p>
<p>1) I propose that we announce this change now with the date 01 June 2019 , and at that point we publish all the newly submitted files (data and products) as .gz in all IGS DCs, whether the owner submits it that way or not ... do you agree that DCs should
enforce such a change or should we insist all the owners transition their own submitted files?
<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>2) Do we change all the historical files to .gz ? This will generate "new files" which the myriad of sync processes (private and public) running between all sort of servers will cause a lot of duplications ... I propose we leave the old files as they are
for now to avoid a lot of potential duplication of files in IGS and user's servers
<o:p></o:p></p>
<p>3) are you aware of specific places were the .Z compression is requested? required? recommended? ... I think the site guidelines are generic enough, what do you think?<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>We have some other recommendations to discuss with you in the next few days, and in the next months I will organize a telecon so we can all agree a way forward for each one.<o:p></o:p></p>
<p>Please let us know your comments on this specific recommendation and I will collate all the discussion points for the coordination telecon. Thanks.<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="http://www.navigation-office.esa.int">www.navigation-office.esa.int</a><o:p></o:p></pre>
<pre><a href="http://www.canaryspaceconsulting.co.uk">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>
</div>
</body>
</html>