- mkgmap-dev - The mkgmap lists

Squaring off of land outlines
by Mike Baggaley 28 Jan '20

28 Jan '20

Hello, I am getting squaring off of the outline between land and sea at low zoom levels (less than 16) - see attached BaseCamp images of Gran Canaria at resolution 16 and at resolution 14 displayed at the same size. Obviously some reduction in accuracy is expected at lower zoom level, but not these artefacts. I'm not sure when this started happening but believe it was some time ago. I can't seem to find the old releases to try previous versions, http://svn.mkgmap.org.uk/mkgmap/releases/ just shows me an empty folder. Can you point me to the correct download folder that contains the previous jar files, and/or let me know if this is a known problem, and if so whether there is a workaround? Thanks, Mike

2 7

Commit r4432: utf8-v3.patch by Ticker Berkin
by svn commit 27 Jan '20

27 Jan '20

Version mkgmap-r4432 was committed by gerd on Mon, 27 Jan 2020 utf8-v3.patch by Ticker Berkin - uses StandardCharsets.* where possible. - notes some usage of the java local DefaultCharset. - changed a couple of these to force utf-8 instead. - if --read-config file gives decoding errors, names the charset used to read the file (ie DefaultCharset) instead of 'utf-8' in the error message. - accepts/ignores unicode BOM in more files - uses try (open...) {} where possible in files changed for the above reasons. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4432

1 0

Download r4430 ?
by Steph 25 Jan '20

25 Jan '20

Hi, No version of mkgmap was generated for download since r4425 on the website. Hope it's not a big deal… Regards Steph

2 2

Commit r4431: Improve typ file mapnik.txt
by svn commit 25 Jan '20

25 Jan '20

Version mkgmap-r4431 was committed by gerd on Sat, 25 Jan 2020 Improve typ file mapnik.txt mapnik.patch by Ticker Berkin: Patch attached that makes the following changes to mapnik.txt. This is held in resources/typ-files and distributed in examples/typ-files. - Add UTF-8 BOM at the start of the file, so that many text editors and mkgmap will recognise the encoding. - Add following line near start of file, for the same reasons: ; -*- coding: UTF-8 -*- - comment out lines in the [_id] section; these are supplied / overridden by mkgmap -- options - Change polygon 0x3d / "Bay" to be transparent, with a low _drawOrder - Add a default language label string to every entry. This is used by the Garmin device when there is no label for the language the device is set to. The basis on which I've set the default labels is roughly as follows: - Where my old Garmin device, without TYP file and for an unlabeled object, gave a specific and unique label, used that. - For other cases, eg where the standard Garmin label is something like Road, Line, Area or Unnamed, used wording relevant to the OSM tags that are being mapped. - For some of the many Garmin Rivers and Lakes codes that we use for other water areas, again used wording related to the OSM tag. - Where the English translation (language code 0x04) is close enough to the default label, I've deleted the English. I've also deleted the English where I think the label (probably in all languages) doesn't reflect the tag for which it is being used, but the default label does. I've avoided making any changes to the visuals this TYP file produces (apart from Bay), or to any language other than English. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4431

1 0

Commit r4430: default style: don't add routable way for railway=abandoned
by svn commit 23 Jan '20

23 Jan '20

Version mkgmap-r4430 was committed by gerd on Thu, 23 Jan 2020 default style: don't add routable way for railway=abandoned http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4430

1 0

Suggestions for roadNameConfig.txt
by Alexandre Folle de Menezes 23 Jan '20

23 Jan '20

Hi, I have some suggestions to improve Portuguese handling on roadNameConfig.txt: # portugese prefix1:pt = "Rua", "Avenida", "Travessa", "Alameda", "Beco", "Estrada", "Rodovia" prefix2:pt = "da ", "do ", "de ", "das ", "dos ", "d'" # Section 2 lang:AGO = pt lang:BRA = pt lang:GNB = pt lang:MOZ = pt Best regards, Alexandre

