Skip to main content
added 3 characters in body
Source Link
eckes
  • 1.5k
  • 10
  • 18

I think „UTC Timestamp“ is not the correct term since UTC is defined in terms of Leap Seconds.

What is a more usual term here is TAI time or GPS time (as the Timestamps used for example in GPS, both use no leap seconds and based on coordinated atomic clocksUTC is defined in terms of TAI -19s) have no(GPS is basically TAI starting at a different offset, so it has 19s less leap second logictime).

The difference of UTC time to TAI time at any given point cannot be algorithmically calculated (unless you have both stamps, then you just need to Substractsubtract them).

To Instead, tTo get the official offset at any point in the past and some time in the Future you need to lookup the official tables, this is the authoritative source: http://hpiers.obspm.fr/eop-pc/index.php

I think some timezone Information files/libraries also have that information, but have not seen any support in commercial databases.

I think „UTC Timestamp“ is not the correct term since UTC is defined in terms of Leap Seconds.

What is a more usual term here is TAI time or GPS time (as the Timestamps used for example in GPS and based on coordinated atomic clocks -19s) have no leap second logic).

The difference of UTC time to TAI time at any given point cannot be algorithmically calculated (unless you have both stamps, then you just need to Substract them).

To get the official offset at any point in the past and some time in the Future you need to lookup the official tables, this is the authoritative source: http://hpiers.obspm.fr/eop-pc/index.php

I think some timezone Information files/libraries also have that information, but have not seen any support in commercial databases.

I think „UTC Timestamp“ is not the correct term since UTC is defined in terms of Leap Seconds.

What is a more usual term here is TAI time or GPS time, both use no leap seconds and UTC is defined in terms of TAI (GPS is basically TAI starting at a different offset, so it has 19s less leap time).

The difference of UTC time to TAI time cannot be calculated (unless you have both stamps, then you just need to subtract them). Instead, tTo get the official offset at any point in the past and some time in the Future you need to lookup the official tables, this is the authoritative source: http://hpiers.obspm.fr/eop-pc/index.php

I think some timezone Information files/libraries also have that information, but have not seen any support in commercial databases.

added 59 characters in body
Source Link
eckes
  • 1.5k
  • 10
  • 18

I think „UTC Timestamp“ is not the correct term since UTC is defined in terms of Leap Seconds.

What is a more usual term here is TAI time or GPS time (as the Timestamps used for example in GPS and based on coordinated atomic clocks -19s) have no leap second logic).

The difference of UTC time to TAI time at any given point cannot be algorithmically calculated (unless you have both stamps, then you just need to Substract them).

To get the official offset at any point in the past and some time in the Future you need to lookup the official tables, this is the authoritative source: http://hpiers.obspm.fr/eop-pc/index.php

I think some timezone Information databasesfiles/libraries also have that information, but have not seen any support in commercial databases.

I think „UTC Timestamp“ is not the correct term since UTC is defined in terms of Leap Seconds.

What is a more usual term here is TAI time or GPS time (as the Timestamps used for example in GPS and based on coordinated atomic clocks -19s) have no leap second logic).

The difference of UTC time to TAI time at any given point cannot be algorithmically calculated (unless you have both stamps, then you just need to Substract them).

To get the official offset at any point in the past and some time in the Future you need to lookup the official tables, this is the authoritative source: http://hpiers.obspm.fr/eop-pc/index.php

I think some timezone Information databases also have that information.

I think „UTC Timestamp“ is not the correct term since UTC is defined in terms of Leap Seconds.

What is a more usual term here is TAI time or GPS time (as the Timestamps used for example in GPS and based on coordinated atomic clocks -19s) have no leap second logic).

The difference of UTC time to TAI time at any given point cannot be algorithmically calculated (unless you have both stamps, then you just need to Substract them).

To get the official offset at any point in the past and some time in the Future you need to lookup the official tables, this is the authoritative source: http://hpiers.obspm.fr/eop-pc/index.php

I think some timezone Information files/libraries also have that information, but have not seen any support in commercial databases.

Source Link
eckes
  • 1.5k
  • 10
  • 18

I think „UTC Timestamp“ is not the correct term since UTC is defined in terms of Leap Seconds.

What is a more usual term here is TAI time or GPS time (as the Timestamps used for example in GPS and based on coordinated atomic clocks -19s) have no leap second logic).

The difference of UTC time to TAI time at any given point cannot be algorithmically calculated (unless you have both stamps, then you just need to Substract them).

To get the official offset at any point in the past and some time in the Future you need to lookup the official tables, this is the authoritative source: http://hpiers.obspm.fr/eop-pc/index.php

I think some timezone Information databases also have that information.