DANGEROUS BUG: Sending tracks/routes from Basecamp to Forerunner 255 reduces precision

When sending tracks or routes to my new Forerunner 255 using Basecamp, the tracks or routes arrive on the device with much fewer points.

The according point reduction options in "Settings > Device transmission" are not enabled, so that is not the cause.

When exporting a track from Basecamp as GPX, then sending that to my phone, then importing that GPX file into Garmin Connect, and finally sending that track to the Forerunner via Bluetooth, the track arrives with all points correctly. So the Forerunner definitely can handle routes with that many points.

This bug is dangerous because a change of just 25m can mean the difference between life and death when navigating in the mountains. The current situation has the potential of luring people into very dangerous terrain. It was pure luck that I noticed something was odd about the shape of the track before any serious consequences could ensue.

Please fix this bug urgently. Thank you very much!

  • I returned the Forerunner 255 after observing similar issues with routes and tracks transmitted via Garmin Connect.

    For whatever reason, the first time the issue occured it occured only with a track transferred through Basecamp at my PC at home and in the field I was able to retransmit the original GPX file from my phone via Connect, and the issue was gone.

    But at some later mountain tour I did a systematic test of all four combinations (GPX containing a track vs. one containing a route; transfer via Basecamp on PC or transfer via Connect on phone) and in ALL FOUR combinations did the Forerunner oversimplify the course.

    This actually caused concrete issues on my mountain trip (nothing serious, but it lead to taking a wrong turn in non-critical terrain and having to backtrack, because the oversimplified track cut off a little loop that was necessary to take first before then turning in the opposite general direction). Thus the Forerunner is quite simply useless to me.