Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-popular-posts domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/grafcan/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the insert-headers-and-footers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/grafcan/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/grafcan/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-pagenavi domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/grafcan/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/grafcan/wp-includes/functions.php on line 6114
Estandarización de ficheros RINEX (Red GNSS) - GRAFCAN - Mapas de Canarias

Estandarización de ficheros RINEX (Red GNSS)

02.06.2022

La Red de Estaciones Permanentes de Canarias REPCAN se integra desde hace un año en la red europea de estaciones GNSS EUREF. Siguiendo las recomendaciones europeas (EUREF, EPN), y en la línea de cambios realizados por el Instituto Geográfico Nacional de España (IGN) y varias redes GNSS regionales sobre en la estandarización del formato RINEX a la versión 3, empezaremos a almacenar únicamente en dicho formato, dejando de almacenar los ficheros en versión 2.11 a partir del próximo mes de julio. Igualmente, los ficheros almacenados hasta ahora seguirán estando disponibles en nuestro repositorio de datos ftp://gnss.grafcan.es/

Los ficheros RINEX versión 3 están disponibles desde 2019 y recientemente se han añadido las estaciones de Tías (Lanzarote) y San Miguel de Abona (Tenerife), completando así todas las estaciones de la red. Los ficheros RINEX versión 2.11 dejarán de almacenarse. La ubicación de los ficheros no se modifica con este cambio.

Si su software de postproceso no soporta los ficheros RINEX 3 sería necesario transformarlos a versión 2.11. Puede consultar sobre este proceso a nuestro soporte técnico en gnss@grafcan.com. La nomenclatura del formato RINEX 3 y las diferencias con el formato 2.11 puede consultarse en https://files.igs.org/pub/data/format/rinex305.pdf

Enlaces de interés: http://www.epncb.oma.be/   https://gnss-metadata.eu/   https://twitter.com/be_GNSS

↑