[teqc] helpful tip of week 1907

Lou Estey lou at unavco.org
Wed Jul 27 07:34:20 MDT 2016


This week's tip: the '+C2', '+L5', "+L6', '+L7', '+L8', and '+all' options

Some of you are using these options and are getting the general idea: they are
merely shortcuts for adding specific observables when reading raw data, usually
for translation, but can be used in other instances (e.g. with the '-O.sum .'
option).  The alternative to using these options and adding observables is to
list all the observables you want with the '-O.obs' option.

Background: The default behaviour of teqc for reading raw data formats for
translation (and other uses) automatically establishes observables for the
legacy GPS, GLONASS, and SBAS signals:

GPS and SBAS L1C/A, or GLONASS G1SA: RINEX L1 C1 S1 observables
GPS L1P(Y), or GLONASS G1HA: RINEX L1 P1 S1 observables
GPS L2P(Y), or GLONASS G2HA: RINEX L2 P2 S2 observables

(Exactly which observable list you get is tuned, in most cases, to the specific
format that is being read.)

Later, when Galileo came around, you got RINEX L1, C1, and S1 for the Galileo
E2-L1-E1 signal, for free.

The options '+C2', '+L5', "+L6', '+L7', and '+L8' are a shortcut for adding,
if you want or need them, extra phase, pseudorange, and SNR observables in
standard RINEX 2.11:

+C2: include RINEX C2 observable for GPS L2C, or GLONASS G2SA
+L5: include RINEX L5, C5, and S5 observables for GPS and SBAS L5, or Galileo E5a
+L6: include RINEX L6, C6, and S6 observables for Galileo E6
+L7: include RINEX L7, C7, and S7 observables for Galileo E5b
+L8: include RINEX L8, C8, and S8 observables for Galileo E5a+b

And if you want to use teqc's "extended" 2.11 for other constellations (e.g.
Beidou, QZSS) or other signals (e.g. GLONASS G3 or GPS L1C which will be on
Block III), see http://postal.unavco.org/pipermail/teqc/2013/001492.html

The option '+all' is a further shorthand for '+C2 +L5 +L6 +L7 +L8'.

You should only consider using these when reading raw data.  If you are reading
a RINEX observation file, teqc gets the necessary observable list from the
RINEX obs file header.

So what about Doppler observables with the '+C2', '+L5', "+L6', '+L7', '+L8', or '+all'
options?  The Doppler observables are not included.  More about that next week.

There is a small complication revolving around '+C2', or including the C2 observable
with the '-O.obs' option, and whether or not the '+L2C_L2' or '-L2C_L2' options
work as you expect; see 2009 Aug 3 entry in
http://www.unavco.org/software/data-processing/teqc/log/log.html

     - using '+C2' or '-O.obs' with C2: '+L2C_L2' and '-L2C_L2' are ignored; the
       L2 (and S2, D2) are based on L2(L2C) if present, based on L2(P2) otherwise

     - using '-C2' and '-O.obs' w/o C2: '+L2C_L2' or '-L2C_L2' takes effect, allowing
       pure L2(L2C) or pure L2(P2), respectively; default would continue to be -L2C_L2,
       i.e. RINEX L2 (and S2, D2) based on L2(P2)

One other little detail: Suppose you want to explicitly include or exclude only
Beidou PRN 2.  You can't use '+C2' or '-C2' because these options mean include or
exclude the L2C or G2SA pseudorange.  So if you ever need to include or exclude only
Beidou PRN 2, use '+C02' or '-C02', respectively.  (All the SV filters by SV id
work with 1 or 2 digits of the id.)

Happy teqc-ing!

cheers,
--lou

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Louis H. Estey, Ph.D.              office:  [+001] 303-381-7456
UNAVCO, 6350 Nautilus Drive           FAX:  [+001] 303-381-7451
Boulder, CO  80301-5554            e-mail:  lou  unavco.org
      WWW:  http://www.unavco.org   http://jules.unavco.org

"If the universe is the answer, what is the question?"
                                                -- Leon Lederman
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Past helpful tips:

week 1894: using teqc config files - http://postal.unavco.org/pipermail/teqc/2016/002067.html
week 1895: qc of high-rate data - http://postal.unavco.org/pipermail/teqc/2016/002071.html
week 1896: UNIX/Linux shells for Windows - http://postal.unavco.org/pipermail/teqc/2016/002072.html
week 1897: '-' vs. '+' teqc options - http://postal.unavco.org/pipermail/teqc/2016/002076.html
week 1898: auto-identification of formats - http://postal.unavco.org/pipermail/teqc/2016/002092.html
week 1899: auto-identification vs. format flags - http://postal.unavco.org/pipermail/teqc/2016/002096.html
week 1900: square brackets in options - http://postal.unavco.org/pipermail/teqc/2016/002105.html
week 1901: using option '+mds' - http://postal.unavco.org/pipermail/teqc/2016/002108.html
week 1902: qc results w/ problematic nav messages - http://postal.unavco.org/pipermail/teqc/2016/002113.html
week 1903: '-no_orb[it]' and '-no_pos[ition]' options - http://postal.unavco.org/pipermail/teqc/2016/002115.html
week 1904: '-week' option - http://postal.unavco.org/pipermail/teqc/2016/002117.html
week 1905: using '+bcf' for XYZ/geodetic conversion - http://postal.unavco.org/pipermail/teqc/2016/002126.html
week 1906: the '+v[erify]' option - http://postal.unavco.org/pipermail/teqc/2016/002128.html




More information about the teqc mailing list