As important as UT1 is in astrology, look to South Asia/East Asia for a solution to this problem. It is also important in the determination of Jewish and Islamic prayer times.
Many existing apps that provide these services rely on UTC as a rough representation of UT1, but if UTC drifts from UT1 by more than 1 second, they will develop new ways to handle that difference. I expect there will be a proliferation of updated apps, some of which are tied to various national observatories, that will compete in the offering of some form of UT1 or DUT1 that could then be related to UTC on local systems. But given the importance of UT1 to many people, I will be curious to see if some nations set up their own time synchronization protocols to disseminate UT1. Between China and India, there's a large enough market for this. Cheers, Kevin ------------------ "Time is the measure of a wobbly world, and things slipping away." Rabanus Maurus, 9th century. Kevin K. Birth Department of Anthropology Queens College, CUNY Flushing, NY 11367 From: LEAPSECS <leapsecs-boun...@leapsecond.com> On Behalf Of Seaman, Robert Lewis - (rseaman) Sent: Sunday, November 20, 2022 10:55 AM To: Leap Second Discussion List <leapsecs@leapsecond.com> Subject: Re: [LEAPSECS] future access to solar time? Hi Tony, Getting the solar time currently means looking at your watch or the upper right-hand corner of the monitor. Would anybody else's summary of the notion of "easy access" include phrases like: "8.23 bits two's complement fixed point" or "NMEA sentences that contain anything like UT1 or DUT1 or delta-T"? I have been presuming tenth-second DUT1 values are slated for demolition with leap seconds. Can anybody confirm differently? I applaud the goal of ensuring understanding and usage of whatever infrastructure will exist. Few systems currently use DUT1. One of the issues is that many more will need to start. UT1 itself is only known retroactively. If your use of the word "stunt" wasn't a typo, it seems to me that NIST rather needs robust and easy-to-use infrastructure. I was never able to get reliable access to the UT1 NTP server, and generally, our group doesn't build reliance on third-party NTP pools into our operational systems. We should all welcome GNSS support for access to UT1 (or a coherent variation known in advance), but as you suggest this will require new infrastructure and standards. Perhaps I'm off the mark, but that most definitely doesn't imply anybody else has yet found the mark themselves. Rob Seaman, Robert Lewis - (rseaman) <rsea...@arizona.edu<mailto:rsea...@arizona.edu>> wrote: > The plan, rather, is to cease easy access to solar time. The resolution says the GCPM : encourages the BIPM to work with relevant organizations to identify the : need for updates in the different services that disseminate the value of : the difference (UT1-UTC) and to ensure the correct understanding and use : of the new maximum value. So I think your summary is a bit off the mark. I guess the ITU is going to revise TF.460 to allow larger values of DUT1 in time signals, and MSF etc. will accommodate the change too. (Do any of the national broadcast signals actually follow the ITU spec?) GPS L5 signals provide UT1 as an 8.23 bits two's complement fixed point difference from GPS time. This is enough to cope with the changes in the CGPM resolution. See IS-GPS-705 p. 87 at https://www.gps.gov/technical/icwg/<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gps.gov%2Ftechnical%2Ficwg%2F&data=05%7C01%7Ckevin.birth%40qc.cuny.edu%7C0032e12a552a4f38e1e908dacb0f94e9%7C6f60f0b35f064e099715989dba8cc7d8%7C0%7C0%7C638045565490819930%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UkI6Nr1O%2FtHAf4Hx3f32qFwzA58K6r%2B3TrK8MQL%2BCvc%3D&reserved=0> I have not been able to find any specs for NMEA sentences that contain anything like UT1 or DUT1 or delta-T, but I expect they will be created before too long, as more GPS receivers support L5 signals. And there are other sources of UT1 like NIST's stunt NTP servers. -- Tony Finch <d...@dotat.at<mailto:d...@dotat.at>> https://dotat.at/<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdotat.at%2F&data=05%7C01%7Ckevin.birth%40qc.cuny.edu%7C0032e12a552a4f38e1e908dacb0f94e9%7C6f60f0b35f064e099715989dba8cc7d8%7C0%7C0%7C638045565490819930%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rW6Z4%2F9joFauwpFzsMmi24ULV3S8HcfEKkSC%2FAffO98%3D&reserved=0>
_______________________________________________ LEAPSECS mailing list LEAPSECS@leapsecond.com https://pairlist6.pair.net/mailman/listinfo/leapsecs
