Invalid file (Extra_POI_Editor)

What is the full name on the folder/file/extension?

Did you use some file as input to EPE or did you enter totally new data points?

What was the full error message from POI loade

it's something like empty data fields. You may also want to just recreate the GPX as sometimes it will write a bad file.

When I first created the file months ago the POI Loader worked just fine. I have recently corrected/deleted some of the entries and then resorted the POIs in EPE. That is when the trouble began.

I "Browse" to select the input file so I'll have to try and load again to see the exact directory path; it's many layers deep.

The error message shows the directory path with file name and say...invalid file.

The GPS is out of the huse right now I'll try to get the exact path and message later.

When I use a CSV file to recreate a new GPX file, there is no problem...except...I have information in the original GPX file that cannot be included in the CSV file. I hate the thought of reentering all that additional information.

If you did a browse in POI Loader to get to the file, then that is probably not the issue. I asked the question becase I have been caught by POI loader remembering a file name that I thought was correct EXCEPT that I had moved it to another directory.

You do need to make sure the file extension is .gpx, not something else.

In "correcting" some entries, you may have pit in a blank field as has already been suggested.

The answer seems to lie in the web link field. I had included a link that began http://. Once I removed the link, the file loaded properly. Maybe I should just used www at the begining.

Thanks to turboccc for some suggestions on debugging the GPX file with a multi-column CSV file.

What would the link have done had it been acceptable?

The only value of the link field is to save the web address of the campground. It's of no value in navigation but it could make it easier to find information about rates and features of the campground.

I'll have to check and see if the link shows up in MapSource.

The only value of the link field is to save the web address of the campground. It's of no value in navigation but it could make it easier to find information about rates and features of the campground.

I'll have to check and see if the link shows up in MapSource.

Isn't there something about enclosing certain fields in double quotes?

Please post the file somewhere so we can all have a look at it. Alternatively, you can email it to me and I will check it. Most of the time, there is an illegal character somewhere. I have seen everything, so no special hint I can give you.

email: turboccc at hotmail.com

Turbo

Actually, I did send the file to you through email. Your suggestion in a reply email is what helped me debug the file. Thanks for your help.

This same thing happened to me. My problem was I left the . out of one of the Latitdes in my file.
Each time this happens I now look for a missing . and that is what it is. Guess my fingers don't slways want to put the . where it goes!!

Congratulations on your EUREKA! moment. Those little things can drive you carzy.

Yes, I have seen someone replacing a 0 by a O in the lon/lat coordinates. Hard to see...

I downloaded this file, as usual, and received an "Invalid GPX" notification when using the Garmin POI Loader.

I have run into a "size" limit with POI Loader before.

As a test, I deleted 103 entries from the front of the file. POI Loader took that.

There is some limit to the size of a file POI Loader will accept. I have fooled around with trying to isolate the limit but have been unsuccessful.

Maybe I'll work some more on it.

Note that EPE is happy to read the 21075 entry file.

If you reduce the file to 20986 entries, then POI Loader will accept the file.

I kept reducing the file by 10 until I got a file that worked and then I went up by 5 until it didn't then went up by 1 until it did.

02/04/2016 01:16 PM 10,214,107 20985 North America Campgrounds by rivopom.gpxx
02/04/2016 01:18 PM 10,214,604 20986 North America Campgrounds by rivopom.gpx
02/03/2016 09:03 PM 10,257,445 21075 North America Campgrounds by rivopom.gpxx
02/04/2016 01:32 PM 0 contents.txt

I was not sure what this meant. So I got the .csv file of campgrounds and converted it to a .gpx file using EPE. POI Loader has no problem with that .gpx file.

Campgrounds by rivopom.gpxx
02/04/2016 01:37 PM 2,230,427 21050 North America Campgrounds by rivopom.csvx
02/04/2016 01:38 PM 5,735,759 21050 North America 02/04/2016 01:39 PM 0 contents.txt

I then looked at the differences in the .gpx files for the 21075 GPX file and the 21050 CSV file.

A similar entry looks like what is listed below with the CSV converted to GPX file first

It looks like the fact that "Address" "StreetAddress" "City" and "PhoneNumber" are extra characters in every entry has of the GPX file has created a situation where POI Loader has run out of space in its work area.

Anyone have any ideas.

Before we had EPE, I had used other methods to create the GPX file and found that different Utils and programs will write the file out different. Some will add a space or 2 to keep a place holder while EPE does not, in fact, if EPE has a blank field, it sometimes skips even the header unless it is def. needed.

Some GPX files will have Every field in it even if it is not needed, that makes it harder to read/write back.