Updated Guidelines on Long Product Filenames in the IGS
Dear IGS community,
The “Guidelines for Long Product Filenames in the IGS” have been updated to version 2.0 and accepted by the IGS Governing Board.
The changes will take effect on any file submitted after February 16, 2023.
Please refer to the “Document History” section of these guidelines to have an overview of all changes. With this message we’d like to take the opportunity to make you aware of the major changes.
1) Station dependent part of filename
To accommodate products that are valid for a specific station an optional part to the file naming convention has been added following the SINEX_TRO v2 specification (https://files.igs.org/pub/data/format/sinex_tro_v2.00.pdf).
Example:
GFZ0OPSRAP_20220300900_05M_05M_POTS00DEU_TRO.TRO denotes a Rapid Operational TZD file processed by the GFZ analysis centre and for the IGS station POTS00DEU.
EUR0OPSFIN_20190480000_07D_01H_TRO.SUM denotes a Final EUREF TZD summary file from a weekly combination process.
2) Major and breaking change to IONO products
To better differentiate between the two established ionospheric products; IGS Global Ionospheric TEC Maps, GIM, since 1998) and ROTI fluctuation maps (ROT, since 2015) two new content types have been introduced: GIM and ROT.
- The former content identifier ION used to describe the Global Ionospheric TEC Maps has been removed to avoid misunderstandings.
- Furthermore, the formerly used extension IOX has been renamed to INX.
These changes have been agreed upon in discussions in the IGS Ionospheric Working Group. We apologise for the inconveniences these changes cause in advance.
Example:
The ionospheric product ESA0OPSFIN_20223190000_01D_02H_ION.IOX will be renamed to ESA0OPSFIN_20223190000_01D_02H_GIM.INX.
Additional Note:
As you may have noticed, the majority of the ionospheric products are still submitted in the short file naming convention. An announcement about the transition to the long format will be given in advance and in coordination with the IGS Ionospheric Working Group and/or each individual analysis centre.
3) ERP filenames
The accumulated ERP files transition to the long product file naming convention as well. This will affect the three products below. Note that the length of the files is set to “unspecified” (00U).
- Accumulated final ERP file:
igs00p03.erp.Z → IGS0OPSSNX_19961821200_00U_01D_ERP.ERP.gz
- Accumulated rapid ERP file:
igs96p02.erp.Z → IGS0OPSRAP_19961821200_00U_01D_ERP.ERP.gz
- Accumulated ultra-rapid ERP file:
igu00p01.erp.Z → IGS0OPSULT_20000851200_00U_06H_ERP.ERP.gz
Additional information can be found in Guidelines for the transition of the IGS products to the long filenames v2.0.
If you have any questions, concerns, or general feedback to this document or the implementation, please let us know.
Best regards,
Markus Bradke
(on behalf of the IGS Infrastructure Committee)
Dear Colleagues,
Following the [IGSMAIL-8309], there is now an updated version available for the Guideline for the transition of the IGS products to the long filenames describing the changes to the filenames for IGS terrestrial frame, orbit and clock products, including the latest changes to align with the new version of the Guidelines For Long Product Filenames in the IGS.
The changes according to the new version will occur starting from February 16, 2023.
In particular, please note the following:
– The Version/Solution Identifier is now limited to “0” for the IGS operational products. In case of resubmission of the products, the resubmitted products replace the previously submitted products keeping the same file name (with version number as 0)
– Accumulated ERP products will be provided in long filenames only.
Details of the above and additional changes are described in the updated version of the guideline for the transitions.
Kind Regards,
Salim Masoumi
IGS Analysis Centre Coordinator
Last Updated on 8 Feb 2023 16:13 UTC