- mkgmap-dev - The mkgmap lists

Multipolygons and disappearing coastlines
by Mark Burton 28 Dec '09

28 Dec '09

Hi team, I have been asked by the Open Sea Map people to help them generate some maps with marine objects and while working on that I have noticed that if a way is part of a multipolygon then all its tags get removed. This is unfortunate because (in the test map I am looking at around Keil) the coastline is part of a multipolygon (some administrative boundary) and, therefore, the coastline doesn't appear in the map because its tags have been removed (or is it global warming?) So, is putting the coastline into a multipolygon a reasonable OSM thing? If so, should mkgmap be breaking the coastline by removing its tags? If not, how do we fix that? Any thoughts? Cheers, Mark

5 7

boundary relations duplicated by splitter, not merged by mkgmap
by Marko Mäkelä 28 Dec '09

28 Dec '09

I am not sure if this is a splitter or mkgmap bug. In my map generated from Geofabrik's finland.osm.bz2, in the national border between Finland and Sweden, the name Sverige (name:sv for Sweden) occurs three times, apparently once per map tile. In the *.osm.gz files output by splitter, only the relation 52822 has name=Sweden, and that relation does occur in every *.osm.gz tile file. In the generated gmapsupp.img, the name occurs in two labels, like this: SVERIGE/SVERIGE/SVERIGE/NORRA NORRLAND/NORRA NORRLAND/NORRA NORRLAND/NORRBOTTENS LÄN/NORRBOTTENS LÄN/NORRBOTTENS LÄN/SUOMI SVERIGE/SVERIGE/NORRA NORRLAND/NORRA NORRLAND/NORRBOTTENS LÄN/NORRBOTTENS LÄN/SUOMI For some reason, the second occurrence is apparently only using two of the tiles. The desired label would mention each area only once. Would it be possible for mkgmap to merge relations between input tiles, if each carries the same id? A quick-and-dirty solution might be a not-substring filter that would not append the relation name to the mkgmap:boundary_name in the relations file if it is already contained. But I am wondering if the duplicate relations could be causing other problems. Best regards, Marko

2 3

naming map layers in a gmapsupp.img
by Torsten Leistikow 27 Dec '09

27 Dec '09

