POI File Generation Failure when Input Contains Special Characters

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

POI File Generation Failure when Input Contains Special Characters

ypna
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

GC_CH_Tests.zip (252K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

tsteven4-2
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve

On 8/29/2014 3:20 PM, [hidden email] wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/


_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

test.style (408 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

tsteven4-2
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.

On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve

On 8/29/2014 3:20 PM, [hidden email] wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/


_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc



------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

ypna
Good evening Steve
 
That is what I call “just in time”! I read your first answer earlier today and I started to put together a new test bed. Returning from a peaceful evening walk I dreaded the thought to run through the different scenarios all night, still unsure whether it would work or not.
 
Now I do at least know that it probably will not ;-) Your suggestion about my input not being UTF-8 has triggered another mini project, though.
 
As for the POI file, I might just scan through the input, convert the umlaut characters and nuke the rest.
 
Also, I find the idea with the style file quite charming. I had noticed it in the documentation but with your working sample I feel a lot more comfortable (basically, I prefer trial and error over RTFM ;-)
 
Many thanks for your help!
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 16:28 Uhr
Von: tsteven4 <[hidden email]>
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.
 
On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve
 
On 8/29/2014 3:20 PM, ypna@... wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

tsteven4-2
Peter,

To get the style file to work you will need to get rid of the quotes in GC_CH.gpi.txt.  Then you should be able to convert to gpx as I outlined.  Then you can try to convert the gpx to gpi using the garmin poi loader.  I suspect if you do this last step in gpsbabel we won't convert the character strings correctly.

Steve
On 8/30/2014 12:39 PM, [hidden email] wrote:
Good evening Steve
 
That is what I call “just in time”! I read your first answer earlier today and I started to put together a new test bed. Returning from a peaceful evening walk I dreaded the thought to run through the different scenarios all night, still unsure whether it would work or not.
 
Now I do at least know that it probably will not ;-) Your suggestion about my input not being UTF-8 has triggered another mini project, though.
 
As for the POI file, I might just scan through the input, convert the umlaut characters and nuke the rest.
 
Also, I find the idea with the style file quite charming. I had noticed it in the documentation but with your working sample I feel a lot more comfortable (basically, I prefer trial and error over RTFM ;-)
 
Many thanks for your help!
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 16:28 Uhr
Von: tsteven4 [hidden email]
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.
 
On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve
 
On 8/29/2014 3:20 PM, ypna@... wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/


_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

tsteven4-2
In reply to this post by ypna
This modified style file handles the quotes so you don't have to remove them.

On 8/30/2014 12:39 PM, [hidden email] wrote:
Good evening Steve
 
That is what I call “just in time”! I read your first answer earlier today and I started to put together a new test bed. Returning from a peaceful evening walk I dreaded the thought to run through the different scenarios all night, still unsure whether it would work or not.
 
Now I do at least know that it probably will not ;-) Your suggestion about my input not being UTF-8 has triggered another mini project, though.
 
As for the POI file, I might just scan through the input, convert the umlaut characters and nuke the rest.
 
Also, I find the idea with the style file quite charming. I had noticed it in the documentation but with your working sample I feel a lot more comfortable (basically, I prefer trial and error over RTFM ;-)
 
Many thanks for your help!
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 16:28 Uhr
Von: tsteven4 [hidden email]
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.
 
On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve
 
On 8/29/2014 3:20 PM, ypna@... wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/


_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

test.style (420 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

tsteven4-2
In reply to this post by ypna
Here is a style file that handles the quotes in your input, unlike my fist attempt.

On 8/30/2014 12:39 PM, [hidden email] wrote:
Good evening Steve
 
That is what I call “just in time”! I read your first answer earlier today and I started to put together a new test bed. Returning from a peaceful evening walk I dreaded the thought to run through the different scenarios all night, still unsure whether it would work or not.
 
Now I do at least know that it probably will not ;-) Your suggestion about my input not being UTF-8 has triggered another mini project, though.
 
As for the POI file, I might just scan through the input, convert the umlaut characters and nuke the rest.
 
