This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Imported Routes, Starred Strava Routes, ClimbPro, and Strava Segments

I recently upgraded to Firmware version 10 and was excited to finally have ClimbPro integration with Strava Segments and Strava route syncing.  Unfortunately, my experience after several rides has been terrible.  I have compared several imported routes from Strava GPX files against the same route starred.

Example: 

I created a route on Strava and exported the GPX file, and also starred it.  So, I have 2 of the same routes on my 1030, but they are not the same.

 - The exported GPX file is 24.7mi, est time 1.35, 2 climbs.  If I ride the route with no navigation, there are 5 Strava segments along the route

- The starred route is also 24.7mi est time 2.04 2 climbs, but the climbs are in different locations, different lengths, and have elevation profiles that do not make sense when riding them. There are only 3 segments, and the segments do not always work.

has anyone else had experiences like mine?

  • Can you look in details of the stared route, to check every segment?

    Seems that there is an bug when the route is sent to garmin connect , elevation is *** up ,cannot be used

    You can also check the third option, the one with strava route iq app, seems that is still give the best functionality

    I put a while ago a topic about this issue but nobody from garmin say anything

  • What is interesting is that on any given Strava route, when viewed in Strava, it displays the segments it believes lie along the route.  However, when the route is ridden, additional segments show up.  I don't know why this is, or why a Strava route picks up only a subset of all the segments available.  Whatever the case, this is a Strava problem, not a Garmin problem.

    The starred Strava route seems to contain the subset of the segments associated with the route, and does not include some of the starred strava segments that have been downloaded to the Garmin 1030.  I think this makes sense in that if Strava doesn't recognize the segment as part of a route, then it wouldn't be included in the starred route when sent to the 1030.

    For sure, there are compatibility issues between Routes, Segments, and Climbs between Strava and Garmin.  I'm assuming it will take time for Garmin to sort this out.  Since these are the two largest players in the segment, I would hope they can get things corrected soon.  However, from my experience with Garmin devices in Aviation, they do not want to work and play well with others, especially the sharing of data component.