Understanding activity data #1389

Open
by KeironO opened 3 years ago · 1 comments
KeironO commented 3 years ago (Migrated from github.com)
Owner

Like many of you, I am annoyed at the vendor lock-in aspect of current health tracker platforms and am actively seeking to make that switch over to something more freedom respecting in the form of Gadgetbridge.

Part of this would be to facilitate seamless migration from Fitbit. As a result of GDPR regulation it is now possible for a user to export their data from the service in a form of JSON files. My goal is to write something that'll make that conversion, and provide the user a sqlite file in the format that Gadgetbridge accepts.

Unfortunately, I'm not able to understand what data is being tracked - and why it's being tracked in the way that it is.

It looks like all supported watches have their own tables, which could potentially be brought into a single standardised form. But before I even consider that, I need assistance in understanding the raw data in its entirety.

For the Amazefit Bip, we have the following columns:

  • TIMESTAMP: The time that the recording was taken in Unix time, rounded to the nearest minute.
  • DEVICE_ID: The unique identifier of the device in which the recording was taken, referencing table DEVICE.
  • USER_ID: The unique identifier of the user, referencing table USER.
  • RAW_INTENSITY: I don't know?
  • STEPS: The number of steps taken.
  • RAW_KIND: I don't know?
  • HEART_RATE: The BPM recorded by the device.

Any sort of help disseminating the data would be massively appreciated.

Thanks,

Keiron.

Like many of you, I am annoyed at the vendor lock-in aspect of current health tracker platforms and am actively seeking to make that switch over to something more freedom respecting in the form of Gadgetbridge. Part of this would be to facilitate seamless migration from Fitbit. As a result of GDPR regulation it is now possible for a user to export their data from the service in a form of JSON files. My goal is to write something that'll make that conversion, and provide the user a ```sqlite``` file in the format that Gadgetbridge accepts. Unfortunately, I'm not able to understand what data is being tracked - and why it's being tracked in the way that it is. It looks like all supported watches have their own tables, which could potentially be brought into a single standardised form. But before I even consider that, I need assistance in understanding the raw data in its entirety. For the Amazefit Bip, we have the following columns: - TIMESTAMP: The time that the recording was taken in Unix time, rounded to the nearest minute. - DEVICE_ID: The unique identifier of the device in which the recording was taken, referencing table DEVICE. - USER_ID: The unique identifier of the user, referencing table USER. - RAW_INTENSITY: I don't know? - STEPS: The number of steps taken. - RAW_KIND: I don't know? - HEART_RATE: The BPM recorded by the device. Any sort of help disseminating the data would be massively appreciated. Thanks, Keiron.
Rubemlrm commented 3 years ago (Migrated from github.com)
Owner

upvote on this issue, i'm trying to understand the table structure and have the same doubts of @KeironO . In my case we are trying to do a research work for a paper, and despite the contacts we tried to do with Huami , they don't inform us in a right way and don't give many options.

upvote on this issue, i'm trying to understand the table structure and have the same doubts of @KeironO . In my case we are trying to do a research work for a paper, and despite the contacts we tried to do with Huami , they don't inform us in a right way and don't give many options.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.