GNSS Catalog File Description and Maintenance

ODTK uses GNSS Catalog files to initialize GNSS SV parameters. They are ASCII text files that you can edit using any ASCII file editor such as Microsoft’s Notepad or WordPad. Each GNSS Catalog file is applicable to a single GNSS system and is used as input to the GNSS constellation object associated with that system. For scenarios containing mixed GNSS systems, ODTK requires a separate constellation object and catalog file for each system. The Catalog files are in C:\ProgramData\AGI\ODTK 7\Databases\GNSS and appear as *_Catalog.txt (e.g., BeiDou_Catalog.txt, Galileo_Catalog.txt, GLONASS_Catalog.txt, GPS_Catalog.txt, and QZSS_Catalog.txt).

ODTK reads the Catalog file during the initialization of the GNSS constellation object to initialize all the SVs contained within the GNSS Source Ephemeris/Clock file. The GNSS constellation object defaults to a GPS constellation and points to the GPS_Catalog.txt. If you want to initialize a GNSS that is different from GPS, you must change the constellation SVReference.Catalog.Filename property to point to the catalog associated with the GNSS of interest. You should do this before specifying the source file of interest. The SVs are identified in ODTK and in the Source Ephemeris file by PRN number. ODTK uses the Catalog file to map the run date/time and PRN number to the GPS SV number, and then map the SV number to the Block Type and Clock Type. ODTK then uses the nominal parameter settings for each Block and Clock type to initialize the SV.

You might need to do some file maintenance and updates to make the Catalog file delivered with the ODTK installation usable with the current time constellation data. You need to do file maintenance when:

  • A new SV has been launched.
  • An existing SV has been decommissioned.

Updated catalog files are often available through the ODTK Data Update Utility. In case the files available through the Data Update Utility have not been updated, or in the case where you do not have internet access, follow these instructions for GNSS file maintenance:

This topic also includes a file format description as well as an example file.

Adding a newly operational SV

This section provides information on adding the following SVs: GPS, BeiDou, QZSS, Galileo, and GLONASS.

Adding a newly operational GPS SV

A newly launched SV is not declared operational until it has completed testing. The clock may not be declared operational for weeks or months after the launch. After a new launch, monitor the Notice Advisory to Navstar Users (NANU) messages at the Coast Guard site to see when the SV is declared operational.

To add a newly operational SV:

  1. Obtain the SV number, PRN number, USSPACECOM number (also known as the NORAD or SSC number), GPS Block Type, and active Clock Type. A good reference is the National Geospatial Intelligence Agency (NGA) for the current satellites. Another good reference is the US Coast Guard’s Navigation Center web site. Also see the US Naval Observatory (USNO) site for files gpstd.txt and gpsb2.txt. ODTK does not actually use the USSPACECOM ID number, so it’s listed as a quick reference.
  2. If single frequency data is to be processed, obtain the L1, L2 group delay differential. The group delay differential is a parameter on the GPS NAV Message file. For RINEX format, see ftp://igs.org/pub/data/format/rinex303.pdf, p. A23, TGD parameter. Otherwise, use a value of zero a placeholder. You can obtain NAV messages from the CDDIS web site, which which describes how to get ephemeris files. See the file brdcddd0.yyn.Z, where ddd is the day of year. For example, PRN 1’s record might look like the one below. The PRN and group delay are highlighted.
    3. 1 11 8 13 22 0 0.0-7.383991032839D-06 1.250555214938D-12 0.000000000000D+00
       6.500000000000D+01 4.593750000000D+01 4.534831751088D-09-3.044815212775D-01
       2.438202500343D-06 2.897552913055D-04 9.018927812576D-06 5.180359760284D+03
       5.976000000000D+05 3.725290298462D-08-2.259532647701D+00 7.450580596924D-08
        9.603173368431D-01 1.985625000000D+02 2.380181211850D+00-7.816754170616D-09
       5.582375385485D-10 1.000000000000D+00 1.648000000000D+03 0.000000000000D+00
       2.800000000000D+00 6.300000000000D+01 7.916241884232D-09 6.500000000000D+01
       5.904180000000D+05 4.000000000000D+00
  3. Enter a new SV record to the STATUS block containing the SVN, PRN, USSPACECOM , Block Type, Clock Type, Launch Date, and Group Delay values (see Status Block).
  4. If this SV is from a new block type, then you will need to add both a new BLOCK type and CLOCK type block. Refer to Block Type Definition Blocks and Clock Definition Blocks. Also see note 1.
  5. If a CLOCK type block exists for this {BLOCK type ,CLOCK type} combination, then you do not need to add a new CLOCK type block, otherwise, add a CLOCK type block.
  6. If the nominal block type and clock type parameter values are applicable to this SV, then no further action is needed. Otherwise, you need to add SV-specific data to the SV block. This is often the case with the Block II and later satellites, to specify the antenna location offset. This information is available from the NGA GPS web site in the section titled NGA GPS Ephemeris/Station/Antenna Offset Documentation. For the GPS III satellites SVN 74 and greater, the antenna offset information is listed in the NAVCEN website as a series of memos containing the phase center offsets.
  7. The IGS and NGA both publish GPS ephemeris but use different GPS antenna offset values. In order to use IGS ephemeris, you must use the IGS antenna offset values. Therefore, AGI maintains a separate GPS_Catalog_IGS.txt file that parallels the GPS_Catalog.txt and GPS_Catalog_NGA.txt files but with the IGS antenna offsets. You can obtain the IGS offsets from the ANTEX (Antenna Exchange) files that they publish. Use the latest igs14_NNNN.atx file. For example GPS SVN 61’s record would look like the following with antenna offsets of 1.3, -1.10, and 728.8 mm; the units are millimeters, whereas the ODTK catalog files use meters. 
