Re: [mkgmap-dev] emergency_access_point

2021-08-02 Thread nick
Hi Bernhard The only documented type number  linked to an emergency is 0x3000 or possibly any number higher that 0x3010 Having said that, this type number may not be used any longer and most likely when indexed may produced unforeseen results. R. Nick On 02/08/2021 21:02, Manfred Haiduk

Re: [mkgmap-dev] emergency_access_point

2021-08-02 Thread Manfred Haiduk
Hm Bernhard i think it's the same if they get the names of the emergency access point or if they get the coordinates from your gps device. As far as i know, if there was a fire in the forest near by, thy also sent the geo coords to the fire brigade or the ambulance Am 02.08.2021 um 17:32

Re: [mkgmap-dev] emergency_access_point

2021-08-02 Thread Bernhard Hiller
Hi Gerd, the question is not so much where the next emergency access point is, but its reference number (or name). So that I can tell them e.g.: "we are in the forest halfway between WI-1234 and RÜD-9876". That's an information they can make use of. Regards, Bernhard Am 01.08.2021 um 13:05

Re: [mkgmap-dev] signed maps / new device

2021-08-02 Thread Marek Greško
Hi, that is what I was afraid about. I use only UTF-8 maps. My current device of choice would be GPSmap66s since the other do not possess features I would expect. Has somebody experience with this device and UTF-8 maps? Are they working? Thanks Marek 2021-07-31 15:18 GMT+02:00, Andrzej

Re: [mkgmap-dev] signed maps / new device

2021-08-02 Thread Andrzej Popowski
Hi Felix, I guess the idea is that Garmin holds certificates and only offers signing services for money. Or doesn't offer at all. Well, maps aren't encrypted, so you could hack firmware in your GPS to disable verification. -- Best regards, Andrzej

Re: [mkgmap-dev] Improper transliteration of Bulgarian text

2021-08-02 Thread Felix Hartmann
The transliteration is never good. So either use cyrillic codepage or Unicode without transliteration. Do not transliterate at all - that*s the best solution. Essentially you have 4 options: local codepage - no transliteration using name key - transliterate other letters into cyrillic unicode

Re: [mkgmap-dev] Improper transliteration of Bulgarian text

2021-08-02 Thread osm.dimitar155
HI Gerd, I'm writing from a different email since the mail.bg one seems to add ads on the end of the message which I've removed from the bottom of this message. According to a user on the forum the issue is about improper transliteration of Cyrillic text that could be caused by this program. My

Re: [mkgmap-dev] Improper transliteration of Bulgarian text

2021-08-02 Thread Gerd Petermann
Hi Dimitar, not sure what you try to achive. Several options have an influence here, most important are --name-tag-list and --codepage See https://www.mkgmap.org.uk/doc/options I am not sure if --code-page=1257 or --code-page=65001 (unicode) should be used. Does that help? Gerd

[mkgmap-dev] Improper transliteration of Bulgarian text

2021-08-02 Thread osm_dimitar155
Hello all, There has been a post on the Bulgarian section of the OSM forum that Bulgarian names are not correctly transliterated (https://forum.openstreetmap.org/viewtopic.php?id=73331). According to these users, names show as question marks or if they show up the transliteration is