Skip to main content
Answer

Does anyone understand splits_metric vs splits_standard?

  • September 28, 2023
  • 1 reply
  • 66 views

jsumners
Forum|alt.badge.img+4

The docs for `DetailedActivity` claim that these fields are only for runs, but I seem them on rides as well. And what I am seeing makes no sense. I would assume the first split in each collection would be equivalent to one another, i.e. cover the same physical space on Earth. But I'm seeing a metric split like:

 

{ "distance": 1007.7, "elapsed_time": 171, "elevation_difference": 25.8, "moving_time": 170, "split": 1, "average_speed": 5.93, "average_grade_adjusted_speed": null, "average_heartrate": 138.79041916167665, "pace_zone": 0 }

 

And the "corresponding" standard split as:

 

{ "distance": 1610.2, "elapsed_time": 249, "elevation_difference": 29.6, "moving_time": 248, "split": 1, "average_speed": 6.49, "average_grade_adjusted_speed": null, "average_heartrate": 140.66122448979593, "pace_zone": 0 }

 

These numbers do not match up. Presumably the `elapsed_time` would be equal if the splits were covering the same stretch of Earth.

Also, anyone know if `average_grade_adjusted_speed` is a float? This property isn't mentioned at all in the documentation.

Best answer by Jan_Mantau

The so called "standard" split is for every mile. Grade adjusted speed is decimal like every other speed and only calculated for runs.

1 reply

Jan_Mantau
Superuser
Forum|alt.badge.img+27
  • Superuser
  • Answer
  • September 28, 2023

The so called "standard" split is for every mile. Grade adjusted speed is decimal like every other speed and only calculated for runs.