GPS Time ignores (does not deal with) "Leap Seconds." It is dealt with in the software translation from GPS time to UTC or local time. That is part of the reason there is a 16 second time difference between GPS Time and UTC/local time.
--- Graham == On Mon, Nov 9, 2015 at 4:15 PM, Chuck Harris <cfhar...@erols.com> wrote: > Seems to me that there is more to this than just > getting the displayed date wrong. > > It is true that the date will present wrongly, but > what about leap seconds? > > If the GPS week rolls over at 1024, how will the > GPS figure out which is the proper calendar date > to apply the leap second? > > -Chuck Harris > > Hal Murray wrote: > >> >> paulsw...@gmail.com said: >> >>> Hmmm then why do I have to figure it out at all? I don't care what the >>> date >>> says. >>> >> >> Only that the Austron locks and does its frequency offset compare. It >>> would >>> be great not to have to do this. >>> >> >> If you don't care about the date, then don't worry about it. >> >> It will do everything it did before. The only glitch is that the date >> will >> be off by 1024 weeks. >> >> >> If you can't get the right date into your GPS unit, you can work around >> the >> issue in software. Just add 1024 weeks to the date until the date is past >> the build time of your fixup software. >> >> That assumes you have some software to work with. That won't help if you >> are >> using a program that the vendor no longer supports. >> >> >> _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