Also, I find the idea with the style file quite charming. I had noticed it in the documentation but with your working sample I feel a lot more comfortable (basically, I prefer trial and error over RTFM ;-)
 
Many thanks for your help!
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 16:28 Uhr
Von: tsteven4 [hidden email]
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.
 
On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve
 
On 8/29/2014 3:20 PM, ypna@... wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/


_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

test.style (432 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

ypna
Thank you very much Steve!
 
I already resorted to the lowest common denominator on this one.
 
I adapted my program generating the input file to do so in US-ASCII format, thereby getting rid of everything GPSBabel does not seem to correctly process for the garmin-poi option.
With this approach, I can use my original command without the need for a style file. I do, of course, lose all the fancy characters used around the world.
 
I will keep your style file for future reference! I prefer GPSBabel over the Garmin POI Loader.
I had used the Garmin POI Loader in in the past, directly generating an input file without using GPSBabel. I just looked at the code now… it contains hundreds of statements to translate all sorts of characters, because the Garmin POI Loader is of course equally picky ;-)
 
In case it helps somebody: my program is written in ObjectREXX (without the objects). The code to convert the input looks as follows:
 
  /*------------------------------------------------------------------*/
  /*  1252 - ANSI Latin 1; Western European (Windows)                 */
  /* 20127 - US-ASCII 20127                                           */
  /* 65001 - Unicode (UTF-8)                                          */
  /*------------------------------------------------------------------*/
  RC = SysToUnicode(NewLine, "UTF8", , utf8.)
  If RC = 0 Then Do
    RC = SysFromUnicode(utf8.!TEXT, "20127", , , ascii.)
    If RC = 0 Then Do
      NewLine = ascii.!Text
    End
    Else Do
      Say 'Convert UTF16 to 20127 failed. RC:' RC
    End
  End
  Else Do
    Say 'Convert UTF8 to UTF16 failed. RC:' RC
  End
  /*------------------------------------------------------------------*/
 
Newline contains a UTF-8 line read from the input byte by byte. The line is converted to US-ASCII and output to the file used to generate the POI database.
 
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 22:35 Uhr
Von: tsteven4 <[hidden email]>
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
Here is a style file that handles the quotes in your input, unlike my fist attempt.
 
On 8/30/2014 12:39 PM, ypna@... wrote:
Good evening Steve
 
That is what I call “just in time”! I read your first answer earlier today and I started to put together a new test bed. Returning from a peaceful evening walk I dreaded the thought to run through the different scenarios all night, still unsure whether it would work or not.
 
Now I do at least know that it probably will not ;-) Your suggestion about my input not being UTF-8 has triggered another mini project, though.
 
As for the POI file, I might just scan through the input, convert the umlaut characters and nuke the rest.
 
Also, I find the idea with the style file quite charming. I had noticed it in the documentation but with your working sample I feel a lot more comfortable (basically, I prefer trial and error over RTFM ;-)
 
Many thanks for your help!
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 16:28 Uhr
Von: tsteven4 <tsteven4@...>
An: ypna@..., gpsbabel-misc@...
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.
 
On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve
 
On 8/29/2014 3:20 PM, [hidden email] wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

tsteven4-2
Peter,

I know you resolved your issue, but I would like to ask you if the following file resolves it as well.  I am testing a modification to the garmin_gpi writer and reader to use the windows code pages it seems to prefer, by default Windows-1252.
My test script is quoted below.  I didn't have GC.bmp so I skipped that option.  At this time the unicsv reader assumes UTF-8, so I converted your file from Windows-1252 to UTF-8.  Then I read this file and output a garmin_gpi file using Windows-1252, GC_CH.gpi. 
1. Is GC_CH.gpi loadable on your device, i.e. does it show up in the extras list of POI databases?
Then I converted this gpi file back to unicsv.  Unfortunately the output is not directly comparable due to new fields in the output and the order of the output.
#!/bin/bash
iconv -f CP1252 -t UTF8 GC_CH.gpi.txt  > GC_CH.utf8.gpi.txt
./gpsbabel -i unicsv -f GC_CH.utf8.gpi.txt -o garmin_gpi,sleep=1,category="GC_CH" -F "GC_CH.gpi"
./gpsbabel -i  garmin_gpi -f GC_CH.gpi -o unicsv -F GC_CH_roundtrip.txt
Thanks,
Steve

