PoiLoader 2.6.1

Do you mean that your GPS automatically copies it from the card to the GPS? I put mine on the card for a reason. I am asked if I want to copy it to the GPS when I reboot. I have to say NO every time I reboot. Having to say no every time is a function of the newer GPS units. Since I leave it on the card, there is no referance of it on the GPS.

On my Nuvis, when I choose "Yes" to the question "Would you like to install this data ...." the next screen has a box beside "Don't ask me again".

I tap the box to put a check mark in it and tap "Skip". After that the question does not appear during startup.

My 650 has that. My 1350 does not. There are other units where the 2nd question never comes up. An email to Garmin got a response of "that sounds like a great idea for future enhancements".

on windows 7 with sp1 the new loader does not work, it stays at 2% and hangs out there, nothing wrong with any of my files that i can see all have loaded well with 2.5.4

any ideas??!!

Try an uninstall and reinstall of the new POI loader, I installed it after I put on 7 SP1 and other updates and it worked fine when I used it yesterday

I agree. I installed 2.6.1 after Service Pack 1 and it works for me. So an uninstall and reinstall of 2.6.1 would be the first thing to try.

Now if only I can get my laptop to sleep or hiberbate again after my Service Pack installation

Maybe it is not the "newer" nuvis but rather what series they are?

Most of the 13xx series are described as "Affordable, easy-to-use GPS navigator"

While the 2xx series are described as "Affordable, full-featured navigator".

Other series have descriptions such as "Affordable, feature-packed navigator"

I am thinking it is the "entry level" 13xx series that do not give the option of not asking again.

I just love how certain MS updates "break" some PCs but not others. Luckily, Win7 SP1 did not prevent my laptop from going into or coming out of sleep/hibernate. Sorry for your problem.

When I try to load USA_and_CANADA_ANTIQUE_SHOPSm.csv with either 2.5.4 or 2.6.1 there is an error reported on line 78 and only 77 out of the 3458 POIs are actually loaded.

In the csv file these records are not useable because there is nothing in the name field:

record 78 -93.97820,39.27840,
record 79 -93.88290,39.18550,
record 80 -93.88120,39.18540,
record 81 -94.07440,39.13070,
record 921 -84.87130,41.42940,
record 1048 -75.64400,41.51720,
record 1049 -77.89010,43.22530,

Thanks. I had no problems on my 64-bit desktop but the 32-bit laptop is having some issues. I think I've got Sleep working again. I need to work on Hibernate now. (At least I can install POI files )

was my first thought too, been there done that, no go BUT i have no issues with sleep mode

OK, how about trying 2.6.1 (with Win7 SP1) with a single POI file that we know will work: say the Rest Areas Combined or Redlights? Try it without an associated icon or wav/mp3. That should let us know if your 2.6.1 post SP1 will work at all. If it does, then we can try to work on why your desired multi-file POI load isn't working. Good luck.

One last question. 2.6.1 has several progress bars that appear when loading POIs. Which bar is stuck at 2%?

I'm running Windows 7 32bit with the SP1 update and the new loader version 2.6.1 works fine for me.

I had to copy the sox file to the new install directory for it to work with the wav audio files that my Garmin/Kenwood KNA-G610 built-in Navigation requires to announce camera warnings.

Yet the file would go ahead and transfer with 2.5.4. I went over the file carefully and found several minor errors (which 2.5.4 appparently overlooked/ignored). After I corrected the errors, 2.6.1 quickly transferred the file.

As I read many of these posts, it appears that most of the transfer issues that have come up with version 2.6.1 are related to errors in files or operator error (one of mine was failing to add sox.exe).

Garmin gave us a quick response and, from what I can see, PoiLoader 2.6.1 is a good fix.

Loaded 2.61 and it created a new Garmin folder in program files.Once you click on it you will see the poiloader folder.You will need to put the sox.exe in that folder for the wav files to work for windows.

Money talks...trust me it wasn't just this board but a mass amount of p-offed GPSer's.

Thanks for the info.
Cheers

The actual error is probably on line 77, which screws up line 78.

It is true that sometimes the actual error is in the record just before the one reported by POI Loader, but in this case the errors are in the records I listed. Note that it loaded record 77.

