<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Dear all,<div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">The receiver internal translator to RINEX 3.02 in firmware v5.14 for Trimble NetR9 receivers introduces two new bugs.</div><div class=""><br class=""></div><div class="">1) </div><div class="">The first bug is an inconsistency with RINEX 3.02 standard. Page A10 / A14 at <a href="https://igscb.jpl.nasa.gov/igscb/data/format/rinex302.pdf" class="">https://igscb.jpl.nasa.gov/igscb/data/format/rinex302.pdf</a> 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.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">GLONASS COD/PHS/BIS#</div></blockquote></div><div class=""><div class=""><br class="webkit-block-placeholder"></div><div class="">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.</div><div class=""><br class=""></div><div class="">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:</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">ANMG00MYS_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">BRUN00BRN_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">CMUM00THA_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">CPNM00THA_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">CUT000AUS_R_20162900000_01D_30S_MO.crx.gz GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">DAE200KOR_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">DLTV00VNM_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">EUSM00MYS_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">JCTW00ZAF_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">JNAV00VNM_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">NCKU00TWN_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">PFRR00USA_R_20162900000_01D_30S_MO.crx.gz C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS#</div></blockquote></div><div class=""><br class=""></div><div class="">However, only CUT0 reports firmware NetR9 5.14 and thus gets this bug from the receiver internal translator.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">CUT000AUS_R_20162900000_01D_30S_MO.crx.gz NetR9 5.14 N Nadarajah 20161016 000000 UTC PGM / RUN BY / DATE</div></blockquote><blockquote type="cite" class=""><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">CUT000AUS_R_20162900000_01D_30S_MO.crx.gz 5023K67889 TRIMBLE NETR9 5.14 REC # / TYPE / VERS</div></blockquote></div><div class=""><br class=""></div><div class="">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):</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">ANMG00MYS_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004302 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">BRUN00BRN_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004354 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">CMUM00THA_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004518 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">CPNM00THA_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004531 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">DAE200KOR_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004406 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">DLTV00VNM_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004554 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">EUSM00MYS_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004547 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">JCTW00ZAF_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004619 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">JNAV00VNM_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004339 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">NCKU00TWN_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004450 UTC PGM / RUN BY / DATE</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">PFRR00USA_R_20162900000_01D_30S_MO.crx.gz dconv JAXA 20161017 004506 UTC PGM / RUN BY / DATE</div></blockquote></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">2)</div><div class="">In addition, the v5.14 receiver internal translator to RINEX also does not fix the IGS naming convention (<a href="https://igscb.jpl.nasa.gov/igscb/station/general/rcvr_ant.tab" class="">https://igscb.jpl.nasa.gov/igscb/station/general/rcvr_ant.tab</a>) for the receiver type name that is still reported uncapitalised (i.e., Trimble NetR9 instead of TRIMBLE NETR9). </div><div class=""><br class=""></div><div class="">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:</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">AUCK00NZL_R_20162900000_01D_30S_MO.crx.gz 5035K69859 Trimble NetR9 5.14 REC # / TYPE / VERS</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">CHTI00NZL_R_20162900000_01D_30S_MO.crx.gz 5049K72269 Trimble NetR9 5.14 REC # / TYPE / VERS</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">DUND00NZL_R_20162900000_01D_30S_MO.crx.gz 5444R50040 Trimble NetR9 5.14 REC # / TYPE / VERS</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">MQZG00NZL_R_20162900000_01D_30S_MO.crx.gz 5049K72153 Trimble NetR9 5.14 REC # / TYPE / VERS</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">SCTB00ATA_R_20162900000_01D_30S_MO.crx.gz 5034K69673 Trimble NetR9 5.14 REC # / TYPE / VERS</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">SPTU00BRA_R_20162900000_01D_30S_MO.crx.gz 5239K52833 Trimble NetR9 4.85 REC # / TYPE / VERS</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">WARK00NZL_R_20162900000_01D_30S_MO.crx.gz 5522R50052 Trimble NetR9 5.14 REC # / TYPE / VERS</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">WGTN00NZL_R_20162900000_01D_30S_MO.crx.gz 5034K69714 Trimble NetR9 5.14 REC # / TYPE / VERS</div></blockquote></div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">Hopefully, the responsible persons to correct these bugs and inconsistencies will find the information beneficial.</div><div class=""><br class=""></div><div class="">Best regards,</div><div class="">Octavian</div><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" 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><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Twitter: @coandrei</div>
</div>
<br class=""></div></body></html>