On 8/30/2014 3:02 PM, [hidden email] wrote:
Thank you very much Steve!
 
I already resorted to the lowest common denominator on this one.
 
I adapted my program generating the input file to do so in US-ASCII format, thereby getting rid of everything GPSBabel does not seem to correctly process for the garmin-poi option.
With this approach, I can use my original command without the need for a style file. I do, of course, lose all the fancy characters used around the world.
 
I will keep your style file for future reference! I prefer GPSBabel over the Garmin POI Loader.
I had used the Garmin POI Loader in in the past, directly generating an input file without using GPSBabel. I just looked at the code now… it contains hundreds of statements to translate all sorts of characters, because the Garmin POI Loader is of course equally picky ;-)
 
In case it helps somebody: my program is written in ObjectREXX (without the objects). The code to convert the input looks as follows:
 
  /*------------------------------------------------------------------*/
  /*  1252 - ANSI Latin 1; Western European (Windows)                 */
  /* 20127 - US-ASCII 20127                                           */
  /* 65001 - Unicode (UTF-8)                                          */
  /*------------------------------------------------------------------*/
  RC = SysToUnicode(NewLine, "UTF8", , utf8.)
  If RC = 0 Then Do
    RC = SysFromUnicode(utf8.!TEXT, "20127", , , ascii.)
    If RC = 0 Then Do
      NewLine = ascii.!Text
    End
    Else Do
      Say 'Convert UTF16 to 20127 failed. RC:' RC
    End
  End
  Else Do
    Say 'Convert UTF8 to UTF16 failed. RC:' RC
  End
  /*------------------------------------------------------------------*/
 
Newline contains a UTF-8 line read from the input byte by byte. The line is converted to US-ASCII and output to the file used to generate the POI database.
 
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 22:35 Uhr
Von: tsteven4 [hidden email]
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
Here is a style file that handles the quotes in your input, unlike my fist attempt.
 
On 8/30/2014 12:39 PM, ypna@... wrote:
Good evening Steve
 
That is what I call “just in time”! I read your first answer earlier today and I started to put together a new test bed. Returning from a peaceful evening walk I dreaded the thought to run through the different scenarios all night, still unsure whether it would work or not.
 
Now I do at least know that it probably will not ;-) Your suggestion about my input not being UTF-8 has triggered another mini project, though.
 
As for the POI file, I might just scan through the input, convert the umlaut characters and nuke the rest.
 
Also, I find the idea with the style file quite charming. I had noticed it in the documentation but with your working sample I feel a lot more comfortable (basically, I prefer trial and error over RTFM ;-)
 
Many thanks for your help!
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 16:28 Uhr
Von: tsteven4 <tsteven4@...>
An: ypna@..., gpsbabel-misc@...
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.
 
On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve
 
On 8/29/2014 3:20 PM, [hidden email] wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/


_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