Moin, I have multiple map layers in my gmapsupp.img file, but I can not set the name of the layers, so that they can be identified on my nuvi. The first layer is created by the following call: java -jar -Xmx6144M ../../mkgmap-r1170/mkgmap.jar --style-file=../../styles/06_restrictions_motorcar --remove-short-arcs=5 --transparent --product-id=7 --family-id=46 --country-name="Deutschland" --country-abbr="D" --family-name="OSM_M_OV" --tdbfile --draw-priority=18 --max-jobs=3 ../../osm/Europa/66666???.osm.gz The second layer is created by the following call: java -jar -Xmx6144M ../../mkgmap-r1170/mkgmap_style_2.jar --style-file=../../styles/03_topo_base --remove-short-arcs=5 --product-id=7 --family-id=43 --country-name="Deutschland" --country-abbr="D" --family-name="OSM_BASE" --tdbfile --draw-priority=8 --max-jobs=3 ../../osm/Europa/66663???.osm.gz And in a third step I combine both layers into the gmapsupp.img: java -jar mkgmap-r1429/mkgmap.jar --product-id=7 --mapset-name=OSM_M004 --gmapsupp img/06_restrictions_motorcar/*.img img/03_topo_base/*.img img/03_topo_base/OSM_BASE.TYP The resulting map is working ok, just when I look at the map settings in my nuvi, both layers are displayed in the same way family name [1] OSM street map family name [1] OSM street map So, what parameters do I have to set, so that I can identify the layers on the nuvi by the mapname? Gruss Torsten

11 28

Problem displaying mkgmap created maps with TTQV(Touratech Quo vadis)
by Gert Münzel 27 Dec '09

27 Dec '09

Hi, i have experienced( and also red that otherones maked the same experience) sometimes, that mkgmap created maps/overlays couldn't be displayed with TTQV althought the same map could be used with Mapsource perfectly. Meanwhile accidently i created this possible erroneous map with a style from another of my maps and amazingly then i could use it in TTQV. I'm shamed to say that i unfortunately forgot making a backup of the lines-file which seems to cause these kind of problem, so it's difficult for me going on investigating it. May be some of you have an idea if there is compability issue by using style file entries with different mkgmaps versions which should be keep in mind by map builders. Example which could not be displayed with TTQV OSM Reit Wanderkarte http://topo.geofabrik.de/OSM_Wanderkarte_mapsource.zip cheers Gert

2 2

Commit: r1440: Don't show highways under construction as if they were normal roads
by svn commit 26 Dec '09

26 Dec '09

Version 1440 was commited by steve on 2009-12-24 17:31:17 +0000 (Thu, 24 Dec 2009) Don't show highways under construction as if they were normal roads -Ondrej Novy

4 3

SEVERE (PolishMapDataSource): error decoding label
by Igor Brejc 26 Dec '09

26 Dec '09

Hi, I'm trying to generate Garmin maps files from Polish maps generated by GroundTruth. I get the following exception (using the latest version of mkgmap): SEVERE (PolishMapDataSource): error decoding label java.nio.charset.UnmappableCharacterException: Input length = 1 at java.nio.charset.CoderResult.throwException(Unknown Source) at java.nio.charset.CharsetDecoder.decode(Unknown Source) at uk.me.parabola.mkgmap.reader.polish.PolishMapDataSource.recode(PolishMapDataSource.java:535) at uk.me.parabola.mkgmap.reader.polish.PolishMapDataSource.isCommonValue(PolishMapDataSource.java:442) at uk.me.parabola.mkgmap.reader.polish.PolishMapDataSource.processLine(PolishMapDataSource.java:287) at uk.me.parabola.mkgmap.reader.polish.PolishMapDataSource.load(PolishMapDataSource.java:127) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:148) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) SEVERE (PolishMapDataSource): error decoding label java.nio.charset.UnmappableCharacterException: Input length = 1 at java.nio.charset.CoderResult.throwException(Unknown Source) at java.nio.charset.CharsetDecoder.decode(Unknown Source) at uk.me.parabola.mkgmap.reader.polish.PolishMapDataSource.recode(PolishMapDataSource.java:535) at uk.me.parabola.mkgmap.reader.polish.PolishMapDataSource.isCommonValue(PolishMapDataSource.java:442) at uk.me.parabola.mkgmap.reader.polish.PolishMapDataSource.processLine(PolishMapDataSource.java:287) at uk.me.parabola.mkgmap.reader.polish.PolishMapDataSource.load(PolishMapDataSource.java:127) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:148) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) The same MP file works in cgpsmapper without problems. It's quite large (47 MB) so I'm not able to detect which label is the culprit for the exception. Is there any way to see which line of the MP file causes the problem? Thanks, Igor

2 2

Commit: r1442: Deal with characters that cannot be mapped onto the target charset better.
by svn commit 26 Dec '09

26 Dec '09

Version 1442 was commited by steve on 2009-12-26 12:10:34 +0000 (Sat, 26 Dec 2009) Deal with characters that cannot be mapped onto the target charset better. Invalid characters will be replaced with a '?' rather than throwing an exception.

1 0

Commit: r1441: Make boundaries more visible. Use 0x1d and 0x1e for major borders.
by svn commit 25 Dec '09

25 Dec '09

Version 1441 was commited by marko on 2009-12-25 21:10:15 +0000 (Fri, 25 Dec 2009) Make boundaries more visible. Use 0x1d and 0x1e for major borders. National borders are now visible on the Edge 705 at 30km zoom level, province borders at 2km and city borders at 500m.

1 0

Routing Problem in Southern Minnesota
by Jeffrey Ollie 24 Dec '09

24 Dec '09

Hello, I'm having an issue with routing in southern Minnesota along I-35 with my Oregon 300 (firmware 3.40). If I pick two points along I-35, one south of Albert Lea and the other north of Owatonna my Garmin wants to route me over to US 218 instead of using I-35. The same route using Cloudmade just goes straight up I-35 as one would expect. Is this a bug in my Garmin, is there a deficiency in the OSM data or am I generating my maps incorrectly? I'm using osmosis merge last week's planet plus the dailies and then split out Iowa and Minnesota. I've attached a PNG which shows the odd route the Garmin gives me. I've used JOSM to look over the data in OSM and fixed the obvious issues. Can anyone point out where I'm going wrong? -- Jeff Ollie

3 3

splitter broken with multiple files
by Greg Troxel 24 Dec '09

24 Dec '09

I updated this morning and ran the splitter with mass/conn/ri extracts (3 files). I got a map that had only connecticut. SO I wonder if the bounds code in r102 is using the last bound, rather than unioning them. here's my log. search down for connecticut bounds, and the bounds chosen for writeout. cache= description= geonames-file= legacy-mode=false mapid=63240001 max-areas=255 max-nodes=800000 mixed=false overlap=2000 resolution=13 split-file= status-freq=120 write-kml= Elapsed time: 0s Memory: Current 80MB (2MB used, 78MB free) Max 1994MB Time started: Thu Dec 24 09:07:50 EST 2009 Map is being split for resolution 13: - area boundaries are aligned to 0x800 map units - areas are multiples of 0x1000 map units wide and high The input osm file(s) will be re-parsed during the split (slower) because no --cache parameter was specified Processing massachusetts.osm.bz2 A <bounds/> tag was found. Area covered is (41.23593807220459,-73.50664615631104) to (42.888779640197754,-69.93184089660645) 2,500,000 nodes processed... 5,000,000 nodes processed... Elapsed time: 2m 0s Memory: Current 80MB (27MB used, 53MB free) Max 1994MB 7,500,000 nodes processed... Processing rhode_island.osm.bz2 A <bounds/> tag was found. Area covered is (41.149635314941406,-71.89511060714722) to (42.0211386680603,-71.12078905105591) Processing connecticut.osm.bz2 A <bounds/> tag was found. Area covered is (40.99842309951782,-73.72570753097534) to (42.0546555519104,-71.78900241851807) A total of 9,772,793 nodes, 0 ways and 0 relations were processed in 3 files Min node ID = 196471 Max node ID = 591033429 Time: Thu Dec 24 09:10:22 EST 2009 Exact map coverage is (40.99842309951782,-73.72570753097534) to (42.0546555519104,-71.78900241851807) Trimmed and rounded map coverage is (40.95703125,-73.7841796875) to (42.099609375,-71.7626953125) Splitting nodes into areas containing a maximum of 800,000 nodes each... 3 areas: Area 63240001 covers (0x1d2000,0xffcb8800) to (0x1df000,0xffcc3800) Area 63240002 covers (0x1d2000,0xffcc3800) to (0x1da000,0xffccf800) Area 63240003 covers (0x1da000,0xffcc3800) to (0x1df000,0xffccf800) Writing out split osm files Thu Dec 24 09:10:22 EST 2009 Processing 3 areas in a single pass Starting pass 1 of 1, processing 3 areas (63240001 to 63240003) Processing massachusetts.osm.bz2 A <bounds/> tag was found. Area covered is (41.23593807220459,-73.50664615631104) to (42.888779640197754,-69.93184089660645) 2,500,000 nodes processed... Elapsed time: 4m 0s Memory: Current 80MB (49MB used, 31MB free) Max 1994MB 5,000,000 nodes processed... 7,500,000 nodes processed... Writing ways Thu Dec 24 09:12:34 EST 2009 500,000 ways processed... Writing relations Thu Dec 24 09:13:19 EST 2009 Processing rhode_island.osm.bz2 A <bounds/> tag was found. Area covered is (41.149635314941406,-71.89511060714722) to (42.0211386680603,-71.12078905105591) Processing connecticut.osm.bz2 A <bounds/> tag was found. Area covered is (40.99842309951782,-73.72570753097534) to (42.0546555519104,-71.78900241851807) Elapsed time: 6m 0s Memory: Current 80MB (58MB used, 22MB free) Max 1994MB Wrote 9,772,793 nodes, 799,729 ways, 1,537 relations Time finished: Thu Dec 24 09:14:03 EST 2009 Total time taken: 372s

2 2