START OF ANTENNA
BLOCK IIR-B         G02             G061    2004-045A TYPE / SERIAL NO    
0    29-JAN-17 METH / BY / # / DATE
0.0                                                    DAZI                
0.0  17.0   1.0                                        ZEN1 / ZEN2 / DZEN  
2                                                      # OF FREQUENCIES    
2004    11     6     0     0    0.0000000              VALID FROM          
IGS14_2129                                             SINEX CODE          
G01                                                    START OF FREQUENCY  
1.30     -1.10    728.80                               NORTH / EAST / UP   
NOAZI   10.70   10.10    8.00    4.60    0.50   -3.80   -7.50   -9.70  -10.30 
G01                                                    END OF FREQUENCY    
G02                                                    START OF FREQUENCY  
1.30     -1.10    728.80                               NORTH / EAST / UP   
NOAZI   10.70   10.10    8.00    4.60    0.50   -3.80   -7.50   -9.70  -10.30
G02                                                    END OF FREQUENCY    
END OF ANTENNA

A workaround to steps 4-6 would be to add the SV using an existing Block Type and Clock Type, then use the ODTK property panel attributes to set all SV parameter values.

Adding a newly operational BeiDou SV

Reference the QZSS website BeiDou section for BeiDou constellation information.

Adding a newly operational QZSS SV

Reference here for QZSS constellation information.

You’ll also need to update the QZSS_ISCDelayData.isc file in your ODTK install to add or update any satellites. This file contains the Inter-Signal Correction values. See the corresponding PDF document that describes this process in your ODTK install.

Adding a newly operational Galileo SV

See the official website for GALILEO satellites. There are some other sites that provide information, but remember that they are not official.

You can find physical satellite characteristics at the ILRS website.

You can find group delay information in the GSFC directories. Data does not appear to be filled until a later time, often lagging a few weeks from the current time. The general location is ftp://cddis.gsfc.nasa.gov/pub/gnss/data/daily/2016/ ddd/yyl/.

Galileo satellites require two group delay values called BGD F/Nav and BGD I/NAV in the catalog file. These are broadcast in the Galileo NAV message; you can find them in the *_EN.rnx or *_MN.rnx files at ftp://igs.ign.fr/pub/igs/data/2021/038/. Both values must be nonzero for them to be valid. Occasionally values of zero occur in the files depending on how the receiver was collecting at the time. Take note of the software tool that is used to produce the RINEX file as noted in the header in the lined marked with PGM (program). At least one tool, TPP 4.1.3, is known to have reversed the F/Nav and I/Nav values and so these must be switched (or ignored) if the data is produced by that tool.

You can find information regarding a new Galileo satellite’s mass and antenna offset values at the EUSPA site.

See an example file.

