Richard, or Martin, or anyone,
What's the latest on how GLONASS handles leap seconds? I remember years ago
receivers (or the SV itself) reset their timescale across the leap event --
because they use UTC(SU)+3h (Moscow local time) as their system time and not a
leap-less, timezone-free
I did not monitor what was going on with GLONASS at the time of the leap
second. But no NAGUs were issued indicating that any of the satellites had
difficulties around the time of the leap second. Also, I've not yet heard of
any issues from users. Roscosmos had this to say about the event (in