Add a way to address historical, inaccurate segment times on changed/re-routed trails

[doubleduhric]

So I keep running into a GREAT problem and I wanted to see if it was something anyone may already be working on. 

In Summit County, CO (and countless other areas) trail-building and re-routing has become a fairly BIG business. This is AMAZING for our environment but has at least one major drawback in coordination with STRAVA's platform. Currently you can make all the new segments you would like, but if a historical run is 'close' enough to the new trails path, it counts.

I propose an option when adding/creating new segments to select a 'reroute'. This would then essentially allow the creator to add a 'start date' or 'trail completion date' to limit the leaderboards from searching and finding historical data from before the update to the trail was complete. i.e. Hattie's Trail (Frisco, CO) reroute was just finished. The reroute allows the trail to be ridden both up and down, rather than almost entirely down. Almost 1/2 a mile of trail was added via switchbacks and flow. Obviously old statistics from the 'straighter' trail will be much different than those from the reroute. 

Just a thought.. hope its helpful!

[jtuck13]

It would be nice to "retire" a segment that is no longer possible to complete but still be able to view the segment/leaderboard. Use cases include a segment that goes over a bridge, but the bridge is torn down and a new one is built. Another example is a trail that has to be re-routed due to environmental reasons. 

[IAB]

Agree.

[mike]

Would clean things up a bit.