- mkgmap-dev - The mkgmap lists

Commit r4159: area_size.patch: allows to use area_size() style function
by svn commit 13 Apr '18

13 Apr '18

Version mkgmap-r4159 was committed by gerd on Fri, 13 Apr 2018 area_size.patch: allows to use area_size() style function in lines style for members of type=multipolygon and type=boundary relations. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4159

1 0

Commit r4158: expr-func2.patch by Steve Ratcliffe
by svn commit 13 Apr '18

13 Apr '18

Version mkgmap-r4158 was committed by gerd on Fri, 13 Apr 2018 expr-func2.patch by Steve Ratcliffe corrects handling of expresions like c!=d & a=$b http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4158

1 0

Commit r4155: fix error in handling of zipped hgt files with directory
by svn commit 11 Apr '18

11 Apr '18

Version mkgmap-r4155 was committed by gerd on Wed, 11 Apr 2018 fix error in handling of zipped hgt files with directory The old code did not recognize that a wanted file is not in the zipped directory, it always used the last found file. No error message was printed but wrong data was processed. As a result, DEM was wrong. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4155

1 0

No hillshading gpsmap64?
by Arndt 10 Apr '18

10 Apr '18

Hi all, one user reports, that his gpsmap64 dont show hillshading. He tested the Speichenkarte and the openfietsmap. The options are OK. Any knowledge what the problem is? Greets Arndt

4 5

Commit r3842: Improve ResidentialHook / BoundaryQuadTree: suppress misleading warnings about overlapping admin_level=11 boundaries
by svn commit 09 Apr '18

09 Apr '18

Version mkgmap-r3842 was committed by gerd on Sat, 11 Mar 2017 Improve ResidentialHook / BoundaryQuadTree: suppress misleading warnings about overlapping admin_level=11 boundaries http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3842

8 15

overlapping highways and route restrictions
by Gerd Petermann 06 Apr '18

06 Apr '18

Hi all, please help, I just try to make up my mind what mkgmap should do when it finds overlapping road segments and one (or both) of the overlaps is a part of a (valid) restriction relation. This doesn't happen very often, but it is possible. The attached example contains these two overlapping ways, and both are members of (different) restriction relations: https://www.openstreetmap.org/way/48218016 https://www.openstreetmap.org/way/48218008 (I did not try what the trunk version produces for this mess) I see different possibilities: 1) ignore route restrictions when removing overlaps, remove those which are invalid after overlapping segments were removed and log a warning 2) ignore overlaps when the ways are members of restriction relations 3) complex: remove overlaps but try to "repair" the restriction I am currently trying to implement 3) but it looks too complicated for such a rare case and in the end we have a clear case of wrong input data here. What do you think? Gerd

4 13

highway=* with area=yes
by Gerd Petermann 05 Apr '18

05 Apr '18

Hi all, in Italy I found a lot of closed ways with e.g. highway=residential & area=yes, like here: https://www.openstreetmap.org/way/48017634 I think they were created before area:highway=* was established and probably should be changed to that. I wondered why the default style creates routable lines for them while e.g. highway=pedestrian & area=yes is ignored for routing. I assume the problem is that there are also ways like this: https://www.openstreetmap.org/way/106220928 If that way would be ignored for routing the connection to the track is lost. The major difference between the two samples is that there is a "real" highway=residential going through the 1st: https://www.openstreetmap.org/way/34371138 Wouldn't it be good if mkgmap could detect this somehow? For these ways around 48017634 this is quite difficult because the "real" highway is not even connected to the area way. Gerd

1 0

overlaps at roundabouts
by Gerd Petermann 05 Apr '18

05 Apr '18

Hi all, I tried to change the code in OverlapRemover so that it can handle the case when a roundabout is overlapped by another (flare) road. The current code in r4149 would not allow that unless both are roundabouts. The problem: The default style also assigns different road_speed values to roundabouts. So I can change the code to 1) also ignore road_speed when one way is a roundabout or I can change the code to 2) always allow different road_speed values. If we select 2) I'd say that mkgmap should keep the smaller value. What do you think? Gerd

2 1

new branch overlaps
by Gerd Petermann 03 Apr '18

03 Apr '18

Hi all, as a follow up of [1] and esp. [2] I started a new branch ovelaps for mkgmap. Please see http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4145 Gerd [1] http://gis.19327.n8.nabble.com/Bug-in-Road-Merging-actually-doubling-roads-… [2]http://gis.19327.n8.nabble.com/Bug-in-Road-Merging-actually-doubling-road…

1 0

DEM Resolution and size savings
by Felix Hartmann 31 Mar '18

31 Mar '18

Hi everyone, I noticed that the DEM layer if created for resolution 23 only (with a map that has not 24 resolution) will only be half the size of the DEM in resolution 24 (dem-dist=3312) - however in Basecamp/Mapsource the detail is virtually identical - I cannot see any difference in quality. So I think there must be some way to still save a lot of data/space - but it's not by going for dem-dits=6624 - that will result in much worse DEM detail. (I still really haven't found a good solution for DEM on GPS devices though. Need more time trying out different values and possibilities. Right now I think best is probably a separate transparent but except for DEM empty DEM only gmapsupp.img). -- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich

2 10