Hi,
After importing Polar all data I noticed that power numbers are only from single side, so they end up as power/2 (approximately)
I can provide activity ID and the xml if this issue is not known.
Hi,
After importing Polar all data I noticed that power numbers are only from single side, so they end up as power/2 (approximately)
I can provide activity ID and the xml if this issue is not known.
Are you using single or double sided power meter?
Is it paired to your Polar device as ANT+ or as BLE?
ANT+ will normally always be correct. BLE depends on the BLE stack version of both power meter and device. Older BLE did not support double streams and had only one power stream.
If connection is BLE, most power meter apps have a setting to send ‘Unified left’, meaning that it sends double value if single sided, or sum if double sided.
My guess is that you have Polar app correcting for that, but the original file with wrong power data is forwarded to Intervals.
You can correct historical activities from the Action - Fix data menu. But you should correct the initial recording to your device to always get the correct info in the activity file.
What format is the Polar historical data? Is it JSON/XML/FIT/TCX…
If new activities are processed correctly, there might be a change/problem in the Polar archive import function.
More info lower in this thread
It’s JSON, originally in a zip file, the one from Polar link later provided to Intervals for upload.
All activities were imported, so no similar issue as you linked.
Sorry I’m new in this community, are you dev? If not, do devs review the bugs forum and investigate? Or it needs a lot of traction and other comments to bring their attention?
I looked into Polar api, new activities can be pulled in one of 3 formats: tcx, fit or gpx.
Full Polar data import zip file contains JSON files with schema which seem like proprietary Polar’s format. I guess Intervals must have implemented custom importer/converter for it and there might be a bug? …
I’m not a dev, I’m part of the moderator team. We try to sift through all the bug reports and help beginners getting started.
When something is confirmed as a bug by one of the moderators, we tag the (small) dev team. This is to avoid that the devs have to spent to much time on the forum questions. Dev team is 3 persons and not all full time.
I agree that there is likely a bug in the JSON importer, probably creeped in during the last overhaul. @david or @eva will have to take a look.