August 2018 - mkgmap-dev - The mkgmap lists

address rules
by Gerd Petermann 08 Aug '18

08 Aug '18

Hi all, I wonder why we have a small difference between german and austrian rules like this: mkgmap:country=DEU & mkgmap:city!=* & mkgmap:admin_level8=* { set mkgmap:city='${mkgmap:admin_level8|subst:Gemeinde |subst:Stadt}' } mkgmap:country=AUT & mkgmap:city!=* & mkgmap:admin_level8=* { set mkgmap:city='${mkgmap:admin_level8|subst:Gemeinde |subst:Stadt }' } In the rules for AUT both subst clauses end with a blank, in the rules for DEU there is no blank after "Stadt". Is this intended? Gerd

1 1

Commit r4216: correct DouglasPeuckerFilter: Never remove the first or last point of a way.
by svn commit 03 Aug '18

03 Aug '18

Version mkgmap-r4216 was committed by gerd on Fri, 03 Aug 2018 correct DouglasPeuckerFilter: Never remove the first or last point of a way. In opposite to the javadoc the method sometimes removed the last point because of some special handling introduced long ago. This introduces problems when the code is called by WrongAngleFixer, because the preserved flag is not yet set. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4216

1 0

Commit r4215: correction: don't remove ways as "unused" when they are via ways of turn restrictions
by svn commit 03 Aug '18

03 Aug '18

Version mkgmap-r4215 was committed by gerd on Fri, 03 Aug 2018 correction: don't remove ways as "unused" when they are via ways of turn restrictions Such a way will not appear in NOD but without this correction the corresponding relation is not marked as invalid and thus produces error messages like "can't locate arc from 'via' node at ... to next 'via' node on way ... http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4215

1 0

new option --add-boundary-nodes-at-admin-boundaries
by Gerd Petermann 01 Aug '18

01 Aug '18

Hi all, please try r4213 in the country-border branch, I think it is ready for merge into trunk: http://www.mkgmap.org.uk/download/mkgmap.html I hope this description is clear enough, please suggest improvements / corrections: --add-boundary-nodes-at-admin-boundaries=NUM This option controls how mkgmap calculates special routing nodes which are needed by Garmin software to allow routing between different map tiles. These nodes are written to section 3 and 4 in the NOD file. When a road crosses the tile boundary (bbox), the road is split at this point and such a special node is written. This allows routing between one set of tiles produced by splitter.jar. However, if you create a map from different sets of tiles, those tiles are likely to overlap. For the overlapping tiles, none of the entries in NOD3 match and thus routing across tile border doesn't work when the route is not fully covered by one of the tiles. The option tells mkgmap to add special nodes whereever a road touches or crosses an administratve boundary. The NUM parameter specifies a filter for the admin_level. Boundaries with a higher admin_level value are ignored. The default value is 2 (country borders). Another reasonable value might be 4. A value less or equal to 0 tells mkgmap to ignore intersections at administrative boundaries. Gerd

2 5