3 5

mapnik TYP file changes
by Ticker Berkin 22 Jan '20

22 Jan '20

Hi all Patch attached that makes the following changes to mapnik.txt. This is held in resources/typ-files and distributed in examples/typ-files. - Add UTF-8 BOM at the start of the file, so that many text editors and mkgmap will recognise the encoding. - Add following line near start of file, for the same reasons: ; -*- coding: UTF-8 -*- - comment out lines in the [_id] section; these are supplied / overridden by mkgmap -- options - Change polygon 0x3d / "Bay" to be transparent, with a low _drawOrder - Add a default language label string to every entry. This is used by the Garmin device when there is no label for the language the device is set to. The basis on which I've set the default labels is roughly as follows: - Where my old Garmin device, without TYP file and for an unlabeled object, gave a specific and unique label, used that. - For other cases, eg where the standard Garmin label is something like Road, Line, Area or Unnamed, used wording relevant to the OSM tags that are being mapped. - For some of the many Garmin Rivers and Lakes codes that we use for other water areas, again used wording related to the OSM tag. - Where the English translation (language code 0x04) is close enough to the default label, I've deleted the English. I've also deleted the English where I think the label (probably in all languages) doesn't reflect the tag for which it is being used, but the default label does. I've avoided making any changes to the visuals this TYP file produces (apart from Bay), or to any language other than English. Ticker

2 4

change handling of railway=abandoned
by Gerd Petermann 21 Jan '20

21 Jan '20

Hi all, the default style has this rule: # following really should be removed, but see: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2016q3/025104.html railway=abandoned [0x0a road_class=0 road_speed=1 resolution 22] I agree with Ticker that it is not a good idea to make such a way routable. I would accept this when it has also a tag like bicycle=yes. I found a few ways like this, e.g. https://www.openstreetmap.org/way/122268824 (I wonder why nobody added a highway tag since 2011) BUT we should not assume access=yes for a railway=abandoned. So, what about this: railway=abandoned {add access=no} [0x0a road_class=0 road_speed=1 resolution 22] Gerd

6 10

Commit r4429: Default style: Use railway=abandoned only as routable way when certain criterias match
by svn commit 21 Jan '20

21 Jan '20

Version mkgmap-r4429 was committed by gerd on Tue, 21 Jan 2020 Default style: Use railway=abandoned only as routable way when certain criterias match http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4429

1 0

TYP files and character encoding
by Ticker Berkin 19 Jan '20

19 Jan '20

