Problem Displaying Polygons with Extended Type codes
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?.
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
Charlie, thanks for your response. I have been doing a few controlled tests and I am now fairly sure that it is the GPSMap62s that will not display the 'extended' polygon codes. What I did was to compile a map using the 'default' style with r1979 together with a very simple TYP defining only 'leisure=playground [0x24 resolution 24]' (at draw level 7). This displayed correctly. Then I simply edited the 'polygons' file line to read 'leisure=playground [0x10103 resolution 24]' and suitably changed the TYP. In this case the polygon was NOT displayed. In both cases I used only the minimal arguments in the mkgmap compile command line. I will try to put a small GMAPSUPP.IMG online somewhere for others to confirm. Conversely, it would be good if I could test a build that someone else has made using an extended polygon code. Bill. Charlie Ferrero wrote:
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 _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 04/07/2011 12:50, Bill Lancashire wrote:
Charlie, thanks for your response.
I have been doing a few controlled tests and I am now fairly sure that it is the GPSMap62s that will not display the 'extended' polygon codes.
What I did was to compile a map using the 'default' style with r1979 together with a very simple TYP defining only 'leisure=playground [0x24 resolution 24]' (at draw level 7). This displayed correctly.
Then I simply edited the 'polygons' file line to read 'leisure=playground [0x10103 resolution 24]' and suitably changed the TYP. In this case the polygon was NOT displayed. In both cases I used only the minimal arguments in the mkgmap compile command line.
I will try to put a small GMAPSUPP.IMG online somewhere for others to confirm.
Conversely, it would be good if I could test a build that someone else has made using an extended polygon code.
Bill.
You can download a gmapsupp.img from http://www.cferrero.net/maps/gcc_downloads.html that includes lots of extended type polygons (land background, archeological sites, woods, gardens etc). You can get the TYP that is used here: http://www.cferrero.net/maps/map_downloads.html -- Charlie
Charlie, Thank you for providing the download links. They were very useful. After many rebuilds and recombination's of the TYP file split from your gmapsupp.img with my compiles I found the problem. It was a 'beginners' mistake on my part. I had been saving my TYP files with the 'OLD' Header format which meant that the drawing orders of the extended-code polygon types were somehow very messed up. No problem therefore with display of extended polygon codes on the Garmin GPSMAP62s. Thanks for the help. Bill. Charlie Ferrero wrote:
On 04/07/2011 12:50, Bill Lancashire wrote:
Charlie, thanks for your response.
I have been doing a few controlled tests and I am now fairly sure that it is the GPSMap62s that will not display the 'extended' polygon codes.
What I did was to compile a map using the 'default' style with r1979 together with a very simple TYP defining only 'leisure=playground [0x24 resolution 24]' (at draw level 7). This displayed correctly.
Then I simply edited the 'polygons' file line to read 'leisure=playground [0x10103 resolution 24]' and suitably changed the TYP. In this case the polygon was NOT displayed. In both cases I used only the minimal arguments in the mkgmap compile command line.
I will try to put a small GMAPSUPP.IMG online somewhere for others to confirm.
Conversely, it would be good if I could test a build that someone else has made using an extended polygon code.
Bill.
You can download a gmapsupp.img from http://www.cferrero.net/maps/gcc_downloads.html that includes lots of extended type polygons (land background, archeological sites, woods, gardens etc).
You can get the TYP that is used here: http://www.cferrero.net/maps/map_downloads.html
-- Charlie _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (2)
-
Bill Lancashire -
Charlie Ferrero