Impo Time System

ITS Clock

Why ITS?

• Precision — 1 nanosecond resolution, based on UT1 with DUT1 spline interpolation from IERS data
• Convenient day scale — 1 ITS day = 86400 SI seconds, just like the civil day
• Uniform months and years — every month is 21 days, every year is 147 days (7 months). No 28/29/30/31 chaos
• No leap seconds — UT1-based means no UTC leap second disruptions. DUT1 is just a correction, not a jump
• Easy conversion from system UTC — just subtract the epoch and add DUT1. Your OS clock is the input
• Full tool set — its (reference), itstime (Unix-style), its-offset (offset generator), itsd (auto-update daemon)
• No daylight saving time — ITS is DST-free. Always stable
• Infinite technical lifespan — 64-bit integer gives ~292 years of nanosecond range. GMP mode goes arbitrary-precision
• No timezones — one time for everyone. The clock reads the same worldwide

API

GET /api/its_nsecs returns the current ITS time as nanoseconds since epoch:

{"nsecs":"1483762602217913"}

The value is an integer string (arbitrary-precision). How to parse:

1 ITS day  = 86400000000000 ns
1 ITS year = 147 days
1 ITS month = 21 days

days       = nsecs / 86400000000000
rem        = nsecs % 86400000000000
seconds    = rem / 1e9
HH:MM:SS   = format from seconds

years      = days / 147
r          = days % 147
months     = r / 21
days_rem   = r % 21