Re Updated POI Loader to V 2.6.0

I downloaded and installed the new poi loader and now can't use hardly any of my poi's I have allready downloaded... been trying now for like 4 hours to find and download the earlier version of poi loader, does anyone know where I can go to download the old version of poi loader

Thanks
Darrell

http://www.gawisp.com/perry/POILoaderforWindows_254.exe

http://gawisp.com/perry/

You want the 11.9MB Oct. 14 2009 POILoaderForWindows version.

http://www.gawisp.com/perry/

scroll down the page a bit.

http://gawisp.com/perry/
Go to POILOADERforWINDOWS 14 OCT 2009

Did anybody mentioned:

http://gawisp.com/perry/
Go to POILOADERforWINDOWS 14 OCT 2009

Oh yeah! 3 times... LOL!

No one will every accuse the POI Factory of not being helpful LOL

But it does bring up a point.

Ms. POI does Drupal have a function to advise a poster that a previous comment has been submitted while he / she is composing a response?

Just curious Turbo if any files that were made using EPE and saved as Garmin GPX, then after the files is finished and a copy was saved as Garmin CSV, would these CSV files be affected by this problem???

Yes the spaces outside the quotes in field 3 causes an error.

Example:

This works:

-71.107665,42.834129,"Singer Subaru LLC ","77 Plaistow Road
Plaistow, NH 03865
(603) 382-7101"

This does not work:

-71.107665,42.834129, "Singer Subaru LLC " ,"77 Plaistow Road
Plaistow, NH 03865
(603) 382-7101"

But this also works:
-71.107665,42.834129, Singer Subaru LLC , "77 Plaistow Road
Plaistow, NH 03865
(603) 382-7101"

Note the space outside the comma in field 4 does not cause an error.

Thanks Garmin! I can see myself explaning this to everybody now... Not!

At least, there is a workaround.... I guess...

@trubocc: Please note that at 9:32am today, I responded that the spaces had no effect on whether or not your file loaded on my 255.

The issue appears to be that there was no "-" in front of the value in column 1. I corrected the format and the file loaded.

I just confirmed again that [-10.222, 22.333, "POI Name", "bla bla"] (without the parentheses) will load in my 255, spaces and all.

selfruler

turbocc had mentioned a space before and after the quotes. I think it is a space after the quote.

Try this version:

-10.222, 22.333, "POI Name" , "bla bla" (space before and after)

and this version:

-10.222, 22.333,"POI Name" , "bla bla" (space after)

Neither of those work with 2.6.0

But this one does:

-10.222, 22.333, "POI Name", "bla bla" (space before no space after)

BTW I am loading the .gpi file to my computer so the above results are independent of the model of the garmin.

DID fully load CSV files with spaces on a Garmin nuvi 255.

I used the file as turboccc posted it earlier: 10.222, 22.333, "POI Name", "bla bla" (notice the spaces after each comma). It appears that I may not have been as careful this morning when I was not able to confirm loading.

Tonight, I even added 5 spaces at the beginning of each and every column. Version 2.6.0 loaded the file without issue.

There are indeed appear to be conflicting results as evem multiple spaces have no noticeable effect on a CSV file loaded by 2.6.0 on my nuvi 255.

Note: On a whim before I posted this comment, I placed 50 spaces before each column for a total of 200 spaces. Even this large number of spaces had no noticeable effect on how 2.6.0 loaded the file on the 255.

Tested my files, and no problems found with POI Loader 2.6.0.

Despite that, I think that the problems with commas are the reintroduction of a bug that Garmin fixed with 2.5.4. In my opinion though, a dash would be a better separator than a semicolon, especially if preceded and followed by a space.

Re: Installation.

I installed 2.6.0 on top of 2.5.4 and not only did it find the POI Loader directory (C:/Garmin) it successfully updated the files there. I'm curious if those people who had problems with the install uninstalled 2.5.4 before installing 2.6.0.

When I installed 2.6.0 it uninstalled what I had for 2.5.4 located in C:/Garmin and installed 2.6.0 in C:/Program Files/Garmin.

So it looks like the following can be said about using quotes in field 3 of a csv record when using poiloader 2.6.0:

Within the commas delimiting the field, you may have one or more spaces before the opening quote but must not have any spaces after the closing quote.

You must not put a comma between the quotes.

When I installed 2.60 it installed same place 2.54 was.

So it looks like the following can be said about using quotes in field 3 of a csv record when using poiloader 2.6.0:

Within the commas delimiting the field, you may have one or more spaces before the opening quote but must not have any spaces after the closing quote.

You must not put a comma between the quotes.

Thanks very much. 2.5.4 successfully installed my custom POIs. It's clear that 2.6 has lots of bugs. I'll stick with the "old" version for the time being.

I finally mustered up enough courage to download POI Loader v2.6.0, and here’s a recap of what I’ve found:

1. After bringing up V2.5.4 and right-clicking on the title bar, then “Check for Software Updates…”, I get “There are no software updates currently available for POILoader.”
2. Then, upon going to www8.garmin/support/download.jsp , then in left column, “POI Loader for Windows 2.6.0 (January 14, 2011), I downloaded & installed the loader. As someone previously stated – they may still be working on this version.
3. The old version was installed as/in “C:Garmin/POILoader.exe”, and the new version (2.6.0) was installed as/in: "C:\Program Files (x86)\Garmin\PoiLoader.exe", with no problems encountered.
4. Upon running the new version & after finding your unit, a new option is immediately available – “Choose a name for the newly created custom POI file:”, with the default choice of “Documents”. This may tend to confuse some people, not realizing that the loader puts all of your files, however many, into only one gpi file within the GPS. If you use the default “Documents” name, the resulting name of the finished file in your GPS will be “Documents.gpi”. Upon subsequent loading of csv files, the program will create a different gpi file if you choose, or overwrite the “Documents.gpi” file if you agree. If another file name is chosen, however, this may be the reason for seemingly different results at different times, bringing up previous trials.
5. After creating different scenarios for the Name Column 3, I found that both commas and pipe (|) symbols cause the Description Column 4 (with addresses & other info) to disappear entirely.
6. I found that using Excel or Open Office Calc, there is no need to use quotes in column 3 at all. Normally, since this is the Name column, there will be no requirement for line breaks in this column, as multi-word Names of your locations will be automatically word-wrapped in your GPS (probably for most models).
7. I have never used quotes even in column 4 either, because of the use of Pipe (|) line breaks which work in most units and can be very easily edited to use in other models of GPS units. (Different models of GPS units require different types of line breaks). Of course I have also never used Notepad for creating files, and I have never had a complaint concerning format.
8. Bottom line: If we never use quotes in a csv file & never use commas or pipe symbols in column 3, then version 2.6.0 may work very well indeed. But then again, I’m still learning.

