February 2015 - mkgmap-dev - The mkgmap lists

Commit: r3436: use not-contained filter to avoid duplicated values in route_ref,
by svn commit 03 Feb '15

03 Feb '15

Version mkgmap-r3436 was committed by gerd on Mon, 02 Feb 2015 use not-contained filter to avoid duplicated values in route_ref, use semicolon instead of comma to separate the values. Proposed by A drian: "I have chosen the semicolon because it is the recommended separator in OSM https://wiki.openstreetmap.org/wiki/Semicolon Also, using a comma as separator would not fix my example. Another possibility might be to recognise multiple characters as separators, e.g. the semicolon and the comma would both be treated as a separator. This would depend on whether it is feasible to extend Maxim's patch to recognise multiple separators."

2 1

Re: [mkgmap-dev] FW: Lines distorted
by Gerd Petermann 02 Feb '15

02 Feb '15

Hi Dave, I agree that these options are difficult to understand. The options -- polygon-size-limits and -- min-size-polygon use the size of the bounding box of an object. The size is measured in Garmin units. With the style rules you specify the resolutions at which an object should be drawn. For each resolution besides 24 several filters are used to do the rounding of coordinates and smothing of lines for the lower resolution for each object. One of the filters is the SizeFilter which is configured with the above options. If the larger value of width and height is smaller than the given value in NUM scaled by the resolution, the element is dropped before more complex filters are used. So, if you change the value to e.g. 50 you may not find as many small parks or forest polygons at resolution 22 as with the default. The --polygon-size-limits option works similar, but allows to specify different NUM values for the different levels. Gerd From: daveswarthout(a)gmail.com Date: Mon, 2 Feb 2015 19:11:36 +0700 Subject: Re: [mkgmap-dev] FW: Lines distorted To: gpetermann_muenchen(a)hotmail.com Well, it's probably mostly because I'm not at all familiar with the operations required to produce these maps. AFAIK, the options file is the only place some of these parameters are described. For example, --min-size-polygon=NUM Removes all polygons smaller than NUM from the map. This reduces map size and speeds up redrawing of maps. Recommended value is 8 to 15, default is 8. See also polygon-size-limits. What does this mean? "removes all polygons smaller than NUM". Is NUM a length, the number of sides, or what? What effect does it have on the outputted map with a setting of 8 as opposed to 15? I was really hoping there was a manual of some sort that described the processing, the options, etc., with some nice examples and explanatory text. If there is not, I'll just have to learn a little bit every day until I'm up to speed <g> If I ever reach a point where I'm knowledgeable enough to help with the documentation, I would certainly be willing to do that. Thanks, Dave On Sun, Feb 1, 2015 at 4:39 PM, Gerd Petermann <gpetermann_muenchen(a)hotmail.com> wrote: Hi Dave, not sure how to help you. You say that you have a lot of open questions. after reading the docu. Please post them if they are still open or help to improve the documentation. Gerd From: daveswarthout(a)gmail.com Date: Sun, 1 Feb 2015 13:04:45 +0700 To: mkgmap-dev(a)lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] FW: Lines distorted I'm still reading this thread but haven't tried the new mkgmap.jar yet. I was hoping for a way to smooth polygons and Gerd's reply to Enrico indicates that the patch and new binary only help smoothing lines, so I stopped paying attention. But I'm interested in learning more about mkgmap and the map making process in general. I saw another post a while back where Gerd says something along the lines of "people still don't know how to use a patch". The documentation for mkgmap itself is pretty thin. There's the style manual, and the little blurb about TYP files but nothing to tie it all together. And I've not found anything about how to use mkgmap other then the options text file. The explanatory statements in there are helpful but leave a lot unsaid. A careful reading of the "Optimization Options", for example, left me with more questions than answers. You are the developers of the program, so many of these things must seem glaringly obvious. But they are not. How is one supposed to know how to utilize a patch? Is there a users manual somewhere? Thanks, Dave On Sat, Jan 31, 2015 at 4:41 PM, Gerd Petermann <gpetermann_muenchen(a)hotmail.com> wrote: Hi Enrico, I fear I can't change mkgmap to fix this problem. The problem is more or less bad luck. In some cases, you have placed the points of the ways more or less exactly between the points of the Garmin grid, others are very near to the grid points. If I got it right, we can only produce a straight line in the garmin format when we allow to move certain points by more than 2 metres, and in that case the WrongAngleFixer will prefer the correct position to the bad angle. I''ve attached the grid as a gpx file, if you load that into JOSM you probably see what I mean. If you prefer "nicer" rendering on the Garmin map you may move some points closer to the grid to solve the problem. Gerd > Date: Fri, 30 Jan 2015 09:40:37 -0700 > From: e.rossini73(a)alice.it > To: mkgmap-dev(a)lists.mkgmap.org.uk > Subject: Re: [mkgmap-dev] FW: Lines distorted > > yes you'are right, I'm interested to straight out the line "Via Ronchi Di San > Francesco Di Paola". > would be great if you'll find something to do this. > THANKS. > --enrico > > > > > -- > View this message in context: http://gis.19327.n5.nabble.com/Distorted-lines-tp5831842p5831971.html > Sent from the Mkgmap Development mailing list archive at Nabble.com. > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com

