Skip to content

Conversions

dateconv supports a variety of conversions commonly used in the GNSS community. Every epoch string passed, will be converted to a Golang datetime object (in UTC with nanosecond accuracy).

The following conversions are currently supported. As an example we used the following datetime through all examples: 2022-05-09 12:00:00

Common Date Strings

Format Description Example
date Date format without time 2022-05-09
datetime Date format with time 2022-05-09 12:00:00
datetime_month Date format with a 3-char month abbreviation 09-May-22 12:00
09-May-2022 12:00

GNSS Community

Format Description Example
sitelog, ssss_yyyymmdd IGS sitelog format containing the station name (4 character) pots_20220509.log
sitelog, ssss00ccc_yyyymmdd IGS sitelog format containing the station name (9 character) pots00deu_20220509.log
gpswd GPS week and day 2209.1
rinex3, rinex4, r3, r4 RINEX v.¾ filename POTS00DEU_R_20221281200
_01H_30S_MO.rnx
rinex2, r2 RINEX v.2 filename pots128m.22o
rinex_epoch RINEX v.4/v.3/v.2 epoch header 2022 05 09 12 00 00.0000000
sinex Solution INdependent EXchange Format 2022:128:43200
igs_product2 IGS Product filename (v.2) gbu19162.sp3
igs_product3 IGS Product filename (v.3) GFZ0OPSRAP_20162780000_01D_30S_CLK.CLK
mjd Modified Julian Date 59708.5000
trimble, t0[012] Trimble raw data filename LDRZ202205091200a.T02

GFZ Filenames

Format Description Example
champ Filename used for the CHAMP satellite mission pots22091mz0000.jps
odc GFZ data centre filename POTS00DEU_00001024_FRO_RX3_MO_
20220509_120000_01H_30S_GFZ.rnx
epos GFZ EPOS product filename 2022_128_orb_initial.sp3
housekeeping GFZ monitoring filename pots_monitor_2022_128_1200.info