Re: [mkgmap-dev] Address search on device with --x-split-name-index option

Hi Steve, same problem with r3449 and r3472. I did a clean svn checkout for both and compiled and copied the jar into my My options: --max-jobs --route --bounds=bounds.zip --index --housenumbers --gmapsupp --x-split-name-index -c template.args The template.args contains a few tiles in the alps.

Re: [mkgmap-dev] tag landuse=residential produced false areas

Danke, da muss ich mir was einfallen lassen im Stylefile, wie ich die Kombination aus admin_level und place=village entferne. Muss noch mal nachdenken, was da sinnvoll ist. Die Ursache ist ja jetzt klar. Habe auch die Relation in JOSM gefunden. mfg thomas Am 09.04.2017 um 19:40 schrieb Gerd

Re: [mkgmap-dev] tag landuse=residential produced false areas

Hi Thomas, I've changed the default style to contain echotags like this: place=village {echotags "p=v"} [0x03 resolution 19] and used your input file. The output is JoinedWay generated from 87213118 [admin_level=9, boundary=administrative, mkgmap:cache_area_size=2224558.0389404297,

Re: [mkgmap-dev] tag landuse=residential produced false areas

I use for test the 'buildin-style'. But it makes no differenzes, if I use my own style. Own style is based on defaultstyle older relase mkgmap. Only small differenzes. But is is the 0x3 . See img2ms.de/bilder/Mapedit_0x3.jpg. My .args -file and the java mkgmap-call :

Re: [mkgmap-dev] tag landuse=residential produced false areas

Hi Thomas, what do you mean with "it is the default style" ? I don't see the line place=village | landuse= residential [0x03 resolution 18] in the default style that is shipped with r3890. That uses 0x10 for landuse=residential and 0x03 for place=village So, I assume it is a modified version of a

[mkgmap-dev] tag landuse=residential produced false areas

Hi all, i have testet a few mkgmap-release, included the new r-3890. But the wrong polygons comes with all releases. What i did.: in stylefile polygons is the line : /place=village | landuse= residential [0x03 resolution 18]. / It is the defaultstyle. and in lines : /boundary=administrative &

Re: [mkgmap-dev] gaps in road and other issues with r3875

Thanks Gerd, mkgmap-r3890 solved all issues, gap is gone and the small map with the default style is visisble again. Hi Minko, I think the problem was introduced with r3857. I've reverted those changes in r3889. Please check if it also solves the problem with

Re: [mkgmap-dev] Commit r3889: revert most changes from r3857, they seem to cause incorrect maps under certain circumstances

Hi Steve, yes, sorry, I've made this error before. r3890 is okay again. Gerd Von: mkgmap-dev im Auftrag von Steve Ratcliffe Gesendet: Sonntag, 9. April 2017 12:41:33 An:

[mkgmap-dev] Commit r3890: revert unintended change in build.xml

Version mkgmap-r3890 was committed by gerd on Sun, 09 Apr 2017 revert unintended change in build.xml http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=3890 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk

Re: [mkgmap-dev] Commit r3889: revert most changes from r3857, they seem to cause incorrect maps under certain circumstances

On 09/04/17 11:17, Gerd Petermann wrote: please check, this release is not yet available for download In particular the following line was removed: The builds are done in a clean environment without downloading any dependencies for optional stuff.

Re: [mkgmap-dev] Commit r3889: revert most changes from r3857, they seem to cause incorrect maps under certain circumstances

On 09/04/17 11:17, Gerd Petermann wrote: please check, this release is not yet available for download. That's because it doesn't compile :) ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk

Re: [mkgmap-dev] Commit r3889: revert most changes from r3857, they seem to cause incorrect maps under certain circumstances

Hi Steve, please check, this release is not yet available for download. Gerd Von: mkgmap-dev im Auftrag von svn commit Gesendet: Sonntag, 9. April 2017 11:49:54 An:

Re: [mkgmap-dev] Address search on device with --x-split-name-index option

Hi Steve, okay, I'll try with the older versions. Gerd Von: mkgmap-dev im Auftrag von Steve Ratcliffe Gesendet: Sonntag, 9. April 2017 11:52:09 An: mkgmap-dev@lists.mkgmap.org.uk Betreff:

Re: [mkgmap-dev] gaps in road and other issues with r3875

Hi Minko, I think the problem was introduced with r3857. I've reverted those changes in r3889. Please check if it also solves the problem with the gap. Gerd Von: mkgmap-dev im Auftrag von lig fietser

Re: [mkgmap-dev] Address search on device with --x-split-name-index option

Hi When I change the code in mdr20 to ignore the additional entries produced with the "--x-split-name-index" option the problem seems to be solved, I just don't find "Obere Rheingasse" when I search for "Rheingasse". The on device version of mdr20 certainly supports this, so it should work

[mkgmap-dev] Commit r3889: revert most changes from r3857, they seem to cause incorrect maps under certain circumstances

Version mkgmap-r3889 was committed by gerd on Sun, 09 Apr 2017 revert most changes from r3857, they seem to cause incorrect maps under certain circumstances http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=3889 ___ mkgmap-dev mailing list

Re: [mkgmap-dev] Possible problem with global search index since r3875

Hi The rule that produces the label "13/14 Hauptstrasse" (start is highway shield code) is this: highway=primary {name '${ref|highway-symbol:box} ${name}' | '${ref|highway-symbol:box}' | '${name}'; addlabel '${name} (${ref})' } This may be unpopular but we should stop doing this. This

Re: [mkgmap-dev] gaps in road and other issues with r3875

Thanks, encoded it with UTF8 and it is now working, r3660 accepted ANSI coding but later releases not anymore? Van: mkgmap-dev namens Gerd Petermann Verzonden: zondag 9 april 2017

Re: [mkgmap-dev] gaps in road and other issues with r3875

Next issue is the gap. The gap is only visisble with my OFM styles. Other map styles are ok. It appears with r3875 and later. Does not appear with r3847. The hole is exactly at the junction from the Schijndelseweg where two lanes merge, I think mkgmap throws away a connection node? Nothing

Re: [mkgmap-dev] gaps in road and other issues with r3875

Hi Minko, okay, that is probably a problem of utf8 enocoding. Your file is not utf8. Gerd Von: mkgmap-dev im Auftrag von lig fietser Gesendet: Sonntag, 9. April 2017 11:08:30 An:

Re: [mkgmap-dev] gaps in road and other issues with r3875

Hi Gerd, First a minor problem, license2.txt crashes with 3880 but not with mkgmap-r3660, (3847 crashes too) Error reading license file licentie2.txt java.nio.charset.MalformedInputException: Input length = 1 In my args file I have license-file: licentie2.txt It has nothing to do with the

Re: [mkgmap-dev] gaps in road and other issues with r3875

Hi Minko, okay, tried with that small area and no options beside --nsis and yes, MapSource doesn't show a map. With older version it works. No idea why, I have to compare the img files. Gerd Von: mkgmap-dev im

Re: [mkgmap-dev] gaps in road and other issues with r3875

Hi Minko, most changes since r3487 were for the index, 3877 fixed a routing problem. No change regarding RGN or handling of license file, esp. no change that would explain the gap. Don't know how to reproduce that problem. Is it related to OSM data or only to options / contents of other input

Re: [mkgmap-dev] Address search on device with --x-split-name-index option

I think I got the same results on my Oregon 600, so thats why I dont use --x-split-name-index Van: mkgmap-dev namens Gerd Petermann Verzonden: zondag 9 april 2017 01:15:02 Aan:

[mkgmap-dev] Address search on device with --x-split-name-index option

Hi all, not sure how this works on other devices. I have a map containing a part of the alps with parts of Germany, Switzerland and France. On my Oregon 600 when I search for an address I have some dialogs 1) select a country (I select Switzerland) 2) select city or select "search all" 3) Enter

[mkgmap-dev] gaps in road and other issues with r3875

Hi, Users of my OFM map have reported gaps in the roads (mainly non routable lines used for highways that are forbidden for cyclists). I've found out this is worse in the latest mkgmap releases 3875, 3880. See the screenshot, the location is