I just found this site and software while trying to find a way to convert .trp files from a copilot GPS to a format a new Garmin GPS can read. I found this software and thought it would be perfect.
Here is what I am trying to do. I have run and installed 2.13.3 on both macintosh and windows to make sure it was having the same issue on both. I have a whole directory of .trp files from the copilot, if i open them in textedit/notepad i can see the information. In the software though it EITHER doesn't detect the format and errors out, or detects it as iGO8 and everything is way off. Is there a known issue here?
Like I said I just found the software, but I've been playing around with it for like an hour and getting no where.
I have around 100-200 .trp files I'd like to convert so this new GPS has the right data.
(04.01.2015, 19:44)mvirnoche Wrote: Here is what I am trying to do. I have run and installed 2.13.3 on both macintosh and windows to make sure it was having the same issue on both. I have a whole directory of .trp files from the copilot, if i open them in textedit/notepad i can see the information. In the software though it EITHER doesn't detect the format and errors out, or detects it as iGO8 and everything is way off. Is there a known issue here?
Maybe your files do not match the pattern that RouteConverter uses to detect the format. For the test files that users sent me, this works fine.
(04.01.2015, 19:44)mvirnoche Wrote: Like I said I just found the software, but I've been playing around with it for like an hour and getting no where.
Please send me some test files and I'll have a look what the issue is.
(04.01.2015, 19:44)mvirnoche Wrote: Here is what I am trying to do. I have run and installed 2.13.3 on both macintosh and windows to make sure it was having the same issue on both. I have a whole directory of .trp files from the copilot, if i open them in textedit/notepad i can see the information. In the software though it EITHER doesn't detect the format and errors out, or detects it as iGO8 and everything is way off. Is there a known issue here?
Maybe your files do not match the pattern that RouteConverter uses to detect the format. For the test files that users sent me, this works fine.
(04.01.2015, 19:44)mvirnoche Wrote: Like I said I just found the software, but I've been playing around with it for like an hour and getting no where.
Please send me some test files and I'll have a look what the issue is.
Attached is a .zip with a bunch of the .trp files. I hope this helps! Thanks for the quick response!
(04.01.2015, 22:24)mvirnoche Wrote: Attached is a .zip with a bunch of the .trp files. I hope this helps! Thanks for the quick response!
Yes, they help a lot. Have you've been processing these files? They're all encoded as UCS-2 Little Endian (LE) but without a Byte Order Mark (BOM) while all the other test files I've got are UCS-2 Little Endian with a Byte Order Mark
There is a workaround before we dive into support for with/without BOM files (see Byte order encoding schemes at http://hackipedia.org/Character%20sets/U.../UCS-2.htm for details), which used to be painful in Java, there is a workaround: If you encode them als UCS-2 Little Endian (I've used Notepad++) then RouteConverter can read them. See the attached example.
(04.01.2015, 22:24)mvirnoche Wrote: Attached is a .zip with a bunch of the .trp files. I hope this helps! Thanks for the quick response!
Yes, they help a lot. Have you've been processing these files? They're all encoded as UCS-2 Little Endian (LE) but without a Byte Order Mark (BOM) while all the other test files I've got are UCS-2 Little Endian with a Byte Order Mark
There is a workaround before we dive into support for with/without BOM files (see Byte order encoding schemes at http://hackipedia.org/Character%20sets/U.../UCS-2.htm for details), which used to be painful in Java, there is a workaround: If you encode them als UCS-2 Little Endian (I've used Notepad++) then RouteConverter can read them. See the attached example.
Looking at them the difference just appears to be the removal of blank lines. Am I missing something? Is there a way to batch do this to all of those files in that directory? I'm not quite sure what you meant by reencoding to UCS2 BOM, I'm not sure how to do that, or if it is known as something else on my mac?
(05.01.2015, 00:05)mvirnoche Wrote: Looking at them the difference just appears to be the removal of blank lines. Am I missing something?
The Byte Order Mark.
(05.01.2015, 00:05)mvirnoche Wrote: Is there a way to batch do this to all of those files in that directory? I'm not quite sure what you meant by reencoding to UCS2 BOM, I'm not sure how to do that, or if it is known as something else on my mac?
I don't own a Mac so I would have to google, too. But you're lucky: I think I found a way you can read your files with the latest prerelease, which I've uploaded recently. Please try it and report whether it works.
