[mkgmap-dev] --route and --transparent

Fri Feb 16 10:07:48 GMT 2018

Hi Gerd, I suggest the interface would be better being slightly more
meaningful than transparent=N|Y|S.

I'm also not clear what the use of a transparent map with a non-transparent
background is - surely if it has a non-transparent background you can't see
through it anyway. Obviously I'm missing something! (I don't currently use
transparency.)

Regards,
Mike

-----Original Message-----
From: Gerd Petermann [mailto:gpetermann_muenchen at hotmail.com] 
Sent: 16 February 2018 09:34
To: Development list for mkgmap <mkgmap-dev at lists.mkgmap.org.uk>
Subject: Re: [mkgmap-dev] --route and --transparent

Hi all,

attached is a patch that implements the --transparent option like this:
- If not given, transparent flag is not set and 0x4b background is added
- if given with no parameter, parameter Y is added
- if given with parameter Y, transparent flag is set and 0x4b background is
NOT added
- if given with parameter S, transparent flag is set and 0x4b background is
added

So, with this patch --transparent and --transparent=Y are equal.
Maybe it would be better to change that so that --transparent means
--transparent=S ?

A binary is here:
http://files.mkgmap.org.uk/download/422/mkgmap.jar

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von
osm at pinns <osm at pinns.co.uk>
Gesendet: Freitag, 16. Februar 2018 08:31:56
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] --route and --transparent

Hi Gerd

That sounds very promising  to add an additional transparency option ; I
too have noticed the lack of 0x4b in various Garmin maps.

Nick

On 16/02/2018 06:52, Gerd Petermann wrote:
> Hi all,
>
> GPSMapEdit descripes the transparent option for cgpsmapper like this:
> N : Not a transparent map
> Y : Transparent map without background object
> S:  Transparent map with transparent background object
>
> in mkgmap the meaning of the --transparent option is like Y
> When I change mkgmap so that it creates 0x4b background polygons even when
the transparent flag is set
> routing still works. This matches the "S". My understanding is that the
typ file must define a transparent
> 0x4b polygon.
>
> So, I think we should implement the transparent option as in cpgsmapper,
or maybe simply change it from Y to S.
>
> I've also noticed that the Garmin overview maps for Adria Topo and
TopoGuide Hungary 2.12c don't
> contain 0x4b polygons. In mkgmap we always add a 0x4b polygon to the
overview map, even if the transparent
> flag is set. No idea if this is important somewhere, it doesn't seem to
have an influence on the routing,
> but it seems to waste some bytes.
>
> Gerd
>
>
>
>
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von
Gerd Petermann <gpetermann_muenchen at hotmail.com>
> Gesendet: Donnerstag, 15. Februar 2018 14:41:19
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] --route and --transparent
>
> Hi Steve,
>
> I cannot reproduce that. I changed the code in TREHEader so that the bit
is no set:
> //              if (props.containsKey("transparent"))
> //                      poiDisplayFlags |= POI_FLAG_TRANSPARENT;
>
> Routing doesn't work in Mapsource or Basecamp.
> I've double checked with TreDisplay that the flag is really not set in any
map.
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von
Steve Ratcliffe <steve at parabola.me.uk>
> Gesendet: Donnerstag, 15. Februar 2018 14:01:14
> An: mkgmap-dev at lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] --route and --transparent
>
> On 15/02/18 11:04, Gerd Petermann wrote:
>> 1) it sets the flag in the TRE field at offset 0x3f
>> 2) it disables the additional 0x4b background polygons
>>
>> Maybe only the combination of both actions causes trouble in the PC
programs?
> cgpsmapper had the option to do 2) without doing 1) which it calls a
> semi-transparent map.
>
> I tried un-setting the flag on a transparent map and routing started
> working again in mapsource. So it is just the flag that causes the
> problem.  I don't know what the flag really does.
>
> I also noted from the documentation that cgpsmapper seems to add 32 to
> the draw priority of a transparent map, which is something that we do
> not do.
>
> Steve
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev