Garmin device taking ages to connect within Basecamp

Yep, see the same thing here. My waypoints.gpx file on the device was about 15Mb. After removing the millions of blank lines it's now about 80Kb. Basecamp now connects much quicker.:)
Hopefully this will be corrected shortly as this is a pain if the blank lines come back.

Could someone who has this happen could this with 3.3.2?

We did fix some line break issues with 3.3.2, so hopefully this should not happen anymore.

Hi FALAGAR. Sorry, I'm having the problem with 3.3.2. If I start off with the device empty, select All Data from the PC and send it to the devices All Data I'll get many megabytes of empty lines in the files at the device. Especially the waypoints.gpx file.

And the data in BaseCamp doesn't have all the blank lines?

The test would be to check if BaseCamp adds more lines. 3.3.1 would add lines, 3.3.2 shouldn't.

So you'd have to clean up your data first before testing. BaseCamp will not remove blank lines, because there is no way for us to tell if the lines are intended or not.

OK, I just tried this. I deleted the AllData.gdb file from "....Application Data\GARMIN\BaseCamp\Database\3.3". I then copied all the data from the device back to the PC. I then deleted all the data from the device and sent all the data from the PC back to the device. The files on the device no longer had the excess blank lines! So that works.

Prior to this test I had already done a grep cleanup on all the files on the device so I didn't have corrupted .gpx files to start with. This could be a problem for users who don't want/know how to delete a few million blank lines.

Yes, that is definitely a problem.

I am not sure what a good solution would be though. Maybe we can check if there are more than X (maybe X=5) blank lines in a row then we'd delete the rest.

Yes, that is definitely a problem.

I am not sure what a good solution would be though. Maybe we can check if there are more than X (maybe X=5) blank lines in a row then we'd delete the rest.

There needs to be some kind of "Clean-up" service in BaseCamp to deal with these types of situations though. Most users can't be expected to understand any of this. BaseCamp will need to look at the database and determine if there are "potential" issues moving from one version of BC to another.

Cheers,

I agree, we would not expect most users to understand this.

The clean-up wouldn't just have to clean up BaseCamp's data (which would be possible, we already fix up data on every start-up if necessary), but also the data on the device (which is were the real problem is, because of how slow the device detection process becomes).

I'll see if we can come up with something.

What happened to my reply?! I just got a blank screen then it made me sign in again. Gah. Here we go again...

I've been using Basecamp 3.3.3 and it still starts adding these blank lines. Just on some of the waypoints.

I've also noticed that the date/time stamps on my waypoints on my device get updated to the current date/time when looking at them in Basecamp. Not all of them, but about 90% of them.
Why on earth does it do this?

We will look into the blank line issue.

The time-stamp issue should be resolved in 4.0.