logo separator

[mkgmap-dev] Problem Displaying Polygons with Extended Type codes

From Charlie Ferrero charlie at cferrero.net on Sun Jul 3 06:54:13 BST 2011

On 29/06/2011 01:57, Bill Lancashire wrote:
> I have recently noticed that polygons assigned codes of the type 0x101xx
> are not displayed on my Garmin 62s. However, if I open the compiled maps
> in a package such as GPSMapEdit I can see that the features are indeed
> compiled correctly in the maps.
>
> I am using version r1973
> The polygons are correctly defined in a TYP file
> If I redefine the polygons to alternative unused codes of type 0x2x or
> 0x3x and also change the code in the TYP file then the polygons are
> displayed correctly.
>
> It does not seem to matter what the Drawing Level is in the TYP file.
> Non of the 0x101xx types are ever displayed.
>
> In the case of Polylines, I have used several codes of the types
> 0x100xx, 0x101xx and 0x105xx and they are displayed correctly.
>
> I am really puzzled by this and would really appreciate any insight into
> what is happening.
>
> At the lower drawing levels in the TYP file I have the following defined:
>
> Type *0x4b* [*Background (coverage)*], Drawing order: *1
>
> *Type *0x32* [*Sea*], Drawing order: *2 (Placeholder only)
>
> *Type *0x27* [*?*], Drawing order: *3 **(Placeholder only)
>
> *Then follows Drawing Level 4 with codes 0x02, 0x03 etc.
>
> Any ideas on this please?.
Bill,

If you can post a link to a small gmapsupp.img file (including your 
TYP), we can try it on our own devices and see if this is a "feature" of 
the GPSMap62s, or if there's something else wrong in your compile.

Charlie



More information about the mkgmap-dev mailing list