[GitHub] [cordova-plugin-geolocation] tuckernuck edited a comment on issue #155: Timestamp of getCurrentPosition wrong? (iOS 12)

[GitBox <gi...@apache.org>]

tuckernuck edited a comment on issue #155:
URL: https://github.com/apache/cordova-plugin-geolocation/issues/155#issuecomment-810711508


   After reading all this with interest, I have a question:
   What exactly does the position.timestamp value represent?
   Is it local device time, or satellite/GNSS timestamp?
   
   I'm interested in using the GNSS timestamps for synchronization, but
   a) the values returned by postion.timestamp , via watchPosition() callback, 
   are often rounded to nearest second,although the spec says it's in milliseconds.
   
   b) the position.timestamp is often greater than the device Date() time, which seems to imply 
   that the phone clock is behind the satellite UTC time, which would be expected.
   
   c) I see no way of telling, in terms of local device UTC clock, the age of the position.timestamp 
   
   What I want is the GNSS timestamp which was part of the last location fix - and a device-clock timestamp indicating the time when the last fix was received, both precise to at least millisecond.
   
   By adding elapsed device time to the GNSS timestamp value, I should be able to infer the current 
   satellite time pretty accurately....
   
   How can this be accomplished?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org