For RINEX format (see ftp://igs.org/pub/data/format/rinex303.pdf, p. A26), the BGD parameters are shown highlighted.

E08 2016 03 19 19 00 00 3.557991585694E-04 3.992113306595E-10 0.000000000000E+00
   8.200000000000E+01 7.365625000000E+01 3.395498579002E-09 -1.177681956301E+00
   3.397464752197E-06 7.024733349681E-05 7.690861821175E-06 5.440610483170E+03
   5.868000000000E+05 -1.490116119385E-08 5.814178692223E-01 -4.470348358154E-08
   9.594885162166E-01 1.760312500000E+02 -1.341552449730E+00 -5.711666485264E-09
   5.825242644738E-10 2.580000000000E+02 1.888000000000E+03
   3.120000000000E+00 7.300000000000E+01 -6.519258022308E-09 -7.683411240578E-09
   5.875400000000E+05

Adding a newly operational GLONASS SV

Reference the GLONASS constellation information. The CSNO-TARC site also lists the status of satellites in the Glonass constellation if the Glonass site is unavailable.

When an SV is decommissioned

When a SV is decommissioned, add the decommissioned date to the applicable SV record of the STATUS block.

File description

Refer to the example file.

File layout

Record/Block Description
Version Record This is the first record in the file. It contains the file version identifier string.
System Block

This is the block containing the system identifier: GPS, BeiDou, QZSS, Galileo, GLONASS, or Custom. If you omit the System Block, ODTK defaults to GPS.

The first record in the block contains SYSTEM starting in column 1.

Keyword/Value pairs follow.

The last record in the block contains END_SYSTEM starting in column 1.

Valid keyword/value pairs are:

  • Type {GPS, BeiDou, QZSS, Galileo, GLONASS, or Custom}
  • Custom_Name {Name} - only use this if Type = Custom
  • Identifier {Char ID} - single character to identify system; only use this if Type = Custom
  • Central_Body {CB Name} - name of central body; only use this if Type = Custom

If you are using ODTK 7.5 or earlier, use only the Type keyword, with the System ID specified, on the second record of the SYSTEM block. Do not include the other keywords.
Status Block Contains the status and basic identifiers of each SV that has been launched. Status information includes launch date and, if applicable, the decommissioned date. Basic identifiers include SV number, PRN number, US SPACECOM number (not currently used), Block Type, active Clock Type, and L1, L2 group delay differential.

The first record in the block contains STATUS starting in column 1.

The second record in the block is a comment card.

SV records follow, one record per SV launched.

The last record in the block contains END_STATUS starting in column 1.

Block Type Definition Blocks Contain initial parameter settings for each Block Type (e.g., II, IIA, IIR, etc.) identified in the Status Block section. There is one Block for each Block Type.

The first record in the block contains BLOCK starting in column 1.

“Parameter” records follow.

The last record in the block contains END_BLOCK starting in column 1.

“Parameter” records include (block) ID, MASS, SOLAR_AREA, SOLAR_MODEL, SOLAR_K1, SOLAR_K2, ANTENNA_OFFSET, SIGNALS, and SP3_SIGCOR data. Clock-related data is specified in the clock definition blocks.

Clock Definition Blocks Contain initial parameter settings for each {Block Type, Clock Type} pair identified in the Status Block. There is one Block for each {Block Type, Clock Type} pair.

The first record in the block contains CLOCK starting in column 1.

“Parameter” records follow.

The last record in the block contains END_CLOCK starting in column 1.

Clock “Parameter” records include the Allan Variance a0, a-1, a-2, and aging WN terms as well as the {Block Type, Clock Type} IDs.

SV Specific Definition Blocks These blocks are optional. They are used as an override, for a specific SV, the initial Block Type or Clock parameter settings or both.

The first record in the block contains SV starting in column 1.

“Parameter” records follow.

The last record in the block contains END_SV starting in column 1.

Parameter records include any Block Type or Clock Definition “Parameters”.

Record/Block detailed descriptions

Version Record

The Version Record is the first record in the file.

Columns Type Description
1-12 string ODTK version string of the form ODTK.V.x.y.z where x is the version number and y,z are the release numbers; .y and/or .z may be blank
13 character The semi-colon character ;

System Block

The System Block is optional. If it is present, it immediately follows the Version Record. The System Block is of the form:

        SYSTEM
        {System ID}   or   Type {System ID}
        Custom_Name  {Name}
        Identifier {Char ID}
        Central_Body  {CB Name}
        END_SYSTEM

For System ID, choose one of the following: GPS, BeiDou, QZSS, Galileo, GLONASS, or Custom. Only use Custom_Name, Identifier, and Central_Body when System ID = Custom. Use the single character Identifier to mark entries in RINEX and SP3 files in same manner as you use G to identify GPS entries and E to identify Galileo entries.

If you are using ODTK 7.5 or earlier, use only the Type keyword, with the System ID specified, on the second record of the SYSTEM block. Do not include the other keywords.

If the System block is not present, ODTK defaults to a GPS Constellation.

Status Block

The Status Block immediately follows the Version Record. The Status Block is of the form:

STATUS

SVN PRN USSPCOM BLOCK CLOCK CLOCK AVAIL DECOMISSIONED GROUP DELAY [Group Delay 2]

… SV records -----

END_STATUS

The SV record definition follows. Input fields are “free-format” and separated by white space.

Description Format
SVN number Integer (%d)
PRN number Integer (%d)
US SPACECOM number (not currently used) Integer (%d)
Block Type ID (e.g. ‘II’, ‘IIA’, ‘IIF’, ‘IIR, ‘IIR-M’) String (%s)
Clock Type (e.g. ‘Cs’, ‘Rb’) String (%s)
Clock Avail Date (dd mmm yyyy), e.g. ‘21 Dec 2003’ Date string (%s%s%s)
Decommissioned Date (dd mmm yyyy), if applicable

If the SV is still active, then this field is blank.

Date string (%s%s%s)
For GPS and QZSS, this is the L1 ,L2 group delay differential (ref ICD-GPS-200C Section 3.3.1.7.2), in seconds. Double exponential format (%le)
Not used for GPS and QZSS. For Galileo, this is the I/Nav Broadcast Group Delay BGD (E1, E5b), in seconds. Double exponential format (%le)

Block Type definition blocks

There is one Block Type block for each Block Type ID identified in the Status Block section. ODTK uses this block to initialize SV parameter settings other than clock data. The Block Type Definition block is of the form:

BLOCK

ID ‘xx’

… Parameter records -----

END_BLOCK

The ID record identifies the Block Type. ODTK uses it to match against the Block Type fields given in the Status Block. Parameter records include a parameter ID starting in column 1 followed by the parameter value(s), where the parameter value(s) are delimited by white space. You can enter parameter records in any order. These are nominal parameter settings for this block type. You can override initial parameter values for individual SVs in the SV Specific Definition Block. You can also override parameter values at run time through ODTK white panel attributes.

Parameter ID Description Format
MASS Initial on orbit mass (after orbit adjust) in kg Double (%lf)
SOLAR_AREA Effective solar pressure area in m^2 Double (%lf)
SOLAR_MODEL GPS Solar Pressure Model; see GPS Solar Pressure Models & Parameters for choices String (%s)
SOLAR_K1 GPS solar pressure 2-state K1 parameter initial value (unitless) Double (%lf)
SOLAR_K2 GPS solar pressure 2-state K2 parameter initial value (unitless) Double (%lf)
ANTENNA_OFFSET X, Y, Z offset of the antenna phase center from the satellite's center of gravity in the satellite's body frame, in meters 3 Doubles
(%lf, %lf, %lf)
SIGNALS These are the list of signals processed by SVs of this particular block type. For GPS signals, valid entries include L1CA, L1C, L1P, L2C, L2P, and L5. For Galileo signals, valid entries include E1, E5a, E5b, E5ab, and E6. If you omit this record, then GPS signals L1 CA, L1P, and L2P are the default. List of Strings (%s)
SP3_SIGCOR This is an 8x8 “nominal” SP3 orbit-clock error sigma correlation matrix in upper triangular form. The order of parameters is [R, I, C, Rd, Id, Cd, clock phase, clock frequency]. Position units are meters, velocity units are meters/sec, clock phase is in sec, and clock frequency is sec/sec. Ordering of data is

a11 a12 a13 a14 a15 a16 a17 a18
    a22 a23 a24 a25 a26 a27 a28
        a33 a34 a35 a36 a37 a38
            a44 a45 a46 a47 a48
                a55 a56 a57 a58
                    a66 a67 a68
                        a77 a78
                            a88

36 terms,

double (%lf)

 

1 row/line

Clock Definition blocks

There is one Clock Definition block for each {Block Type, Clock Type} combination identified in the Status Block section. Use this block to initialize the clock Allan variance parameters. The Clock Definition block is of the form:

CLOCK

ID ‘xx’

FREQ_STD ‘yy’

… Parameter records -----

END_CLOCK

The {ID, FREQ_STD} records identify the {Block Type, Clock Type} combination used to match against in the Status Block. Parameter records include a parameter ID starting in column 1 followed by the parameter value(s), where the parameter value(s) are delimited by white space. You can enter parameter records in any order. These are nominal parameter settings for this clock type. You can override initial parameter values for individual SVs in the SV Specific Definition Block. You can also override parameter values at run time through ODTK white panel attributes.

Parameter ID Description Format
a0 Allan variance constant associated with frequency white noise (sec) Double (%lf)
a-1 Allan variance constant associated with frequency flicker noise (unitless);

not used in ODTK

Double (%lf)
a-2 Allan variance constant associated with frequency random walk (sec -1) Double (%lf)
agingWN Constant associated with frequency drift (sec -3) Double (%lf)

SV-specific Definition blocks

SV-specific Definition blocks are optional. Use them to override “nominal” block type and clock type parameters values. The SV Definition block is of the form:

SV

ID xx

… Parameter records -----

END_SV

The ID record identifies the SVN number of the SV given in the Status Block. All other records within the block are optional and may include any of the “Parameter” records types allowed in the Block Type definition and Clock definition blocks. Typically this is where you override the block-specific antenna offset parameters with spacecraft-specific ones. NGA publishes station and antenna offset information on their web site. When new spacecraft are launched, AGI updates the GPS_Catalog.txt file using the antenna offsets from this file. The IGS also publishes antenna offset information:

See the article Innovation: Digging into GPS Integrity, which discusses the significant differences between the two sources.

Example GPS_Catalog.txt file

ODTK.V.6.4.2;

SYSTEM
GPS
END_SYSTEM

STATUS
SVN PRN USSPCOM BLOCK CLOCK CLOCK AVAIL DECOMMISSIONED GROUP DELAY
42 00 0 IIR Rb 17 JAN 1997 17 JAN 1997 0.0000000000000E+00
32 01 22231 IIA Cs 11 DEC 1992 17 MAR 2008 -3.2596290111500E-09
49 01 34661 IIR-M Rb 24 MAR 2009 06 MAY 2011 -1.9092112779600E-08
63 01 37753 IIF Rb 14 OCT 2011 5.1222741603900E-09
13 02 20061 II Cs 10 AUG 1989 12 MAY 2004 -1.3969838619200E-09
61 02 28474 IIR Rb 22 NOV 2004 -2.0489096641500E-08
33 03 23833 IIA Cs 09 APR 1996 02 AUG 2014 -4.6566128730770E-09
69 03 40294 IIF Rb 12 DEC 2014 1.8626451492300E-09
34 04 22877 IIA Rb 22 NOV 1993 03 NOV 2015 -1.9092112779600E-08
35 05 22779 IIA Rb 28 SEP 1993 26 MAR 2009 -4.1909515857700E-09
50 05 35752 IIR-M Rb 27 AUG 2009 -1.0710209608100E-08
36 06 23027 IIA Rb 28 MAR 1994 17 MAY 2014 -5.1222741603850E-09
67 06 39741 IIF Rb 10 JUN 2014 4.1909515857700E-09
37 07 22657 IIA Rb 12 JUN 1993 20 DEC 2007 -1.8626451492300E-09
48 07 32711 IIR-M Rb 24 MAR 2008 -1.1175870895400E-08
38 08 25030 IIA Cs 18 DEC 1997 30 OCT 2014 -4.6566128730800E-09
72 08 40730 IIF Cs 12 AUG 2015 4.6566128730800E-09
39 09 22700 IIA Cs 21 JUL 1993 19 MAY 2014 -5.5879354476930E-09
68 09 40105 IIF Rb 17 SEP 2014 1.3969838619200E-09
40 10 23953 IIA Cs 15 AUG 1996 16 JUL 2015 -3.2596290111500E-09
73 10 41019 IIF Rb 09 DEC 2015 2.3283064365400E-09
46 11 25933 IIR Rb 03 JAN 2000 -1.2107193470000E-08
58 12 29601 IIR-M Rb 13 DEC 2006 -1.2107193470000E-08
43 13 24876 IIR Rb 31 JAN 1998 -1.1175870895400E-08
14 14 19802 II Cs 15 APR 1989 14 APR 2000 -2.7939677238500E-09
41 14 26605 IIR Rb 10 DEC 2000 -9.3132257461600E-09
15 15 20830 II Cs 15 OCT 1990 14 MAR 2007 -2.7939677238500E-09
55 15 32260 IIR-M Rb 31 OCT 2007 -1.0710209608100E-08
16 16 20185 II Cs 14 OCT 1989 13 OCT 2000 -9.3132257461500E-10
56 16 27663 IIR Rb 18 FEB 2003 -1.0244548320800E-08
17 17 20361 II Rb 06 JAN 1990 23 FEB 2005 -1.3969838619200E-09
53 17 28874 IIR-M Rb 16 DEC 2005 -1.0710209608100E-08
18 18 20452 II Cs 14 FEB 1990 18 AUG 2000 -5.1222741603900E-09
54 18 26690 IIR Rb 15 FEB 2001 -1.1175870895400E-08
19 19 20302 II Cs 23 NOV 1989 11 SEP 2001 -3.2596290111500E-09
59 19 28190 IIR Rb 05 APR 2004 -1.5366822481200E-08
20 20 20533 II Cs 18 APR 1990 13 DEC 1996 -1.8626451492300E-09
51 20 26360 IIR Rb 01 JUN 2000 -8.3819031715400E-09
21 21 20724 II Cs 22 AUG 1990 27 JAN 2003 -2.3283064365400E-09
45 21 27704 IIR Rb 12 APR 2003 -1.1641532182700E-08
22 22 22446 IIA Cs 04 APR 1993 06 AUG 2003 -3.7252902984600E-09
47 22 28129 IIR Rb 12 JAN 2004 -1.7695128917700E-08
23 23 20959 IIA Cs 26 NOV 1990 13 FEB 2004 -2.7939677238500E-09
60 23 28361 IIR Rb 09 JUL 2004 -2.0023435354200E-08
24 24 21552 IIA Cs 30 AUG 1991 04 NOV 2011 -1.3969838619200E-09
65 24 38833 IIF Cs 14 NOV 2012 2.3283064365400E-09
25 25 21890 IIA Rb 24 MAR 1992 18 DEC 2009 -7.4505805969200E-09
62 25 36585 IIF Rb 27 AUG 2010 5.5879354476900E-09
26 26 22014 IIA Rb 23 JUL 1992 05 JAN 2015 -6.5192580223100E-09
71 26 40534 IIF Rb 20 APR 2015 6.9849193096200E-09
27 27 22108 IIA Cs 30 SEP 1992 10 JUN 2002 -4.1909515857700E-09
27 27 22108 IIA Rb 21 JUN 2002 10 AUG 2011 -4.1909515857700E-09
27 27 22108 IIA Cs 16 DEC 2011 20 JUN 2013 -4.1909515857700E-09
66 27 39166 IIF Rb 21 JUN 2013 1.3969838619200E-09
28 28 21930 IIA Cs 25 APR 1992 15 AUG 1997 0.0000000000000E+00
44 28 26407 IIR Rb 17 AUG 2000 -1.0710209608100E-08
29 29 22275 IIA Rb 05 JAN 1993 23 OCT 2007 -6.9849193096200E-09
57 29 32384 IIR-M Rb 02 JAN 2008 -1.0244548320800E-08
30 30 24320 IIA Cs 01 OCT 1996 20 JUL 2011 -7.9162418842300E-09
35 30 22779 IIA Rb 16 AUG 2011 28 MAR 2013 -4.1909515857700E-09
64 30 39533 IIF Rb 30 MAY 2014 3.2596290111500E-09
31 31 22581 IIA Rb 13 APR 1993 24 OCT 2005 -6.0535967350000E-09
52 31 29486 IIR-M Rb 12 OCT 2006 -1.3504177331900E-08
23 32 20959 IIA Rb 26 FEB 2008 25 JAN 2016 -3.7252902984600E-09
70 32 41328 IIF Rb 09 MAR 2016 2.7939677238500E-09
END_STATUS

***********************************************************************************************
* Begin Block Definitions *
***********************************************************************************************

BLOCK
ID II
MASS 880.0
SOLAR_MODEL GPS_BlkIIA_GSPM04ae
SOLAR_AREA 18.0
SOLAR_K1 0.0
SOLAR_K2 0.0
ANTENNA_OFFSET 0.279400 0.000000 0.951900
SP3_SIGCOR 1.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
2.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
1.000000 0.000000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000
3.000000E-09 0.000000
3.500000E-14
END_BLOCK

BLOCK
ID IIA
MASS 970.0
SOLAR_MODEL GPS_BlkIIA_GSPM04ae
SOLAR_AREA 18.0
SOLAR_K1 0.0
SOLAR_K2 0.0
ANTENNA_OFFSET 0.279400 0.000000 0.951900
SP3_SIGCOR 1.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
2.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
1.000000 0.000000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000
3.000000E-09 0.000000
3.500000E-14
END_BLOCK

BLOCK
ID IIR
MASS 1100.0
SOLAR_MODEL GPS_BlkIIR_GSPM04ae
SOLAR_AREA 20.0
SOLAR_K1 0.0
SOLAR_K2 0.0
ANTENNA_OFFSET 0.000000 0.000000 1.614000
SIGNALS L1CA L1P L2P
SP3_SIGCOR 1.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
2.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
1.000000 0.000000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000
3.000000E-09 0.000000
3.500000E-14
END_BLOCK

BLOCK
ID IIR-M
MASS 1100.0
SOLAR_MODEL GPS_BlkIIR_GSPM04ae
SOLAR_AREA 20.0
SOLAR_K1 0.0
SOLAR_K2 0.0
ANTENNA_OFFSET 0.000000 0.000000 1.614000
SIGNALS L1CA L1P L2C L2P
SP3_SIGCOR 1.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
2.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
1.000000 0.000000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000
3.000000E-09 0.000000
3.500000E-14
END_BLOCK

BLOCK
ID IIF
MASS 1630.0
SOLAR_MODEL GPS_BlkIIR_GSPM04ae
SOLAR_AREA 21.0
SOLAR_K1 0.0
SOLAR_K2 0.0
ANTENNA_OFFSET 0.392000 0.002000 1.093000
SIGNALS L1CA L1P L2C L2P L5
SP3_SIGCOR 1.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
2.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
1.000000 0.000000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000
3.000000E-09 0.000000
3.500000E-14
END_BLOCK

BLOCK
ID III
MASS 3680.0
SOLAR_MODEL GPS_BlkIIR_GSPM04ae
SOLAR_AREA 21.0
SOLAR_K1 0.0
SOLAR_K2 0.0
ANTENNA_OFFSET 0.000000 0.000000 0.000000
SIGNALS L1CA L1C L1P L2C L2P L5
SP3_SIGCOR 1.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
2.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000
1.000000 0.000000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000 0.000000
0.001000 0.000000 0.000000
3.000000E-09 0.000000
3.500000E-14
END_BLOCK

***********************************************************************************************
* Begin Clock Definitions *
***********************************************************************************************

CLOCK
BLOCKID II
FREQ_STD Cs
a0 3.000000E-21
a-1 0.000000E+00
a-2 1.225000E-31
agingWN 0.000000E+00
END_CLOCK

CLOCK
BLOCKID II
FREQ_STD Rb
a0 9.000000E-24
a-1 0.000000E+00
a-2 9.000000E-32
agingWN 0.000000E+00
END_CLOCK

CLOCK
BLOCKID IIA
FREQ_STD Cs
a0 3.000000E-21
a-1 0.000000E+00
a-2 1.225000E-31
agingWN 0.000000E+00
END_CLOCK

CLOCK
BLOCKID IIA
FREQ_STD Rb
a0 9.000000E-24
a-1 0.000000E+00
a-2 9.000000E-32
agingWN 0.000000E+00
END_CLOCK

CLOCK
BLOCKID IIR
FREQ_STD Rb
a0 9.000000E-24
a-1 0.000000E+00
a-2 9.000000E-32
agingWN 0.000000E+00
END_CLOCK

CLOCK
BLOCKID IIR-M
FREQ_STD Rb
a0 9.000000E-24
a-1 0.000000E+00
a-2 9.000000E-32
agingWN 0.000000E+00
END_CLOCK

CLOCK
BLOCKID IIF
FREQ_STD Rb
a0 9.000000E-24
a-1 0.000000E+00
a-2 9.000000E-32
agingWN 0.000000E+00
END_CLOCK

CLOCK
BLOCKID IIF
FREQ_STD Cs
a0 3.000000E-21
a-1 0.000000E+00
a-2 1.225000E-31
agingWN 0.000000E+00
END_CLOCK

CLOCK
BLOCKID III
FREQ_STD Rb
a0 9.000000E-24
a-1 0.000000E+00
a-2 9.000000E-32
agingWN 0.000000E+00
END_CLOCK

***********************************************************************************************
* SV Specific Definitions - IIR, IIR, IIR-M, and IIF, Antenna Offsets *
* Antenna information obtained from NGA's published data at *
* http://earth-info.nga.mil/GandG/sathtml/documentation.html *
***********************************************************************************************

SV
ID 41
ANTENNA_OFFSET 0.001800 0.000200 1.613700
END_SV

SV
ID 43
ANTENNA_OFFSET 0.002400 0.002500 1.614000
END_SV

SV
ID 44
ANTENNA_OFFSET 0.001900 0.000700 1.513100
END_SV

SV
ID 45
ANTENNA_OFFSET 0.002300 -0.000600 1.584000
END_SV

SV
ID 46
ANTENNA_OFFSET 0.001900 0.001100 1.514100
END_SV

SV
ID 47
ANTENNA_OFFSET 0.001800 -0.000900 0.059800
END_SV

SV
ID 48
ANTENNA_OFFSET 0.001270 0.000250 0.000560
END_SV

SV
ID 49
ANTENNA_OFFSET 0.012450 -0.000380 -0.022830
END_SV

SV
ID 50
ANTENNA_OFFSET 0.002920 -0.000050 -0.016710
END_SV

SV
ID 51
ANTENNA_OFFSET 0.002200 0.001400 1.614000
END_SV

SV
ID 52
ANTENNA_OFFSET 0.001600 0.000330 -0.057500
END_SV

SV
ID 53
ANTENNA_OFFSET -0.009960 0.005990 -0.100600
END_SV

SV
ID 54
ANTENNA_OFFSET -0.009800 0.006000 1.592300
END_SV

SV
ID 55
ANTENNA_OFFSET -0.009960 0.005790 -0.012270
END_SV

SV
ID 56
ANTENNA_OFFSET -0.009800 0.006000 1.663000
END_SV

SV
ID 57
ANTENNA_OFFSET -0.010120 0.005910 -0.015120
END_SV

SV
ID 58
ANTENNA_OFFSET -0.010160 0.005870 -0.093550
END_SV

SV
ID 59
ANTENNA_OFFSET -0.007900 0.004600 -0.018000
END_SV

SV
ID 60
ANTENNA_OFFSET -0.008800 0.003500 0.000400
END_SV

SV
ID 61
ANTENNA_OFFSET -0.009900 0.006100 -0.082000
END_SV

SV
ID 62
ANTENNA_OFFSET 0.392000 0.002000 1.093000
END_SV

SV
ID 63
ANTENNA_OFFSET 0.391000 0.000000 1.091000
END_SV

SV
ID 64
ANTENNA_OFFSET 0.395200 -0.000800 1.090400
END_SV

SV
ID 65
ANTENNA_OFFSET 0.392000 0.002000 1.093000
END_SV

SV
ID 66
ANTENNA_OFFSET 0.391400 0.000300 1.090400
END_SV

SV
ID 67
ANTENNA_OFFSET 0.394700 -0.001000 1.091700
END_SV

SV
ID 68
ANTENNA_OFFSET 0.395500 -0.002000 1.092200
END_SV

SV
ID 69
ANTENNA_OFFSET 0.395000 0.000300 1.090700
END_SV

SV
ID 70
ANTENNA_OFFSET 0.396600 -0.000200 1.084300
END_SV

SV
ID 71
ANTENNA_OFFSET 0.393400 -0.001100 1.092700
END_SV

SV
ID 72
ANTENNA_OFFSET 0.396200 -0.000300 1.085600
END_SV

SV
ID 73
ANTENNA_OFFSET 0.396200 -0.001300 1.083100
END_SV