8000 timestamp api doesn't use date from gps. · Issue #133 · owntracks/recorder · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

timestamp api doesn't use date from gps. #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
matbor opened this issue Aug 16, 2016 · 5 comments
Closed

timestamp api doesn't use date from gps. #133

matbor opened this issue Aug 16, 2016 · 5 comments

Comments

@matbor
Copy link
matbor commented Aug 16, 2016

@jpmens as discussed and confirm by you.

Scenario - If I use a GPS offline for a few days/weeks and then upload ALL that data and at the time of uploading we have rolled into the next month, that information gets recorded in the current months .rec file with the time stamp in the first column of the day it is logged.

Now when using the recorder api and displaying data on a map via the api it doesn't use the date from the GPS data, it uses the date of when the data was recorder. (see screenshot below of the .rec file) which can be an issue if the gps data is from a different timeframe.

In the picture below you can see the date of when the data was uploaded and the data from the GPS was timestamp is for an older date, which is correct.

image 1

Matt.
@jpmens
Copy link
Member
jpmens commented Sep 12, 2016

What we should probably do is to use tst from the location report instead of now

@binarybucks
Copy link

Would also fix some order issues when the Android client has to requeue messages.

@jpmens
Copy link
Member
jpmens commented Sep 12, 2016

What will not change short-notice is that we append to the .rec files as the messages trickle in. So, messages arriving at 10, 11, 10 will be stored in that order, irrespective where we get the timestamp from.

@jpmens jpmens closed this as completed in bfdae39 Oct 30, 2016
jpmens added a commit that referenced this issue Nov 25, 2016
@jpmens
2016-11-25 version 0.6.9
e48b702 
- UPD: REC files now use tst from JSON payload as timestamp (#133)
- FIX: default file is /etc/default/ot-recorder
- FIX: add support for $OTR_BROWSERAPIKEY from environment (#156)
- UPD: packages now have API kill in them (#153)
@jpmens
Copy link
Member
jpmens commented Nov 26, 2016

@matbor this has now been packaged as 0.6.9 for Debian/Raspbian/CentOS and is available in our package repository. I would appreciate you testing it.

@matbor
Copy link
Author
matbor commented Dec 2, 2016

@jpmens thx, will see how I go on the weekend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jpmens @binarybucks @matbor
0