[teqc] helpful tip of week 1975

Lou Estey lou at unavco.org
Wed Nov 15 07:32:14 MST 2017


This week's tip: the '+event' options

The '+event' options are for outputting any "events" that might be in the raw data
being read by teqc:

[2069] teqc +help | grep event
         +event[s] .          output any event info to stdout
         +event[s] ..         output any event info to stderr
         +event[s] name       output any event info to file 'name'
         ++event[s] name      append any event info to file 'name'
         -event[s]            don't output event info (default)

where the command options above follow the same form as the '+eds' ("external data string")
options discussed two weeks ago in http://postal.unavco.org/pipermail/teqc/2017/002317.html
and other other options for outputting special parameters. (Note: You should
probably be using the 2017 Sept 15 version of teqc to take advantage of all features
of the '+event' options in this tip, although most of the functionality exists
with the 2017 Sept 1 version.  The current '+event' options supersede the single
'+event' option in older teqc versions.)

What's an "event"?  It's something that is external to the receiver, often triggered
manually, that can be recorded as a time stamp by certain receivers.  (Though I
haven't seen this myself, I've heard that some photo systems do this, thereby
recording on the receiver when a photo was taken.)  And just as an external data
device creating external data strings is more likely to be used with a stationary
permanent station, an event is more likely to be used with a mobile receiver and
antenna.

Events are important enough for certain segments of the GPS/GNSS community that
recording them has been a part of the RINEX specification for a long time, e.g.
RINEX 2, April 1993: ftp://igs.org/pub/data/format/rinex2.txt

  | EPOCH/SAT   | - Epoch :                                       | 5I3,F11.7, |
  |     or      |     year (2 digits), month,day,hour,min,sec     |            |
  | EVENT FLAG  | - Epoch flag 0: OK                              |     I3,    |
  |             |              1: power failure between           |            |
  |             |                 previous and current epoch      |            |
  |             |             >1: Event flag                      |            |
...
  |             | If EVENT FLAG record (epoch flag > 1):          |            |
  |             |   - Event flag:                                 |            |
...
  |             |     5: external event (epoch is significant,    |            |
  |             |        same time frame as observation time tags)|            |

and they are still a part of RINEX 3.xx, e.g. see ftp://igs.org/pub/data/format/rinex303.pdf

The teqc '+event' suite of options allows you to:
    o read raw data during translation and, in addition to normal GNSS observations, include
      event observations in a resultant RINEX observation file, or
    o read raw data or a RINEX observation file with event observations and get a listing of
      those event observations with or without creating a RINEX observation file
... but you must use one of the '+event' options to have either of these happen.

Note: If you are reading one or more RINEX observation files and creating RINEX obs, then
any event observations will be passed along to the resultant RINEX obs without the need for
including a '+event' option.

If you only create a RINEX obs file with events, these events will be recorded as RINEX "event = 5"
occurrences, as per the RINEX specification above.  The raw data formats (and records/messages)
that teqc can read where events might occur are:

    o Javad JPS [XA], [XB], and some [>>] messages
    o Leica LB2 0x05 and 0x05; MDB 0x11 (17) and 0x71 (113)
    o Navcom binary recod 0xb4 (180)
    o Trimble .dat/.tgd record 19
    o Topcon TPS [XA], [XB], and some [>>] messages
    o u-blox UBX TIM-TP, TIM-TM, and TIM-TM2 records

Note: Additional "event description" information from Leica MDB 0x10 (16) and 0x74 (116),
which do not have time stamps, will also be output if found and if the output is not to
a RINEX obs file.

What do these event observations look like?  Here we're translating a Trimble .dat
file into RINEX obs and showing an example of what the event information might look like
when embedded within the RINEX obs file (as per the RINEX specification above):

[6676] teqc +event . 07460930.dat
...
  07  4  3 17 39 58.6856750  5  1
External Event # 1                                          COMMENT
...
  07  4  3 17 40  3.7095729  5  1
External Event # 2                                          COMMENT
...

or here finding those same events and writing them out to a specified file:
[6677] teqc +event event.log 07460930.dat > tmp.obs
[6678] more event.log
2007 Apr  3 17:39:58.686  External Event # 1
2007 Apr  3 17:40:03.710  External Event # 2
...

The events in Leica MDB 0x11 (record 17) and 0x71 (record 113) can have quite
a bit of extra information per event, e.g.

