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: [email protected] Date: Mon, 2 Feb 2015 19:11:36 +0700 Subject: Re: [mkgmap-dev] FW: Lines distorted To: [email protected] 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 <[email protected]> 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: [email protected] Date: Sun, 1 Feb 2015 13:04:45 +0700 To: [email protected] 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 <[email protected]> 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: [email protected] > To: [email protected] > 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 > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] 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 [email protected] 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 [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
