- mkgmap-dev - The mkgmap lists

Commit r4322: Remove more code regarding type=through_route relations.
by svn commit 26 Oct '19

26 Oct '19

Version mkgmap-r4322 was committed by gerd on Sat, 26 Oct 2019 Remove more code regarding type=through_route relations. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4322

1 0

Commit r4320: Remove code which tried to implement type=through_route relations.
by svn commit 26 Oct '19

26 Oct '19

Version mkgmap-r4320 was committed by gerd on Sat, 26 Oct 2019 Remove code which tried to implement type=through_route relations. Effect: RoadMerger might merge different ways when input data contains such a relation. I did not find any effect on routing. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4320

1 0

type=through_route relations
by Gerd Petermann 24 Oct '19

24 Oct '19

Hi all, I've noticed that the changes in r3649 http://www.mkgmap.org.uk/websvn/listing.php?repname=mkgmap&rev=3649 effectively removed the support for type=through_route relations, which was not intended. I wonder if I should simply remove the rest of the code or if I should try to make it work again. There are only 116 relations : https://taginfo.openstreetmap.org/relations/through_route so I'd prefer to remove the code. My understanding is that the code was used as a work around for some wrong code that calculated the initial heading value. Gerd

2 1

Please test branch NET-no-NOD
by Gerd Petermann 23 Oct '19

23 Oct '19

Hi all, I've tried to work out under what conditions we need routing nodes when using OSM input (not polish *mp): See http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4300 for details. Please try the new version with a few tiles (maybe 4). The version r4301 produces some messages like SCHWERWIEGEND (StyledConverter): d:\mkgmap\test\resources\in\osm\uk-test-1.osm.gz: check: road without connection is not written to NOD Wildwood Rise (OSM id 4013934) 51.570805,-0.178385 SCHWERWIEGEND (StyledConverter): f:\osm\wildeshausen.o5m: check: road without connection is not written to NOD (OSM id 243082453) 52.903136,8.414926 These are not errors, they just help to find the places where the result of the branch version is (very) different. Please compare a map produced with the trunk version (r4299) with a new map produced with the branch version and check address search and routing at some places printed with these error messages. Please try also new experimental option --x-all-roads-to-nod . If given, mkgmap will add at least one routing node to each routable line so that it is added to NOD. I hope the program is stable, so you should not see crashes, else please let me know details. Pleaase let me know which result you prefer. 1) trunk r4299 2) branch r4301 WITHOUT option --x-all-roads-to-nod 3) branch r4301 WITH option --x-all-roads-to-nod 1) should give the largest file, 2) the smallest, 3) between Gerd

4 38

Commit r4314: fix assertion error when option --make-poi-index is used
by svn commit 22 Oct '19

22 Oct '19

Version mkgmap-r4314 was committed by gerd on Mon, 21 Oct 2019 fix assertion error when option --make-poi-index is used Regession from r4147 (img_io_3.patch) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4314

3 4

Commit r4315: code cleanup: remove obsolete call of Collections.sort() after call of MdrUtils.sortList() which already does this.
by svn commit 21 Oct '19

21 Oct '19

Version mkgmap-r4315 was committed by gerd on Mon, 21 Oct 2019 code cleanup: remove obsolete call of Collections.sort() after call of MdrUtils.sortList() which already does this. Those lists are very small, so the obsolete sort did not cause performance problems http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4315

1 0

Commit r4313: Improve code readability, no change in output expected
by svn commit 21 Oct '19

21 Oct '19

Version mkgmap-r4313 was committed by gerd on Mon, 21 Oct 2019 Improve code readability, no change in output expected - Add methods getFirstPoint() and getLastPoint() to class Way and use it - further simplify code in RoadMerger http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4313

1 0

Commit r4311: Ignore turn restrictions in ElementSaver when map is not routable to supress warning "ignoring unspecified/unsupported restriction" for type=restriction relations.
by svn commit 21 Oct '19

21 Oct '19

Version mkgmap-r4311 was committed by gerd on Mon, 21 Oct 2019 Ignore turn restrictions in ElementSaver when map is not routable to supress warning "ignoring unspecified/unsupported restriction" for type=restriction relations. If map is not routable the tag type=restriction might not be used anywhere in the code as the RoutingHook is not enabled and the style probably doesn't use it. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4311

1 0

Commit r4310: Code cleanup, no change in output expected
by svn commit 21 Oct '19

21 Oct '19

Version mkgmap-r4310 was committed by gerd on Mon, 21 Oct 2019 Code cleanup, no change in output expected - use MultiHashMap for field deferredRelationMap in ElementSaver - use of HashMap.computeIfAbsent() in MultiHashMap might give small performance improvement http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4310

1 0

Commit r4309: Improve code readability for KdTree, no functional change
by svn commit 21 Oct '19

21 Oct '19

Version mkgmap-r4309 was committed by gerd on Mon, 21 Oct 2019 Improve code readability for KdTree, no functional change I thought I should replace the recursive calls but that turned out to be quite complex and some investigation showed that the tree is typically well balanced when used in mkgmap so that the depth is well below 100 and threrefore not a problem with the java stack. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4309

1 0