[IGSMAIL-7337] Re: Properly Naming your Rinex 3 files
Alexander Holsteinson
info at geomatica.biz
Fri Jul 22 09:59:47 PDT 2016
Hi
Thanks for your email on this long naming RINEX3 Can you please indicate if our station RDSD has any issues with this?
Best regards
Alex
> On Jul 22, 2016, at 3:13 AM, Nacho Romero <nacho at canaryadvancedsolutions.com> 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. It is now urgent that you 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 using a new software for name conversion (RX3name), 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.
>
> We are currently still receiving almost 20% of RINEX 3 files only in short names;
>
> 81.3 % stations using LongNames (135/166) @ CDDIS
>
> Number of stations only using ShortName; 31
> bik0 cut0 gmsd gop6 gop7 jog2 kit3 lpgs m0se mizu myva nya2 obe4 ous2 pots rio2 roap scrz sgoc sutm tash ulab unb3 voim wind wroc wtz2 wuh2 zim2 zim3 zimj
>
>
> The RINEX 3 format clearly defines the new long 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 Multi-GNSS IGS stations which are providing RINEX 3 Station Data Files (previously "MGEX 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 names can be generated with the new software which can be downloaded here;
> http://acc.igs.org/software/RX3name_v16158_Linux_x86_64.tar.gz
> http://acc.igs.org/software/RX3name_v16158_OSX.tar.gz
> http://acc.igs.org/software/RX3name_v16158_SunOS5.8_64bit_Sparc.tar.gz
>
> If you need more versions or you encounter a problem let me know to my private email.
>
> RINEX 3 files with the correct long names are 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 your station 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, from the CDDIS repository only 31 Multi-GNSS stations 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.
>
>
>
>
> <RINEX 3 long filename creation_RX3name.pdf>_______________________________________________
> IGSMail mailing list
> IGSMail at igscb.jpl.nasa.gov
> https://igscb.jpl.nasa.gov/mailman/listinfo/igsmail
More information about the IGSMail
mailing list