Allow the user to unmatch a segment

Sometimes a segment match is wrong or there is a GPS data issue and a time may be wildly inaccurate (a KOM for doing a 5 minute climb in 2 seconds for example). I have had rides flagged because of this and the fix is either to make my ride private or to request support unmatch the segment which takes time and support resources.

It would be great if the user could simply unmatch the segment themselves. This is different from hiding a segment as that only makes it not visible to the user but you are still on the leaderboard.

Better still if a section of the ride can be marked as no match and therefore no future match could occur in that section. Or add the ability to chop that section out somehow (maybe would have to split the ride into two rides cropping the bad section out perhaps though).

20

コメント

8件のコメント
  • Gps autocorrection feature is really needed.

    For ex, no one run with 30mp/h(45km/h).  And more, if the best previous performance of a runner shows a max pace of 4:00/km,  he can't simply run with a 2:00/km pace if he's not falling down from a hill.  Impossible speeds, pace times should be corrected, cropped or removed...  Strava is already cool, some features will make it even better.

     

    -1
    コメントアクション Permalink
  • I think this feature should be added. You cant crop or remove the bad section if it occurred in the middle of the ride. The rest of the ride may be fine and worth keeping.

    0
    コメントアクション Permalink
  • Agree, just a function to exclude a single effort from any given segment. Just that once. My reasons: sometimes I go on a segment (just because it's on the way), take photos etc. or even have a swim in between. I still get a match. While I don't care about the segment time itself, it makes browsing the history on the app very difficult, because all the efforts are now scaled so that the normal efforts all show up on the top line, i.e. I can't see the differences that really matter. I hope I made my point clear, hard to explain :)

    What ever the reason is one wants the effort to be excluded, I think we should have that option. Of course, opt-in later of course (by re-evaluate function for example).

    I hope the strava matching system can take direct "orders" from users easily.

    And please, while off-topic, the HIDE / UNHIDE -feature! I will fnd a better topic for this, but that's maybe the most misunderstood feature. It should be named VOTE DOWN / VOTE UP or something. It doesn't hide from just yourself, it hides the segment for everyone. Likewise, anyone can try to unhide it.

     

    0
    コメントアクション Permalink
  • This really needs to be fixed as there are some segments where the top 100 or more people in a segment are not even riding the same track/trail, but are riding on the road that parallels it, or are riding a dirt road through a trail section that passes over the road. This leads to segment times that are completely unrealistic and makes shooting for the KOM/QOM worthless.

    2
    コメントアクション Permalink
  • This happened to me this morning.  I now have a KOM on a segment (Frick Kick) that I shouldn't have.  I stopped part way up and turned off my GPS.  After rolling again after passing the top of the segment, I turned my GPS back on and it recorded me as finishing the hill instantly.  How do I fix this?

    1
    コメントアクション Permalink
  • Jason, start with Flag feature, and there are options and a comment field. Describe the problem and it will be fixed eventually. I've had a KOM removed once (not mine), because the speed was unrealistic. It was a gps error, and the team unmatched the KOM pretty quickly.

    -1
    コメントアクション Permalink
  • I would also like to be able to unmatch any KOMs that I earn from short periods of "vehicular traffic assistance" without marking my entire ride Private.  Doing the latter removes the entirety of my real, actual mileage from Clubs.  Thanks!

    2
    コメントアクション Permalink
  • A simple checkbox next to where the "Hide" button which, when checked, tells the Strava matching algorithm that the GPS data does not match the segement. The segment is then removed from the activity but the route obviously isn't changed, it is just like an activity which covers areas which aren't part of a segment. This way the matching algorithm is improved via human assisted machine learning and people don't get K/QOM's and PR's for simply being in the general area of a segment.

    Another way to improve the matching would be to factor in the accuracy of the device and have a user adjustable precision factor. For example if you have  a very accurate GPS and want to minimize mismatches you could require 95% accuracy (what ever that might mean).

    Another idea would be to mark segments as "Mountain Bike Only" and then have a field on the equipment/gear table which indicates road or mtb and the algorithm won't match road rides with mtb segments.

    Personally I think my first suggestion (as suggested by others here too) is the best one.

    Hopefully they can do something about it.

    0
    コメントアクション Permalink

ログインしてコメントを残してください。

お探しのものを見つけられませんでしたか?

新規投稿