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: May 16, 2005 Posts: 86 Location: United Kingdom
Posted: Tue May 22, 2018 5:07 pm Post subject:
Thanks M8TJT. Yes they match exactly. I’ve been following npr’s process since he published it and it’s worked fine. It’s as if POI Loader now doesn’t recognise the file type for some reason.
I’ve reinstalled POI loader on my MAC and also tried it on a Windows PC. However I copied the extracted bmp files from my MAC to the PC. I might download the consolidated Pocket GPS. files direct to the PC and extract them there to see if that makes a difference. I can’t think why it would though.
Joined: May 16, 2005 Posts: 86 Location: United Kingdom
Posted: Tue May 22, 2018 7:35 pm Post subject:
Thanks Richard I’ll take a look as per that thread. It has worked though, that’s the bit I can’t fathom. If not I’ll do the whole process on a PC later in the week and see what happens.
Joined: May 16, 2005 Posts: 86 Location: United Kingdom
Posted: Thu May 24, 2018 12:07 pm Post subject:
I've got this work but I don't see the connection between what I've done and the outcome.
I use a MAC and recently changed to LibreOffice from OpenOffice for Word. Excel, etc - basically an open -source MS Office lookalike.
What I hadn't noticed was that when opening the unzipped csv files to edit them they were being imported with a default number of decimal places, 2 instead of 5. This obviously explains why a number of cameras were off-location as well!
Having corrected that and recompiled the gpi file the icons now associate correctly displaying the right camera types in the icons. Not sure how that would affect things?
For interest, I always convert to 4 decimal places now. Started doing this many months ago in the hope it would put less strain on the poor Merc hardware. Can't say if it's a improvement, but it's certainly not a detriment.
Did you know software version V11 was released at the beginning of this month. Can't see any changes, presumably there's some bug fixes - would be nice if they published a change log.
Joined: May 16, 2005 Posts: 86 Location: United Kingdom
Posted: Fri May 25, 2018 8:33 am Post subject:
@npr
Thanks - no I didn't know the s/w was up to v 11. I checked the SD card with the MB Download Manager only last week but it never offered an update. I think the whole Garmin/Mercedes/Tom Tom traffic is a poor set up. My dealer is clueless and refers me to Garmin for map updates who clearly don't provide them directly and bounce me back to MB.
I'm still on 2015/2016 maps and am reluctant to buy a later one from the well known auction site, even though they seem to work, because I'll lose the traffic "functionality"
Incidentally, using your method do you get the camera type e.g GAT in the red banner? I don't, yet it's in the third column in every line in the csv files in capitals and quotes.
Yes I've had a clueless dealer, I'm far from impressed with Merc's customer service both from their dealers and direct.
IIRC the traffic function only last 3 years so when it expires that may be the time for ebay ;)
I don't have anything in the 3rd column, just use 2 columns. I've seen no evidence that text in the 3rd column is used so I try and keep the POI file size as small as possible.
Joined: 30/12/2002 17:36:20 Posts: 4918 Location: Oxfordshire, England, UK
Posted: Sat May 26, 2018 11:36 am Post subject:
Schouten wrote:
I use a MAC and recently changed to LibreOffice from OpenOffice for Word. Excel, etc - basically an open -source MS Office lookalike.
What I hadn't noticed was that when opening the unzipped csv files to edit them they were being imported with a default number of decimal places, 2 instead of 5. This obviously explains why a number of cameras were off-location as well!
npr wrote:
For interest, I always convert to 4 decimal places now. Started doing this many months ago in the hope it would put less strain on the poor Merc hardware. Can't say if it's a improvement, but it's certainly not a detriment.
Hi,
I use a Mac and Ms Office, I use Mac Excel to create master POI lists which are stored as Excel spreadsheet (.xlsx) files. I use the master lists to create POIs for both Garmin and TomTom formats. I currently have the need to produce only Garmin and TomTom.
When I wish to create .csv files for Garmin, I use Mac Excel to take the .xlsx file, remove the unnecessary columns (i.e. comments, etc) and save the file as a CSV file format, the one Mac Excel labels as "Comma Separated Values (.csv)".
I also store all coordinates with 6 decimal places.
Admittedly I don't use the Mercedes system, I have a Garmin 770 Camper LMT-D and I use Mac POI loader to convert the .csv files into GPI files.
I know nothing about Chinese characters, however I do have a need to use diacritical marks (also referred to as diacritics) and they are the accent marks on alphabetical characters. The most common accents are the acute (é), grave (è), circumflex (â, î or ô), tilde (ñ), umlaut and dieresis (ü or ï – the same symbol is used for two different purposes), and cedilla (ç).
I use the diacritical marks in the master list. Garmin can't use diacritical marks very well, if you have a POI with "café" in the title and type searched for "cafe" the Garmin won't find it. If you change your language keyboard and then search for "café" the Garmin will find your intended search.
My above method removes the diacritical marks for the Garmin so "café" becomes "cafe".
Don't know if this is of any help but it works for my system and it took me a long time to get Mac Excel to produce the right file format for producing Garmin and TomTom POI files.
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
I've been successfully using the method suggested by npr on page 5 of this thread for some time until recently. Everything has worked fine until the last couple of times. The camera icons no longer display correctly, I just get a white box similar to the "built in" icons for fuel or food etc, with a magenta block in one corner.
Hi, I'm a little bit late to this so you might already have an answer to this, the reason for the white box with the purple square in the corner is because the size of your .bmp file is too large. I didn't like the included files as they showed too small so I experimented with new ones, at first I had the size too large (100px x 100px) and the icon showed exactly as you described, by gradually reducing the size I finally got it to show correctly.
It can be a bit temperamental though, the last time I updated 2 of my files were ok but the third (same size) wouldn't show and I had to reduce it by a few px.
I find that usually making the .bmp 50x65 works, although for one I had to have it 50x63. If you make it this uneven size then you can add a background colour and it covers the whole icon just like the factory installed versions.
Joined: May 16, 2005 Posts: 86 Location: United Kingdom
Posted: Wed Jun 06, 2018 12:55 pm Post subject:
@Privateer @Doug123
Thanks both for your replies. All seems ok the moment, I was getting the icon problem with 25x25 bmp files, but since importing the csv's with 4 decimal places and using 44x44 size icon files all seems well.
I've no idea why but at least it's now working again, albeit with hit and miss "bongs!"
I'm sure the Mercedes Audio 20 system is short on memory and this may well be part of the varied problems that occur randomly.
Joined: 30/12/2002 17:36:20 Posts: 4918 Location: Oxfordshire, England, UK
Posted: Wed Jun 06, 2018 9:12 pm Post subject:
Hi Schouten,
On the size of icons, I tend to use 24x24 which is the Size TomTom used to use before they stopped showing icons on their SatNav products.
I think think that the Garmin builtin icons are about 62x62. I’ve created icons of that size and they work well, if not a little large, on my Garmin 770.
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
Going back again to the Chinese writing, does anyone have a problem with the latest software update? I updated a couple of weeks ago and deleted the 6 font files identified earlier in this thread, now mostly the banners don’t show at all, just the boing but when they do show it’s still with the Chinese writing.
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!
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!