[teqc] helpful tip of week 1928

Lou Estey lou at unavco.org
Thu Dec 22 08:08:39 MST 2016

This week's tip: the '+meta' and '+mds' options

The '+meta' option is designed to return metadata about a GPS/GNSS file.  The output
from the command is almost identical for raw data files as for RINEX; the difference
is that when reading a RINEX observation file, you'll get a few extra lines at
the end of the output from the RINEX header that are related to making the RINEX file.

Here's an example of using '+meta' on a Septentrio PolaRx5 SBF file:

[70] teqc +quiet +meta prx5203t.16_.sbf
filename:                prx5203t.16_.sbf
file format:             Septentrio SBF
file size (bytes):       3428328
start date & time:       2016-07-21 19:16:27.000
final date & time:       2016-07-21 19:59:59.000
sample interval:         1.0000
possible missing epochs: 0
4-char station code:     prx5
station name:            prx5
station ID number:       prx5
antenna ID number:       -Unknown-
antenna type:            TRM59800.00     SCIT
antenna latitude (deg):      39.949488
antenna longitude (deg):   -105.194243
antenna elevation (m):       1730.167
antenna height (m):      0.0083
receiver ID number:      3012086
receiver type:           SEPT POLARX5
receiver firmware:       5.0.1

The '+mds' option stands for "metadata, short" and outputs the start and final
epoch times (truncated to the integer second), the file size in bytes, and the
file name all in one line for each file listed on the command line:

[71] teqc +quiet +mds prx5203t.16_.sbf
2016-07-21 19:16:27  2016-07-21 19:59:59   3428328  prx5203t.16_.sbf

And, of course, you could additionally include the '+doy' option with either of these
to have the dates represented in a year:day-of-year format:

[72] teqc +quiet +mds +doy prx5203t.16_.sbf
2016:203 19:16:27  2016:203 19:59:59   3428328  prx5203t.16_.sbf

The question has come up this month from several different directions of what teqc
outputs for the receiver ID number.  The answer is that it depends on the data format.
In some cases this is the serial number of the receiver's shell, in other cases
it is the actual board ID in the receiver, and in yet other cases you might get both.
Here are a few examples:

Septentrio Binary Format (SBF), ID should be the board ID:
[6077] teqc +quiet +meta prx5203t.16_.sbf | grep ^receiver
receiver ID number:      3012086
receiver type:           SEPT POLARX5
receiver firmware:       5.0.1

Javad JPS, ID should be the board ID:
[6088] teqc +quiet +meta all_signals.jps | grep ^receiver
receiver ID number:      03B6B089H04YL3K3HVKE
receiver type:           JAVAD TR_NT
receiver firmware:       3.5.0a1 May,12,2012

Topcon TPS, ID should be the board ID, serial number of shell also found:
[6092] teqc +quiet +meta N183-0407n.tps | grep ^receiver
receiver serial number:  1294-66666
receiver ID number:      W1QLP53MP76
receiver type:           TPS NET-G5
receiver firmware:       5.1 Mar,03,2016 b5

Trimble .dat or .tgd, ID is serial number of original (NetR9) shell:
[6098] teqc +quiet +meta 1607192000I.tgd | grep ^receiver
receiver ID number:      5606R50408
receiver type:           TRIMBLE
receiver firmware:       5.14

You might see the "receiver serial number" line from Javad JPS data sometimes, too.

And, as noted today by one teqc user, you may not get the full receiver and/or
antenna type being displayed.  In many manufacturer formats, the receiver and antenna
types are merely referred to by integer or other codes and one needs the manufacturer's
"codebook" to know how to map a particular code into the usual IGS or other ASCII type
name that one wants, for example, in a RINEX observation file header.  This is one
area where teqc will probably always lag what the manufacturer's software can do:
each manufacturer can easily keep their software up to data in this area and unless
they share that information with UNAVCO, teqc will have holes in the decoding.

Happy teqc-ing!


p.s. There won't be a tip of week for week 1929; I'll be on holiday.

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
week 1907: '+C2', '+L5', "+L6', '+L7', '+L8', and '+all' options -http://postal.unavco.org/pipermail/teqc/2016/002130.html
week 1908: no doppler shortcut; RINEX L2 -http://postal.unavco.org/pipermail/teqc/2016/002131.html
week 1909: using paths w/ file names -http://postal.unavco.org/pipermail/teqc/2016/002132.html
week 1910: the (un)importance of file names -http://postal.unavco.org/pipermail/teqc/2016/002133.html
week 1911: notices, warnings, and errors -http://postal.unavco.org/pipermail/teqc/2016/002134.html
week 1912: the '-max_rx_SVs' option -http://postal.unavco.org/pipermail/teqc/2016/002137.html
week 1913: the end of '++igs' and '+igs' -http://postal.unavco.org/pipermail/teqc/2016/002140.html
week 1914: splicing together RINEX files -http://postal.unavco.org/pipermail/teqc/2016/002144.html
week 1915: using '-O.int' and '-O.dec' -http://postal.unavco.org/pipermail/teqc/2016/002145.html
week 1916: '+doy' option -http://postal.unavco.org/pipermail/teqc/2016/002146.html
week 1917: '-tbin' and '-ast' options -http://postal.unavco.org/pipermail/teqc/2016/002152.html
week 1918: mp12 RMS before/after Oct 2013 -http://postal.unavco.org/pipermail/teqc/2016/002158.html
week 1919: the global windowing options -http://postal.unavco.org/pipermail/teqc/2016/002159.html
week 1920: '-M.dec' and '-N.dec' options -http://postal.unavco.org/pipermail/teqc/2016/002163.html
week 1921: combining time filtering options -http://postal.unavco.org/pipermail/teqc/2016/002176.html
week 1922: helping me (or someone else on the list) help you -http://postal.unavco.org/pipermail/teqc/2016/002187.html
week 1923: the "build" line -http://postal.unavco.org/pipermail/teqc/2016/002190.html
week 1924: the qc '-w[idth]' option -http://postal.unavco.org/pipermail/teqc/2016/002193.html
week 1925: qc with explicit time windowing -http://postal.unavco.org/pipermail/teqc/2016/002194.html
week 1926: the '+rx_state' option - http://postal.unavco.org/pipermail/teqc/2016/002200.html
week 1927: the '-O.sum' option - http://postal.unavco.org/pipermail/teqc/2016/002204.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postal.unavco.org/pipermail/teqc/attachments/20161222/0969c4fe/attachment.html>

More information about the teqc mailing list