[teqc] helpful tip of week 1916

Lou Estey lou at unavco.org
Wed Sep 28 11:08:28 MDT 2016


This week's tip: the '+doy' option  (that's lowercase-O, not lowercase-A)

Using '+doy' (= "use 'day-of-year' notation for dates") is pretty straightforward.
Use this when you want to see year:day-of-year notation for dates -- and note using
'+doy' will _not_ effect how the date is written to any RINEX output.  This date
representation is also known as the "ordinal date"; see e.g.:
https://en.wikipedia.org/wiki/Ordinal_date

'+doy" is useful with other options:
- when also using '+mds' or '+meta' to see metadata, e.g.:

[10850] teqc +doy -ash s +mds gg24c-sl7-dsh-011098.dat
1998:274 00:00:15  1998:274 01:59:00   1000000  gg24c-sl7-dsh-011098.dat

or

[10851] teqc +doy -ash s +meta gg24c-sl7-dsh-011098.dat
filename:                gg24c-sl7-dsh-011098.dat
file format:             Ashtech MBEN/DBEN
file size (bytes):       1000000
start date & time:       1998:274 00:00:15.000
final date & time:       1998:274 01:59:00.000
sample interval:         5.0000
possible missing epochs: 0
4-char station code:     ????
station name:            -Unknown-
station ID number:
antenna ID number:       -Unknown-
antenna type:            -Unknown-
antenna latitude (deg):      42.459415
antenna longitude (deg):    -71.265199
antenna elevation (m):         58.813
antenna height (m):      0.0000
receiver ID number:      -Unknown-
receiver type:           ASHTECH
receiver firmware:       -Unknown-

- when doing '+qc' or '+qcq'

- other situations like the occasional notice, warning, or error message that might
have a date in it.

You'll notice that teqc's output using '+doy' does _not_ currently comply with ISO 8601,
the difference being that the '+doy' formatting uses a colon, ':', to separate
the year and day-of-year.  Why?  To make the '+doy' representation quite distinct
from the normal Gregorian date representation which also uses a hyphen, '-',
to separate the year, month, and day of month, e.g.

[10854] teqc -ash s +mds gg24c-sl7-dsh-011098.dat
1998-10-01 00:00:15  1998-10-01 01:59:00   1000000  gg24c-sl7-dsh-011098.dat

... the distinction being good for humans and good for any code you might have
that parses these results.

Happy teqc-ing!

cheers,
--lou

p.s. For anyone interested, UNAVCO (meaning me) maintains a calendar listing in
our Glossary: http://www.unavco.org/help/glossary/glossary.html#calendar where
for each year you will find the day-of-year for Sunday in the left column for
each month -- just count over to get to the day of the week that you want; the
GPS week for each week is in the right column.

p.p.s. I suppose there could also be '+gps', '+gal', and '+bei' options added
to teqc to represent the date in the GPS, Galileo, or Beidou week plus day-of-week ...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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




More information about the teqc mailing list