January 2015 - mkgmap-dev - The mkgmap lists

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

copyright improvements
by Mike Baggaley 29 Jan '15

29 Jan '15

Hi, The attached 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). Please try, and commit if you are happy with the change. Regards, Mike

2 4

problems with address search in Germany
by Bernd Weigelt 28 Jan '15

28 Jan '15

Hi since a few days, don't know the exact date, i have problems with the address search in Germany on my Oregon 650. The problem is not related to the new firmware 4.40, i got it also with 4.30 A, hopely understandable, description search for an address, before the problem i got a menu first line 'Spell Country' second line 'Deutschland' now i got only 'Country' in the second line next step add the country name 'Deutschland' seems to work third step 'Spell City' adding 'Koln' breaks after 'Ko' results in some cities with 'Ko' like Konz or Korschenbroich go back to 'Spell City' move the cursors manually to the third position behind the 'o' add 'ln', results in 'No results found' Searching for streets in Cologne didn't work, too But with with mkgmap:country=* {echotags ''} in inc/address, i got following as example. 4611686018434217727 (4611686018434217727) - [mkgmap:admin_level6=Köln, mkgmap:admin_level9=Chorweiler, mkgmap:admin_level5=Regierungsbezirk Köln, name=Bundesamt für Verfassungsschutz, addr:city=Köln, mkgmap:postcode=50765, addr:postcode=50765, mkgmap:postal_code=50765, addr:street=Merianstraße, mkgmap:street=Merianstraße, mkgmap:tagsincomplete=true, addr:housenumber=96, mkgmap:mp_created=true, mkgmap:cache_area_size=4114.5802001953125, mkgmap:housenumber=96, building=yes, mkgmap:country=DE, addr:country=DE, mkgmap:stylefilter=polygon, mkgmap:admin_level4=Nordrhein-Westfalen, mkgmap:region=Köln, mkgmap:admin_level10=Volkhoven/Weiler, mkgmap:city=Chorweiler] It strikes me that mkgmap_country for germany has only the letters 'DE' i've expected mkgmap:country=DEU Belgium or the Nederlands are correct tagged withmkgmap:country=BEL or mkgmap:country=NLD Where is the problem? thanks Bernd

2 2

Support place polygons in preprocessed bounds
by "Maxim Düster" 27 Jan '15

27 Jan '15

Hello Gerd, thank you for your reply. Regarding your surprising: you mean that the *.bnd files from the patched version can be used by the non-patched one? Hmm... shouldn't it behave like this? :) I have been thinking, it would just write additional boundaries with their attributes into the bnd files, but as the trunk version cannot use it, they are just ignored and don't disturb it. Anyway, for me it seems to work: after pre-compiling boundaries with the additional rule for osmfilter, I have access to the variables mkgmap:place and mkgmap:place_name which are set to meaningful values. You pointed out an interesting thing: it didn't come to my mind, place polygons could overlap. But actually, two city/town/hamlet/... polygons should not intersect as an object cannot belong to two localities. Or am I wrong? Probably I was too idealistic :) Update: In my region I found a place=town and a place=village that intersect, but it must be an error in the data. Anyway, I will think once more about this all and will have a look at the utilities you mentioned. Max --------------------------------------------- >From Gerd Petermann gpetermann_muenchen at hotmail.com on Mon Jan 26 14:03:52 GMT 2015 Hi Maxim, thanks for the patch. I was a bit surprised to notice that the output produced by the patched version is still usable by the trunk version. I did not see any change to handle e.g. overlapping place polygons. Do you plan to change the utility programs like BoundaryFile2Gpx, BoundaryCoverageUtil, and BoundaryDiff so that one can verify the results? Gerd --------------------------------------------- From: maxc at gmx.de[http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev] To: mkgmap-dev at lists.mkgmap.org.uk[http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev[http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev]] Date: Mon, 26 Jan 2015 11:21:07 +0100 Subject: [mkgmap-dev] Support place polygons in preprocessed bounds Hello everybody! I've attached a patch that supports processing of place polygons in precompiled bounds and using of this information in the style file. See my earlier message: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2015q1/022619.html[http://www… You can use it like following (as example): # Russia mkgmap:country=RUS & mkgmap:city!=* & mkgmap:admin_level8=* { set mkgmap:city='${mkgmap:admin_level8}' } mkgmap:country=RUS & mkgmap:city!=* & (mkgmap:place=city | mkgmap:place=town) { set mkgmap:city='${mkgmap:place_name}' } mkgmap:country=RUS & mkgmap:city!=* & mkgmap:admin_level6=* { set mkgmap:city='${mkgmap:admin_level6}' } To get this working, you have to create your own set of precompiled bounds with additional rule "type=multipolygon and place= and name=" for osmfilter and a run of BoundaryPreprocessor to set the variables mkgmap:place (attribute 'place' from the multipolygon) and mkgmap:place_name (attribute 'name' from the multipolygon). Cheers! Max

1 0

Support place polygons in preprocessed bounds
by "Maxim Düster" 26 Jan '15

26 Jan '15

2 1