As I mentioned before, the problem is caused by records with no names.

run 2.5.3 on my 350. I have never had a problem with it. My thinking is this; if it is working, don't mess with it.

I'm doing the same thing with my Nuvi 350. I'm using 2.5.4 & it works well. I may check in a month or two to see if 2.6.1, or whatever version exists then, works. So far it only locks up on me with the progress bar at 2% & 10 minutes more to go.

Fred

try the records again without the ending comma

Replacing bad records with worse records IS a weird thought.

I'm not into antiques so I don't have this file BUT, why doessn't someone who uses or has this file give the records a name or delete them. They are not of any use without a name anyway are they? What are they?

Just a thought.

I have no idea what the missing names are.

I tried to convince werskine, the registered maintainer of the csv file, that the records need to be fixed but werskine apparently puts the blame on POI Loader instead of on the csv file, so I guess it will not be fixed.

missed my point, comma separated values file you end with a comma basically saying you have more data but in reality you have none, confuses the program, also expecting 4 values instead of 2

In general, it usually is permissible to have no data in one or more fields in a csv record and the parsing program should not be “confused” by the omission of data after a comma. It could be confused though by not having commas where expected.

However, POI Loader by definition expects data in the first three fields because the GPSr needs to have at least these three in order to correctly list and use the point of interest.

Also by definition POI Loader expects to see three commas even if there is no data in the fourth field. So POI Loader should not be confused by having no data after the comma terminating the third field, if that was presented to it.

Any diversion from that standard format is asking for trouble sooner or later.

I don't see the point of records with no names nor trying to get a major manufactuer to change their ways for a single file. So I guess everyone using this file will have to resolve it their own way.

FZbar said: "In my case 2.5.4 worked fine & installed all my POI files. 2.6.1 locked up & installed none.

That's not what I call reliable software. Garmin should be ashamed of their performance."

I thought I'd give 2.6.1 a try. It balked at a line in Ralph's G Markets in CA. I removed that line and tried again. This time POI Loader hung at 10% f..o..r..e..v..e..r.

I deleted Ralph's G file from my folder and tried again. This time POI Loader balked at a line in the Penzey's Spices file. Everything looked O.K. to me in Excel and Notepad. I deleted the offending line from the file and tried again. The second try it balked at the same line number.

I relooked at the file in Excel and noticed word wrap was indicated as being used in the 4th column. I removed the line break/word wrap formatting in the file and used the pipe (|) for line breaks. The file then loaded fine. I had one more file with issues in the 4th column. It was a file I created with a long narrative in a number of lines. Once I trimmed back the description POI Loader had no problem in loading nearly 80,000 poi.

Only one of my many files caused 2.6.1 to hang. IMHO I think FZbar's issues will be found in the file(s) and not with POI Loader 2.6.1.

-=-=-=-=-=-=-=-=-=-

That's not quite correct.

I have many .csv files that contain line items with only 3 fields and only have 2 commas (no comma after the third field) on the line.

such as (an example of a line item in a .csv file)

-77.095316,38.891004,Home

I have been using them for years and they work just fine.

Gary Hayman
Garmin Tricks and Tips ...

http://bit.ly/garmin_gps_tricks

You may be right about the files being the cause of my problems. If that's the case, waiting until they're fixed might do it for me, but there's no sense for me, at this stage, to be an early adopter.
Thanks.
Fred

I DO do beta work..... But Not with GPS's stuff...

I'm staying put with the POILOADER I have... 2.5.x

Until this all shakes out...

Yes, I know that leaving off the third comma when the fourth field is null has been working. I have seen that situation in lots of files from POI Factory and other places that have Garmin CSV files. Garmin actually shows doing that in some of their examples.

But that is not the standard way of dealing with null fields. A four-field data file should always have three commas in each record even if some of the fields have null values. And if you look at the CSV file syntax definition given by Garmin you will see that none of the commas are included in the square brackets that are used indicate optional items.

There have been several non standard ways of creating Garmin csv files that have been “working ok for several years” and recently have stopped working due to updates of POI Loader, likely by a different programmer who is adhering closer to standard syntax.

But the point I was trying to make with blake7mstr was that having the commas when there are null fields is standard and should not confuse POI Loader. POI Loader reports an error when there is no data after the second comma because that IS an error.

