Logo IGS



86 Mails
Nacho Romero 23-Feb-2016 11:19
Craymer, Michael (NRCan/RNCan) 23-Feb-2016 07:02
Craymer, Michael (NRCan/RNCan 23-Feb-2016 07:02
Michael Craymer 13-Aug-2014 15:36
Ryan.Ruddick at ga.gov.au 12-Aug-2014 01:39
Michael Craymer 11-Aug-2014 20:10
Swepos Driften 11-Aug-2014 11:37
Swepos Driften 11-Aug-2014 08:26
Michael Craymer 06-Jul-2014 15:44
Nicholas.Dando at ga.gov.au 04-Jul-2014 05:28
Michael Craymer 14-Jun-2014 00:50
=?ISO-8859-1?Q?Rudolf_St=F6ger?= 13-Jun-2014 16:16
=?ISO-8859-1?Q?Rudolf_St=F6ger?= 13-Jun-2014 12:54
=?ISO-8859-15?Q?Rudolf_St=F6ger?= 12-Jun-2014 12:35
Nicholas.Dando at ga.gov.au 12-Jun-2014 06:42
Michael Craymer 08-May-2014 07:06
Brockmann Elmar swisstopo 07-May-2014 11:33
Michael Craymer 02-May-2014 06:07
Marc Weiss 30-Apr-2014 00:27
Michael Craymer 28-Jun-2012 09:34
Nicholas.Dando at ga.gov.au 28-Jun-2012 03:19
Mike Craymer 09-Dec-2010 22:26
Huot, Caroline 09-Dec-2010 21:46
Mike Craymer 08-Dec-2010 06:41
David Maggert 07-Dec-2010 22:30
Mike Craymer 29-Nov-2010 02:40
Nicolas Le Bonhomme 26-Nov-2010 10:42
Mike Craymer 22-Sep-2010 07:01
Matthew Beldyk 20-Sep-2010 18:41
=?ISO-8859-15?Q?Rudi_St=F6ger?= 20-Sep-2010 14:14
Subject : [IGSMAIL-7253] Properly Naming your Rinex 3 files (32723)
FROM . Nacho Romero - nacho@canaryadvancedsolutions.com
Date : 23-Feb-2016 11:19 -
To : igsmail@igscb.jpl.nasa.gov
- DOMES : 40148M001
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:

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 FIVE
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.

Best regards,

Ignacio (Nacho) Romero
Aerospace Engineer, PhD
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
Type: application/pdf
Size: 85573 bytes
Desc: not available
Url : https://igscb.jpl.nasa.gov/pipermail/igsmail/attachments/20160223/8e7b2bac/attachment-0001.pdf