[teqc] problem with GNSS nav time()
lou at unavco.org
Tue Jun 5 13:44:45 MDT 2018
Completely unrelated. The notice about the GNSS_nav_time() would only be pertinent
when outputting Beidou RINEX nav, and then only if the Beidou navigation messages
rolled from one week to the next. I doubt you are creating those and reading them
in GAMIT/GLOBK. (The mentioned case for GNSS_nav_time() -- Beidou navigation messages
from Leica MDB at week rollover -- is one that I don't have data to test.)
If you do a `teqc -O.sum . <filename>` on one of the RINEX obs files being created
by teqc and used in GAMIT/GLOBK, what do you get back?
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
On 05-Jun-18 01:17 PM, Susilo, ST wrote:
> Dear All,
> I have some problem with leica MDB from GS14 when i convert using teqc.
> there was a notice:
> ! Notice ! Leica MDB 130: survey starts @ 2017 Jul 10 11:11:17.040 GPS time
> ! Notice ! GNSS_nav_time(): case of Leica Beidou nav record for Beidou nav message needs testing for validity during week rollover
> ! Notice ! Leica MDB 130: survey ends @ 2017 Jul 12 00:31:17.800 GPS time
> Actually the teqc still produce the rinex observation file. But the problem is when i process the rinex data using GAMIT/GLOBK most of the
> observation is rejected.
> Is there any relation with the teqc notice about GPS_nav_time():
> Anybody could explain about that?
> Thank you for your help
> Best regards,
> Center for Geodetic Control Network and Geodynamics
> Geospatial Information Agency
> former BAKOSURTANAL
> Jl. Raya Jakarta-Bogor Km. 46 Cibinong - Bogor, INDONESIA
> Phone/fax: +62-21-8758061
> email: susilo at big.go.id; susilosarimun at gmail.com
More information about the teqc