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

Slow map loading on ride

Hello, 

As many there I have some bugs and lags when i try to follow a course.

I have the original Garmin's maps installed, with auto-zoom, level of details is normal.

Yesterday I did a ride for about 80km at 30kmh, but when i arrived around 15km, the map wasn't showing the directions. I only seen my point.

I have created this route in Garmin connect website

Previously i used more Strava to draw a route and there were less bug. i have compared 2 routes in the same area, one created on Garmin connect, and one on Strava. 

Itinéraire Garmin 70km : 2380 track points = 34 per km

Itinéraire Strava 100km : 1917 track points = 19 per km

So, we may think that the bike computer can faster load 19 trackpoints per km than 34

It could be a relevant evidence to faster our GPS

Do you think that the original issues with map lagging and same issues can be result of the route file ?

  • Years ago using the Edge 705, it had difficulty calculating routes with too many track points.  I generally had to limit the course to 1000~1600 track points to get it to load in a reasonable amount of time. I did this by creating the course on various websites (some generating huge numbers of track points) then using the free utility TCXConverter to reduce the number of track points to under 2000.  I'd also break courses over 100km into several shorter courses. That worked well. 

    The problem there was simply loading the course.  I don't believe it affected the navigation or display once it was calculated and loaded. Anyway,  that was many years ago on a relatively primitive device and since using the 820 and creating courses mainly in RWGPS, I've had no such issues.  That said, I can see where having a lot of track points may slow down calculating a course, but once it was calculated and loaded, I wouldn't expect it cause and issue during the ride.

  • For me the loading is well. It takes 1 minute if I still or a little more if I start immediately. 

     After a map update yesterday,
    i tried today with a Strava route, and the problem is the same, few times after the start my edge don’t show anymore the map background, and sometime the turn by turn indications is locked on the previous indication.

    I think that I don’t had this issue last year (with the current firmware at this period)

    it’s not believable that garmin sell products which don’t work well with so basically features 

  • Historically, when one of my Edge devices started doing something weird after having been working OK with whatever rev it was on, I'd do a factory reset after saving my setting to my computer so that I could restore them afterward.  That usually fixed the issue. It might be worth trying in your case.   If the issue seemed to coincide with the a firmware update.  I'd revert to a previous version.  Right now I'm on 11.2 for the 820 as that's worked the best for me. .

  • Today I make some tries. my target was to try to remove this issue without downgrading my Edge. I seen that last year, my firmware was the v11.20

    I tried 1 : Reset to factory settings + delete the device on Garmin connect and Garmin Express

    result: no effects, I made a 2km course, after 2 minutes the TBT was locked on the first indication, and the map wasn't showed anymore.

    2 : reset the the map installed by default + set level of details to "less" it seems to be the default settings.

    result : with a 80km route created with Strava, it was better, I had most of the time (75%) the TBT when i was on an other screen than the map, but the map still generate slow sometimes (may be when i ride faster?), TBT notifications are still delayed and shows an incorrect target distance (except when i climb) 

    so i kept the map screen opened to make my own TBT indications, and I was finally able to follow a course. 

    I will not judge the quality of TBT indications, if you don't see the map it's sometimes hard to now where to go because for exemple when in a roundabout there is 2 road on the half right, the edge will say to go right, but don't know which one...