Bizarre route conversion - 660 - Mapsource

[Wapping]

I recorded a reasonable lenghthy - 210 miles or so - track on my 660.

It goes clockwise, starting at Sainsbury's in Chelmsford, out to Aldborough and ends back in Chelmsford at McDonalds, so it is not a perfect circle.

I uploaded the track to my PC, without a problem. In Mapsource the track looks fine and, as there were no u-turns, I had no need to edit it.

I wanted to save the track as a route for future use, so I sent it back to my 660. The 660 found the track as new data and converted it into a route, absolutely perfectly. So far so good.

I then sent the converted route back to my PC.

Then something truly bizarre happened.

Hopefully on the attached file you can see that the return leg takes a crazy detour from just south of Braintree, west all the way to Stansted airport and returns as a direct straight line. The Stansted airport excursion, nor the straight line return appear on the route on my 660, nor did they appear on the track, nor (most certainly) did I go anywhere near Stansted airport.

As I did not go anywhere near Stansted airport and certainly did not ride across country in a straight line, I am at a loss to understand how Mapsource on my PC has read the route wrongly (creating the detour). I had no other routes or tracks on the 660, so cross-contamination is impossible.

I am running identical mapps (latest version on both my PC and 660. I have also performed the latest software update. The 660 is performing normally.

Unfortunately I deleted the track, so cannot compare it

Any ideas, anyone?

 

[Wapping]

I have contacted Garmin to see if they can throw some light on it.

 

[Deleted account W]

Could it be one breadcrumb track point was logged while in a bad reception area incorrectly showed your location at the airport? Then when turning the track into a route the units included it.

Just a guess though

 

[andyclift]

Really wierd. It can't be an odd breadcrumb as that does not explain the straight line across country. I have tried getting the strange loop out and that seems impossible. It will be interesting to learn what Garmin think.

 

[Wapping]

Could it be one breadcrumb track point was logged while in a bad reception area incorrectly showed your location at the airport? Then when turning the track into a route the units included it.

Just a guess though

Really wierd. It can't be an odd breadcrumb as that does not explain the straight line across country. I have tried getting the strange loop out and that seems impossible. It will be interesting to learn what Garmin think.

Thanks for the replies.

I thought it might be a breadcumb but it does not seem to fit with what I see.

The 660 device is brand new and has not been near Stansted airport, nor were there any other tracks or routes saved onto it.

The track itself uploaded to my PC without a problem and was 100% accurate. I often have to edit out a few U-turns (not Garmin's fault) but the ride was glitch free, meaning I did not not make any changes.

When I sent the track back to the device it converts into a route without a problem. The error creeps in when I send the converted route back to the PC, only to save it for some possible future use. Somehow it puts in the detour.

On closer inspection, the detour departs from south of Braintree following a physical road west to the airport, then returns to exactly the same departure spot as a straight line. Route properties cannot edit the changes, nor show the instructions. This is not surprising as it is simply a converted track, with no via or way points, meaning - of course - it has converted as a single route.