No need to use quotes in Excel because quotes are automatically added by Excel on saving when a column contains commas (and probably line break`s).

This may explain why you do not use them. It may be interesting to know if Excel adds a space before/after the comma delimiter.

that once again it appears that Garmin has put out new software that is a step backwards. I will sit on the sidelines until more positive feedback comes in.

[/quote]
So it looks like the following can be said about using quotes in field 3 of a csv record when using poiloader 2.6.0:

Within the commas delimiting the field, you may have one or more spaces before the opening quote but must not have any spaces after the closing quote.

You must not put a comma between the quotes.
[/quote]

First of all, let me say that I've never seen a company more uncaring about their customers than Garmin. If everything in this thread that I've read about Garmin's response to the problems in their loader is true, then shame on them. Talk about a terrible way to treat their customers...

Now, having said that, I think it's completely reasonable for code-writers to demand that certain SYNTAX rules be followed in order to use a program. Allowing spaces or not allowing spaces before or after quotes is up to the standards of the program. It would be nice if a program allowed free-form syntax, but if not, so what? If a program demands exact syntax, then it's up to us to learn the rules and then follow them. Completely reasonable.

Now, having said THAT, it'd be nice if Garmin actually told us what the rules are. That's the thing that ticks me off.

Just checked my version and had 2.5.2.

When I clicked on Update, it gave me the opportunity of updating to 2.5.4.0

Once 2.5.4 was installed I checked again for an update and was informed I was up to date.

I did read the comment where another person was able to go to garmin's site and find 2.6 available for download.

Would that suggest that Garmin has possibly changed the status of 2.6 pending further study.

Thanks! Just downloaded!

I am beginning to believe that maybe the people at Garmin aren't really sure what the rules are themselves.

Aren't you supposed to make the rules up as you go along?????

Have not gotten an error message yet.

It all depends on what files you are using.
Comments are that GPX works. There are also csv files that are correct. Most errors I have seen are just mistakes in the 3rd column where commas got in inadvertently.

Some commas in the Name column 3 are perfectly normal and natural such as:
- XYZ Company, LLC
- ABC Company, Inc.
- LMN Company – Springfield, OH
- LMN Company – Springfield, MA
- LMN Company – Springfield, MO

They may be perfectly normal and natural BUT poi loader 2.6.0 will error out when you use it.
That is what all the discussion is about.

Is the update for Mac, Windows or both? Thanks.

It's 2.2.0 for MAC and 2.6.0 for PC.

To pwohlrab: My last post above was made with the hope that Garmin would be watching and recognize that we still need the occasional use of a comma – for good looks, if nothing else!

On a 4-column CSV it will error out. On a 3-column CSV the quotations and the comma don't cause a problem, if my test with my Postal Codes file proves anything.

Nevertheless, Garmin changing the rules makes life difficult for POI creators.

whoaboy, we may be among the few who still fully appreciate the good look that results when the comma is correctly used.

In addition to the examples you posted, I still like commas in my numbers: for example: 1,000. However, the electronic generation may not agree. If you do a Google search for "1,000" or "100,000", you won't find commas in numbers in the result list. You will just find "1000" or "100000".

You are correct. There are legitimate and necessary uses for the occasional comma, even in the name of a file. Also, there is no apparent reason why Garmin would intentionally allow the use of virtually unlimited commas in column 4 of csv files but not allow the use of even one comma in column 3 (inside double quotes, of course).

All things considered, I believe Garmin goofed when it unintentionally eliminated the use of all commas inside of double quotes in column 3 of csv files and will issue an update.

I just tried 2.6.0. and as someone stated, commas seem to be okay in the forth column and not the third.

Another problem that popped up was that it failed to copy my wav file over to the gps. It said it was unable to convert it. Same wav file that worked with ver 2.5.4. The file name is three words with spaces between the words which matches the POI file.

Forgot to move sox.exe into the new folder.

Should work now.

I, too, am having problems with the 2.6.0 loader. In particular, line 24 New Brunswick 2 meter repeaters and I-95 speed traps .csv invalid. Going back is one solution but updating 2.6.0 makes more sense.ASAP.
Best Regards,
VE1NPS Nigel

I agree

Are there other data files in the folder you used for POI loader input?

When I run 2.6 with both files you mention, 6409 POIs are loaded with no errors. My hunch is there is some other file in the input folder which is causing the error.

I had a similar experience with the Mac version 2.2 just released. Went back to 2.1 and all works OK again.

I am with you.. Why screw with something when the software is working flawlessly.. Never had an issue with this version

Maybe you have an earlier file? I tried both files (but downloaded after your post) and got no errors either (v2.6.0 on Win XPsp3), although I did notice that semicolons were in the file field 3 where there might have previously been commas.

Earlier I posted that I had asked a Garmin software developer if he thought the v2.6.0 field 3 changes were intentional or an error. No reply so far (imagine that) but I've done some tests and I can't imagine that all of the 'anomolies' were intentional! I posted this on the Garmin forum site as well-

Errors I've found so far with csv file field formatting in v2.6.0:

Errors shown on input (during parsing):

• Field 3- When a chr(10) is used (within or without double-quotes)
• Field 3- When a comma is used within double-quotes and a space exists between the trailing (last) double-quote and the comma between field 3 and 4. (Does not occur if the record contains only 3 fields since the chr after the trailing space is EOL rather than a comma?)
• Fields 1 and 2- When fields are double-quoted and are not the first record(s) in the file (see writing errors below)

Record writing errors (with no program error given):

• Field 3- When a space exists between the trailing (last) double-quote and comma but no comma exists within the double-quotes the entire record will be ignored
• Field 3- When a comma is used within double-quotes the next field will not be written
• Fields 1 and 2- If double-quoted no input error is given for the first consecutive occurences (must be the first line(s) of the file) but the entire record will be ignored. If valid records preceed double-quoted fields 1 and 2 then an input error will be given.
• Records following a blank line (0D-0A EOL) will be ignored with no error shown

I feel for them since I've tried to think of all of the possible file format variations, and it's more than 1500. Needless to say I haven't tested them all!

Looking forward to a new release? (soon??)

.. Although on the positive side of v2.6.0 .. gpx files work fine, and the command line switches have been fixed.

Good catch @JD4x4. JM put this change in effect on 1/27.

@VE1NPS, did you download the files before then?

I see now the command line silent mode has the following choice of switches:

/s /u UsbUnitId to run in silent mode and send poi.gpi to a Garmin unit.
or
/s /d “DIRECTORY” to run in silent mode and send poi.gpi to a folder on a hard drive, flash drive, SD card etc.

I think there should have been a switch so that the .gpi file could be given a “Custom Name” similar to what can be done in GUI mode. (Command line mode does not recognize a previous custom name used in GUI mode.)

Thanks for pointing out that it's poi.gpi that the /d switch works on. I don't think that's mentioned anyplace obvious.

Agree with your other comments, and would add that it would be great if you could specify the input folder as well, not just operating on the last used GUI folder. Then we could make multiple specific custom batch files.

To be more similar to GUI mode, CL mode should default the .gpi name to the source folder name.

And there should be a switch to specify a source folder other than the last one used in GUI mode.

Even with some of the problems being reported I like the 2.60 released just based on the speed alone it now loads the files.I was lucky all the files I use loaded the first time I tried it.Tried some of the files reported with the problems with same results.Don't really see that much trouble to make a few changes in column 3 or c.