[IGSMAIL-7238] Properly Naming your Rinex 3 files
nacho at canaryadvancedsolutions.com
Wed Jan 27 09:37:52 PST 2016
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 Rinex 3 files are no longer appropriate.
Enclosed in the 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:
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.
RINEX 3 file deliveries with the old names can be discontinued if you
want, once you have implemented the new filenames, but they will
continue to be accepted in parallel for six months if you want to
continue to submit them 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 data, and you can see them in
there since the start of 2016.
Rinex 2 files with their standard names can be submitted in parallel to
Rinex 3 files for as long as you want, as they may serve different
communities, all RINEX files will now be stored together for easier
access and "discoverability" by all GNSS data users.
Ignacio (Nacho) Romero
Aerospace Engineer, PhD
SAC @ ESA/ESOC/HSO-GN
IGS Infrastructure Committee
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RINEX 3 long filename creation.pdf
Size: 85148 bytes
Desc: not available
Url : https://igscb.jpl.nasa.gov/pipermail/igsmail/attachments/20160127/0be6ad8b/attachment-0001.pdf
More information about the IGSMail mailing list