GC.zip (435K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

ypna
Hi Steve
 
Sorry for the delay in getting back to you. The short answer is: where can I buy your solution?? Not only do the POIs show up on the GPS, the descriptions also seem to retain the umlaut characters (I found one ä and one ö).
Congratulations and thanks a lot for your efforts!
 
Peter from team YPNA
 
Gesendet: Donnerstag, 18. September 2014 um 23:55 Uhr
Von: tsteven4 <[hidden email]>
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
Peter,

I know you resolved your issue, but I would like to ask you if the following file resolves it as well.  I am testing a modification to the garmin_gpi writer and reader to use the windows code pages it seems to prefer, by default Windows-1252.
My test script is quoted below.  I didn't have GC.bmp so I skipped that option.  At this time the unicsv reader assumes UTF-8, so I converted your file from Windows-1252 to UTF-8.  Then I read this file and output a garmin_gpi file using Windows-1252, GC_CH.gpi. 
1. Is GC_CH.gpi loadable on your device, i.e. does it show up in the extras list of POI databases?
Then I converted this gpi file back to unicsv.  Unfortunately the output is not directly comparable due to new fields in the output and the order of the output.
#!/bin/bash
iconv -f CP1252 -t UTF8 GC_CH.gpi.txt  > GC_CH.utf8.gpi.txt
./gpsbabel -i unicsv -f GC_CH.utf8.gpi.txt -o garmin_gpi,sleep=1,category="GC_CH" -F "GC_CH.gpi"
./gpsbabel -i  garmin_gpi -f GC_CH.gpi -o unicsv -F GC_CH_roundtrip.txt
Thanks,
Steve
 
On 8/30/2014 3:02 PM, ypna@... wrote:
Thank you very much Steve!
 
I already resorted to the lowest common denominator on this one.
 
I adapted my program generating the input file to do so in US-ASCII format, thereby getting rid of everything GPSBabel does not seem to correctly process for the garmin-poi option.
With this approach, I can use my original command without the need for a style file. I do, of course, lose all the fancy characters used around the world.
 
I will keep your style file for future reference! I prefer GPSBabel over the Garmin POI Loader.
I had used the Garmin POI Loader in in the past, directly generating an input file without using GPSBabel. I just looked at the code now… it contains hundreds of statements to translate all sorts of characters, because the Garmin POI Loader is of course equally picky ;-)
 
In case it helps somebody: my program is written in ObjectREXX (without the objects). The code to convert the input looks as follows:
 
  /*------------------------------------------------------------------*/
  /*  1252 - ANSI Latin 1; Western European (Windows)                 */
  /* 20127 - US-ASCII 20127                                           */
  /* 65001 - Unicode (UTF-8)                                          */
  /*------------------------------------------------------------------*/
  RC = SysToUnicode(NewLine, "UTF8", , utf8.)
  If RC = 0 Then Do
    RC = SysFromUnicode(utf8.!TEXT, "20127", , , ascii.)
    If RC = 0 Then Do
      NewLine = ascii.!Text
    End
    Else Do
      Say 'Convert UTF16 to 20127 failed. RC:' RC
    End
  End
  Else Do
    Say 'Convert UTF8 to UTF16 failed. RC:' RC
  End
  /*------------------------------------------------------------------*/
 
Newline contains a UTF-8 line read from the input byte by byte. The line is converted to US-ASCII and output to the file used to generate the POI database.
 
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 22:35 Uhr
Von: tsteven4 <tsteven4@...>
An: ypna@..., gpsbabel-misc@...
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
Here is a style file that handles the quotes in your input, unlike my fist attempt.
 
On 8/30/2014 12:39 PM, [hidden email] wrote:
Good evening Steve
 
That is what I call “just in time”! I read your first answer earlier today and I started to put together a new test bed. Returning from a peaceful evening walk I dreaded the thought to run through the different scenarios all night, still unsure whether it would work or not.
 
Now I do at least know that it probably will not ;-) Your suggestion about my input not being UTF-8 has triggered another mini project, though.
 
As for the POI file, I might just scan through the input, convert the umlaut characters and nuke the rest.
 
Also, I find the idea with the style file quite charming. I had noticed it in the documentation but with your working sample I feel a lot more comfortable (basically, I prefer trial and error over RTFM ;-)
 
Many thanks for your help!
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 16:28 Uhr
Von: tsteven4 <[hidden email]>
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.
 
On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve
 
On 8/29/2014 3:20 PM, [hidden email] wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

------------------------------------------------------------------------------
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

tsteven4-2
Here is the style file, the previous file was the wrong one with the right name.

On 9/27/2014 1:21 PM, tsteven4 wrote:
Peter,

