Need help with POI loader 2.6.1.0

The new POILoader made the new file and sent it somewhere. It doesn't seem to me to be a csv file problem. The new POILoader allows you to set a custom name to the gpi file when compiling.

Is that new filename.gpi file in your POI folder?

Does it have the new date stamp when you made it?

Did you remove the older file before making the new one or overwrite it?

2.6.1 uses the name of the folder as the default POI.GPI file name on the unit. The file is in the same place, it has the name of the folder so you may have two files. the old POI.GPI and the new foldername.gpi.

Looking in the POI folder in the GPSr I see two files, one is named [My POI.gpi] and the other [poi.gpi]

It has to be put in the new 2.6.1.0 POI Loader folder.

No problem making a new file so I would delete all the gpi files from the GPS POI folder (or SD card) and start fresh.

What is the name of the folder you file is in? The new file should have that name unless you renamed it in POILoader.

It is there otherwise the sound would have never made it to the unit.

In the PC the folder name is My POI

In the unit the folder name is POI just like before, the two files are throwing me off, the My POI.gpi has today's date and is only 7kb, the other poi.gpi has a date of 7/27 and is 989kb that was the last day I used the POI Loader 2.4.2.0

The new POILoader did not do load all of your files. Just copy the older gpi to a spot on your hard drive. Then restart the GPS and you'll see what files did not load. Then we'll have a better picture of what's going on and where to go. Let us know.

Thanks, Bear, Box Car and Juggernaut

It is working now, looks like when I first ran the 2.6.1.0 it asked me if I wanted to use My POI as the file name but that wasn't the name being used by the older Loader and that is where the conflict happen.

Seems like everything is working including the WAV files.

Happy Camper!!!

Glad it was a quick fix. POILoader will remember the new folder you directed it to from now on making it easier the next time around.

Bear, there is one file I skipped while working with you earlier, it is a huge file and may have issues even if it loaded fine with the old loader.

It has been trying to for more than 15 minutes and it is stuck on 0% complete, I may have to examine it close and remove unnecesary spaces.

First things first. What is the name of the file and did you download it from POI-Factory? Someone else may have already experienced this files problem.

2nd, how many POIs is it supposed to have? It sounds like it is a csv format problem when stepping up from the old to the new POILoader. I like to load the csv into EPE and see if it sees the proper number of POIs.

If it does have the correct number and you are in a hurry, then just save it as gpx file, close EPE and then rename the .csv extension to something like .csvx so POILoader will ignore it. This is the cheap quick way to get back on the road.

For now lets get the filename so we have somewhere to start. I'll wait for your post.

Some people like to take half the file and see if POILoader will work. If Yes, then do 3/4 of the file. If not, do 1/4 of the file.

It is sometimes the quickest way to isolate the problem, unless you have more than 1 line that has a problem.

The name of the file is DinersDrive-insDives.csv and it was downloaded from POI Factory maybe 6 months ago but that is irrelevant, the file I have no longer resembles the one at POI starting with the one at the Factory only has 424 locations and my file has 453, a good number of the locations in my file have the food that was prepared on the show, this way before I head for a particular restaurant I have an idea of the food they serve .

So it is hard to tell if the problem existed when I downloaded the file or with the stuff I added.

Before you mentioned I took the first record on the file as it was and it loaded fine, I was thinking of taking them in little bunches and loading until it stop and it will be easier to isolate the problem.

Going by halves is the fastest way. It shouldn't be too long, 453 POIs isn't too big.

I'm heading out to a meeting in a bit but later tonight I can help isolate the problem line if you want to email it to me.

1 suggestion, if you have the ones you've added grouped together it may be possible to copy them to another file, download the latest from the site and add yours back in. That way you get them all, the best of the best good eatin's.

I would remove the ones you added in and then try the file unless you manipulated the original file because the file is a good file. I have it and have loaded it with poi loader 2.6.1

No way I have done too much typing on the original locations plus the new ones I added, the problem could be on the new loactions or in the meals I added to the original locations..

In the process of moving 25 at a time to a new file and Loading sooner or later I'll find the culprit.

Thanks for confirming that the original is OK with 2.6.1.0

Did you try to run in through Extra Poi Editor?Save it as a gpx file.Then reload back to EPE and save back as a csv file.

can you explain what will that do? will it find or drop the problem POI?

I have had luck taking some csv files that had problems and saving them as a gpx file and they worked fine after that.Have ran some of my on private csv files that had problems I couldn't find.Re-ran back through EPE and they worked after that.May have been just lucky.EPE should give you a line number if it will not load.You can start your search for the problem from there.

@Flaco,

Just a thought. Since this is a personalize file why just leave it in GPX format. Then you can take advantage of the phone number and other formatting options.

When you load the file into EPE and save it as a gpx, then load the gpx again and save it as a csv it just may fix the error. Quick and dirty method.

Evetually you will find the bad line by dividing and conquering. Even when you find the line sometimes you can look at it for a while and wonder what the heck is wrong. It could be a missing comma or a character it doesn't like or somethat that isn't quite obvious. Or, when you find the line you say, "dang, look what I did" (that's my line).

What's happened is during your additions you have some commas in the POI Name field (Column C) the system doesn't like. Just installing EPE and loading them will find and correct the formatting error. You can then save the file as either a GPX (which with your system won't give you a lot of advantages unless you do some reformatting) or save the file as a Garmin CSV which is what you normally run.

Drop me a note off-line and I'll show you one way to set up your files as a more fully featured GPX that will greatly improve the way the files look on your unit.

Saving the file in the PC as GPX re-loadin into EPE and saving it as garmin.csv worked as far as loading all the 453 poi into the unit but I don't like the way it displays in the GPSr, the formatting is different all bunched up as to the way it looked when I saved as 4-column CSV, and is tacking hash marks [ENTER] at the end of the file as many as 70 little commas

Email me a copy of the original file and I'll take a look at it tomorrow night. Let's see if we can get your file fixed they way you like it.

That may work.

GPX - loads but not formatted the way I like

GARMIN CVS - loads but looks in the unit worst than GPX formatting

4-Column.CVS still not working stuck on 0% complete

Going back to what I was doing earlier of loading in chunks of 50 and try to isolate the error.

The biggest advantage to GPX is you can control the formatting as you have a lot more than 4 columns to play with. Where CSV forces you to do all the comments in the fourth field, you have 2 to play with in GPX - Comment & Description. CSV has only a description field which also has to hold the street address, city, state, zip and phone. These are separate fields in a GPX so the editing is much easier.

Like I said earlier, drop me a note off line and I'll help you set up the GPX.

To get an idea of how different units display the gpx or csv info, have a look at http://www.poi-factory.com/node/21274

It will either enlighten you .. or confuse you!

I followed the link and was blown away - especially by the ability to follow other links (using the CNTL key, of course).

Why can I not find this in FAQ alphabetic list?

When answering questions from newcomers, we often get into .csv versus .gpx. I will save the link above but I really should be able to get there through FAQs.

Thanks very much for that work.

CNTL key? You should just be able to click on them.. maybe you meant opening them in a new tab to compare them?

I guess because Miss Poi put "JD4x4's" as the first word in the description If she changes it, it's OK with me.

It's there.. just keep thinkin' JD4x4

yw.
I haven't updated it since the newer 1xxx units came out, or after we discovered that the "pipe" chr works on some units. I'll try to do that sometime soon.

EDIT- Ok, either there's something in my coffee or Miss Poi changed the name already! It's listed in the Garmin FAQs as 'Guide to nuvi GPX / CSV display differences' now.