Loading gpx files

What files?

Haven't run into that yet myself. I've loaded some pretty big files,but the only ones over 1 mb are .csv extension. The biggest .gpx file I have is just over .5 mb.

One is a Pizza Hut file which is no longer on the site but I have a copy of it on my desktop (I downloaded it last week of March: size 1.01MB). The file on the site (now) is a csv file.

I have not run into this problem with my 350.

Perhaps the file isn't formatted properly.

I have geocaching GPX files that I load all the time. They have a TON of data in them and are between 1.3 and 2.5 MB each and there are 4 of them, so I would have a hard thinking that the problem is the size of the file.

I've had a couple of issues with gpx files from other sites and they would not load via POILoader. I don't believe it was a size issue, I've never loaded anything in the range mentioned above.

I will try and save the csv file for the particular poi in the gpx format and see if there is any difference.
Many thanks.

Is there something you are trying to accomplish with the GPX file that you can't with the CSV file? There are some differences but for many/most users GPX isn't necessary, so I was just wondering.

When you say freezes, what do you mean? POI Loader is not very good at giving any sort of feedback, as to its current activity.

It may have exceeded your boredom threshold , but it could be still processing.
(If you use Task Manager, you should be able to see if it is actually doing anything.)

How long have you waited? ... and how fast is your machine?

I can dial the phone number on the poi file if it is in the gpx format, which I do not think I can do with a csv file. I may be mistaken on this point.
Sometimes, the only format available is the gpx format without a corresponding csv file.

What I meant by freezing was that the poi loader just sits with the processing, with the memory usage ever increasing (looking at the Task Manager) and it goes beyond any threshold for boredom. I leave the machine for more than 20 minutes and it still is on the same spot (sometimes more than 20 minutes really). When I close poi loader, remove the "offending" gpx file, it runs in a couple of minutes and is done. The machine is a P4 (3.00 GHZ).

Have had no problems with my POILoader freezing up on me while uploading any of the gpx files, regardless of size. I'm totally stumped as to why this is happening to you. Do you have the most current version of POILoader? I've got v.2.5.2.0, mind you I've had no problems loading files even in the earlier loader versions. I'm not a tech but I'm wondering if you were to uninstall and then reinstall POILoader and then try to upload the large gpx file to see if that works.

Sure, having the phone number be dialable (if that information is available in the file) is absolutely a reason to use the GPX format rather than the CSV format. That's why I asked what your needs were with the file. (Sometimes people are banging their heads up against a wall trying to do something that they don't need to do.) And when you indicated that you would just download the CSV file that made me wonder.

I still am of the mindset that the file has some sort of weird formatting or errors in it for it to do that.

The CSV file was posted after the GPX file. That reduced the ache. I just thought that some other person may have experienced something similar, but it appears this is a one-off situation. Sure, I can live without it, after all, I lived without it prior to locating the file. As you rightly said, this may be one of those occasions where one is unnecessarily banging the head against the wall. I have to keep my head for better uses than destroy it over a GPX file. That is what I will do, Motorcycle Mama. Thanks for your advice.
(I do have the latest version of POI Loader. Thanks.).

Oh ok, so it's busy doing something - though possibly, nothing useful

So it sounds like you have found some sort of data-specific processing problem. Maybe we could have a look at one of the files in question? If it's a reproducible problem, then Garmin should be able to fix it.

Personally, I am using V2.4.2. I've still not received a response from Garmin's "Software Team" confirming the changes they actually made to it - which we know are vastly different to what they said they did to it.
(Garmin's front-line support said they would pass my request on...)