Option to manually cut out parts of an activity

[RolandRides]

Sometimes when I ride my bike and have a stop, the Auto-Stop features of my Garmin and Wahoo devices don't work, especially when I have to take the computer with me inside. In the end flawed distance and height recordings and up in the gps track of the activity.

Here's an example:

Currently Stava only allows to shorten the activity on start and end or to split the activity. When I do e.g. 3 stops that have such wrong recordings, splitting the activity and shorten the wrong parts is not a sufficient option.

Thanks

[Bryant]

Hey @RolandRides,

Thank you for providing this idea along with an example.
I'm going to archive this idea because we do have a workaround for this situation.

We recommend using the split and crop tools available to remove this portion of the activity. I have included instructions below:

To split an activity:

• From the activity page click on (◦◦◦) the more options menu > click "Split".
• From the split page, choose whether you'd like to make one or two splits. For example, if you are just removing a middle portion of a ride, you will want to choose '2 activities'. (You can always go back and split one of the new split activities again if you need to).
• Drag the orange lines to the exact locations where you'd like to divide the activity. Hover over the speed graph to help you identify where you were stopped or based on the location.
• When you're satisfied with your selection, click "split" on the left-hand side.
• You'll be taken to the "My Activities" page where you'll see your new activities. Your new activities will retain the name of the original activity but you can edit those as you'd like.

To remove the additional data from the beginning or end of an activity, use the crop tool.

To crop an activity:

• From the activity page click on (◦◦◦) the more options menu.
• Select "Crop" from the drop-down menu.
• Use the sliders to specify the portion you would like to keep. You will keep what is shown in orange and remove anything shown in blue. The green dot is your start location and the red dot is the finish location.

For more information, see our articles on how to split activities and Crop Tool for Activities

[RolandRides]

So I need to split my activity in like 12 activities to remove those errors? Really?!

[Bryant]

Hey @RolandRides,

Ideally, if you have trouble in the middle of your activity only 2 or 3 activities at most would need to be created. If you feel this method is too much to go through, would you mind suggesting an alternate idea to edit the middle of an incorrect activity?

[RolandRides]

The issue is that the activity is ruined as it splits over n smaller activities. I suggest a UI like in a video editing application. One can select a start and end segment and then a button "cut" that removes everything on a time line. this should be repeatable.

The date/time information should be sufficient to detect cuts in case this could be a problem with segments/PRs.

[anchskier]

@Bryant - Rather than using the existing "split" function that breaks a single activity into completely separate files, it would be just treating a section in the middle as if the user just stopped and turned off their device for a while and then restarted it on the other end.  It would keep it all as a single activity file, but just not record any data for the portion that was "blocked out".  

[Bryant]

Hey @anchskier,

I appreciate this input.
I'll change the status of this idea to gathering kudos.

[Clochedesvosges]

Oh oui ce serait bien pratique !

[D4nielB]

Was about to suggest the same idea, for me it would probably even be enough to be able to delete single points in the middle of a route.

Sometimes for reasons yet unknown to me my smartphone's gps sometimes jumps, i.e. single points are recorded at a different point (usually earlier point on track), then the track record jumps back. So I would like to delete this erroneous point to correct the track. Or maybe some sort of smoothing/filter function for the track to remove unplausible data (like a short segment where walking speed is suddenly way excess 10km/h).

Cutting and cropping the track is not an option.

Example (see the straight lines):