I ran into some unexpected trouble under Mac OS X, but I think that is fixed now.  We have lots more work to do on encoding, but your issue should be fixed in
https://code.google.com/p/gpsbabel/source/detail?r=4904
With this revision you can do the windows-1252 conversion in gpsbabel (without iconv), but it requires a custom style file.  With it a command like
./gpsbabel -i xcsv,style=ypna.style -f GC_CH.gpi.txt -o garmin_gpi,sleep=1,category="GC_CH" -F "GC_CH.gpi"
should work.
I attached the style file.  We may or may not do something to eliminate the need for the style file in the future.  Alternatively you can continue to use the method I outlined previously.

To use this revision you will have to build code from source.  If you cannot do that you will need to wait for the next release.  If you want to buy something you can make a donation at
http://www.gpsbabel.org/

Steve


On 9/20/2014 3:51 PM, [hidden email] wrote:
Hi Steve
 
Sorry for the delay in getting back to you. The short answer is: where can I buy your solution?? Not only do the POIs show up on the GPS, the descriptions also seem to retain the umlaut characters (I found one ä and one ö).
Congratulations and thanks a lot for your efforts!
 
Peter from team YPNA
 
Gesendet: Donnerstag, 18. September 2014 um 23:55 Uhr
Von: tsteven4 [hidden email]
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
Peter,

I know you resolved your issue, but I would like to ask you if the following file resolves it as well.  I am testing a modification to the garmin_gpi writer and reader to use the windows code pages it seems to prefer, by default Windows-1252.
My test script is quoted below.  I didn't have GC.bmp so I skipped that option.  At this time the unicsv reader assumes UTF-8, so I converted your file from Windows-1252 to UTF-8.  Then I read this file and output a garmin_gpi file using Windows-1252, GC_CH.gpi. 
1. Is GC_CH.gpi loadable on your device, i.e. does it show up in the extras list of POI databases?
Then I converted this gpi file back to unicsv.  Unfortunately the output is not directly comparable due to new fields in the output and the order of the output.
#!/bin/bash
iconv -f CP1252 -t UTF8 GC_CH.gpi.txt  > GC_CH.utf8.gpi.txt
./gpsbabel -i unicsv -f GC_CH.utf8.gpi.txt -o garmin_gpi,sleep=1,category="GC_CH" -F "GC_CH.gpi"
./gpsbabel -i  garmin_gpi -f GC_CH.gpi -o unicsv -F GC_CH_roundtrip.txt
Thanks,
Steve
 
On 8/30/2014 3:02 PM, ypna@... wrote:
Thank you very much Steve!
 
I already resorted to the lowest common denominator on this one.
 
I adapted my program generating the input file to do so in US-ASCII format, thereby getting rid of everything GPSBabel does not seem to correctly process for the garmin-poi option.
With this approach, I can use my original command without the need for a style file. I do, of course, lose all the fancy characters used around the world.
 
I will keep your style file for future reference! I prefer GPSBabel over the Garmin POI Loader.
I had used the Garmin POI Loader in in the past, directly generating an input file without using GPSBabel. I just looked at the code now… it contains hundreds of statements to translate all sorts of characters, because the Garmin POI Loader is of course equally picky ;-)
 
In case it helps somebody: my program is written in ObjectREXX (without the objects). The code to convert the input looks as follows:
 
  /*------------------------------------------------------------------*/
  /*  1252 - ANSI Latin 1; Western European (Windows)                 */
  /* 20127 - US-ASCII 20127                                           */
  /* 65001 - Unicode (UTF-8)                                          */
  /*------------------------------------------------------------------*/
  RC = SysToUnicode(NewLine, "UTF8", , utf8.)
  If RC = 0 Then Do
    RC = SysFromUnicode(utf8.!TEXT, "20127", , , ascii.)
    If RC = 0 Then Do
      NewLine = ascii.!Text
    End
    Else Do
      Say 'Convert UTF16 to 20127 failed. RC:' RC
    End
  End
  Else Do
    Say 'Convert UTF8 to UTF16 failed. RC:' RC
  End
  /*------------------------------------------------------------------*/
 
Newline contains a UTF-8 line read from the input byte by byte. The line is converted to US-ASCII and output to the file used to generate the POI database.
 
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 22:35 Uhr
Von: tsteven4 <tsteven4@...>
An: ypna@..., gpsbabel-misc@...
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
Here is a style file that handles the quotes in your input, unlike my fist attempt.
 
