<font size=2 face="sans-serif">Dear Octavian,</font>
<br>
<br><font size=2 face="sans-serif">thanks for spotting that. </font>
<br>
<br><font size=2 face="sans-serif">Relatively to issue number 2 </font><font size=3>(receiver
type not following IGS naming convention), this has now been fixed for
daily files of 7 out of 8 sites (all the sites located in New Zealand and
Antarctica).</font>
<br>
<br><font size=3>Rinex3 headers will follow IGS standards starting from
doy 301/2016.</font>
<br>
<br><font size=3>Kind regards,</font>
<br>
<br><font size=3>Elisabetta</font>
<br><font size=3> </font>
<br>
<br><font size=2 face="sans-serif"><br>
-----------------------------------<br>
Elisabetta D'Anastasio, PhD, GNS Science - Te Pu Ao<br>
Geodetic Processing Specialist, GeoNet<br>
1 Fairway Drive, PO Box 30368, Lower Hutt, New Zealand<br>
direct phone: +64-4-570 4744 <br>
mobile phone: +64-27-66 55 890<br>
Email: E.DAnastasio@gns.cri.nz<br>
Web: </font><a href=www.gns.cri.nz><font size=2 face="sans-serif">www.gns.cri.nz</font></a><font size=2 face="sans-serif">
, </font><a href=www.geonet.org.nz><font size=2 color=blue face="sans-serif">www.geonet.org.nz</font></a>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Octavian Andrei <octavian.a@chula.ac.th></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">igsmail@igscb.jpl.nasa.gov,
igsstation@igscb.jpl.nasa.gov</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">28/10/2016 01:11</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[IGSMAIL-7365]
RINEX 3.02 bug in TRIMBLE NETR9 firmware v5.14</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">igsmail-bounces@igscb.jpl.nasa.gov</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>Dear all,</font>
<br>
<br><font size=3>I would like to bring into your attention the following
bugs we discovered after we updated the receiver firmware at our CUUT IGS
multi-GNSS station. I believe the information will contribute to higher
consistency in the IGS data archive.</font>
<br>
<br><font size=3>The receiver internal translator to RINEX 3.02 in firmware
v5.14 for Trimble NetR9 receivers introduces two new bugs.</font>
<br>
<br><font size=3>1) </font>
<br><font size=3>The first bug is an inconsistency with RINEX 3.02 standard.
Page A10 / A14 at </font><a href=https://igscb.jpl.nasa.gov/igscb/data/format/rinex302.pdf><font size=3 color=blue><u>https://igscb.jpl.nasa.gov/igscb/data/format/rinex302.pdf</u></font></a><font size=3>
defines the RINEX header label 'GLONASS COD/PHS/BIS’. However, the receiver
internal translator to RINEX outputs an extra hashtag instead of a white
space.</font>
<br>
<br><font size=1>GLONASS COD/PHS/BIS#</font>
<br>
<br><font size=3>As a result, other data management or processing software
that rigorously implements the standard fail to recognise the RINEX 3.02
generated observation file as valid file.</font>
<br>
<br><font size=3>I have done a quick check on all long name files on 2016-290.
There are 30 stations reporting firmware 5.14. Twelve stations report their
RINEX files with the above bug. I give the list below:</font>
<br>
<br><font size=1>ANMG00MYS_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>BRUN00BRN_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>CMUM00THA_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>CPNM00THA_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>CUT000AUS_R_20162900000_01D_30S_MO.crx.gz
GLONASS COD/PHS/BIS#</font>
<br><font size=1>DAE200KOR_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>DLTV00VNM_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>EUSM00MYS_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>JCTW00ZAF_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>JNAV00VNM_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>NCKU00TWN_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br><font size=1>PFRR00USA_R_20162900000_01D_30S_MO.crx.gz C1C
0.000 C1P 0.000 C2C 0.000 C2P 0.000
GLONASS COD/PHS/BIS#</font>
<br>
<br><font size=3>However, only CUT0 reports firmware NetR9 5.14 and thus
gets this bug from the receiver internal translator.</font>
<br>
<br><font size=1>CUT000AUS_R_20162900000_01D_30S_MO.crx.gz NetR9 5.14
N Nadarajah 20161016
000000 UTC PGM / RUN BY / DATE</font>
<br><font size=1>CUT000AUS_R_20162900000_01D_30S_MO.crx.gz 5023K67889
TRIMBLE NETR9 5.14
REC # / TYPE / VERS</font>
<br>
<br><font size=3>The other stations seem to get this bug from JAXA’s dconv
program (or preserve the above bug if the program does not apply rigorous
checks on the RINEX format):</font>
<br>
<br><font size=1>ANMG00MYS_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004302 UTC PGM / RUN BY / DATE</font>
<br><font size=1>BRUN00BRN_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004354 UTC PGM / RUN BY / DATE</font>
<br><font size=1>CMUM00THA_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004518 UTC PGM / RUN BY / DATE</font>
<br><font size=1>CPNM00THA_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004531 UTC PGM / RUN BY / DATE</font>
<br><font size=1>DAE200KOR_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004406 UTC PGM / RUN BY / DATE</font>
<br><font size=1>DLTV00VNM_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004554 UTC PGM / RUN BY / DATE</font>
<br><font size=1>EUSM00MYS_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004547 UTC PGM / RUN BY / DATE</font>
<br><font size=1>JCTW00ZAF_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004619 UTC PGM / RUN BY / DATE</font>
<br><font size=1>JNAV00VNM_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004339 UTC PGM / RUN BY / DATE</font>
<br><font size=1>NCKU00TWN_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004450 UTC PGM / RUN BY / DATE</font>
<br><font size=1>PFRR00USA_R_20162900000_01D_30S_MO.crx.gz dconv
JAXA
20161017 004506 UTC PGM / RUN BY / DATE</font>
<br>
<br>
<br><font size=3>2)</font>
<br><font size=3>In addition, the v5.14 receiver internal translator to
RINEX also does not fix the IGS naming convention (</font><a href=https://igscb.jpl.nasa.gov/igscb/station/general/rcvr_ant.tab><font size=3 color=blue><u>https://igscb.jpl.nasa.gov/igscb/station/general/rcvr_ant.tab</u></font></a><font size=3>)
for the receiver type name that is still reported uncapitalised (i.e.,
Trimble NetR9 instead of TRIMBLE NETR9). </font>
<br>
<br><font size=3>Again at a check on the same files, there are 23 stations
reporting correct 'TRIMBLE NETR9'. However, eight stations (seven with
5.14) report non-IGS name:</font>
<br>
<br><font size=1>AUCK00NZL_R_20162900000_01D_30S_MO.crx.gz 5035K69859
Trimble NetR9 5.14
REC # / TYPE / VERS</font>
<br><font size=1>CHTI00NZL_R_20162900000_01D_30S_MO.crx.gz 5049K72269
Trimble NetR9 5.14
REC # / TYPE / VERS</font>
<br><font size=1>DUND00NZL_R_20162900000_01D_30S_MO.crx.gz 5444R50040
Trimble NetR9 5.14
REC # / TYPE / VERS</font>
<br><font size=1>MQZG00NZL_R_20162900000_01D_30S_MO.crx.gz 5049K72153
Trimble NetR9 5.14
REC # / TYPE / VERS</font>
<br><font size=1>SCTB00ATA_R_20162900000_01D_30S_MO.crx.gz 5034K69673
Trimble NetR9 5.14
REC # / TYPE / VERS</font>
<br><font size=1>SPTU00BRA_R_20162900000_01D_30S_MO.crx.gz 5239K52833
Trimble NetR9 4.85
REC # / TYPE / VERS</font>
<br><font size=1>WARK00NZL_R_20162900000_01D_30S_MO.crx.gz 5522R50052
Trimble NetR9 5.14
REC # / TYPE / VERS</font>
<br><font size=1>WGTN00NZL_R_20162900000_01D_30S_MO.crx.gz 5034K69714
Trimble NetR9 5.14
REC # / TYPE / VERS</font>
<br>
<br><font size=3>As a result, some processing software may not recognise
correctly the receiver type, once again depending on how strict are the
internal checks for the input files.</font>
<br>
<br><font size=3>Hopefully, the responsible persons to correct these bugs
and inconsistencies will find the information beneficial.</font>
<br>
<br><font size=3>Best regards,</font>
<br><font size=3>Octavian</font>
<br><font size=3><br>
---<br>
Dr. Octavian Andrei, lecturer<br>
Chulalongkorn University<br>
Faculty of Engineering<br>
Department of Survey Engineering<br>
<br>
Phayathai Road, Pathumwan,<br>
Bangkok 10330<br>
THAILAND<br>
<br>
tel. +66 2 218 6651-307<br>
m. 09 2267 1421<br>
Skype: octavianandrei.work</font>
<br><font size=3>Twitter: @coandrei</font>
<br><tt><font size=2>_______________________________________________<br>
IGSMail mailing list<br>
IGSMail@igscb.jpl.nasa.gov<br>
</font></tt><a href=https://igscb.jpl.nasa.gov/mailman/listinfo/igsmail><tt><font size=2>https://igscb.jpl.nasa.gov/mailman/listinfo/igsmail</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>
<div>
<div style="border-top: solid 1px black; border-bottom: solid 1px black;
padding: 10px 0; margin: 20px 0; font-size: 8pt;
font-family: Verdana, Arial, Helvetica, sans-serif;">Notice: This email and any attachments are confidential and may not be used, published or redistributed without the prior written consent of the Institute of Geological and Nuclear Sciences Limited (GNS Science). If received in error please destroy and immediately notify GNS Science. Do not copy or disclose the contents.</div>
</div>