<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Dr Andrei,<br>
<br>
Thanks for investigating and approaching the developers to address
this problem, you are correct of course in your interpretation and
conclusions; the R3.01/3.02/3.03 situation with the B1 signals
(C2x/C1x/C2x) has been most unfortunate and I hope the affected
files can be corrected and or substituted. Please note that the
fact that files may or may not have long names is independent of
this issue, although they are related in these cases through the
use of <b>gfzrnx</b>. Here we have just an issue with <b>gfzrnx</b>
which I am glad to learn will be corrected very soon.<br>
<br>
I again encourage station operators not to use <b>gfzrnx</b> to
rewrite your files to R3.03 files unless you are very sure about
the process, especially if your receiver does not generate R3.03,
just use <b>gfzrnx</b> to edit the RINEX 3 header and create the
long names to rename the file. Luckily through the header records
the issue can be traced.<br>
<br>
Thanks to all station operators that have switched to the correct
RINEX 3 filenames in these few months, enclosed are the suggested
instructions if you are still submitting to the IGS RINEX 3 short
name files, please switch to long name files as soon as possible.
<br>
<br>
regards,<br>
<br>
Nacho Romero<br>
IGS Infrastructure Committee Chair<br>
</tt><br>
<br>
<div class="moz-cite-prefix">On 12/04/2016 09:12, Chula wrote:<br>
</div>
<blockquote
cite="mid:56ECF5F2-EFF3-49D0-8E33-EE895B84A728@chula.ac.th"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Dear all,
<div class=""><br class="">
</div>
<div class="">
<div class="">Following an inconsistency we discovered in our
IGS daily file submissions, I would like to bring into your
attention the following findings regarding the differences
between RINEX 3.02 and 3.03 in handling BDS observations.</div>
<div class=""><br class="">
</div>
<div class="">According to p.9 from the RINEX 3.03 definition (<a
moz-do-not-send="true"
href="ftp://igs.org/pub/data/format/rinex303.pdf" class=""><a class="moz-txt-link-freetext" href="ftp://igs.org/pub/data/format/rinex303.pdf">ftp://igs.org/pub/data/format/rinex303.pdf</a></a>):
"RINEX 3.03 also changes the BeiDou B1 signal convention back
to the 3.01 convention where all B1 signals are identified as
C2x (not C1 as in RINEX 3.02)”. However, this difference is
rather unaccounted for by many RINEX 3 long file names.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Now, when looking at all submitted RINEX 3
*.crx.gz files from <a moz-do-not-send="true"
href="ftp://cddis.gsfc.nasa.gov/pub/gnss/data/daily/2016/095/16d/"
class="">ftp://cddis.gsfc.nasa.gov/pub/gnss/data/daily/2016/095/16d/</a>, one
can summarise the followings:</div>
<div class="">
<ul class="">
<li class="">there are all together 71 stations: 2 (v3.01),
61(v3.02), 8(v.3.03)</li>
<li class="">65 stations report BDS observations</li>
<li class="">two stations (LMMF & USN8) report C2x obs
type though their version is 3.02</li>
<li class="">the eight stations reporting v3.03
(CUUT, GANP, HOFN, LHAZ, NICO, REYK, WTZR, WTZS) do not
comply with the 3.03 definition for B1 signals. </li>
<li class="">Apart GANP that uses 'RINEX_DB.pm’, all the
other seven stations use ‘FILE CONVERSION’ from
gfzrnx-1.0x. Therefore, their original RINEX version is
changed to 3.03</li>
<li class="">17 other stations use only ‘HEADER EDIT’ from
gfzrnx tool. Therefore, their original RINEX version is
preserved. </li>
</ul>
</div>
<div class="">Regarding the 3.03 version, the bug was found to
come from the gfzrnx translator. The developers have already
been informed about it. They confirmed that a fix will be
available in the next release.</div>
<div class=""><a moz-do-not-send="true"
href="http://semisys.gfz-potsdam.de/semisys/software/gfzrnx/1.04-6579/changelog.txt"
class="">http://semisys.gfz-potsdam.de/semisys/software/gfzrnx/1.04-6579/changelog.txt</a></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Please notice, that no short file name (i.e., *.Z
files) was analysed.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Kind regards,</div>
<div class="">Octavian</div>
<div class="">
<br class="">
---<br class="">
Dr. Octavian Andrei, lecturer<br class="">
Chulalongkorn University<br class="">
Faculty of Engineering<br class="">
Department of Survey Engineering<br class="">
<br class="">
Phayathai Road, Pathumwan,<br class="">
Bangkok 10330<br class="">
THAILAND<br class="">
<br class="">
tel. +66 2 218 6651-307<br class="">
m. 09 2267 1421<br class="">
Skype: octavianandrei.work
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 24 Mar 2016, at 23:56, Nacho Romero <<a
moz-do-not-send="true"
href="mailto:nacho@canaryadvancedsolutions.com" class=""><a class="moz-txt-link-abbreviated" href="mailto:nacho@canaryadvancedsolutions.com">nacho@canaryadvancedsolutions.com</a></a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">Authors: Nacho Romero, Infrastructure
Committee Chair<br class="">
David Maggert, Network Coordinator<br class="">
<br class="">
<br class="">
To all station data providers currently providing RINEX 3
files as part of the IGS network. Please at your earliest
convenience implement the correct naming scheme for your
RINEX 3 files as the old RINEX 2 names for the RINEX 3
files are no longer appropriate.<br class="">
<br class="">
In the enclosed pdf is a set of recommendations that you
may find useful, but many different organizations have
implemented their own renaming methods, and some vendors
already allow correct naming of RINEX 3 files but clearly
not all so some action from Station Operators is needed.<br
class="">
<br class="">
The RINEX 3 format clearly defines the new naming
structure: <a moz-do-not-send="true"
href="http://bit.ly/1YaodnI" class="">http://bit.ly/1YaodnI</a><br
class="">
<br class="">
To find your "IGS station long name" go to <a
moz-do-not-send="true" href="http://igs.org/network"
class=""><a class="moz-txt-link-freetext" href="http://igs.org/network">http://igs.org/network</a></a> click on "Options" ,
and in the first column "Site" select the checkbox "Long
Name" to show the name expected by the IGS for all
stations. If you disagree with the country code in the
Long Name assignment please inform us quickly so as to
avoid confusion, for now all stations have "00" for
receiver and antenna.<br class="">
<br class="">
Again this affects only RINEX 3 Station Data Providers
(previously "MGEX stations", now called "multi-GNSS
stations") .<br class="">
<br class="">
The data files acceptable for the IGS continues to be;
Daily (30sec), Hourly (30 sec) and Highrate (1sec) 15 min
files. The "expected" name is assumed, if you have doubts
please let us know. If you base your long name on the
current filenames you are delivering as part of "mgex"
then the name will be fine.<br class="">
<br class="">
RINEX 3 filenames are very flexible for the benefit of the
entire GNSS community, but the IGS will not be taking
advantage of that full flexibility, so continue to submit
properly named 24 hour files, 1 hour files and 15 minute
files only.<br class="">
<br class="">
RINEX 3 file deliveries with the short names can now be
discontinued to avoid confusion, once you have confirmed
the new filenames are fine.<br class="">
<br class="">
RINEX 3 files with short names will continue to be
accepted for FOUR more months at least, and will be stored
as always in the "/mgex" campaign directories in the
different IGS Data Centers.<br class="">
<br class="">
RINEX 3 files with the correct long names will be merged
into the regular IGS GNSS data repository together with
the RINEX 2 files, and you can see them there now, since
the start of 2016.<br class="">
<br class="">
Station RINEX 2 files with their regular names can be
submitted in parallel to RINEX 3 longname files for as
long as you want, as they may serve different communities,
all RINEX data files will now be stored together for
easier access and "discoverability" by all GNSS data
users.<br class="">
<br class="">
Thanks to everyone that has already switched, we have gone
from 40 stations to more than 85 stations using the
correct names in a little over a month! ... still about 60
to go.<br class="">
<br class="">
-- <br class="">
Best regards,<br class="">
Nacho<br class="">
_______________________________________________________________<br
class="">
<br class="">
Ignacio (Nacho) Romero<br class="">
Aerospace Engineer, PhD<br class="">
SAC @ ESA/ESOC/HSO-GN<br class="">
IGS Infrastructure Committee<br class="">
<a moz-do-not-send="true"
href="http://www.canaryadvancedsolutions.com" class="">www.canaryadvancedsolutions.com</a><br
class="">
_______________________________________________________________<br
class="">
Este mensaje, y en su caso, cualquier fichero anexo al
mismo,<br class="">
puede contener informacion clasificada por su emisor
como confidencial<br class="">
en el marco de su Sistema de Gestion de Seguridad de la<br
class="">
Informacion siendo para uso exclusivo del destinatario,
quedando<br class="">
prohibida su divulgacion copia o distribucion a terceros
sin la<br class="">
autorizacion expresa del remitente. Si Vd. ha recibido
este mensaje<br class="">
erroneamente, se ruega lo notifique al remitente y
proceda a su borrado.<br class="">
Gracias por su colaboracion.<br class="">
_______________________________________________________________<br
class="">
This message including any attachments may contain
confidential<br class="">
information, according to our Information Security
Management System,<br class="">
and intended solely for a specific individual to whom
they are addressed.<br class="">
Any unauthorised copy, disclosure or distribution of
this message<br class="">
is strictly forbidden. If you have received this
transmission in error,<br class="">
please notify the sender immediately and delete it.<br
class="">
<br class="">
<br class="">
<br class="">
<span id="cid:EA52B7E2-5C72-4BE6-93BE-D511CA32B36D"><RINEX
3 long filename creation.pdf></span>_______________________________________________<br
class="">
IGSMail mailing list<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:IGSMail@igscb.jpl.nasa.gov">IGSMail@igscb.jpl.nasa.gov</a><br class="">
<a class="moz-txt-link-freetext" href="https://igscb.jpl.nasa.gov/mailman/listinfo/igsmail">https://igscb.jpl.nasa.gov/mailman/listinfo/igsmail</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards,
Nacho
_______________________________________________________________
Ignacio (Nacho) Romero
Aerospace Engineer, PhD
SAC @ ESA/ESOC/HSO-GN
IGS Infrastructure Committee
<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>