On 8/30/2014 12:39 PM, [hidden email] wrote:
Good evening Steve
 
That is what I call “just in time”! I read your first answer earlier today and I started to put together a new test bed. Returning from a peaceful evening walk I dreaded the thought to run through the different scenarios all night, still unsure whether it would work or not.
 
Now I do at least know that it probably will not ;-) Your suggestion about my input not being UTF-8 has triggered another mini project, though.
 
As for the POI file, I might just scan through the input, convert the umlaut characters and nuke the rest.
 
Also, I find the idea with the style file quite charming. I had noticed it in the documentation but with your working sample I feel a lot more comfortable (basically, I prefer trial and error over RTFM ;-)
 
Many thanks for your help!
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 16:28 Uhr
Von: tsteven4 <[hidden email]>
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.
 
On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve
 
On 8/29/2014 3:20 PM, [hidden email] wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk


_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc



------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

ypna.style (526 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: POI File Generation Failure when Input Contains Special Characters

tsteven4-2
Peter,

Oops.  There are more uncommitted changes to get the style file I sent to work, and we are not happy with them yet.  You will have to use the method I outline previously.
#!/bin/bash
iconv -f CP1252 -t UTF8 GC_CH.gpi.txt  > GC_CH.utf8.gpi.txt
./gpsbabel -i unicsv -f GC_CH.utf8.gpi.txt -o garmin_gpi,sleep=1,category="GC_CH" -F "GC_CH.gpi"
./gpsbabel -i  garmin_gpi -f GC_CH.gpi -o unicsv -F GC_CH_roundtrip.txt
Steve

On 9/27/2014 1:24 PM, tsteven4 wrote:
Here is the style file, the previous file was the wrong one with the right name.

On 9/27/2014 1:21 PM, tsteven4 wrote:
Peter,

I ran into some unexpected trouble under Mac OS X, but I think that is fixed now.  We have lots more work to do on encoding, but your issue should be fixed in
https://code.google.com/p/gpsbabel/source/detail?r=4904
With this revision you can do the windows-1252 conversion in gpsbabel (without iconv), but it requires a custom style file.  With it a command like
./gpsbabel -i xcsv,style=ypna.style -f GC_CH.gpi.txt -o garmin_gpi,sleep=1,category="GC_CH" -F "GC_CH.gpi"
should work.
I attached the style file.  We may or may not do something to eliminate the need for the style file in the future.  Alternatively you can continue to use the method I outlined previously.

To use this revision you will have to build code from source.  If you cannot do that you will need to wait for the next release.  If you want to buy something you can make a donation at
http://www.gpsbabel.org/

Steve


On 9/20/2014 3:51 PM, [hidden email] wrote:
Hi Steve
 
Sorry for the delay in getting back to you. The short answer is: where can I buy your solution?? Not only do the POIs show up on the GPS, the descriptions also seem to retain the umlaut characters (I found one ä and one ö).
Congratulations and thanks a lot for your efforts!
 
Peter from team YPNA
 
Gesendet: Donnerstag, 18. September 2014 um 23:55 Uhr
Von: tsteven4 [hidden email]
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
Peter,

I know you resolved your issue, but I would like to ask you if the following file resolves it as well.  I am testing a modification to the garmin_gpi writer and reader to use the windows code pages it seems to prefer, by default Windows-1252.
My test script is quoted below.  I didn't have GC.bmp so I skipped that option.  At this time the unicsv reader assumes UTF-8, so I converted your file from Windows-1252 to UTF-8.  Then I read this file and output a garmin_gpi file using Windows-1252, GC_CH.gpi. 
1. Is GC_CH.gpi loadable on your device, i.e. does it show up in the extras list of POI databases?
Then I converted this gpi file back to unicsv.  Unfortunately the output is not directly comparable due to new fields in the output and the order of the output.
#!/bin/bash
iconv -f CP1252 -t UTF8 GC_CH.gpi.txt  > GC_CH.utf8.gpi.txt
./gpsbabel -i unicsv -f GC_CH.utf8.gpi.txt -o garmin_gpi,sleep=1,category="GC_CH" -F "GC_CH.gpi"
./gpsbabel -i  garmin_gpi -f GC_CH.gpi -o unicsv -F GC_CH_roundtrip.txt
Thanks,
Steve
 
On 8/30/2014 3:02 PM, ypna@... wrote:
Thank you very much Steve!
 
I already resorted to the lowest common denominator on this one.
 
I adapted my program generating the input file to do so in US-ASCII format, thereby getting rid of everything GPSBabel does not seem to correctly process for the garmin-poi option.
With this approach, I can use my original command without the need for a style file. I do, of course, lose all the fancy characters used around the world.
 
I will keep your style file for future reference! I prefer GPSBabel over the Garmin POI Loader.
I had used the Garmin POI Loader in in the past, directly generating an input file without using GPSBabel. I just looked at the code now… it contains hundreds of statements to translate all sorts of characters, because the Garmin POI Loader is of course equally picky ;-)
 
