Completada

Display distances to two decimal places

Strava - please display distance measurements to 0.01 of a km/mile, instead of the current limitation of one tenth.

The existing granularity of just one tenth of a mile makes it very difficult to meaningfully compare activities, especially for runners where it takes some time to cover that distance.  I'm sure cyclists would also appreciate the change.

This limitation has been identified in a number of threads as the reason people use other apps so should be of concern to Strava.

102

Comentarios

167 comentarios
  • +1 to this. I learned from someone on reddit to always make sure my garmin says at least 0.03 past my goal distance or else the distance strava shows is going to be short. Like others said, obviously the data is stored to the hundredths place. We see that in various stats and when we export data. Why can't that also be applied to an individual activity?

    4
    Acciones de comentarios Permalink
  • So Strava is telling us that GPS can't tell when I have moved more than 50 feet? That's simply not true.

    As for the person who asked how much of a code change this is - It's a change in a single line of code. Actually, it should be _one character_ in a single line of code. The effort is trivial!

    Strava simply doesn't want to make this change which means to me, one of two things. One possibility is that the display page is completely hand coded, which makes the code change non-trivial. But if this is the case, then Strava has done a lot of things wrong and I don't want their app. The other possibility is that Strava really wants us to upgrade. Ah, there we go. Make the free app irksome (not wrong, just irksome) so that the people will upgrade to the money-making version. But if all Starva can think about is how to inconvenience their users in ways to get them to cough up for the pay version, then I guess I don't want their app in that case either.

    2
    Acciones de comentarios Permalink
  • Umm Bruce, I am a premium user. We don't get two decimal places either. 

    3
    Acciones de comentarios Permalink
  • Please fix the display.   If you have the data and use it to calculate the total distance please display it. I just went premium thinking that was the issue.  I always run w/ my Garmin watch.  The Garmin site clearly and easily reflects the total distances down to hundredths.

    3
    Acciones de comentarios Permalink
  • Even if Strava prefers to stick with the 1/10th mile accuracy, this does not explain why the distance is truncated.  9.98 should be rounded to 10, not truncated to 9.9.  This is inaccurate and unacceptable mathematically.  I love the site been using for years but this is perhaps my biggest frustration that makes me consider other apps/sites as alternatives.

    3
    Acciones de comentarios Permalink
  • Thanks Joshua, we have traditionally floored distances for weekly totals and training log totals which causes some distances to round down (Garmin does not floor it's distances, so a 9.98 km run will be 10 k on Garmin, but 9.9 on Strava). Over the summer, we began displaying the floored distances on the activity pages as well. 

    -2
    Acciones de comentarios Permalink
  • So, you are confirming the incorrect program action. Please FIX it. There is no reason to impose the floor operation to round floating point values. Why are you not using rounding instead? This is simply incorrect logic.

    Similarly, the is no viable reason for limiting the distance to a single digit. Please FIX it.

    If Strava declines user input like this, I can assure you that I will NEVER purchase any Strava product. Disregard of your users is the fastest way to kill your company

    2
    Acciones de comentarios Permalink
  • I'll communicate your thoughts to the team Bruce. Thanks. 

    2
    Acciones de comentarios Permalink
  • Thank you. I would very much appreciate that, and I think a number of other people here would appreciate it as well. These changes represent modifying exactly one line of code each. As you can see from some of the comments here, the refusal of Strava to make these very minor changes is extremely frustrating to your users - and to what gain for Strava? So that no one can say that you're off by 0.01 miles? You'll get a lot less resistance to that sort of error than you will for refusing to make simple, reasonable changes for your users.

    2
    Acciones de comentarios Permalink
  • Please communicate my thoughts as well. I'm astonished you haven't fixed this yet. It's a glaring mistake.

    2
    Acciones de comentarios Permalink
  • Thank you Elle.  Hopefully they this will be corrected asap.  Have a great holiday!

    2
    Acciones de comentarios Permalink
  • Strava definitely stores the information to 2 decimal places. If I export a GPX of the activity and import into another service it reports the correct distance to 2 decimal places.

    Please fix this!

    1
    Acciones de comentarios Permalink
  • Oh yes, please! If that gets changed, Strava will be fantastic! Thank you for your work and happy new year to the Strava team!

    1
    Acciones de comentarios Permalink
  • You say "We do not calculate distance stats to the hundredth place because GPS data is not accurate to hundredths."

    Your response shows a fundamental misunderstanding of the concept of accuracy. You cannot measure the accuracy of GPS as some number of decimal places for all distances. Accuracy is a percent of distance traveled. Instead of thinking in terms of tenths or hundredths, you need to think in terms of significant digits. A good GPS watch will be within 1-2 percent for routes with a minimum number of turns.

    See http://fellrnr.com/wiki/GPS_Accuracy for a much better (and more recent) analysis of GPS accuracy.

    For example, if you run a marathon with a good GPS watch, on a fairly straight course, without obstructions like skyscrapers, the distance measured by the watch will likely be within within 3/10 of a mile, so tenths are appropriate. But if you run a 5km race (3.1 miles), that same 1% accuracy means your watch will be within 3/100 of a mile so you need to go to hundredths. You cannot just arbitrarily pick some number of decimal places. Tenths is fine for 10 miles or more. But for distances of less than 10 miles, particularly for lap distances which are usually 1 mile or less, you need to go to hundredths, and GPS is accurate enough for that.

    For distances of 10 miles or more, show tenths. For distances less than that, show hundredths. At the very least, for lap distances of less than 1 mile, you need to show two decimal places. And do your rounding correctly. There is just no excuse for simply truncating the distances. That's just embarrassing.

    As a math teacher of some 26 years, I am appalled by the lack of understanding of basic math concepts shown by the Strava response to this issue.

    3
    Acciones de comentarios Permalink
  • I decided to check the accuracy of my GPS watch (Epson SF-810) for several of my recent runs, mostly about 5 mile runs. In every case, the distance given by the watch was within about half a percent of the actual distance. Another article I read, using data from thousands of marathons run by people wearing GPS watches, showed the vast majority measured the distance about 0.2 miles long. Much of that error was probably not running the ideal tangents. Even so, the measurements were within 1% of the actual distance on certified courses.

    There is plenty of evidence that most GPS watches will be accurate within 1% on typical routes. Two decimal places is reasonable for that kind of accuracy. You are basing your decision making on incorrect and outdated articles. You need to stop making excuses and fix the problem.

     

    1
    Acciones de comentarios Permalink
  • Here's another link showing that GPS watches are generally accurate within 1% of the total distance:

    https://www.theguardian.com/lifeandstyle/the-running-blog/2016/apr/15/course-accuracy-why-your-gps-watch-isnt-infallible

    Scroll down to the two charts. The chart near the end shows data on nearly 7,000 runners who did a marathon. Probably 90% of them showed a distance within 1% of the marathon distance. Keep in mind that most of those runners were running in a crowd and were not able to run the shortest distance on the course, the one measured when certifying the course.

    I take partial exception to the earlier description of the error of each GPS reading. Consider two possibilities. First, if each GPS reading has a small random error from your actual position, that will lead to some segments being long and some segments being short. Those errors will cancel over time. Or perhaps the GPS errors at each reading will be off systematically, perhaps always showing you 10 meters further north than you actually are. Those kind of errors will not have much effect on the measured distance.

    Based on the data in this article and my own checks of my runs, it seems reasonable to assume that under normal circumstances, GPS will measure within 1% of the actual distance run. If that is the case, that would allow two decimal places for distances under 10 miles.

    What I want to see from Strava is:

    1. Lap distances should show 2 decimal places and should be rounded to the nearest hundredth. What they do now results in huge errors when I do a fartlek workout, things like .29 miles showing as .2 miles.

    2. Total distances under 10 miles should show 2 decimal places. GPS is accurate enough to support this under most conditions. Do not penalize everyone for the worst case scenarios like running among skyscrapers or in a dense forest.

    3. Round all distances. When I emailed support they said they truncate so distances match goals. That makes no sense. They should show the most accurate number.

    These suggestions seem reasonable. I would like to have someone from Strava respond.

    1
    Acciones de comentarios Permalink
  • Please add two digits! That is the only drawback I have seen so far on Strava

    1
    Acciones de comentarios Permalink
  • What a shame. First time user of this app after hearing so many good things. Completed run today and it said 2.3 miles. 2.3 what?

    Tried to get it to two decimal places and thought I was doing something wrong and then stumbled across this forum.

    Sorry this is no use to me when the basics are missing. Glad I discovered it on a small run. Hopefully you'll change this one day, in the meantime I'll use something else.

    3
    Acciones de comentarios Permalink
  • Me too.

    2
    Acciones de comentarios Permalink
  • Elle,

    Has there been any update on this request?  Again, there is no reason to post the distance 'floored' instead it should either be posted as two decimal places or at the very least to the tenths place but rounded to the correct value.  So 3.58 should be either 3.58 or 3.6, NEVER 3.5. Thanks

    Josh

    2
    Acciones de comentarios Permalink
  • Bumped into this recently as well, when I noticed that Strava displays a 5.98 run (according to Garmin) as 5.9, but exploring the run, Strava shows 6 mile markers

    2
    Acciones de comentarios Permalink
  • Please Strava - this is my number 1 feature request.

    2
    Acciones de comentarios Permalink
  • I cannot believe this hasn't been corrected yet.  Strava, could you please fix this very simple, yet integral issue?

    2
    Acciones de comentarios Permalink
  • We need this!!!

    3
    Acciones de comentarios Permalink
  • This is a must! This is the only thing holding me back from being a premium member and using this app full time

    3
    Acciones de comentarios Permalink
  • Hi, Elle!
    Any word from the devs on when they can fix this issue, please?  I believe it's just a one-character fix (something like changing from "printf(%0.1d)" to "printf(%0.2d)".


    Having to go back to Garmin's page to lookup distances is not the greatest endorsement for Strava.  :)  Thanks!

    2
    Acciones de comentarios Permalink
  • Seriously. It's just bewildering. Strava, what is the hold up on this? I'm not sure what more it's going to take. Let me reiterate what others have said: I will pay money for Strava but not until you fix this issue.

    2
    Acciones de comentarios Permalink
  • With all the prior requests for this seemingly simple functionality change being ignored to-date, one might assume that Strava:

    1. Brought their code from someone else and can't modify it.

    2. Doesn't know how to modify what they wrote originally.

    3. Found that too many parts of their code would need to be changed.

    3. Doesn't give a crap.

    Make you choice.

    2
    Acciones de comentarios Permalink
  • Elle, we were in contact regarding this upgrade back in December.  What is the update here?  This is a no brainer fix.  I will be letting my premium membership lapse at this point.  Sorry, but if you aren't willing to resolve a simple user issue in a timely manner, it is becoming obvious that the user's aren't what the company believes drives the site.

    Josh

    2
    Acciones de comentarios Permalink
  • I don't know how I can trust Strava numbers anymore. It is not just the distance - it is also the time and the pace, and calories, and vertical ascent. 

    Today's run - 3.10 miles on my Suunto Ambit, 3.10 miles in movescount, 3.0 miles on Strava. However when I look at splits on Strava activity there is an extra 0.1 mile split, so according to splits it is 3.1 miles.

    Furthermore - time on movescount is 28:24. On Strava - moving time is 28:17 and elapsed time is 28:21. How come elapsed time is different?

    Pace is 9:09/mile on movescount and 9:08/mile on Strava.

    Calories is 381 on movescount and 504 on Strava.

    1
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.

¿No encontró lo que buscaba?

Nueva publicación