Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Joined: Dec 07, 2006 Posts: 563 Location: North Devon
Posted: Mon Jan 08, 2018 4:39 pm Post subject: A snippet from the Web
I found this in the official Garmin forum, which intrigued me...
Code:
Tried to import POIs from Alpenrouten.de however they are encoding to ISO-8859 but POI loader (on Mac) needs UTF-8 to properly handle Umlauts. Simply use this command line on a Mac to fix the files (in case the original is ISO-8859 - use "file ＜filename＞" to see the encoding)
I don't know what "iconv" is, but the post implies that Mac POI Loader does understand (and translate) UTF-8 encoded CSV files.
(To recap - on Windows, POI Loader just passes the text from CSV files through to the GPI file. If you try and tell POI Loader that the file is encoded using UTF-8 (by adding a BOM), it rejects the file completely. If you encode the file as UTF-8 and don't include a BOM, the UTF-8 data will end up on the Nüvi and will not display properly - it only understand Windows-1252/ANSI)
Joined: Dec 27, 2006 Posts: 998 Location: South Lincs, UK.
Posted: Mon Jan 08, 2018 6:13 pm Post subject:
iconv is a command-line program in unix and similar operating systems, used to convert between different character encodings. I don't know if it is available on the Mac but it seems likely that it is.
So in your example above it would convert the Hochpunkt.csv file from iso-8859-1 to utf-8 and write the output into a new file called Hochpunkt.utf8.csv
So you are correct that this implies that the MAC version of POI loader should understand UTF-8 encoded csv files. _________________ Paul
Contains a pre-built .GPI file - copy to your Nüvi to see what it should look like when built 'properly'
There's two files - a simplistic ANSI encoded CSV file and a UTF-8 encoded (with BOM) GPX file. Each entry has a special character in its name ... and I've filled every field I can think of (so you should see an attached JPEG) and if you were to simulate a drive past each POI, an alert should sound. Pair your phone and it should offer the ability to make a call too
I think the GPX version has a reference to every field in Garmin's schema, that (Windows) POI Loader understands.
Last edited by PhilHornby on Tue Jan 09, 2018 1:28 pm; edited 1 time in total
Joined: Dec 07, 2006 Posts: 563 Location: North Devon
Posted: Tue Jan 09, 2018 1:16 pm Post subject:
M8TJT wrote:
Will you please give us a list of aforementioned fields?
That would be quite a big job; but a bit of a summary :-
The .GPI format has lots of fields that POI Loader can't access (for example, think how Garmin-supplied speed camera alerts display, compared with ones you've built yourself). Equally there are elements in the schema that aren't relevant to Custom POIs (Route/Track info for instance).
Thinking about it, my test file doesn't demonstrate Speed-related alerts, nor per-POI custom icons, nor TourGuides (circular, rather than along-route proximity alerts, who's audio you can control).
There are other things that POI Loader understands, but ignores - such as the date/time that a POI was last edited.
Here's a sample POI (I had to mangle the brackets to get the forum to accept them) :-
One thing I haven't mentioned, is that the Nüvi supports GML (Garmin Markup Language) - an HTML like syntax, that lets you specify text colour and such like. If you hunt around the Nüvi's file system, there should be some .GML files to use as examples.
Joined: 30/12/2002 17:36:20 Posts: 4912 Location: Oxfordshire, England, UK
Posted: Thu Jan 11, 2018 2:46 pm Post subject:
Hi Phil
V4.gpi gives us two POI categories, CSVfile a "simplistic" ANSI encoded CSV file and GPXFile a UTF-8 encoded (with BOM) GPX file. Both files have the same following individual POIs:
Çomewhat confused
Fenêtre
£ ＞ €
moög
Café
Nüvi
Whilst the ANSI encoded CSV file looks good, the UTF-8 encoded (with BOM) GPX file is much better as it has more fields and even the attached JPEG image.
I haven't been able to simulate a drive by yet, so I haven't experienced the alert - which would be useful for my Jersey POIs.
Unfortunately, the big thing is that with both files is that you still have to use the correct diacritical marks to search. So if I'm searching for "Çomewhat confused" I have to use "Çomewhat" instead of the non diacritical marked "Comewhat". This is a Garmin issue as the search function isn't language independent.
Regards, _________________ Robert.
iPhone 6s Plus, iOS 14.0.1: iOS CamerAlert v2.0.7
TomTom GO Mobile iOS 2.3.1; TomTom (UK & ROI and Europe) iOS apps v1.29
Garmin Camper 770 LMT-D
Posted: Today Post subject: Pocket GPS Advertising
We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
All times are GMT + 1 Hour Goto page Previous1, 2, 3
Page 3 of 3
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Forum FAQ
Search
Usergroups
Profile
Log in for private messages
Log in
