-
Notifications
You must be signed in to change notification settings - Fork 26
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.
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
no points found #11
Comments
Yes, I had to rewrite the cycle that creates the timestampMs list. Timestamp is no longer in milliseconds in the json file so it has to be converted |
@delagra care sharing your updated code? |
Hello, I would be great if you can share that block of code with the rest of us. I had already found that this was the issue, but as I'm not familiar with Python, I didn't manage to get it working. Thanks |
@delagra Would greatly appreciate some insight on how to re-write this... I tried removing milliseconds; no dice. I'm hesitant to start combing through the JSON cause it's so big LOL... thanks in advance if you don't mind sharing this :) |
The file definition for Records.json seems to be in question. https://locationhistoryformat.com/reference/records/#/$defs/locationRecord/ |
Hello, after some tinkering with Python for something else, I give this a try and managed to get it working : #13 . Enjoy ! |
Google renamed the json file to Records.json.
Also the timestamp key is renamed. Therefore the total number of points keeps returning zero.
The text was updated successfully, but these errors were encountered: