<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="+1">Dear all, (sorry for cross-posting!)<br>
<br>
<font size="+1"><font size="+1">P</font>lease not<font size="+1">e
that we had recently incidents with the RINEX data stored in
the BKG repository. Some files coming from streamed data
where stored as hourly and data Rinex 2 files in the BKG data
center something which is not welcomed in the IGS ex<font
size="+1">c</font>e<font size="+1">p</font>t in very l<font
size="+1">imited circumstances (some MGEX Rinex 3 stations)<br>
<br>
<font size="+1"><font size="+1">A</font>dditionally the data
that </font>was being stored in the RINEX files had the a<font
size="+1">ntenna pattern appli<font size="+1">ed by<font
size="+1"> the tracking receiver making the
measurements unsuitable for RINEX storage<font
size="+1">, and this circumstance caused proce<font
size="+1">ssing problems at several IGS ACs in
particular for stations KOUC and NRMD.</font></font><br>
<br>
<font size="+1">The BKG have now addressed this
problem and from my recent spot checks no BNC files
are available in their IGS daily data repository,
but before that note that up to 12 stations could
come from "streams<font size="+1">" (i.e. for 234 <font
size="+1">b</font>efore the data purge the
affected stations were; auck2340.13o<font
size="+1"> </font>azu12340.13o<font size="+1">
</font>braz2340.13o<font size="+1"> </font>chti2340.13o<font
size="+1"> </font>daej2340.13o<font size="+1">
</font>dund2340.13o<font size="+1"> h</font>ueg2340.13o<font
size="+1"> </font>kouc2340.13o<font size="+1">
</font>mobs2340.13o<font size="+1"> </font>nrmd2340.13o<font
size="+1"> </font>suwn2340.13o<font size="+1">
</font>wgtn2340.13o)</font></font><br>
</font></font></font></font><br>
checking for the recent week 1755 the data for KOUC and <font
size="+1">NRMD is as follows;<br>
<br>
<font size="+1">for wk1755 (d237 -> d243):<br>
<br>
</font><font size="+1">CDDIS; KOUC and NRMD from streams on
d241 !!<br>
<font size="+1">IGN<font size="+1">; </font></font></font></font></font></font></font><font
size="+1"><font size="+1"><font size="+1"><font size="+1"><font
size="+1"><font size="+1"><font size="+1"><font size="+1"><font
size="+1"><font size="+1"><font size="+1"><font
size="+1">KOUC and NRMD from streams on d241
!!<br>
<font size="+1">BKG; no KOUC or NRM</font>D
data all week.<br>
<br>
<font size="+1">the CDDIS and IGN DCs have
been warn<font size="+1">ed to rem<font
size="+1">ove the d241 files for these
two stations and hopefully correct
alternatives can be found.<br>
<br>
<font size="+1">Therefore I would
recommend th<font size="+1">at <font
size="+1">all</font> IGS data
users check their data repository
for stations with the string "BNC"
in the header to ensure that they
fully understand the source of the<font
size="+1"> data and in case of
doubt re-download the affected
data files. <font size="+1">C</font>orrect
data files are available now in
the Data Centers, and the
affected files have been removed
from the BKG repositories. They
are implementing procedures to
prevent this problem from <font
size="+1">happening</font>
again.<br>
<br>
<font size="+1">This is
important to avoid applying
the a<font size="+1">ntenna
pattern twice <font
size="+1">to</font> the
affected stations' data. <br>
<br>
<font size="+1">please let
me know if there is
anything else to clarify
or address ...</font> </font></font><br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font>
<pre class="moz-signature" cols="72">--
Best regards,
Nacho
IGS Infrastructure Committee Chair
_______________________________________________________________
Ignacio (Nacho) Romero
Aerospace Engineer, PhD
SAC @ ESA/ESOC/HSO-GN
IGS Infrastructure Committee Chair
<a class="moz-txt-link-abbreviated" href="http://www.canaryadvancedsolutions.com">www.canaryadvancedsolutions.com</a>
_______________________________________________________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
puede contener informacion clasificada por su emisor como confidencial
en el marco de su Sistema de Gestion de Seguridad de la
Informacion siendo para uso exclusivo del destinatario, quedando
prohibida su divulgacion copia o distribucion a terceros sin la
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje
erroneamente, se ruega lo notifique al remitente y proceda a su borrado.
Gracias por su colaboracion.
_______________________________________________________________
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>