Re Updated POI Loader to V 2.6.0

 

as of January 14, 2011

Change History
Changes made from version 2.5.4 to 2.6.0:

* Added ability to specify a custom POI file's name
* Added ability to handle swapped lat and lon values in CSV files
* Fixed issue with multi-line CSV files not being read correctly
* Fixed issue with extended ASCII characters in CSV files
* Fixed issue with reading large gpx and csv files making the application unresponsive

--
All the worlds indeed a stage and we are merely players. Rush
1 2 3 4
<<Page 5

2.6.0 is the way to go.

charlesd45 wrote:

Even with some of the problems being reported I like the 2.60 released just based on the speed alone ....

That and I also like the ability to name the .gpi file and the way the GUI default names it based on the source folder name.

Although I would have liked the switches I mentioned above, 2.6.0 was also a step in the right direction for the command line mode.

I am keeping it on my computers.

Update POI loader to Vr 2.6

I also had recently updated to ver 2.6 from 2.5.4. As others have noted I too received an error message, not allowing the files to be installed. I was able to notice Directory stream (ie C://computer/desktop/garminpoi) had a change in the naming protocol. It used a [\] instead of the [/] at the end of the sequence as seen in the earlier version. Re installation to version 2.5.4 cured my problems as well. Hope this helps others as well.

Have a great weekend
Tim

--
Edgar Watson Howe: When a friend is in trouble, don't annoy him by asking if there is anything you can do. Think up something appropriate and do it.

Please elaborate

Mr Rooby, I am curious where you are seeing the “change in the naming protocol” and what your problems were.

Seems to be a mix of unix and window's use of forward vs back slashes??

Also, wouldn't "C://computer/desktop/garminpoi " involve the syntax of a path rather than the naming protocol of a data stream?

As far as I can tell

As far as I can tell, the directory shouldn't cause a problem with v2.6.0

The only errors I've found are the ones that I listed in my earlier post but with one correction about field 3 double quotes-

An input error is given If double quotes are used in field 3 (with or without a comma in the field) AND a space exists between the last field 3 double quote and the field 3-4 separator comma.

This sample csv input file may help:
"-94.799018",38.85555,"Record Ignored if first record(s) in file, Otherwise Input Error"
-94.799018,"38.85555","Record Ignored if first record(s) in file, Otherwise Input Error"
-94.799018,38.85555,"Accepted, Example 1"
-94.799018,38.85555,"Accepted; Example 2","My comment, etc"
-94.799018,38.85555,"Accepted; Example 3", "My comment, etc"
-94.799018,38.85555,Accepted; Example 4,"My comment, etc"
-94.799018,38.85555,Accepted; Example 5, "My comment, etc"
-94.799018,38.85555,Accepted; Example 6 ,"My comment, etc"
-94.799018,38.85555,"Partially Accepted, but field 4 Ignored","My comment, etc"
-94.799018,38.85555,"Input Error Example 1" ,"My comment, etc"
-94.799018,38.85555,"Input Error, Example 2" ,"My comment, etc"
-94.799018,38.85555,"Input Error; Example 3" ,"My comment, etc"
"-94.799018",38.85555,"Record Ignored if first record(s) in file, Otherwise Input Error"
-94.799018,"38.85555","Record Ignored if first record(s) in file, Otherwise Input Error"

--
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.

2.6.0 bah humbug

How do I get back to 2.5.4.0?? Too many headaches with new version. Two Nuvi's are failing to "Initialize transfer" at end.

--
73 VE1NPS Nigel

Download here

--
Charlie. Nuvi 265 WT and Nuvi 2597 LMT. Android Here WeGo - Offline Maps & GPS.

CSV Files with Commas

Loaded the new version and had problems creating the poi file from my CSV files. It kept popping up with an error after such and such a line. Did a bit of research and found the new version does not support commas in CSV files. Had to remove all the commas and you know how tedious that can be? Well, I was able to do it quite quickly by using the find and replace function in excel. Find "," (without quotes) and replace with (space). Worked like a charm...

.

Or, just convert to gpx files.

--
nüvi 3790T | nüvi 775T | Those who make peaceful revolution impossible, will make violent revolution inevitable ~ JFK

.

canadianation wrote:

Did a bit of research and found the new version does not support commas in CSV files. Had to remove all the commas and you know how tedious that can be?

No commas, eh? laugh out loud

Just to be clear, the new POI Loader 2.6 will not accept a comma in the POI name (third field). This has been discussed earlier in the thread.

Hopefully it is a bug which Garmin will fix in a future release. In the meantime, POI Factory has implemented a change that will automatically remove any commas in the third field when CSV files are downloaded.

--
DriveAssist 50 (stolen), Nüvi 2595LMT

Will allow Commas .. Sort of

With v2.6.0 (from example above)

Quote:

..
-94.799018,38.85555,"Accepted, Example 1"
..
-94.799018,38.85555,"Partially Accepted, but field 4 Ignored","My comment, etc"

..But

Quote:

An input error is given If double quotes are used in field 3 (with or without a comma in the field) AND a space exists between the last field 3 double quote and the field 3-4 separator comma.

--
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.
1 2 3 4
<<Page 5