None of this gives support just putting in the coordinates and leaving off the second comma (and the third comma) as suggested by blake7mstr.

That actually sort of works because POI Loader 2.6.1 accepts it and uses the second coordinate as text for a name and the digits as a coordinate. But that is not a name that would properly identify the poi when seen in a Garmin, and is very likely to be seen as an error by a future update of POI Loader because data in the name field is required, not optional.

Again, the required fix for the Antique Shops CSV file is to put some proper text in the name field.

Sage words, Evert.

I think that they are probably a 'word to the wise' and I will plan on using that third comma in future preparations of my 3 field .csv line entries as an ending comma -- just in case.

In analyzing the Garmin's file syntax defination for a .csv line item, as you have pointed out, there are no brackets around the last comma.

Although the lack of a comma still works (when only using 3 fields), I will take positive action and alter my current .csv files for my nuvi plus examine my WEB site's Custom POI area to see if I need to insert the additional comma (if absent).

Thanks for your cogent explanation. You have a convert.

Gary Hayman
Garmin Tricks & Tips

http://bit.ly/garmin_gps_tricks

Problems resulting in csv files not having just the name in column c and other info in column d.Compared to cramming all the info in column c and leaving column d blank for Garmin.Example when traveling I have categories set up on my unit.When I select food or hotels I use the all tab to see what is in the area and make my choice from there.Ones with no names in the column c field you have no idea what it is.Plus the arrival message is based on column c.Excess info gets cut off on the arrival message.Plus some arrival messages would not make much sense if left intact.My work around is to run the files through Extra Poi Editor and use the replace all to put a name in the field and save as a gpx or csv file.GPX if I want to build the alert in and have dialable numbers for Bluetooth.

The new Garmin loader has some flaws
The Garmin tech told me go to the older program
and it works great.

Exactly how far back did the tech say to go. There are no doubt faults in all the older ones, else there would have been no reasons for updates.

Which one has the least faults? And are the old faults better or worse than the new faults.

Did the tech say anything about putting out a revision that will fix all the faults?

2.5.4 works well, right? That was the previous 'latest'.

2.6.1 works well for me but I would like to hear the details that the Garmin tech knows about.

Ok, I'm sort-of with you on the first statement because I thought I had seen that someplace (but now can't find it), and it just makes sense to at least give your points a name.

But, I don't see where there is a definition anywhere that there must be three commas.

Three fields make sense. Since commas separate the fields and EOL ends the record there should be no requirement for more than two commas, imo & experience.

Garmin's examples (at http://www8.garmin.com/products/poiloader/creating_custom_po... ) bear this out as well (note the first example).

Now, some type of content after the second comma and before the EOL is another story altogether.

The Garmin csv file format definition is right above the example you are talking about. It is given following this statement:

(All the characters, including the commas, in a csv file are considered as “text”.)

Note that in the format definition there are four fields. Text is optional in the fourth field, but each record still has four fields even if there is no text in the fourth field.

As I mentioned before, none of the comma separators have square brackets around them, which indicates that the commas are not optional (in other words, all three are required).

And that is standard practice in many of the csv files I have dealt with since about 1968. Once the number of fields is specified there are always that number minus 1 commas in all records even those where the last field is null. This is because the last field has a value even if it is null and needs to have a comma separating it, same as the other comma separated values in the record.

BTW: I mentioned in a prior post that even Garmin gives examples with only two commas when the optional text is omitted in the fourth field. That is inconsistent with their own definition. If they mean for the third comma to be optional, it should be included in the last set of square brackets.

I don't think that implies (see below) that there must be 4 fields, but I agree with your original assertion that there must (should) be at least 3 fields. I recall seeing 3 fields minimum in Garmin documentation somewhere, but I quickly looked and didn't find either 3 or 4 fields minimum stipulated on Garmin's site or help files.

I submit to you that though the format syntax example appears to be a definition, I wouldn't necessarily say that. Rather, I take it it to show Garmin's acceptable field content format (not csv file delimiter format), and it's also contradicted by the same authority in the sample entry format examples in the same section.

