IS-GPS-800A - US Coast Guard Navigation Center
IS-GPS-800A - US Coast Guard Navigation Center IS-GPS-800A - US Coast Guard Navigation Center
The user shall use the broadcast URA oc Index to derive URA ocb . The index is a two’s complement representation ofa signed integer in the range of +15 to –16 and has the following relationship to the clock-related user derivedURA ocb :URA oc IndexURA ocb (meters)15 6144.00 < URA ocb14 3072.00 < URA ocb 6144.0013 1536.00 < URA ocb 3072.0012 768.00 < URA ocb 1536.0011 384.00 < URA ocb 768.0010 192.00 < URA ocb 384.009 96.00 < URA ocb 192.008 48.00 < URA ocb 96.007 24.00 < URA ocb 48.006 13.65 < URA ocb 24.005 9.65 < URA ocb 13.654 6.85 < URA ocb 9.653 4.85 < URA ocb 6.852 3.40 < URA ocb 4.851 2.40 < URA ocb 3.400 1.70 < URA ocb 2.40-1 1.20 < URA ocb 1.70-2 0.85 < URA ocb 1.20-3 0.60 < URA ocb 0.85-4 0.43 < URA ocb 0.60-5 0.30 < URA ocb 0.43-6 0.21 < URA ocb 0.30-7 0.15 < URA ocb 0.21-8 0.11 < URA ocb 0.15-9 0.08 < URA ocb 0.11-10 0.06 < URA ocb 0.08-11 0.04 < URA ocb 0.06-12 0.03 < URA ocb 0.04-13 0.02 < URA ocb 0.03-14 0.01 < URA ocb 0.02-15 URA ocb 0.01-16 No accuracy prediction available—use at own riskThe user may use the upper bound value in the URA ocb range corresponding to the broadcast index, therebycalculating the maximum URA oc that is equal to or greater than the CS predicted URA oc , or the user may use thelower bound value in the range which will provide the minimum URA oc that is equal to or less than the CS predictedURA oc .48 IS-GPS-800A8 June 2010
The transmitted URA oc1 Index is an integer value in the range 0 to 7. URA oc1 Index has the following relationship tothe URA oc1 :whereURA oc1 =1N (meters/second)2N = 4 + URA oc1 Index.The transmitted URA oc2 Index is an integer value in the range 0 to 7. URA oc2 Index has the following relationship tothe URA oc2 :whereURA oc2 =1N (meters/second 2 )2N = 25 + URA oc2 Index.3.5.3.9 Group Delay Correction ParametersBits 527 through 565 of subframe 2 provide the group delay differential correction terms for L1C signal users. Thefollowing algorithms shall apply when interpreting the correction parameters in the message. The bit lengths, scalefactors, ranges, and units of these parameters are given in Table 3.5-1. The bit string of “1000000000000” shallindicate that the group delay value is not available. The related algorithm is given in paragraphs 3.5.3.9.1 and3.5.3.9.2.3.5.3.9.1 Inter-Signal CorrectionThe correction terms, T GD , ISC L1CP , and ISC L1CD , are initially provided by the CS to account for the effect of SVinter-signal biases between L1 P(Y) and L2 P(Y), between L1 P(Y) and L1C P , and between L1 P(Y) and L1C D ,respectively, based on measurements made by the SV contractor during SV manufacture. The values of T GD andISCs for each SV may be subsequently updated to reflect the actual on-orbit group delay differential. For maximumaccuracy, the single frequency L1C P user must use the correction terms to make further modifications to the codephase offset in paragraph 20.3.3.3.3.1 of IS-GPS-200 with the equation:(t SV ) L1CP = t SV - T GD + ISC L1CPwhere T GD (see paragraph 20.3.3.3.3.2 of IS-GPS-200) and ISC L1CP are provided to the user as subframe 2 data. Formaximum accuracy, the single frequency L1C D user must use the correction terms to make further modifications tothe code phase offset given by:(t SV ) L1CD = t SV - T GD + ISC L1CD49 IS-GPS-800A8 June 2010
- Page 5 and 6: 3.2.3.3 Cyclic Redundancy Check ...
- Page 7 and 8: LIST OF FIGURESFigure 3.2-1. Genera
- Page 9 and 10: 1. INTRODUCTION1.1 ScopeThis Interf
- Page 11 and 12: 3. SIGNAL REQUIREMENTSThe requireme
- Page 13 and 14: Carriers of the two L1C components
- Page 15 and 16: 3.2.2 PRN Code CharacteristicsThe c
- Page 17 and 18: The overlay codes are derived from
- Page 19 and 20: 3.2-2 L1C Ranging Codes Parameter A
- Page 21 and 22: GPS PRNSignal No.3.2-3 L1C O Overla
- Page 23 and 24: FIXED LENGTH-10223 LEGENDRE SEQUENC
- Page 25 and 26: 3.2.2.2 Non-Standard CodesThe non-s
- Page 27 and 28: corresponding to MSB = 0. (A SV tra
- Page 29 and 30: This code has the following charact
- Page 31 and 32: 3.2.3.5 InterleavingThe 1748 encode
- Page 33 and 34: 3.3 Signal ModulationThe signals mo
- Page 35 and 36: Bit valueL1C DbitstreamSubcarrier s
- Page 37 and 38: 3.5 Message DefinitionAs shown in F
- Page 40 and 41: DIRECTION OF DATA FLOW FROM SV100 B
- Page 42 and 43: DIRECTION OF DATA FLOW FROM SV100 B
- Page 44 and 45: DIRECTION OF DATA FLOW FROM SV100 B
- Page 46 and 47: 3.5.3 Subframe 2Subframe 2 provides
- Page 48 and 49: Table 3.5-1. Subframe 2 Parameters
- Page 50 and 51: 3.5.3.1 Transmission Week NumberBit
- Page 52 and 53: 3.5.3.6 Ephemeris Parameter Charact
- Page 54 and 55: Table 3.5-2. Elements of Coordinate
- Page 58 and 59: where, ISC L1CD is provided to the
- Page 60 and 61: 3.5.3.10.1 Integrity Status Flag (I
- Page 62 and 63: The ionospheric data shall be updat
- Page 64 and 65: 3.5.4.2.3 User Algorithm for Applic
- Page 66 and 67: transmitted by the SVs will degrade
- Page 68 and 69: Table 3.5-7.Midi Almanac Parameters
- Page 70 and 71: MSBCDC = Clock Differential Correct
- Page 72 and 73: 3.5.4.5 Subframe 3, Page 6 - TextSu
- Page 74 and 75: 5. RESERVED66 IS-GPS-800A8 June 201
- Page 76 and 77: LSF - Leap Seconds FutureL1C - Comm
- Page 78 and 79: Table 6.2-1.Legendre Sequence (Octa
- Page 80 and 81: Table 6.2-2 LDPC Submatrix A for Su
- Page 82 and 83: Table 6.2-2 LDPC Submatrix A for Su
- Page 84 and 85: Table 6.2-2 LDPC Submatrix A for Su
- Page 86 and 87: Table 6.2-2 LDPC Submatrix A for Su
- Page 88 and 89: Table 6.2-2 LDPC Submatrix A for Su
- Page 90 and 91: Table 6.2-3. LDPC Submatrix B for S
- Page 92 and 93: Table 6.2-7. LDPC Submatrix T for s
- Page 94 and 95: Table 6.2-7. LDPC Submatrix T for s
- Page 96 and 97: Table 6.2-8. LDPC Submatrix A for s
- Page 98 and 99: Table 6.2-8. LDPC Submatrix A for s
- Page 100 and 101: Table 6.2-9. LDPC Submatrix B for S
- Page 102 and 103: Table 6.2-13. LDPC Submatrix T for
- Page 104 and 105: Table 6.2-16. Number of 1’s in LD
The user shall use the broadcast URA oc Index to derive URA ocb . The index is a two’s complement representation ofa signed integer in the range of +15 to –16 and has the following relationship to the clock-related user derivedURA ocb :URA oc IndexURA ocb (meters)15 6144.00 < URA ocb14 3072.00 < URA ocb 6144.0013 1536.00 < URA ocb 3072.0012 768.00 < URA ocb 1536.0011 384.00 < URA ocb 768.0010 192.00 < URA ocb 384.009 96.00 < URA ocb 192.008 48.00 < URA ocb 96.007 24.00 < URA ocb 48.006 13.65 < URA ocb 24.005 9.65 < URA ocb 13.654 6.85 < URA ocb 9.653 4.85 < URA ocb 6.852 3.40 < URA ocb 4.851 2.40 < URA ocb 3.400 1.70 < URA ocb 2.40-1 1.20 < URA ocb 1.70-2 0.85 < URA ocb 1.20-3 0.60 < URA ocb 0.85-4 0.43 < URA ocb 0.60-5 0.30 < URA ocb 0.43-6 0.21 < URA ocb 0.30-7 0.15 < URA ocb 0.21-8 0.11 < URA ocb 0.15-9 0.08 < URA ocb 0.11-10 0.06 < URA ocb 0.08-11 0.04 < URA ocb 0.06-12 0.03 < URA ocb 0.04-13 0.02 < URA ocb 0.03-14 0.01 < URA ocb 0.02-15 URA ocb 0.01-16 No accuracy prediction available—use at own riskThe user may use the upper bound value in the URA ocb range corresponding to the broadcast index, therebycalculating the maximum URA oc that is equal to or greater than the CS predicted URA oc , or the user may use thelower bound value in the range which will provide the minimum URA oc that is equal to or less than the CS predictedURA oc .48 <strong>IS</strong>-<strong>GPS</strong>-<strong>800A</strong>8 June 2010
Change language