July 2018 - mkgmap-dev - The mkgmap lists

mkgmap:set_unconnected_type differentiate between connected on both sides or on one side only
by Felix Hartmann 14 Nov '19

14 Nov '19

Would it be possible to have the mkgmap:set_unconnected_type=... differentiate between conncected on both sides for lines and only connected on one side? For example I would like to delete all service=driveway shorther than 100m length if they are connected only on one side to another routable line - if they are in between I would like to keep them. (in some countries - e.g. Switzerland and France) often highway=service&service=driveway leads not only to a house but also connects e.g. to a highway=track or highway=path. -- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich

5 44

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

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

wrong mdr25 and mdr27 data in global index?
by Gerd Petermann 30 Jul '18

30 Jul '18

Hi, while looking at my problem with restaurant POI I noticed that MdrCheck complains about the MDR27 in the index created by mkgmap (Cities sorted by region) The check complains (correctly) about duplicate entries in this index. We have a similar index in MDR25 (Cities sorted by country). For MDR27 the current code in mkgmap doesn't remove any duplicates, for MDR25 it removes duplicate entries when the combination of city name, region name and country name is repeated, no matter in how many different tiles the combination appears. On the other hand, MdrCheck only complains when the 3 names are equal AND two subsequent entries in the index point to the same tile. So, if I got that right we may have to few entries in MDR25, and for sure we have too many in MDR27. My problem: I did not find a difference when I changed the code, it seems that both my Oregon and the PC software seems to ignore these 2 indexes. Maybe older software/firmware versions used these indexes? Gerd

2 4

Commit r4214: refactoring: Move some code into class RoadSegmentIndex
by svn commit 28 Jul '18

28 Jul '18

Version mkgmap-r4214 was committed by gerd on Sat, 28 Jul 2018 refactoring: Move some code into class RoadSegmentIndex seems to improve throughput a little bit http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4214

1 0

routing between different maps
by Andrzej Popowski 27 Jul '18

27 Jul '18

Hi, I'm not sure, if I have already written about this problem, sorry if I repeat myself. Routing between maps require external nodes at the same position on both maps. With rectangular tiles external nodes are created only at borders of the tiles (at least this is what I would expect). Different maps most probably do not get the same borders of tiles in common area, co there is no correct external nodes for routing. My idea is to create external nodes at each intersection of administrative border with routable road. Since administrative borders and roads are the same for all maps, then external nodes should appear at exact the same position for all maps. This would allow (I hope, I haven't tested) for seamless routing between maps. From point of view o a user of mkgmap, there could be an option, indicating which borders should be used for creating nodes. Something like: --external-nodes=admin_level2 -- Best regards, Andrzej

4 21

Commit r4208: simplify and improve UnusedElementsRemoverHook
by svn commit 22 Jul '18

22 Jul '18

Version mkgmap-r4208 was committed by gerd on Sun, 22 Jul 2018 simplify and improve UnusedElementsRemoverHook (improved unused.patch published 2018-07-17) 1) The old code was not adapted to some changes in r3175: It checks if a way without tags is member of a relation, because the rules in relation may add tags to this way. This was okay when the hook was added to the source, but the hook is now executed after those rules were executed, so that check is not needed. 2) It doesn't remove nodes outside of the tile bbox when such a node has tags keys that are used by the POI generator (--pois-to-areas-placement) I've changed the code so that it checks for the combination of tag key and value, not only for the key. 3) The check if a way is outside of the tile bbox did not work for ways which have a bbox that intersects with the tile bbox while the way itself neither crosses the bbox nor contains it (e.g. a large polygon). http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4208

1 0

Commit r4207: eval natural=cape in points rules
by svn commit 21 Jul '18

21 Jul '18

Version mkgmap-r4207 was committed by gerd on Sat, 21 Jul 2018 eval natural=cape in points rules http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4207

1 0

natural=cape
by lig fietser 21 Jul '18

21 Jul '18

On the osm forum someone mentioned natural=cape is not listed as feature. Could be added in the points file: natural=cape [0x6606 resolution 24]

1 0

new branch country-borders
by Gerd Petermann 19 Jul '18

19 Jul '18

Hi all, I've started this new branch to test code that adds external routing nodes for admin_level=2 borders, r4200 seems to do something useful. The code in WrongAngleFixer prints some error messages, I am not yet sure how to handle the new info in this routine. Performance is poor, but can be improved once that we know that this really helps. The current code is executed before style rules for lines are applied, it adds nodes to all ways with highway=* I am not yet sure where exectly this should be done, probably I will move parts of the code so that this happens later in the data flow. @Andrzej: I did not test if it helps in your case because I don't know for sure in which scenario this can be used. It would be great if you could create a small test set for me. Gerd

2 4