- mkgmap-dev - The mkgmap lists

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

PT rules in relations file
by Bernd Weigelt 31 Jan '15

31 Jan '15

Hi i'm playing around with the PT rules in relations, as example this node [1]. The node belongs to two route relations (RE8 and RB27) and one track relation (2324) When i enable the rules in relations i got the labels Unkel (Re8,re8,rb27,rb27) my wanted result is to get only one entry per relations, btw apply_once didn't help this is my code # Public transportation routes. type=route & (route=bus| route=trolleybus| route=ferry| route=subway| route=train| route=tram) & (ref=* | name=*) { add ref='${name}'; apply { set route_ref='$(route_ref),${ref}' | '${ref}'; set mkgmap:relref='${ref}'; apply role=passengers { set route_ref='$(route_ref),${mkgmap:relref}' | '${mkgmap:relref}'; } delete mkgmap:relref; } } How can get this result? And where is my error? Bernd [1] http://www.openstreetmap.org/way/58522211

2 4

Patch: New filter "not-contained"
by "Maxim Düster" 31 Jan '15

31 Jan '15

6 17

leading and trailing spaces
by Mike Baggaley 31 Jan '15

31 Jan '15

Good evening all, I've noticed that there are a number of unwanted leading and trailing spaces in OSM data. You can get a list of the ones on the name field using the following: name~'.* ' {echotags "name ends with a space"} name~' .*' {echotags "name starts with a space"} I can't see any facility in mkgmap to remove these, and was wondering whether the best way would be simply to code them out by replacing the following line in parseDense, parseNodes, ParseWays and parseRelations: String val = getStringById(...); With String val = getStringById(...).trim(); I can't think of any reason why a value would need to start or end with a space, so it seems reasonable to just remove them. Are there any other suggestions, or reasons why this should not be done? Regards, Mike

4 7

Commit: r3435: trimspaces2.patch: remove leading and trailing spaces from
by svn commit 31 Jan '15

31 Jan '15

Version mkgmap-r3435 was committed by gerd on Sat, 31 Jan 2015 trimspaces2.patch: remove leading and trailing spaces from tag values before style processing - Mike Baggaley

1 0

Commit: r3434: more debugging aids for WrongAngleFixer
by svn commit 31 Jan '15

31 Jan '15

Version mkgmap-r3434 was committed by gerd on Sat, 31 Jan 2015 more debugging aids for WrongAngleFixer - create WrongAngleFixer instance when bbox is known. - create gpx with Garmin Grid when bbox is small This has no effect unless special debugging code is activated which uses the bbox.

1 0

Commit: r3433: quote pipe symbol in doc
by svn commit 30 Jan '15

30 Jan '15

Version mkgmap-r3433 was committed by gerd on Fri, 30 Jan 2015 quote pipe symbol in doc

1 0

Commit: r3432: mkgmap_filter_not-contained.patch by Maxim Düster.
by svn commit 30 Jan '15

30 Jan '15

Version mkgmap-r3432 was committed by gerd on Fri, 30 Jan 2015 mkgmap_filter_not-contained.patch by Maxim Düster. Implements the new not-contained style filter. Can be used to test if a tag with a list of values already contains a given value.

1 0

Lines distorted
by demon.box 30 Jan '15

30 Jan '15

Excuse me, there are a method (option of mkgmap, etc.) to reduce the lines distorted? from OSM <http://gis.19327.n5.nabble.com/file/n5831842/mappa2.jpg> rendered for MapSource <http://gis.19327.n5.nabble.com/file/n5831842/mappa1.jpg> Thanks very much. --enrico -- View this message in context: http://gis.19327.n5.nabble.com/Lines-distorted-tp5831842.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

5 5

Commit: r3430: copyright3.patch by Mike Baggaley
by svn commit 29 Jan '15

29 Jan '15

Version mkgmap-r3430 was committed by gerd on Thu, 29 Jan 2015 copyright3.patch by Mike Baggaley The patch adds --copyright-file=file to the command options to allow multiple copyright messages to be included with the map. It also cosmetically changes the code for handling fake ids so that it conforms to the capitalisation convention (no functional change).

1 0