Hi A couple of problems with typ-files and unicode. With 'Codepage=65001' the final contents of the labels in mapnik.typ that is included with the composite map is unicode, but if the map is codepage 1252, the unicode characters with the top bit set are simply displayed as if in 1252. Removing the codepage statement from mapnik.txt and making fixes elsewhere to ensure that the file is read correctly as utf-8 and then generating a map with --code-page=1252, it gives the error: SEVE: uk.me.parabola.imgfmt.MapFailedException ../svn/trunk/resources/typ-files/mapnik.txt: (thrown in TypCompiler.makeMap()) TYP file cannot be written in code page 1252 Changing the exception handling in imgfmt/app/typ/TypElement.java, so that makeLabelBlock() reads as ... CharBuffer cb = CharBuffer.wrap(tl.getText()); try { ByteBuffer buffer = encoder.encode(cb); out.put((byte) tl.getLang()); out.put(buffer); out.put((byte) 0); } catch (CharacterCodingException ignore) { // ignore.printStackTrace(); String name = encoder.charset().name(); System.out.println("Cannot represent String=" + tl.getLang() + "," + tl.getText() + " in CodePage=" + name); // throw newTypLabelException(name); } ... It gives output like: Cannot represent String=21,Gara|e in CodePage=windows-1252 Cannot represent String=21,Obszar przemysBowy in CodePage=windows-1252 Cannot represent String=21,ZieleD in CodePage=windows-1252 Cannot represent String=21,Zaro[la in CodePage=windows-1252 Cannot represent String=21,MokradBa in CodePage=windows-1252 Cannot represent String=21,Droga wojew\363dzka (B^Ecznik) in CodePage=windows-1252 Cannot represent String=21,Droga szybkiego ruchu (B^Ecznik) in CodePage=windows-1252 Cannot represent String=21,Droga szybkiego ruchu (B^Ecznik) in CodePage=windows-1252 Cannot represent String=21,Zcie|ka rowerowa in CodePage=windows-1252 Cannot represent String=21,Wybrze|e in CodePage=windows-1252 Cannot represent String=21,Zcie|ka in CodePage=windows-1252 Cannot represent String=21,StrumieD in CodePage=windows-1252 Cannot represent String=21,Granica paDstwa in CodePage=windows-1252 Cannot represent String=21,Rzeka, KanaB in CodePage=windows-1252 Cannot represent String=21,StrumieD in CodePage=windows-1252 Cannot represent String=21,Ruroci^Eg in CodePage=windows-1252 Cannot represent String=21,Kabel wysokiego napi^Ycia in CodePage=windows-1252 Cannot represent String=21,Tor wy[cigowy in CodePage=windows-1252 Cannot represent String=21,Droga szybkiego ruchu (B^Ecznik) in CodePage=windows-1252 Cannot represent String=21,Droga krajowa (B^Ecznik) in CodePage=windows -1252 Cannot represent String=21,Droga wojew\363dzka (B^Ecznik) in CodePage=windows-1252 Cannot represent String=21,Wie[ (>5 tys.) in CodePage=windows-1252 Cannot represent String=21,Wie[ (>5 tys.) in CodePage=windows-1252 Cannot represent String=21,Restauracja (AmerykaDska) in CodePage=windows-1252 Cannot represent String=21,Restauracja (ChiDska) in CodePage=windows -1252 Cannot represent String=21,Restauracja (Mi^Ydzynarodowa) in CodePage=windows-1252 Cannot represent String=21,Restauracja (WBoska) in CodePage=windows -1252 Cannot represent String=21,Restauracja (MeksykaDska) in CodePage=windows-1252 Cannot represent String=21,Restauracja (P^Eczki) in CodePage=windows -1252 Cannot represent String=21,Restauracja (WegetariaDska) in CodePage=windows-1252 Cannot represent String=21,Kr^Ygle in CodePage=windows-1252 Cannot represent String=21,Sklep odzie|owy in CodePage=windows-1252 Cannot represent String=21,Wypo|yczalnia samochod\363w in CodePage=windows-1252 Cannot represent String=21,Gara| in CodePage=windows-1252 Cannot represent String=21,Sprzeda| samochod\363w in CodePage=windows -1252 Cannot represent String=21,Sklep |eglarski in CodePage=windows-1252 Cannot represent String=21,S^Ed in CodePage=windows-1252 Cannot represent String=21,O[rodek kultury in CodePage=windows-1252 Cannot represent String=21,Wi^Yzienie in CodePage=windows-1252 Cannot represent String=21,Stra| po|arna in CodePage=windows-1252 Cannot represent String=21,SBupek in CodePage=windows-1252 Cannot represent String=21,PrzystaD in CodePage=windows-1252 Cannot represent String=21,L^Edowisko helikopterowe in CodePage=windows -1252 Cannot represent String=21,Wie|a in CodePage=windows-1252 Cannot represent String=21,yr\363dBo in CodePage=windows-1252 Cannot represent String=21,Pla|a in CodePage=windows-1252 Cannot represent String=21,Przyl^Edek in CodePage=windows-1252 Cannot represent String=21,SkaBa in CodePage=windows-1252 Which makes sense if codepage 1252 doesn't handle Polish (hex 0x15, decimal 21). NB the non ascii characters in above are messed up by my cutting and pasting. Checking the French, on my Garmin device, the type descriptions now display accents correctly. Ticker

2 14