locator rules and transparent maps
Hi, I tried to create a transparent map (an additinal layer on top of my basemap) containing address informations, but this does not seem to work. If I include the locator rules (means only create mkgmap:* variables), the maps are no longer transparent, independent of what I use for options. If I remove all mkgmap:* assignements, the map is transparent again. Any idea about this? 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, I've observed a similar behaviour in BaseCamp. I don't know why the parameter '--transparent' does not what it is expected to do, but the background with type '0x4b' is always shown in BaseCamp regardless if the parameter is set or not. Is this caused due to BaseCamp behaviour or due to a possible bug in mkgmap? Is one of these parameters I use at least the reason for creating the background (multi)polygon? ... --add-pois-to-lines --add-pois-to-areas --pois-to-areas-placement --link-pois-to-ways --adjust-turn-headings=1 --process-exits --merge-lines --remove-short-arcs --reduce-point-density --reduce-point-density-polygon --min-size-polygon --draw-priority=10 --index --route --tdbfile ... A workaround is to add a transparent bitmap with type '0x4b' to the '.typ' file and delete the corresponding entry in the '[_drawOrder]' section. Is there already an answer / a solution to the previous post from Thorsten? Thank you. -- View this message in context: http://gis.19327.n5.nabble.com/locator-rules-and-transparent-maps-tp5740571p... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Please ensure that you use at least mkgmap version r2479. In older versions it happened that --transparent did not work for some countries. WanMil
Hi,
I've observed a similar behaviour in BaseCamp. I don't know why the parameter '--transparent' does not what it is expected to do, but the background with type '0x4b' is always shown in BaseCamp regardless if the parameter is set or not. Is this caused due to BaseCamp behaviour or due to a possible bug in mkgmap?
Is one of these parameters I use at least the reason for creating the background (multi)polygon? ... --add-pois-to-lines --add-pois-to-areas --pois-to-areas-placement --link-pois-to-ways --adjust-turn-headings=1 --process-exits --merge-lines --remove-short-arcs --reduce-point-density --reduce-point-density-polygon --min-size-polygon --draw-priority=10 --index --route --tdbfile ...
A workaround is to add a transparent bitmap with type '0x4b' to the '.typ' file and delete the corresponding entry in the '[_drawOrder]' section.
Is there already an answer / a solution to the previous post from Thorsten?
Thank you.
Hi WanMil, WanMil wrote
Please ensure that you use at least mkgmap version r2479. In older versions it happened that --transparent did not work for some countries.
Sorry, I've forgotten to mention that I'm using mkgmap version 2540. Greetings -- View this message in context: http://gis.19327.n5.nabble.com/locator-rules-and-transparent-maps-tp5740571p... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Another option is to replace 0x4b with another polygon without special behaviour. That gives consistent results and no drawbacks that I could notice so far... On 30.03.2013 18:20, WanMil wrote:
Please ensure that you use at least mkgmap version r2479. In older versions it happened that --transparent did not work for some countries.
WanMil
Hi,
I've observed a similar behaviour in BaseCamp. I don't know why the parameter '--transparent' does not what it is expected to do, but the background with type '0x4b' is always shown in BaseCamp regardless if the parameter is set or not. Is this caused due to BaseCamp behaviour or due to a possible bug in mkgmap?
Is one of these parameters I use at least the reason for creating the background (multi)polygon? ... --add-pois-to-lines --add-pois-to-areas --pois-to-areas-placement --link-pois-to-ways --adjust-turn-headings=1 --process-exits --merge-lines --remove-short-arcs --reduce-point-density --reduce-point-density-polygon --min-size-polygon --draw-priority=10 --index --route --tdbfile ...
A workaround is to add a transparent bitmap with type '0x4b' to the '.typ' file and delete the corresponding entry in the '[_drawOrder]' section.
Is there already an answer / a solution to the previous post from Thorsten?
Thank you.
_______________________________________________ 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
littlehelper wrote
I've observed a similar behaviour in BaseCamp. I don't know why the parameter '--transparent' does not what it is expected to do, but the background with type '0x4b' is always shown in BaseCamp regardless if the parameter is set or not. Is this caused due to BaseCamp behaviour or due to a possible bug in mkgmap?
I've tried a lot and I can say defenitely YES, this is due to BaseCamp. According to GMapTool, mkgmap applies the transparent flag to '*.img' files correctly. This is true for a map created with --tdbfile to show in BaseCamp and it is true for maps built with --gmapsupp. In both cases transparent maps are visible 'above' the basemap (higher --draw-priority assumed) and are transparent like expected. Only if I use the transparent map as the only visible layer in BaseCamp or on the GPS device, BaseCamp and the GPS device insert a surrounding background. So this - I would say undesired fact - is due to Garmin and NOT due to mkgmap. In short: mkgmap works espacially well regarding the --transparent option, even if 'mkgmap:*' tags are used. Greetings -- View this message in context: http://gis.19327.n5.nabble.com/locator-rules-and-transparent-maps-tp5740571p... Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (4)
-
Felix Hartmann -
littlehelper -
Thorsten Kukuk -
WanMil