Open greghutch opened 2 years ago
Do you remember by chance if this was spurious jumps for the time based jumps or the velocity based jumps?
I think both. The problem was with my time measurement -- and use of a date value that was generated server side (and likely wrong in the case of rpcs that were retired).
--greg
On Thu, Aug 29, 2024, 4:36 PM regeter @.***> wrote:
Do you remember by chance if this was spurious jumps for the time based jumps or the velocity based jumps?
— Reply to this email directly, view it on GitHub https://github.com/googlemaps/fleet-debugger/issues/74#issuecomment-2318928397, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDD3TPGL77NVN5H7W6CWEDZT6A3FAVCNFSM6AAAAABNLFXMKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJYHEZDQMZZG4 . You are receiving this because you authored the thread.Message ID: @.***>
The visualization is currently using the 'date' field from the log which corresponds to the time at which the server got the request.
For retried requests we should consider only using the 'rawLocationTime' field which appears to correspond to the time at which the location was recorded on device ... maybe.