From jimr@maia.usno.navy.mil Thu Aug 27 15:47:57 EDT 1998 Received: (from jimr@localhost) by maia.usno.navy.mil (8.8.6 (PHNE_14041)/8.8.6) id PAA07543 for gpst@maia; Thu, 27 Aug 1998 15:20:32 -0400 (EDT) From: Jim Ray (USNO 202-762-1444)Message-Id: <199808271920.PAA07543@maia.usno.navy.mil> Subject: Format to exchange clock data -- Initial version To: gpst@maia.usno.navy.mil Date: Thu, 27 Aug 1998 15:20:31 EDT X-Mailer: Elm [revision: 212.4] Status: RO Dear Colleagues, Below is a final (for now) draft for the exchange of clock data. This version is modified, compared with the previous draft (20 July), in the following ways: - Exponential representations (E19.12) are now used for all clock data rather than fixed format, floating point (F19.16). - The text has been clarified (hopefully) to recognize the possibility of satellite-based receivers. I thank Gerard Petit for pointing out the previous format limitations and appreciate the many helpful suggestions from Jim Zumberge, Jan Kouba, and Werner Gurtner. I suggest that this version be regarded as the initial implementation effective today, 27 August 1998, and now available for utilization. Best regards, --Jim Proposed RINEX Extensions to Handle Clock Information ***************************************************** Jim Ray, US Naval Observatory Werner Gurtner, University of Berne (Initial version, 27 August 1998) 0. INTRODUCTION Thus far, the IGS has produced clock results only for the GPS satellites and these are tabulated and distributed at the 15-minute intervals used in the sp3 orbit ephemerides files. There is much interest in increasing the satellite clock interval to 30 seconds (e.g., to overcome SA effects on interpolation) and also in producing station clock results (at some appropriate interval, probably 5 minutes). In principle, the sp3 format could continue to be used for both of these extensions, but it would be wasteful considering that the vast majority of the file space is set aside for orbit information. Also, the variety of other clock information that also needs to be exchanged does not lend itself to the sp3 format. Alternatively, the IGS could devise a new format specifically for distributing clock information. It does not appear that the timing community already uses a standard data format that is well suited for the IGS needs. 1. CLOCK DATA TYPES At the level of monitoring and reporting data from a specific GPS station (or more generally, a "receiver", which could include low Earth-orbiting satellites and other non-stationary platforms) the following types of observations can be expected: calibration data (CR): time delay measurements between a GPS receiver and some external reference point (e.g., local master clock) discontinuity data (DR): a phase-tracking GPS receiver (e.g., AOA TurboRogue) maintains an internal clock that sometimes will reset itself; in principle, there may be methods to monitor such changes which could then be logged as a relative change in clock state >From analysis of GPS data, the results for an ensemble of receiver and satellite clocks can be determined differentially. Normally, all clock values are estimated relative to a single clock being held fixed as a reference. Alternatively, a linear combination of the estimated clocks can be held fixed to some apriori value (normally, zero). In any case, the data are: analysis data (AR,AS): results from GPS phase/pseudorange data analysis for a network of station/receiver (AR) and satellite (AS) clocks, all relative to a fixed reference clock (or ensemble) adopted in the analysis In addition, the broadcast clocks of the satellites can be monitored and compared to a laboratory standard: monitor data (MS): broadcast values for satellite clocks as compared with a laboratory standard via monitor receivers (usually timing receivers) 2. FORMAT TYPES AND FILE NAMING Following established practice, the receiver-specific data ("CR" and "DR") could be reported using an extension of the RINEX format while the analysis data ("Ax" and "MS") could be reported using an extension to a standard product format, such as SINEX. However, since all of these data types are related and probably need similar format requirements, it seems more economical to consider a single file format type suitable for all. RINEX seems the most appropriate file type, even though it is not normally used for analysis products. When it becomes feasible and necessary to include clock estimates with other analysis products, then suitable formats can be incorporated into SINEX. Until then, it is suggested that a RINEX format extension be used for all clock/timing results. Normally, "CR" and "DR" data types would be collected at the stations, files would be prepared at the data centers, and the files would flow to the Global Data Centers named as: for calibration data (CR) & discontinuity data (DR) --------------------------------------------------- ssssdddf.yyC ssss: 4-character station/receiver name designator ddd: day of the year of first record f: file sequence number within day 0: file contains all the existing data of the current day yy: year C: file type "C" for clock information The suffix "C" would be a new RINEX file type. Normally, data would be compiled into files by each 24-hour day (GPS time). The analysis results "AR", "AS", and "MS" would be formed at IGS Analysis Centers or by IGS/BIPM Pilot Project analysis groups and would normally include results for a number of stations/receivers and/or satellites. These files would be named as: for analysis data (Ax) & monitor data (MS) ------------------------------------------ cccwwwwd.clk ccc: 3-character analysis center name designator wwww: GPS week number d: day within GPS week (0 - 7) clk: suffix to identify clock information product files Files could be either daily (d = 0,...,6) or weekly (d = 7). However, despite the file names, a single format for the contents would apply for all data types. 3. NUMERICAL PRECISION All timing quantities (units sec, sec/sec, sec/sec**2) are reported in exponential format with a precision of 12 decimal places. 4. CLOCK DISCONTINUITIES Clock discontinuities (in bias, rate, and/or acceleration) could be reported in either of two ways. If monitored in situ and logged, these could be reported as "DR" data types in .yyC station files. If detected in data analysis, these can be reported in .clk files as two "AR" data records for the same station at the same epoch but with two different sets of clock values. 5. RECEIVER AND SATELLITE NAMES Since the clock data are normally used in conjunction with data analysis results (even for the calibration and discontinuity data types), it is most convenient to use naming conventions for the receivers and satellites which correspond to the same names used in analyses. In order to ensure uniqueness and complete identification, it is also necesssary to supply the receiver ID number (for fixed terrestrial receivers, the DOMES number issued by the Terrestrial Frame Section of the IERS). Thus, receivers should be identified by: Station names: IGS official 4-character receiver name designator Station number: DOMES number (or other unique identifier) For satellite names, the following designations are used in RINEX: Satellite names: 3-character string: "Gnn": nn is the PRN number for GPS satellites "Rnn": nn is the almanac number for GLONASS satellites If other satellite transmitters become available with suitable GPS- or GLONASS-like signals, such as the geostationary platforms currently being considered, then they can also be included using future RINEX naming conventions. 6. RINEX CLOCK FORMAT DEFINITIONS AND EXAMPLES The header recorders should be included in the order indicated, when required. The records below marked with * are optional. It is recommended that each record be read into a blank buffer string and then the information can be decoded afterwards from the buffer. Header and data records are limited to 80 characters. If more than bias and bias sigma are reported, a continuation line must be used. A data file must begin with the header records. Data records begin immediately after the "END OF HEADER" record and complete the remainder of the data file. +----------------------------------------------------------------------------+ | TABLE A15 | | CLOCK DATA FILE - HEADER SECTION DESCRIPTION | +--------------------+------------------------------------------+------------+ | HEADER LABEL | DESCRIPTION | FORMAT | | (Columns 61-80) | | | +--------------------+------------------------------------------+------------+ |RINEX VERSION / TYPE| - Format version (2.00) | F9.2,11X, | | | - File type ("C" for Clock Data) | A1,39X | +--------------------+------------------------------------------+------------+ |PGM / RUN BY / DATE | - Name of program creating current file | A20, | | | - Name of agency creating current file | A20, | | | - Date of file creation | A20 | +--------------------+------------------------------------------+------------+ *|COMMENT | Comment line(s) | A60 |* +--------------------+------------------------------------------+------------+ *|LEAP SECONDS | Number of leap seconds since 6-Jan-1980 | I6 |* | | Recommended as an aid to convert from | | | | GPS time to UTC | | +--------------------+------------------------------------------+------------+ |# / TYPES OF DATA | - Number of different clock data types | I6, | | | stored in the file | | | | - List of clock data types | 5(4X,A2) | | | | | | | The following clock data types are | | | | defined in RINEX Version 2: | | | | | | | | "AR": Data analysis results for receiver | | | | clocks derived from a set of | | | | network receivers and satellites | | | | wrt to a reference clock fixed in | | | | the analysis | | | | "AS": Data analysis results for satellite| | | | clocks derived from a set of | | | | network receivers and satellites | | | | wrt to a reference clock fixed in | | | | the analysis | | | | "CR": Calibration measurements for a | | | | single GPS receiver wrt an | | | | external local reference clock | | | | "DR": Discontinuity measurements for a | | | | single GPS receiver | | | | "MS": Monitor measurements for the | | | | broadcast satellite clocks wrt a | | | | standard timescale | | | | | | +--------------------+------------------------------------------+------------+ |STATION NAME / NUM | - 4-character receiver name designator | A4,1X, | | | - Unique receiver identifier, | A20,35X | | | preferably the DOMES number for | | | | fixed stations | | | | | | | | * REQUIRED for data types "CR" & "DR" | | | | | | +--------------------+------------------------------------------+------------+ |STATION CLK REF | Unique identifier for external | A60 | | | reference clock being used as the | | | | standard for calibration | | | | | | | | * REQUIRED for data type "CR" | | | | | | +--------------------+------------------------------------------+------------+ |ANALYSIS CENTER | Name of Analysis Center | | | | - 3-character IGS AC designator | A3,2X, | | | - Full name of Analysis Center | A55 | | | | | | | * REQUIRED for data types "Ax" & "MS" | | | | | | +--------------------+------------------------------------------+------------+ |# OF CLK REF | - Number of analysis clock references | I6,54X | | | (satellite or receiver clocks) | | | | | | | | * REQUIRED for data types "Ax" | | | | | | +--------------------+------------------------------------------+------------+ |ANALYSIS CLK REF | List of the analysis clock references | | | | (repeat for each reference clock | | | | enumerated in the previous record) | | | | - Name of the receiver or satellite | A4,1X, | | | used as the fixed reference in data | | | | analysis | | | | - Unique identifier for reference | A20,15X, | | | clock (if a receiver), preferably | | | | the DOMES number for fixed stations | | | | - Optionally a non-zero value for the | E19.12,1X | | | the apriori clock constraint can be | | | | provided (unit: seconds). | | | | | | | | * REQUIRED for data types "Ax" | | | | | | +--------------------+------------------------------------------+------------+ |# OF SOLN STA / TRF | - Number of receivers included in the | I6,4X, | | | clock data records and listed in | | | | following header records | | | | - Terrestrial reference frame or | A50 | | | SINEX solution for the station/ | | | | receiver coordinates which match | | | | the clock solution | | | | | | | | * REQUIRED for data types "Ax" | | | | | | +--------------------+------------------------------------------+------------+ |SOLN STA NAME / NUM | For each station/receiver included in | | | | the clock data records (number given in | | | | the previous header record), include one | | | | record with the following information: | | | | - 4-character station/receiver name | A4,1X, | | | designator | | | | - Unique station/receiver identifier, | A20,35X | | | preferably the DOMES number for | | | | fixed stations | | | | | | | | * REQUIRED for data types "Ax" | | | | | | +--------------------+------------------------------------------+------------+ |END OF HEADER | Last record in the header section. | 60X | +--------------------+------------------------------------------+------------+ +----------------------------------------------------------------------------+ | TABLE A16 | | CLOCK DATA FILE - DATA RECORD DESCRIPTION | +-------------+-------------------------------------------------+------------+ | OBS. RECORD | DESCRIPTION | FORMAT | +-------------+-------------------------------------------------+------------+ |TYP/EPOCH/CLK| - Clock data type (AR, AS, CR, DR, MS) | A2,1X, | | | | | | | - Receiver or satellite name | A4,1X, | | | - Receiver name is the IGS 4-character | | | | designator | | | | - Satellite name is a 3-character string: | | | | - "Gnn" where nn is the PRN number | | | | for GPS satellite | | | | - "Rnn" where nn is the almanac number | | | | for GLONASS satellite | | | | | | | | - Epoch in GPS time (not local time!): | | | | year (4 digits),month,day,hour,min, | I4,4I3, | | | second | F10.6, | | | - Number of data values to follow | I3,3X, | | | - Clock data in the following sequence: | | | | - Clock bias (seconds) | E19.12,X | | | - Clock bias sigma [optional] (seconds) | E19.12 | +-------------+-------------------------------------------------+------------+ |TYP/EPOCH/CLK| - Clock rate [optional] (dimensionless) | E19.12,X, | | (CONT) | - Clock rate sigma [optional] (dimensionless)| E19.12,X, | | | - Clock acceleration [optional] (per second) | E19.12,X, | | | - Clock acceleration sigma [optional] | E19.12 | | | (per second) | | | | | | | | The continuation line is necessary for more | | | | than 2 data values | | | | | | | | NB: For data types "Ax", "CR", and "MS", | | | | clock data are in the sense of | | | | reported station/satellite clock | | | | *minus* reference clock value. | | | | For data type "DR", clock data are | | | | the sense of clock value after | | | | discontinuity *minus* before. | | | | | | | | Clock data apart from bias values are | | | | optional. However, if any optional values | | | | are included, then all lower order values | | | | must be supplied even if optional (although | | | | zero values may be given) | | | | | | +-------------+-------------------------------------------------+------------+ +------------------------------------------------------------------------------+ | TABLE A17 | | CLOCK DATA FILE - EXAMPLE FOR ANALYSIS DATA | +------------------------------------------------------------------------------+ ----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8| 2.00 CLOCK DATA RINEX VERSION / TYPE TORINEXC V9.9 USNO 3-APR-96 00:10 PGM / RUN BY / DATE EXAMPLE OF A CLOCK DATA FILE COMMENT IN THIS CASE ANALYSIS RESULTS ARE INCLUDED COMMENT 10 LEAP SECONDS 2 AS AR # / TYPES OF DATA USN USNO USING GIPSY/OASIS-II ANALYSIS CENTER 1 # OF CLK REF USNO 40451S003 -.1234567890123456 ANALYSIS CLK REF 4 ITRF96 # OF SOLN STA / TRF GOLD 40405S031 SOLN STA NAME / NUM AREQ 42202M005 SOLN STA NAME / NUM TIDB 50103M108 SOLN STA NAME / NUM HARK 30302M007 SOLN STA NAME / NUM END OF HEADER AR AREQ 1994 07 14 20 59 0.000000 6 -0.1234567890123456 -0.1234567890123456 -0.1234567890123456 -0.1234567890123456 -0.1234567890123456 -0.1234567890123456 AS G16 1994 07 14 20 59 0.000000 2 -.1234567890123456 -.1234567890123456 AR GOLD 1994 07 14 20 59 0.000000 4 -.1234567890123456 -.1234567890123456 -.1234567890123456 -.1234567890123456 AR HARK 1994 07 14 20 59 0.000000 2 .1234567890123456 .1234567890123456 AR TIDB 1994 07 14 20 59 0.000000 6 .1234567890123456 .1234567890123456 .1234567890123456 .1234567890123456 .1234567890123456 .1234567890123456 ----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8| +------------------------------------------------------------------------------+ | TABLE A18 | | CLOCK DATA FILE - EXAMPLE FOR CALIBRATION/DISCONTINUITY DATA | +------------------------------------------------------------------------------+ ----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8| 2.00 CLOCK DATA RINEX VERSION / TYPE TORINEXC V9.9 USNO 3-APR-96 00:10 PGM / RUN BY / DATE EXAMPLE OF A CLOCK DATA FILE COMMENT IN THIS CASE CALIBRATION/DISCONTINUITY DATA GIVEN COMMENT 10 LEAP SECONDS 2 CR DR # / TYPES OF DATA USNO 40451S003 STATION NAME / NUM UTC(USNO) MASTER CLOCK VIA CONTINUOUS CABLE MONITOR STATION CLK REF END OF HEADER CR USNO 1994 07 14 20 59 50.000000 2 .1234567890123456 .1234567890123456 CR USNO 1994 07 14 22 19 30.000000 2 -.1234567890123456 .1234567890123456 DR USNO 1994 07 14 22 23 14.500000 2 -.1234567890123456 .1234567890123456 CR USNO 1994 07 14 23 44 50.000000 2 -.1234567890123456 .1234567890123456 ----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|