Delivered-To: igsstation@igscb.jpl.nasa.gov Content-class: urn:content-classes:message Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: [IGSSTATION-805]: 1 Sec Epoch Error for GOPE and THU2 Date: Fri, 3 Feb 2006 14:29:20 +0100 Message-ID: <371BE82A03680E4087F343D5C9883D8D178E54@FS029EXCH.bkg> Thread-Topic: 1 Sec Epoch Error for GOPE and THU2 thread-index: AcYoxdbCnkVyjoH8RcW4h5cugq+oCA== From: "Habrich, Heinz" To: "IGSSTATION_Mail (E-Mail)" Cc: , , "Jakub Kostelecky (E-Mail)" Sender: owner-igsstation Precedence: bulk ****************************************************************************** IGS Station Mail 03 Feb 05:29:32 PST 2006 Message Number 805 ****************************************************************************** Author: Heinz Habrich, Peter Neumaier The GLONASS observations from the sites GOPE and THU2 show obviously wrong observation epochs in the RINEX files since January 1, 2006. This inconsistency is caused by the leap second for UTC as was introduced at that day. We assume that the two mentioned stations don't handle the new leap second correctly and ask the station operators the check the receiver settings. A code single point positioning results in an error of about 300 m, as we found in our analysis. The RINEX header show 13 sec for GPS-UTC difference, but now it should be 14 sec. Furthermore, we detected the wrong 13 sec for GPS-UTC in the RINEX header for DARR and STR2, but these 2 stations could be analyzed without problems.