tag:blogger.com,1999:blog-4722727826918942842.post4951846452562803847..comments2024-03-20T07:12:27.811+08:00Comments on dominoc925: Convert GPS week/seconds to local date time Google Gadgetdominoc925http://www.blogger.com/profile/09946927285702210239noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-4722727826918942842.post-45354751017379881832013-07-22T22:37:25.546+08:002013-07-22T22:37:25.546+08:00DST has been neutralized in the code.DST has been neutralized in the code.dominoc925https://www.blogger.com/profile/09946927285702210239noreply@blogger.comtag:blogger.com,1999:blog-4722727826918942842.post-1491746143530006992013-07-22T20:37:59.126+08:002013-07-22T20:37:59.126+08:00Hi Martin,
I have figured out the cause of the pro...Hi Martin,<br />I have figured out the cause of the problem. It's the daylight savings time in effect now that is affecting the date calculations. <br />Thx for letting me know.<br />rgdominoc925https://www.blogger.com/profile/09946927285702210239noreply@blogger.comtag:blogger.com,1999:blog-4722727826918942842.post-87339362361486628102013-07-22T20:21:45.823+08:002013-07-22T20:21:45.823+08:00But not on mine pc, I always got wrong value not o...But not on mine pc, I always got wrong value not only for 116,7201<br />-> 1982/03/28 01:00:00, but even for succesive. The values were shifted for 1 hour. But it didn't depend on local time zone. I choosed these 116,3601 and 116,7201 as I recognise they return me equal output values.<br />Well this might be a problem of google gadget implementation, which I don't understand how it martinhttps://www.blogger.com/profile/13246435969063623575noreply@blogger.comtag:blogger.com,1999:blog-4722727826918942842.post-71884194538846473292013-07-22T18:13:20.919+08:002013-07-22T18:13:20.919+08:00hi Martin
I'm sorry I cannot reproduce
116,72...hi Martin<br />I'm sorry I cannot reproduce <br />116,7201 -> 1982/03/28 01:00:00<br />The gadget is converting correctly to <br />116,7201 -> 1982/03/28 02:00:00<br />dominoc925https://www.blogger.com/profile/09946927285702210239noreply@blogger.comtag:blogger.com,1999:blog-4722727826918942842.post-21299007117896469242013-07-22T17:13:22.347+08:002013-07-22T17:13:22.347+08:00hi dominoc,
i think in the coversion algorithm is ...hi dominoc,<br />i think in the coversion algorithm is some kind of bug, at least in this example:<br />116,3601 -> 1982/03/28 01:00:00<br />116,7199 -> 1982/03/28 01:59:58<br />116,7201 -> 1982/03/28 01:00:00<br /><br />although in your android app, these gps times are coverted all right<br />martinhttps://www.blogger.com/profile/13246435969063623575noreply@blogger.comtag:blogger.com,1999:blog-4722727826918942842.post-23957644197033219012013-05-31T15:07:18.183+08:002013-05-31T15:07:18.183+08:00Bhargava, yesBhargava, yesdominoc925https://www.blogger.com/profile/09946927285702210239noreply@blogger.comtag:blogger.com,1999:blog-4722727826918942842.post-88186364989044792422013-05-31T12:41:44.168+08:002013-05-31T12:41:44.168+08:00Thanks. Will this page be updated if leap seconds ...Thanks. Will this page be updated if leap seconds are added in future?bhargavahttps://www.blogger.com/profile/16955546425765174010noreply@blogger.com