[LEAPSECS] leapseconds, converting between GPS time (week, second) and UTC

[Steve Allen]

On Tue 2019-01-15T12:41:27-0700 Rob Seaman hath writ:
> The bread-and-butter leap second discussions on this list seem
> irrelevant to simply meeting an engineering requirement to adhere to
> whatever standard. If POSIX, python, excel, whatever don't provide
> canned tools to convert seamlessly between GPS and UTC, or to handle
> format conversions from week:ms to sexagesimal, such tools must be
> implemented outside those languages/libraries. There are a vast number
> of other science-related data engineering details that POSIX (for
> example) also does not implement.

IEEE 1588 version 2 (PTP) makes it clear that the intended time
scale on the underlying hardware is TAI counted from some epoch.
It must be the case that vendors selling such hardware have chosen
solution strategies and written code to handle converting between
civil time and system time.
I would love to find pointers to such strategies and code.

--
Steve Allen                    <sla at ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m