Question on this topic at the end of this post (you can't miss it )

Strava directed me to this post in forums. It seems this topic started for three years. However, We still experience this problem wit route calculation. Following is my adress to strava on this issue:

We Design a bike route on Strava. Last Sunday my route was 400 km long. It is uploaded via Garmin Connect to my Garmin Edge 1030.

After 280 km my Garmin Edge says that I've reached my destination, but there still 120 km to go. This is not the first time this happened and it looks to us that it has somehow to do with the length of the route as this only happens at tours longer than 250km.

So at 280km no more information about where to go, street names and so on. But the route still appears on the map of the Edge (must admit it is hardly to see, very weak line) so you can somehow still ride the route but it is uncomfortable, especially when you ride these long distances and it is getting dark.

At the end, ending the training, my Edge will register the tour completely and it is uploaded to Strava as well.

And this is the final reply on this subject from Strava:

Actually, this appears to be a known issue from Garmin and specifically with the Edge 1030. More info can be found here:
https://forums.garmin.com/sports-fitness/cycling/f/edge-1030/146594/route-calculation-stops-at-80-when-navigating-to-another-country#pifragment-447=1

Apologies for any inconvenience on that there, but the fix would need to come from Garmin directly. We simply push the Route data to the device.

Do let me know if you require any further assistance.

Much appreciated.

Question to Garmin: what's the issue here and how to resolve it. We have experienced this issue on several (long, i.e. >250km routes). Strava states that the routes made with strava are 100% ok, the problem should be solved by Garmin.

Best regards, Theo Herpers

Theo,

I spoke once someone doing truckrallys.

At that time I had a Garmin Edge 800, and he said that making routes of 100+ km rides could give problems, because there is a maximum of the amount of waypoints.

While you are talking about a 400K-ride this could be the same problem.

At that time I decided to split very long trips in two parts. And used a long straight piece of street to finish part 1 and start loading part 2. So do not miss any junctions, while loading part 2.

Of course not stopping the logging of the  :-)

Donald

I've done several rides 300 Km+ up to 450 Km, which were planned with RideWithGPS & all have worked without issue. Some of which crossed several country borders

I'm having this problem with my 1030 Plus with version 5.0.  I stopped on a road and tried to navigate home by the most direct route.  It drew a straight line from me to my house some 2.x miles away.  A second or two later, it had refined this straight line into a route along the various streets and the updated distance was now 3.7 miles.  Quite reasonable.  I hit the RIDE button and it stopped calculating at 80%.  I left it for several minutes but it wouldn't budge past 80%, even though it had just showed me that it could find a route in about 1 second just a moment before.

I ended up disabling ALL my maps except North America 2020.x (I don't recall the 'x' number at the moment).  I am in Los Angeles.  I have a few trailforks maps and other stuff.  All used to work at some point in the past.  I don't navigate very often but when I'm on dirt I like having the Edge to help me find new routes and get back to where I started.  At the moment, its letting me down.  I bet my ~20 year old Garmin 60CS could do a better job.

There is a slight chance that this is the wrong place for your question / problem...

There is a dedicated 1030 Plus subforum (this one is the 1030 or 1030 minus Plus).

Also the problem described here is over three years and 7 major revisions old. And also specifically about very long routes and cross-country navigation. I don't think 3.7 miles around LA to be somewhere near the OP conditions.