I too have used delimited formats since pre-Windows days, and early on software acceptance of delimited formats varied wildly (as they still do). Eventually, we now have some de-facto delimited file standards that are not 'exactly' standards (a definition issued by an authoritative body).

However, I've never seen software that would not put the text "blah" in the 3rd field (of whatever) if the CSV input line were:

,,blah<eol>

In what application would that not work?

In the CSV line below however,
,,blah,<eol>
The fourth field would theoretically be the value null, which is er, nothing. Hard to say where someone's software puts nothing, and harder to prove.

Regardless, it is what it is. Until it isn't anymore.

I agree with you Fred. There's really no reason for anyone to be an early adopter or changing from 2.5.4 or earlier other than wanting "the latest and [?]greatest" and expecting it to work. v2.5.4 seemed to work well. Why did Garmin see a need to change it?

But having said that, 2.6.1 seems to indicate we have some "bad" files coming out of the Factory. Most files worked when initially created. Others got massaged to make them work. Apparently some workarounds or "make it pretty" techniques irritate 2.6.1 causing the rejection and hangs. What's one to do?

2.6.1 works well with my file selection so I'll keep it. For others I'd recommend keeping their current version of POI Loader unless they are prepared to clean up or delete some files as necessary for a clean load.

POI loader 2.6.0 and now 2.6.1 do have issues with some of the files. We all know that. If those that use early versions want to stay in the dark, then so be it. There are reasons to upgrade to the latest. To name a couple. You can name the gpi file, and it shows a progress bar. It is also allowing the maintainers to correct some files.
Unfortunately there are some maintainers that have absolutely no clue about what is even close to proper format and just throw a file up there. There are others that do not even verify the file, and there are maintainers that have no way to be contacted so the file can be corrected.
These are the files that need to be corrected and/or taken down till they are corrected. They could also be given to some one who cares. But doing this will most likely "step" on someones toes and they will have "hurt feelings".

I never said that would not work. I said that POI Loader would expect (not demand) 3 commas and thus would not give an error if the third comma with no data after it were encountered in a csv file.

In the C programs I wrote to parse csv files, my data structure was designed based on the defined number of fields. I put the data from each field in a nul terminated string. Thus the strings representing the data in the first, second, and fourth fields of your example record would have only the nul character.
So in those fields “nothing” would be represented by “something” and that something is the nul character.

Another way of saying this is that when a data base is defined to have four fields, the fields are always there whether or not there is any data in them.

Poi Loader does accept csv records in both of these forms:

long,lat,foo,
long,lat,bar

The first because it is the expected format.
The second because it went through additional logic to deal with hitting end of line without finding the third comma.

It's the files that have issues. Granted 2.6.0 did have a parsing error which was corrected, the the speed at which the new versions convert files is almost reason enough to upgrade. For those doubters, try 7 times faster.

You are correct! I should have clarified that better. I kinda did further down when I mentioned "It is also allowing the maintainers to correct some files", but I was not really clear.

And...yes, the speed of loading has greatly incresed!

Great for them,now if they can step up and get their POI's and maps corrected quicker.

Much better than the older versions.

Liked that you can name the gpi files. I store all my files in separate subfolders on my computer and on my SD card. I may have more than one file in a folder, but it's nice to have the gpi named. It picks up the name of my subfolder automatically.

Also like that it retains the target subfolder. It was always such a pain, when I had to browse all the wa7y through the various subfolders before I could load.

I did find that I had to delete the poi.gpi file in each up my sd card subfolders, but that was only for the first install. After that it was easy.

I like that it saves the folder locations and that you can name the gpi file. The naming the file is especially important to me because I compile every file individually to a hard drive folder.

I do this because I routinely like to change the display order in the Custom POIs by deleting them off the SD card sub-folder and dragging them back in, in the order I want them to display.

When I see a file I use is updated I download and compile it immediately so it is ready when I copy the files to the GPS SD card the next time.

This also helps when compiling since I only do 1 file at a time. I have had 2 csv files fail while compiling, it gave me the line numbers, went in and fixed 'em, then recompiled.

Whether I'm traveling for work in the car or on the Harley I load different files at the top of the list to eliminate scrolling.

So the new POI Loader saves me a lot of time with its new features. Besides, this is an addiction so I have to feed it, change it, reorder it, play with it, etc.