Skip to main content

I’ve come across two segments in my personal heatmap that simply have VERY wrong elevation and gradient data.  One example is on segment “Conant Road Climb” in Lincoln MA, segment 4177639.

This is the 0.45 mile section of Old Conant Road southbound from the end of the unpaved footpath and going down to Hawk Hill Road. Elevation at start is 274', at Old Conant Rd meets Hawk Hill Rd is 232. So the elevation change is -42 feet, a slight downhill. But the Strava user who created this segment named it Conant Road Climb!  Despite its negative elevation delta, the segment is listed as having a 232' rise, yielding the VERY incorrect 9.6% grade over its 0.45 mile length. At segment creation, it appears the elevation change was incorrectly set to the actual elevation at the segment's endpoint. The segment’s definition shows a crazy pair of values:

  • Lowest Elev-114ft        Highest Elev118ft    Elev Delta: +232

Clearly no location in Massachusetts sits at -114ft.  Could this be a MapBox problem, or is it Strava?  It’s interesting that the elevation profile on ride activities, and on the segment record correctly illustrates this section as going DOWNHILL on the southbound segment. 
A similar Strava segment covering nearly the identical roadway but northbound is called Old Conant NB segment 12618002, and shows a reasonably accurate 46-foot rise over 0.52 miles, for a 0.9% climb. So how can both the Southbound and the NB half-mile both have a positive grade?

Another segment with VERY wrong elevation/grade data is segment 2798887, Rindge Ave Climb in Arlington MA. It’s also not really a climb at all, despite the segment name. Its definition shows a ridiculous Lowest Elev: -213ft, and a grade of 16.9%, yet lots of strava users have covered this segment at 22-to-25+ mph. 

My QUESTIONS: 

1- Can I request that Strava review and correct the elevation data for a segment I believe is way wrong?

2- Can I submit actual elevation data to fix the segment definition for a segment like this? How?

3- Can I find the name of the Strava user who created a given segment, and can I query that user to find out why they used a misleading segment name - including the word CLIMB in these two cases. 

Wrong segment data occur when the creator of the segment has wrong data in the activity the segment is created from, be it from GPS errors, barometric errors or using an imprecise elevation map.

There is no workflow for reporting that, Strava has that for safety/legality/propriety concerns only. They have disabled the flagging reason “Wrong GPS information” that was formerly available.

Usually you would hide such a segment in the web browser UI. Until some time ago you could create a better segment instead but meanwhile this is often denied because Strava don’t want duplicates, regardless if they are much more precise than the original or not.

You can’t find out anything about the segment creator. You could vote to change that in the idea 

 

Terms & ConditionsCookie settings