- mkgmap-dev - The mkgmap lists

Commit r3694: Invalid style expression fix.
by svn commit 18 Aug '16

18 Aug '16

Version mkgmap-r3694 was committed by steve on Thu, 18 Aug 2016 Invalid style expression fix. maxspeed=* & ( maxspeedkmh()>120 | maxspeed = none ) & ( highway = motorway | highway = trunk ) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3694

1 0

Move to Java 1.8
by Gerd Petermann 18 Aug '16

18 Aug '16

Hi all, Java 1.7 is no longer maintained, so I guess that most users are already using Java 1.8 I'd like to change the build of splitter and mkgmap to use 1.8 instead of 1.7 soon, JOSM already requires 1.8. I needed a newer ant version, 1.8.4 did not work with JDK 1.8, but 1.9.7 seems to work fine. @Steve : I think we don't need a warning message for users with an older JRE, but I don't know if you need time to change the build environment? Gerd

5 17

Commit r3693: check_roundabout_connections_v4.patch : More checks for the check-roundabout option
by svn commit 10 Aug '16

10 Aug '16

Version mkgmap-r3693 was committed by gerd on Wed, 10 Aug 2016 check_roundabout_connections_v4.patch : More checks for the check-roundabout option Mike Baggaley: Hi Gerd, please find attached a version 3 patch, that seems to me to provide everything we need at the moment. It provides two warning messages of forms “Roundabout is connected to more than one road at…” and “Roundabout is connected to a road and other highways at…”. It does not warn for multiple highways where there is no road with car access (e.g. a cycleway that goes straight across a roundabout). http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3693

1 0

Re: [mkgmap-dev] [Patch v2] improve roundabout checks
by Mike Baggaley 08 Aug '16

08 Aug '16

HI Gerd, that looks like a good start. The attached patch improves on it slightly by ignoring highways that do not have access for cars. Regards, Mike From: Gerd Petermann [mailto:GPetermann_muenchen@hotmail.com] Sent: 03 August 2016 14:40 To: mkgmap-dev(a)lists.mkgmap.org.uk Subject: [mkgmap-dev] [Patch v1] improve roundabout checks Hi all, attached is a patch for the roundabout checks. It adds a test that will warn when a node on a roundabout is connected to more than one routable way (ways which are not accessable are not counted, e.g. highway=construction with the default style) The check is only performed when option --check-roundabouts is used, you have to enable logging to see the result. The check is implemented in class RouteNode, so a config line in logging.properties might be uk.me.parabola.imgfmt.app.net.RouteNode.level=WARN A binary based on r3688 is here: http://files.mkgmap.org.uk/download/306/mkgmap.jar Note that this check is very basic, it doesn't ignore when the road is going straight through the roundabout or when it builds a tagent. If you think that this produces too many false warning I may add code for this. Gerd

3 5

No Sea in my Europemap
by Arndt Röhrig 06 Aug '16

06 Aug '16

2 2

Splitter diagnostic messages
by Mike Baggaley 06 Aug '16

06 Aug '16

Hi Steve/Gerd (or whoever is the splitter expert), I was just wondering whether it would be possible to reduce the amount of diagnostic information produced by Splitter. I use a batch file to build my map, and the output from each process is appended to a log file. I get an enormous amount of uninteresting info from Splitter that I have to scroll past to see the output from mkgmap. Not a major problem, but it would be useful if there was an option to reduce this (I already have --status-freq=0 in my command line). Cheers, Mike

2 3

Commit r3692: fix problmems with unit tests on windows
by svn commit 06 Aug '16

06 Aug '16

Version mkgmap-r3692 was committed by gerd on Sat, 06 Aug 2016 fix problmems with unit tests on windows Use try-with-ressources to make sure that files are closed. Windows doesn't allow to remove open files. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3692

1 0

released Splitter r438 compiled with java 1.8
by Gerd Petermann 05 Aug '16

05 Aug '16

Hi all, besides that a few small changes reg. logging. See also http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&rev=438 Gerd

1 0

Re: [mkgmap-dev] render landuse=orchard
by Greg Troxel 05 Aug '16

05 Aug '16

Gerd Petermann <GPetermann_muenchen(a)hotmail.com> writes: > If I got that right we should change the style rules in at least two places. > > If a way with railway=abandoned is member of a route relation with > e.g. route=hiking we want the way to be routable for pedestrians, see > e.g https://www.openstreetmap.org/way/56214377 which is part of > relation https://www.openstreetmap.org/relation/1735816 > > If we simply change the lines style to > > railway=abandoned {add access=no} [0x0a road_class=0 road_speed=1 resolution 22] > this way would not be usable for pedestrians. True. I think this is a general problem, when a way (or its relations - I don't see relation vs direct tags as being super important for this dicussion) has multiple tags, then mkgmap has to decide which of them controls the garmin line code. That said, I tealize that relations are not necessarily handled the same, so that may complicated the implementation. But I don't think it affects the intended semantics. > So we need an additional rule in relations to store the info that a > way is member of a route relation, and we should evaluate that > information somewhere in lines or inc\access. It's not really about being a route relation. The thing that matters is that the railway=abandoned is also either highway=path or highway=cycleway, or something else that if it did not have railway=abandoned would be routable. Usually that sort of physical tag belongs on the way, not on a relation which would assign ref tags or route tags to a collection of ways. So I think if someone has a route relation over a bunch of ways that are railway=abandoned and the route is about cycling and not an old railroad, and there are no highway=path/cycleway/footway/track tags, then it is correct to have a nonroutable line type and the tagging should be updated to reflect the access. What mkgmap has to do is just to evaluate the rules that assign path/footway/cycleway/track tags before the railway=abandoned tags. Or a fancier style could have two types, routable and a non-routable, that both render as old railroad, and use the routable one for path/rail and the nonroutable one for just rail. > I assume that this should also be done for highway=*, but I am not > sure how to handle conflicts, for example a way may have > "highway=footway and no explicit bicycle tag" and be a part of a > route=bicycle relation. Does that mean that the relation is wrong or > that the way should be accessible for bicycles? Two thoughts here: 1) The tag highway=footway is equivalent to highway=path foot=designated and neither says yes or no for bicycle. The default for path (and thus for highway=footway) is bicycle=yes. So that should be the same. 2) "route=bicycle" denotes a bicycle route, which is a logical association of some bicycle route ref with all the underlying ways. It really does not say anything about access. There could be a bicycle route for which many or all of the ways are access=private. Overall I would recommend to let the route=bicycle relation simply associate the refs (and shields), and to let access tags be about access, and not try to do anything fancier. Does this make sense?

1 1

Commit r3691: preserve_v2.patch: reduce distortion at lower zoom levels
by svn commit 04 Aug '16

04 Aug '16

Version mkgmap-r3691 was committed by gerd on Thu, 04 Aug 2016 preserve_v2.patch: reduce distortion at lower zoom levels improve the routines which preserve points so that the line simplification (DouglasPeuckerFilter) doesn't remove points which are important for correct rendering Expected effects: . fewer distored polygons and lines at resolutions below 24, esp. where different lines or polygons share points (e.g. white triangles in the sea or unconnected T-junctions visible in GPSMapEdit) - slightly increased img size http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3691

1 0