Small .gpx file truncated when transferred to Legend HCx internal memory

Former Member over 13 years ago

I have a 99Kb .gpx file that is truncated when I transfer it to internal memory in my Legend HCx. My tracklog is empty before transfer and there are no saved tracks. That seems a very small file size to be partly rejected, especially considering 1) I transfer far larger files in the other direction from my Legend internal memory to BaseCamp or MapSource and 2) so far as I can determine, the Legend HCx has 24Mb internal memory.
a) What might be the cause that this transfer is truncated?
b) If I am unable to transfer that file size, what are my alternatives to getting this track on to my Legend?

SOLVED?
It appears that if I rename the file, 'ACTIVE LOG', the whole track is transferred. Then, I can save it and return it to its previous filename in my Legend. Is this how it is supposed to work?

0 Former Member over 13 years ago

What evidence are you seeing that makes you think the file is being truncated? E.g. have you looked inside and determined that data is actually missing from the file? Or are you going by the filesize as reported by Windows Explorer when it's on the hard drive versus when it's on the eTrex?

...ken...

0 Former Member over 13 years ago

Ken,
'Track Truncated' usually appears within a box in the Legend display and I can see by the breadcrumb track itself that it is incomplete. I recognise now, too, that the transfer progress bar completes much more quickly than when the whole track is transferred.
Bob

0 Former Member over 13 years ago

Thanks Bob. I just wanted to be sure it wasn't simply an issue of the difference in block allocation size between the file on a hard drive versus in the internal memories file system.

The symptoms you are seeing makes it pretty clear that it's a problem with "magic" file names on a lot of the newer devices. E.g. certain file names or file types trigger specific, and sometimes unexpected, behaviour on some of the devices.

...ken...