- mkgmap-dev - The mkgmap lists

Error in TreHeader.java
by Gerd Petermann 28 May '13

28 May '13

Hi, I found a bug that probably causes the problems reported by Felx for Australia-Oceania: http://gis.19327.n5.nabble.com/SeaGenerator-in-overview2-branch-tp5761296p5… If the bounding box of a tile goes to 180.0 degrees (including), mkgmap saves the value 0x800000. This is interpreted as a negative value when the value is read back for the creation of the overview map. I've added a plausibility check to fix this, see attached patch. Maybe the better place for a correction would be in the write routine, but GPSMapEdit seems to have no problem with the value. @Steve: The same problem occurs in the display tool. Gerd

2 1

SeaGenerator in overview2 branch
by Gerd Petermann 28 May '13

28 May '13

Hi all, WanMil pointed out that the change in r2610 introduced a bug for large sea areas with islands. Merging all sea-only rectangles could produce polygons with holes: sssss ssoss sssss r2613 fixes this. For the above example, two large sea polygons are created instead of one. Change: The algo merges rectangles only if the result is a singular area. It also tries to avoid creating long narrow areas. The img sizes are not much different to those of r2612, and run time is similar. Gerd

3 7

Strange forest polygon
by Jaromír Mikeš 28 May '13

28 May '13

Hi, I encountered strange behavior of forest polygon. I certain zoom level it looks like forest polygon is straitly cut. But when zooming closer forest appear suddenly. When zooming out again suddenly disappear. splitter 304 mkgmap 2618 Screenshots from my garmin unit. https://plus.google.com/u/0/photos/104247758975882866759/albums/ 5881597797792315057 I can't see this strange behavior in qlandkartgt. Is it bug? Or can do something to fix it? thanks for help mira

6 23

problem with style
by Henning Scholland 27 May '13

27 May '13

Hi, does someone has an explanation, why the second line isn't rendered in the map? Only results of line 1 and 3 are visiblewith overview2 r2616(haven't tried other versions). Henning highway=trunk& area!=yes & access=no { set name='${name} (${ref})' | '${ref}' | '${name}'} [0x10003 level 6 continue] highway=trunk & area!=yes & access!=no { set name='${name} (${ref})' | '${ref}' | '${name}'} [0x10003 level 6-1 continue] highway=trunk & area!=yes & access!=no { set name='${name} (${ref})' | '${ref}' | '${name}'} [0x03 road_class=1 road_speed=1 level 0 continue]

3 3

brainstorming about country-specific styles
by Henning Scholland 25 May '13

25 May '13

Hi there, while cycling in New Zealand I found out, thats a little bit toeasy just taking a style (routing and map-look) and use it in parts of the world, which are very different to Central Europe. Eg. it's not that interesting if the road is a trunk or a unclassified, but it's very interesting to show if a road is sealed or unsealed. If there are only small things, which are country-specific it's pretty easy to use just & mkgmap:country=???. But this will makes the style quite confusing to understand. So I thought it would be nice to have something like: if( <key>==<value> ) { <includes or style rules> } I think such a if-clause would also in general makes style-files a little bit more readabeland shouldn't bethat complex to implement (or am I wrong?). What do you think about such a if-clause? Maybethere is a better way for it. Henning

1 0

Commit: r2620: While writing email, discovered more and changed my mind.
by svn commit 23 May '13

23 May '13

Version 2620 was committed by steve on Thu, 23 May 2013 While writing email, discovered more and changed my mind. Now remove the uses of the labelled paragraph syntax. Also remove workaround from PDF generation since it makes things worse.

1 0

Commit: r2619: Add config file to asciidoc to make up for missing functionallity
by svn commit 23 May '13

23 May '13

Version 2619 was committed by steve on Thu, 23 May 2013 Add config file to asciidoc to make up for missing functionallity in earlier versions of asciidoc. This is not a complete solution to using prior versions, but it allows the html version to be created (seemigly) correctly and without errors.

1 0

Commit: r2618: Improve address rules for Germany
by svn commit 21 May '13

21 May '13

Version 2618 was committed by wanmil on Tue, 21 May 2013 Improve address rules for Germany -- Henning

1 0

Commit: r2617: Remove "Gemeinde " and "Stadt " from austrian city names
by svn commit 21 May '13

21 May '13

Version 2617 was committed by wanmil on Tue, 21 May 2013 Remove "Gemeinde " and "Stadt " from austrian city names -- Minko

1 0

Problem for routing with different zoom levels
by Geoff Sherlock 21 May '13

21 May '13

Not sure if anyone has spotted this before, as I have not been keeping a close eye on the mailing list lately. I had the following defined in my style file; to show thinner lines for primary highways at different zoom levels: highway=primary [0x1b road_class=2 road_speed=1 level 3-4 continue] highway=primary [0x03 road_class=2 road_speed=1 level 2] This seems to have broken routing in Mapsource and on the device. I removed the first line and changed the level on the second to 3 and it worked fine (I assume 4 would have worked fine as well). Is there a restriction on doing this type of thing regarding routing? Geoff.

2 2