09-14-2020, 08:20 PM
Hi John,
That's because the virtual mileage we send to Fitbit is estimated from your cadence to best represent your workout, whereas the virtual mileage to Strava is needs match the actual map ground you've covered, which can be influenced by your difficulty setting, virtual hills, and speed limits that can make it less representative of your workout.
The precise measure we send to Fitbit is 4.31 meters per spin, which is the distance you'd travel with 2:1 bicycle gearing that represents an average touring speed on flat ground. Your virtual mileage in Explorer starts with a 3:1 gearing but hits an earlier speed limit, and can be affected from 50-200% by your choice of difficulty, and 50-150% by hills.
But it's looking more like we should send the same numbers to Fitbit, and rely more on the calories we send to Fitbit to represent your workout, considering that VZfit can now be played with devices that can measure speed and power in addition or instead of cadence.
That's because the virtual mileage we send to Fitbit is estimated from your cadence to best represent your workout, whereas the virtual mileage to Strava is needs match the actual map ground you've covered, which can be influenced by your difficulty setting, virtual hills, and speed limits that can make it less representative of your workout.
The precise measure we send to Fitbit is 4.31 meters per spin, which is the distance you'd travel with 2:1 bicycle gearing that represents an average touring speed on flat ground. Your virtual mileage in Explorer starts with a 3:1 gearing but hits an earlier speed limit, and can be affected from 50-200% by your choice of difficulty, and 50-150% by hills.
But it's looking more like we should send the same numbers to Fitbit, and rely more on the calories we send to Fitbit to represent your workout, considering that VZfit can now be played with devices that can measure speed and power in addition or instead of cadence.