In case it helps somebody: my program is written in ObjectREXX (without the objects). The code to convert the input looks as follows:
 
  /*------------------------------------------------------------------*/
  /*  1252 - ANSI Latin 1; Western European (Windows)                 */
  /* 20127 - US-ASCII 20127                                           */
  /* 65001 - Unicode (UTF-8)                                          */
  /*------------------------------------------------------------------*/
  RC = SysToUnicode(NewLine, "UTF8", , utf8.)
  If RC = 0 Then Do
    RC = SysFromUnicode(utf8.!TEXT, "20127", , , ascii.)
    If RC = 0 Then Do
      NewLine = ascii.!Text
    End
    Else Do
      Say 'Convert UTF16 to 20127 failed. RC:' RC
    End
  End
  Else Do
    Say 'Convert UTF8 to UTF16 failed. RC:' RC
  End
  /*------------------------------------------------------------------*/
 
Newline contains a UTF-8 line read from the input byte by byte. The line is converted to US-ASCII and output to the file used to generate the POI database.
 
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 22:35 Uhr
Von: tsteven4 <tsteven4@...>
An: ypna@..., gpsbabel-misc@...
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
Here is a style file that handles the quotes in your input, unlike my fist attempt.
 
On 8/30/2014 12:39 PM, [hidden email] wrote:
Good evening Steve
 
That is what I call “just in time”! I read your first answer earlier today and I started to put together a new test bed. Returning from a peaceful evening walk I dreaded the thought to run through the different scenarios all night, still unsure whether it would work or not.
 
Now I do at least know that it probably will not ;-) Your suggestion about my input not being UTF-8 has triggered another mini project, though.
 
As for the POI file, I might just scan through the input, convert the umlaut characters and nuke the rest.
 
Also, I find the idea with the style file quite charming. I had noticed it in the documentation but with your working sample I feel a lot more comfortable (basically, I prefer trial and error over RTFM ;-)
 
Many thanks for your help!
Peter from team YPNA
 
Gesendet: Samstag, 30. August 2014 um 16:28 Uhr
Von: tsteven4 <[hidden email]>
An: [hidden email], [hidden email]
Betreff: Re: [Gpsbabel-misc] POI File Generation Failure when Input Contains Special Characters
I think my suggestion is going to fail writing to garmin_gpi.  in the garmin_gpi writer we try to convert from utf-8 to cp1252 and I don't think it is going to work.  doing the input conversion as a separate step (1 below) and using the style file (2 below) seems to work for writing to gpx, but not garmin_gpi.
 
On 8/30/2014 7:06 AM, tsteven4 wrote:
Peter,

At this time it is ugly, gpsbabel is in a state of transition regarding characters set conversion.

Here is something that might work for you.
1. convert GC_CH.gpx.txt to utf-8.  I believe the file GC_CH.gpx.txt you supplied is encoded with CP1252.
 a) on linux you can use "iconv -f CP1252 -t UTF-8 GC_CH.gpi.txt > GC_CH.gpi.txt.utf8, OR
 b) you can also do this online at http://i-tools.org/charset.  set the source charset to 1252, the new charset to utf-8, set the file to upload and check download result.
