01-08-2021 07:36
01-08-2021 07:36
My Fitbit Versa measures the barometer data correctly, but through the web API I get only zeros as an intraday elevation and floors data
Answered! Go to the Best Answer.
01-15-2021 01:40
01-15-2021 01:40
I think I have a clue.
Fitbit's algorithms calculate elevation and floors as natural numbers, they are positive for both ascending and descending. You can see it perfectly in the collage of three charts: from Fitbit Fit, Fitbit Web API, and Google Fit.
Or am I wrong? Where can I find it in the docs?
01-11-2021 14:52
01-11-2021 14:52
Hi @terraincure
I test elevation and floors using the Web API Explorer against my own data and I see intraday elevation and floors. Would you please try this too?
https://dev.fitbit.com/build/reference/web-api/explore/
Best,
Gordon
01-12-2021 00:35 - edited 01-12-2021 00:52
01-12-2021 00:35 - edited 01-12-2021 00:52
01-12-2021 13:55
01-12-2021 13:55
Hi @terraincure
Would you please private message me your Fitbit user ID so I may look at the data that is uploaded to our server?
Thanks!
Gordon
01-13-2021 00:59 - edited 01-13-2021 01:25
01-13-2021 00:59 - edited 01-13-2021 01:25
01-14-2021 13:26
01-14-2021 13:26
Hi @terraincure
Thank you for providing me your user id. Based on the example you provided in this thread, I looked at your data on 2021-01-09. I see you have elevation changes that occur in the 4pm hour (16:00) not 3pm (15:00). You can see this by logging into your Fitbit.com account, click Log -> Activities -> and select floors. I tested all the intraday endpoints using the elevation resource and detail-level = 1min during that timeframe and see elevation data being returned.
Would you please double check this on your end?
01-15-2021 00:57
01-15-2021 00:57
Hello, Gordon,
Yes, I already have the elevation data on 2021-01-09 in the 16:00, please see above. I am sure that this data does not reflect reality.
For better understanding I picked another route example with the height differences of more than 30m, please see the Google Fit screenshot above.
Here the screenshot from Google Earth with the elevation profile of this route.
Here's the Fitbit Web API showing the same really strange peaks.
I hope you will be able to find the right answer
Best,
Oleksandr Tugayev
01-15-2021 01:40
01-15-2021 01:40
I think I have a clue.
Fitbit's algorithms calculate elevation and floors as natural numbers, they are positive for both ascending and descending. You can see it perfectly in the collage of three charts: from Fitbit Fit, Fitbit Web API, and Google Fit.
Or am I wrong? Where can I find it in the docs?