[6683] teqc +event event.log ORB12950.mdb > tmp.obs
[6683] more event.log
2006 Oct 22 18:48:33.005  External Event # 1
2006 Oct 22 18:48:33.005  Pnt id: ORB110151848330a   port: 1
2006 Oct 22 18:48:33.005  Pos (ddm): 43.575660640 -121.708548154 2449.1201
2006 Oct 22 18:48:33.005  Vel (LatLonH, m/s): -0.4083 74.1361 -0.2837
2006 Oct 22 18:48:33.005  Ant height: 1.2410 VERTICAL
2006 Oct 22 18:48:33.005  HDOP= 0.8 VDOP= 1.2 TDOP= 0.7
2006 Oct 22 18:48:33.005  SV available= 10  used= 10
2006 Oct 22 18:48:40.944  External Event # 2
2006 Oct 22 18:48:40.944  Pnt id: ORB110221848409a   port: 1
2006 Oct 22 18:48:40.944  Pos (ddm): 43.575633858 -121.701204203 2447.9191
2006 Oct 22 18:48:40.944  Vel (LatLonH, m/s): -0.4265 75.1705 0.1769
2006 Oct 22 18:48:40.944  Ant height: 1.2410 VERTICAL
2006 Oct 22 18:48:40.944  HDOP= 0.8 VDOP= 1.2 TDOP= 0.7
2006 Oct 22 18:48:40.944  SV available= 10  used= 10
...

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

"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', '+all' options - http://postal.unavco.org/pipermail/teqc/2016/002130.html
week 1908: getting RINEX doppler and 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
week 1928: the '+meta' and '+mds' options - http://postal.unavco.org/pipermail/teqc/2016/002206.html
week 1930: more on '-O.sum' - http://postal.unavco.org/pipermail/teqc/2017/002207.html
week 1931: the '-O.s[ystem]' option - http://postal.unavco.org/pipermail/teqc/2017/002208.html
week 1932: leap seconds - http://postal.unavco.org/pipermail/teqc/2017/002215.html
week 1936: what you can (and shouldn't) do in a RINEX obs file - http://postal.unavco.org/pipermail/teqc/2017/002229.html
week 1938: the '+psp' option - http://postal.unavco.org/pipermail/teqc/2017/002231.html
week 1939: the '+diag' option - http://postal.unavco.org/pipermail/teqc/2017/002235.html
week 1951: '-n_<system>' and SV filtering options - http://postal.unavco.org/pipermail/teqc/2017/002277.html
week 1953: more with '+diag' option - http://postal.unavco.org/pipermail/teqc/2017/002287.html
week 1954: using '+diag' output to split raw files - http://postal.unavco.org/pipermail/teqc/2017/002290.html
week 1955: current qc notation - http://postal.unavco.org/pipermail/teqc/2017/002302.html
week 1956: the '+qcq' option - http://postal.unavco.org/pipermail/teqc/2017/002304.html
week 1957: using Trimble formats - http://postal.unavco.org/pipermail/teqc/2017/002305.html
week 1958: ToC != ToE messages - http://postal.unavco.org/pipermail/teqc/2017/002310.html
week 1959: receivers vs. formats - http://postal.unavco.org/pipermail/teqc/2017/002311.html
week 1960: when the '-week' option is very wrong to use - https://postal.unavco.org/pipermail/teqc/2017/002314.html
week 1961: "less" is usually best - https://postal.unavco.org/pipermail/teqc/2017/002315.html
week 1962: using GPS L2C with teqc - https://postal.unavco.org/pipermail/teqc/2017/002316.html
week 1964: the '+eds' options - https://postal.unavco.org/pipermail/teqc/2017/002317.html
week 1965: handling RINEX comment lines - https://postal.unavco.org/pipermail/teqc/2017/002324.html
week 1966: the '+dUTC_p' options - https://postal.unavco.org/pipermail/teqc/2017/002331.html
week 1967: the strange position from '+meta' - https://postal.unavco.org/pipermail/teqc/2017/002355.html
week 1972: what shows up as metadata in RINEX headers - https://postal.unavco.org/pipermail/teqc/2017/002362.html
week 1973: GPS L2C navigation messages - https://postal.unavco.org/pipermail/teqc/2017/002363.html
week 1974: the '+ion_p' options - https://postal.unavco.org/pipermail/teqc/2017/002370.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postal.unavco.org/pipermail/teqc/attachments/20171115/e6ad8b08/attachment-0001.html>


More information about the teqc mailing list