[teqc] translation of Ashtech R files one week off

Lou Estey lou at unavco.org
Fri Jan 21 11:04:09 MST 2005


I wrote:

> I'll look to see if there is a possible fix for this case
> so that file Rhouea04.340 would translate (or extract the
> metadata) correctly without needing '-week 1300', but given the
> past record of this type of problem, I'm not too hopeful.

Dear Olivier,

No fix is possible for this file.  You can see what happens
by running (sh, ksh, etc.):

[816] teqc +diag Rhouea04.340 2>&1 | more

The file has an initial record 23; this is a data file, but
it has no GPS week information from the file yet.  Teqc outputs
the translation basing the GPS week on a total guess (using
the OS's system time).

Next are several record 3 (= navigation information), which
includes the GPS week of the nav message.  Upon reading the
first one record 3, teqc detects the GPS week problem
and reports (to stderr):

! Warning ! wrong GPS week of 1299? GPS NAV ToW minus observation epoch = 168 hours
         (try using "-week 1300" or "-week 1301" option)

You see the same message when translating without -week:

[817] teqc Rhouea04.340 > /dev/null
! Notice ! GPS week initially set= 1299
! Warning ! wrong GPS week of 1299? GPS NAV ToW minus observation epoch = 168 hours
         (try using "-week 1300" or "-week 1301" option)
! Notice ! GPS week in Ashtech SNV record = 1300; (default) GPS week = 1299
! Error ! 2004 Nov 28 00:17:00.000: poss. incr. of sampling int. OR data gap of 60.000 seconds (min. dt found= 30.000 s)
! Error ! 2004 Nov 28 08:00:30.000: poss. incr. of sampling int. OR data gap of 60.000 seconds (min. dt found= 30.000 s)

So even here teqc is giving you fair warning that something
is amiss with the GPS week, and its first guess, 1300, is
correct.  So, yes, the default translation is one week off
for this file but teqc gives you plenty of chance to see and
fix the problem.

--lou






More information about the teqc mailing list