
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

On Thu, Apr 11, Henning Scholland wrote:
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?
For me working with levels is much easier than with resolution. It's much easier to maintain and if you want to change one resolution, you don't need to edit it in all places, only one is enough. 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)

Hi, just another question: Is there a limit of number of levels if I'm using level? In wiki ( http://wiki.openstreetmap.org/wiki/Mkgmap/help/style_rules#level_.28see_also... ) there is only a limited documented with resolution. If the number of levels is limited, the limited should be added to documentation (wiki and help-file). Henning

On Thu, Apr 11, Henning Scholland wrote:
Hi, just another question: Is there a limit of number of levels if I'm using level? In wiki ( http://wiki.openstreetmap.org/wiki/Mkgmap/help/style_rules#level_.28see_also... ) there is only a limited documented with resolution. If the number of levels is limited, the limited should be added to documentation (wiki and help-file).
Since level and resolution are the same "This is an alternative way of specifying the zoom level", of course the limitations are the same, too. 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)

Am 11.04.2013 11:53, schrieb Thorsten Kukuk:
On Thu, Apr 11, Henning Scholland wrote:
Hi, just another question: Is there a limit of number of levels if I'm using level? In wiki ( http://wiki.openstreetmap.org/wiki/Mkgmap/help/style_rules#level_.28see_also... ) there is only a limited documented with resolution. If the number of levels is limited, the limited should be added to documentation (wiki and help-file). Since level and resolution are the same "This is an alternative way of specifying the zoom level", of course the limitations are the same, too. Of course the garmin-map-level limit is the same. I meant if there is a limit for the number of level. Is it theoretic possible to define 24 levels? Like --levels="0=24, 1=23, ..., 23=1"?
Henning

yes the limit is 7 (0-6). That's why it would be great, if there would be a separate style-file for the overview map, that doesn't depend on the levels of the map. So then theoretically 24,23,22,21,20,18,16 (with 16 being empty) and 16, 14,12,10 (10 being empty) for the overview map would be possible. The overview map itself may also contain up to 7 levels. And instead of a complex reading mechanism for the normal .img files, it would suffice to read the old overview map (in case you add maps like contourlines which need no data in the overview map, or take out maps (just leave it inside and delete the tiles from the overview map so Mapsource/Basecamp don't crash when routing). On 11.04.2013 14:57, Henning Scholland wrote:
Am 11.04.2013 11:53, schrieb Thorsten Kukuk:
On Thu, Apr 11, Henning Scholland wrote:
Hi, just another question: Is there a limit of number of levels if I'm using level? In wiki ( http://wiki.openstreetmap.org/wiki/Mkgmap/help/style_rules#level_.28see_also... ) there is only a limited documented with resolution. If the number of levels is limited, the limited should be added to documentation (wiki and help-file). Since level and resolution are the same "This is an alternative way of specifying the zoom level", of course the limitations are the same, too. Of course the garmin-map-level limit is the same. I meant if there is a limit for the number of level. Is it theoretic possible to define 24 levels? Like --levels="0=24, 1=23, ..., 23=1"?
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
participants (3)
-
Felix Hartmann
-
Henning Scholland
-
Thorsten Kukuk