Related

transfer computer to basecamp

Former Member
Former Member
After downloading a GPX track from the web to my desktop, and then clicking 'import to my collection', then browsing to the GPX and clicking 'open', the track does not appear in the library. I'm a newbie with windows 7 and new 64s which is not connected to the computer while I try this transfer. I thought I would try someone else's track which opens on the desktop with a big list of points.

Thx in advance for any help.
  • 0
    I downloaded the file and it had the extension ".xml". I changed it to ".gpx" and it imported fine into BaseCamp v4.2.5.
  • 0
    Yes it imported no problem. As I said it imported with the name "Track" did you look for it with that name?
  • Former Member
    0 Former Member
    I downloaded the file and it had the extension ".xml". I changed it to ".gpx" and it imported fine into BaseCamp v4.2.5.


    Sorry for delay. Thanks again for all responses here. It was enough to get me to figure this out. The file came to me extended '.gpx.xml' Once I paid enough attention to that and got the extra .xml deleted from the end, it worked fine. So, the browser might be responsible for this? I tried a couple others with no apparent change. Is there a browser that may have worked better?

    Thank you very much.
  • 0
    So, the browser might be responsible for this?


    Well, yes and no. When a web server "serves" a file, it should tell the browser what kind of file it is, and what to do with it. When it doesn't, the browser takes a look at the contents of the file and then decides what to do with it. When a file seems to be an image, the browser will display it. When it looks like a .zip file it downloads the file, because it's not a file type it can display.

    GPX files contain XML data; actually a familiar format for web browsers (it's a cousin of HTML). So some browsers will just display the contents of the file (just like it would do with a regular web page), some will offer to download it with a default file extension (.xml), and some will download it like you would expect in the first place.

    This changes completely when the web server tells the browser what to do with the file; if done properly, every browser will download it as a file with the correct file extension. So it's up to the web site owner to serve the files properly (the same applies to the KML files)

    Is there a browser that may have worked better?


    Google Chrome seems to download the file with the correct extension.