1 0

Bug in handling of bus stops
by A drian 02 Feb '15

02 Feb '15

This bug was highlighted in r3334 when the test public_transport=platform was added to these four rules in the default points style file (lines 45-63): (public_transport=platform | highway=bus_stop | railway=tram_stop | railway=halt | railway=station) & (ref=* | route_ref=*) { set ref='${ref|def:}(${route_ref})'; } (public_transport=platform | highway=bus_stop | railway=tram_stop | railway=halt | railway=station) & lit=yes & (shelter=yes | covered=yes) { set ref='${ref|def:}*'; } (public_transport=platform | highway=bus_stop | railway=tram_stop | railway=halt | railway=station) & lit!=yes & (shelter=yes | covered=yes) { set ref='${ref|def:}+'; } (public_transport=platform | highway=bus_stop | railway=tram_stop | railway=halt | railway=station) & (shelter=no | covered=no) { set ref='${ref|def:}-'; } What happens is that if a node has two of the tags in the list public_transport=platform | highway=bus_stop | railway=tram_stop | railway=halt | railway=station then the node is processed twice by each rule, so the route_ref and the shelter marker (*, + or -) are doubled-up. Looking at https://www.openstreetmap.org/node/1424432523 - this node is tagged public_transport=platform and highway=bus_stop. Prior to r3334, the node had only one tag that matched and there was no doubling-up. From r3334 onwards, there are two tags that match and the result is Agglo Hérault Méditerranée: (1;2;3;4;5,4,4,3,3)(1;2;3;4;5,4,4,3,3)++ Gare SNCF. I believe it is not intended that style rules should work in this way, therefore it is a bug in the code. In which case it is a question for the Java experts. Adrian

4 8

[Patch v2] avoid duplicate evaluation of rules
by Gerd Petermann 02 Feb '15

02 Feb '15

Hi all, cosmetic change : always report the new rule-id field in the style stats. binary: http://files.mkgmap.org.uk/download/245/mkgmap.jar Gerd

1 0

Copyright message not showing up starting 3433
by Ervin Malicdem 01 Feb '15

01 Feb '15

Hi I believe we had a change regarding copyright messages on 3430. It seems on 3433, Copyright message is no longer shown on the device (About page or About>Detailed Maps page) I am only using license text and copyright message but not copyright file. License text is showing up without problems on Basecamp but Copyright Message is no longer seen on the device. I test it on Nuvi 1360 and GPSMap 62s. Thanks. Ervin M. *Schadow1 Expeditions* - A Filipino must not be a stranger to his own motherland. http://www.s1expeditions.com

2 2

Commuter rail stations
by Brian Egge 01 Feb '15

01 Feb '15

When I look at POIs with a Garmin map, I have a category for 'Suburban Rail Station'. In the NYC area, there are hundreds of commuter rail stations and a handful of regional stations. Having the two listed separately in the POI search is useful, as usually you are searching for one or the other. When using an mkgmap, it only has the single railway station type. I believe the suburban railway stations can be tagged with commuter=yes, but I do not know what Garmin hex code causes this category to appear. Any idea what the code is or how to figure it out? Brian

2 1

FW: Lines distorted
by Gerd Petermann 01 Feb '15

01 Feb '15

From: gpetermann_muenchen(a)hotmail.com To: daveswarthout(a)gmail.com Subject: RE: [mkgmap-dev] Lines distorted Date: Fri, 30 Jan 2015 09:02:45 +0100 Hi Dave, up to now the reduce-point-xxx options are used for the DouglasPeuckerFilter which smoothes lines at lower resolutions. They are ignored for resolution 24, in which the WrongAngleFixer is used to guess how an object can be placed on the Garmin raster so that it looks as much as possible like the OSM described by the OSM data. If you want to play with that: The WrongAngleFixer has a few constants, e.g. you may increase the value MAX_DIFF_ANGLE_STRAIGHT_LINE = 3; or change the method calcMaxErrorDistance() to allow larger errors. Gerd From: daveswarthout(a)gmail.com Date: Fri, 30 Jan 2015 07:14:07 +0700 To: mkgmap-dev(a)lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Lines distorted I want to continue Enrico's questioning a bit. I have a similar issue with the way polygons display on my Garmin device. What appears as a smooth curve on the OSM slippy map are very blocky on the device. I have played with the reduce-point-density=4 and reduce-point-density-polygon=8 parameters in an attempt to smooth those curves but they seem to have no effect. I can live with the distortion but I wonder, what do these two parameters actually control? Cheers,Dave On Fri, Jan 30, 2015 at 12:22 AM, Andrzej Popowski <popej(a)poczta.onet.pl> wrote: Hi Enrico, Garmin maps have limited resolution, about 2.4m. One can't draw precisely a line, which length is near to this resolution. You can try to assign the same Garmin object type to all these segments, then probably mkgmap will be able to merge them and smooth. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

5 19