From octavian.a at chula.ac.th Tue Apr 12 01:12:55 2016 From: octavian.a at chula.ac.th (Chula) Date: Tue, 12 Apr 2016 15:12:55 +0700 Subject: [IGSMAIL-7287] RINEX 3: on the B1 signals In-Reply-To: <56F41C50.6070101@canaryadvancedsolutions.com> References: <56F41C50.6070101@canaryadvancedsolutions.com> Message-ID: <56ECF5F2-EFF3-49D0-8E33-EE895B84A728@chula.ac.th> Dear all, 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. According to p.9 from the RINEX 3.03 definition (ftp://igs.org/pub/data/format/rinex303.pdf ): "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. Now, when looking at all submitted RINEX 3 *.crx.gz files from ftp://cddis.gsfc.nasa.gov/pub/gnss/data/daily/2016/095/16d/ , one can summarise the followings: there are all together 71 stations: 2 (v3.01), 61(v3.02), 8(v.3.03) 65 stations report BDS observations two stations (LMMF & USN8) report C2x obs type though their version is 3.02 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. 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 17 other stations use only ?HEADER EDIT? from gfzrnx tool. Therefore, their original RINEX version is preserved. 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. http://semisys.gfz-potsdam.de/semisys/software/gfzrnx/1.04-6579/changelog.txt Please notice, that no short file name (i.e., *.Z files) was analysed. Kind regards, Octavian --- Dr. Octavian Andrei, lecturer Chulalongkorn University Faculty of Engineering Department of Survey Engineering Phayathai Road, Pathumwan, Bangkok 10330 THAILAND tel. +66 2 218 6651-307 m. 09 2267 1421 Skype: octavianandrei.work > On 24 Mar 2016, at 23:56, Nacho Romero wrote: > > Authors: Nacho Romero, Infrastructure Committee Chair > David Maggert, Network Coordinator > > > 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. > > 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. > > The RINEX 3 format clearly defines the new naming structure: http://bit.ly/1YaodnI > > To find your "IGS station long name" go to http://igs.org/network 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. > > Again this affects only RINEX 3 Station Data Providers (previously "MGEX stations", now called "multi-GNSS stations") . > > 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. > > 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. > > RINEX 3 file deliveries with the short names can now be discontinued to avoid confusion, once you have confirmed the new filenames are fine. > > 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. > > 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. > > 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. > > 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. > > -- > Best regards, > Nacho > _______________________________________________________________ > > Ignacio (Nacho) Romero > Aerospace Engineer, PhD > SAC @ ESA/ESOC/HSO-GN > IGS Infrastructure Committee > www.canaryadvancedsolutions.com > _______________________________________________________________ > 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. > > > > _______________________________________________ > IGSMail mailing list > IGSMail at igscb.jpl.nasa.gov > https://igscb.jpl.nasa.gov/mailman/listinfo/igsmail -------------- next part -------------- An HTML attachment was scrubbed... URL: https://igscb.jpl.nasa.gov/pipermail/igsmail/attachments/20160412/c93a2b86/attachment.html