- mkgmap-dev - The mkgmap lists

Question about MP processing/area2poi
by Thorsten Kukuk 12 Apr '13

12 Apr '13

Hi, There is the IJsselmeer Relation (http://www.openstreetmap.org/browse/relation/945096) for example. All outer ways are tagged with "natural=coastline", the MP is tagged additional with name and toponym=water. Now I have the following rule in my style/points file: (place=sea | place=ocean | toponym=water) & name=* [0x1400 level 6] But this POI is never created. I tried to find and understand the relevant java code myself, but failed :( So is this again the problem that outer ways and MP are tagged and the MP tags are ignored? I think merging outer lines with coastline and the multipolygon tags is a bad idea, and deleting the natural=costline tag in the style is too late (I really don't need it). Else any way to solve this? Or is my error somewhere else? Thanks, Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

6 9

Commit: r2566: Fix center point calculation of large ways and polygons
by svn commit 11 Apr '13

11 Apr '13

Version 2566 was committed by wanmil on Thu, 11 Apr 2013 Fix center point calculation of large ways and polygons There was a possible integer overflow for ways and polygons with a large number of points or in case the points were located far aways from 0°/0°. In this case the center point calculation returned a wrong location.

2 1

Question reg. StyleImpl
by GerdP 11 Apr '13

11 Apr '13

Hi programmers, I found quite a lot of places in mkgmap source with a block like below. I'd prefer to put this into a static method like public static Style readStyle(Properties props) in the StyleImpl class. Any reasons why that wasn't done until now? String loc = props.getProperty("style-file"); if (loc == null) loc = props.getProperty("map-features"); String name = props.getProperty("style"); if (loc == null && name == null) name = "default"; try { this.style = new StyleImpl(loc, name); this.style.applyOptionOverride(props); } catch (SyntaxException e) { System.err.println("Error in style: " + e.getMessage()); throw new ExitException("Could not open style " + name); } catch (FileNotFoundException e) { String name1 = (name != null)? name: loc; throw new ExitException("Could not open style " + name1); } Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Question-reg-StyleImpl-tp5756589.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 1

Creating non-NT maps
by Nuno Pedrosa 11 Apr '13

11 Apr '13

Good evening, I'm trying to create a POI only map, to be uploaded into a Garmin Quest GPS. But I keep getting a NT map and I could not find any specific options to force a non-NT file format. How can I choose non-NT format? Right now, I'm running this command line: java -jar -Xmx256M \mkgmap\mkgmap.jar --code-page=1252 --output-dir=Tenerife --read-config=options.txt and the options file contains: product-id: 1 index tdbfile family-name: Caches Tenerife family-id: 222 series-name: Caches Tenerife description: Caches Tenerife overview-mapnumber: 85452345 mapname: 85452346 overview-mapname: imgfromgpx style-file: Resources/styles style: default transparent input-file: out.osm Thank you, Nuno Pedrosa.

3 3

levels vs. resolution
by Henning Scholland 11 Apr '13

11 Apr '13

Hithere If I got it right you can use resolution in style-file and this is directly used as a garmin-map-level. OR I can use level in style-file and this is transferred via --levels="..." to agarmin-map-level. Is there a reason for having two ways of telling mkgmap on which garmin-map-level a object should be displayed? Maybe in help-file it should be written a little bit clearer that --levels="..." is only needed if level is used in style-file. Like: --levels=levels code Change the way that the levels on the map correspond to the zoom levels in the device. See customisation help. The default is: "0=24, 1=22, 2=20, 3=18, 4=16, 5=15", although each style can have its own default. Only needed if level is used in style instead of resolution. Henning

3 5

Translation system proposal
by Carlos Dávila 11 Apr '13

11 Apr '13

Currently we have the English word "Exit" in the default lines style file, which is used by the exit_hint option. Obviously it isn't appropriate for all languages, so I'm using a simple hack to avoid it, that consist in changing "Exit" by the variable ${mkgmap:exit_tr} in the style file and defining it in addresses file with lines of the form mkgmap:country=ESP { set mkgmap:exit_tr='Salida' }. It works fine, but I have thought of an better system that may be worth implementing it to be used somewhere else (may be in the nsis template). It would consist in: 1-Adding a lang=xx definition to each country entry in LocatorConfig.xml 2-Creating a translations file with entries for each language: exit_tr: en=Exit es=Salida fr=Sortie ... another_word_tr: en=word es=palabra fr=mot ... What do you think? Would it be easy to implement it?

5 9

Patch: remove warning of admin_centre/label in multipolygons
by Thorsten Kukuk 10 Apr '13

10 Apr '13

Hi, a huge amount of mulitpolygons contains meanwhile points with the role 'admin_centre' and 'label'. So I think mkgmap should print no longer a warning about this, especially as we use the role 'label' some lines later ourself. This will only fillup the log file. Attached is a small patch I'm using. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

2 1

Commit: r2565: Issue no warning for mp node elements with role admin_centre or label
by svn commit 10 Apr '13

10 Apr '13

Version 2565 was committed by wanmil on Wed, 10 Apr 2013 Issue no warning for mp node elements with role admin_centre or label --Thorsten Kukuk

1 0

routing problems since r2448
by GerdP 10 Apr '13

10 Apr '13

Hi, for details see also http://gis.19327.n5.nabble.com/No-roads-near-target-bug-in-Schwabmunchen-tp… For those that did not follow this thread: I hope we found the explanation for some strange routing problems which occur in combination with styles that assign routable types to ways but do not set road_class or road_speed. It seems that this can cause problems when searching e.g. for POI . If I got this right, the problem occurs when such a way is written to a sub division in the img file before any "real" road. It seems to confuse the algo in the device. With r2448 up to r2564, it is much more likely that this problem occurs, because the program always stores non-routable ways first, roads later. This was a side effect of the change in the short-arc-removal function. I've created a patch for this, see http://gis.19327.n5.nabble.com/No-roads-near-target-bug-in-Schwabmunchen-tp… Gerd -- View this message in context: http://gis.19327.n5.nabble.com/routing-problems-since-r2448-tp5756510.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

1 0

extra-used-tags in style file options
by WanMil 09 Apr '13

09 Apr '13

In the mkgmap default style the options file contains the option: extra-used-tags= name hello world I think this option could be empty: extra-used-tags= Any objections? Otherwise I will commit it. WanMil

1 0