2. convert using the attached style file.  this allows you to avoid the attempt by gpsbabel to convert the input file.  I dropped your bitmap option as you didn't supply GC.bmp.
gpsbabel -D9 -p "" -w -i xcsv,style=test.style -f /media/sf_Shared/GC_CH.gpi.txt.utf8 -o garmin_gpi,sleep=1,category="GC_CH" -F x.gpi

Steve
 
On 8/29/2014 3:20 PM, [hidden email] wrote:
Hello
 
I ran into a problem trying to generate a garmin_gpi file from a unicsv file. On my Windows 8.1 machine, GPSBabel appears to correctly generate the POI file using the command
 
GPSBabel.exe -D9 -p "" -w -i unicsv -f "GC_CH.gpi.txt" -o garmin_gpi,sleep=1,category="GC_CH",bitmap="GC.bmp" -F "GC_CH.gpi"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "US-ASCII" to "UTF-8", done.
options: module/option=value: garmin_gpi/bitmap="GC.bmp"
options: module/option=value: garmin_gpi/category="GC_CH"
options: module/option=value: garmin_gpi/sleep="1"
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
cet_util: Converting from "UTF-8" to "CP1252", done.
 
The problem manifests itself when I copy the generated POI file to my Garmin device… it simply does not show up in the “Extras” list of POI databases.
Assuming that GPSBabel would understand its own output, I ran the reverse command:
 
GPSBabel.exe -D9 -p "" -w -i garmin_gpi -f "GC_CH.gpi" -o unicsv -F GC_CH_reverse.csv"
 
The output from this command is:
 
GPSBabel Version: 1.5.1
options: module/option=value: garmin_gpi/category="My points" (=default)
options: module/option=value: garmin_gpi/unique="1"
options: module/option=value: garmin_gpi/units="m" (=default)
garmin_gpi: Unknown tag (0x29726574). Please report!
garmin_gpi: Unknown tag (0x29726568). Please report!
garmin_gpi: Unknown tag (0x296e776f). Please report!
garmin_gpi: Unknown tag (0x322d3430). Please report!
garmin_gpi: Unknown tag (0x217e4b17). Please report!
garmin_gpi: Unknown tag (0x5240000). Please report!
cet_util: Converting from "CP1252" to "UTF-8", done.
options: module/option=value: unicsv/datum="WGS 84" (=default)
options: module/option=value: unicsv/prec="6" (=default)
cet_util: Converting from "UTF-8" to "US-ASCII", done.
 
I was able to narrow down the problem to the offending records by performing individual encode/decode operations for each record in the original input file. The problem appears to be related to “special” characters in 555 of the 2846 input records. You may want to look at http://www.geocaching.com/geocache/GC4A0B4_freu-dich-nicht-zu-fruh for a particularly nasty example (you will find that the umlaut left in my test case was enough to let GPSBabel struggle…).
 
I also tried to run GPSBabel with the “-c” parameter to force it to process the input file as UTF-8 format. However, this results in the error message “Unknown option ‘-c’, regardless of where I put the parameter.
 
Both operations completed successfully. I got a working POI file and the reverse operation returned a complete CSV file with one notable twist: all “special” characters from the original input file had been replaced by “$” (dollar) signs.
Of course, my aim is to get the POI file including those “special” characters. And I would like to do the processing on my PC.
 
Any hint would be greatly appreciated!
 
Many thanks
Peter from team YPNA
 
As this is the my first post to this forum, I do not know if the attached ZIP file "GC_CH_Tests.zip" reaches the forum. It contains the test cases as follows:
 
- "GC_CH.gpi.txt" containing all records
- "GC_CH_NOK.gpi.txt" containing the offending records
- "GC_CH_OK.gpi.txt" containing the records correctly encoded/decoded
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
 
 
 
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
 
 
 
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk


_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc




------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc