Skip to main content
Solved

ActivityById - Activity Splits - for running

  • April 24, 2024
  • 1 reply
  • 11 views

Forum|alt.badge.img+2

 

If we look at the distance of each split, the splits are not exactly at 1 km mark.

would like to know the difficulty (in terms of both hardware or technical related) in dividing the splits by exactly 1km each. 

Best answer by ActivityFix

The reason they aren't at exactly the 1km mark is that it is based on the recorded data. Most devices record 1 data point per second. Unless your speed is constant and evenly divides into 1000m, you likely won't end up with a data point at exactly the 1km (or multiples of it) mark. 

In hardware it isn't really possible to fix without a high sampling rate, which would likely reduce battery life and may still not exactly line up with a 1km split still, especially for higher speed activities where the distance between each point is larger.

In software you can make an estimate based on the average speed over that split, but it probably won't be perfect. Alternatively you can pull the full data stream (using https://developers.strava.com/docs/reference/#api-Streams-getActivityStreams) and calculate the splits yourself, again estimating/interpolating the intermediate distances. You'd get a better estimate since you would have the speed at each data point.

View original
Did this topic help you find an answer to your question?

1 reply

ActivityFix
Superuser
Forum|alt.badge.img+24
  • Superuser
  • 246 replies
  • Answer
  • April 24, 2024

The reason they aren't at exactly the 1km mark is that it is based on the recorded data. Most devices record 1 data point per second. Unless your speed is constant and evenly divides into 1000m, you likely won't end up with a data point at exactly the 1km (or multiples of it) mark. 

In hardware it isn't really possible to fix without a high sampling rate, which would likely reduce battery life and may still not exactly line up with a 1km split still, especially for higher speed activities where the distance between each point is larger.

In software you can make an estimate based on the average speed over that split, but it probably won't be perfect. Alternatively you can pull the full data stream (using https://developers.strava.com/docs/reference/#api-Streams-getActivityStreams) and calculate the splits yourself, again estimating/interpolating the intermediate distances. You'd get a better estimate since you would have the speed at each data point.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept, you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings