Problem with aeroway=aerodrome as a relation
Could somehow mkgmap have an issue with aeroway=aerodrome as a relation? (instead a simple closed way) For example, this airport http://www.openstreetmap.org/way/90834745 have its internal grasses properly represented like here: http://cocardl.com.br/pv/viracopos.jpg On the other hand, this airport http://www.openstreetmap.org/relation/3896781 seems to overlap every internal feature (like grasses): http://cocardl.com.br/pv/galeao.jpg Is mkgmap giving different treatments for aeroway=aerodrome as a closed way and as a relation?
Hi Nelson, there is no special java code in mkgmap to treat aeroways. I guess you don't use the default style, so I can't say what goes wrong. A good tool to find out what mkgmap writes to the img file is GPSMapEdit. Use it to open the corresponding img file and double click into the area you want to analyse. It shows you what Garmin type the area has. Press escape to close the dialog box followed by delete to remove that polygon. Repeat this process until GPSMapEdit shows something like "Area of map coverage (0x4b, polygon)" If you do this for both img files (the good and the bad one) you should be able to find out what's different. Gerd
Date: Wed, 23 Sep 2015 23:45:05 -0300 From: naoliv@gmail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] Problem with aeroway=aerodrome as a relation
Could somehow mkgmap have an issue with aeroway=aerodrome as a relation? (instead a simple closed way)
For example, this airport http://www.openstreetmap.org/way/90834745 have its internal grasses properly represented like here: http://cocardl.com.br/pv/viracopos.jpg
On the other hand, this airport http://www.openstreetmap.org/relation/3896781 seems to overlap every internal feature (like grasses): http://cocardl.com.br/pv/galeao.jpg
Is mkgmap giving different treatments for aeroway=aerodrome as a closed way and as a relation? _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Thu, Sep 24, Gerd Petermann wrote:
Hi Nelson,
there is no special java code in mkgmap to treat aeroways. I guess you don't use the default style, so I can't say what goes wrong.
I would expect this is the drawing priority of objects as defined in the TYP file. My guess is, they are identical, and the device renders them in random order. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
Hi Gerd, assisting Nelson, using the default style we have ever encountered the first problem is the style does not look landuse = grass forcing us to include in inc / landuse_polygons line landuse = grass [0x17 resolution 20]. Using the default style (with grass included) we only have succeeded using the "comment out" in the following polygons lines of "default style": :# aeroway=airport [0x07 resolution 20] # aeroway=aerodrome [0x07 resolution 20] Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 4:32 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Nelson, there is no special java code in mkgmap to treat aeroways. I guess you don't use the default style, so I can't say what goes wrong. A good tool to find out what mkgmap writes to the img file is GPSMapEdit. Use it to open the corresponding img file and double click into the area you want to analyse. It shows you what Garmin type the area has. Press escape to close the dialog box followed by delete to remove that polygon. Repeat this process until GPSMapEdit shows something like "Area of map coverage (0x4b, polygon)" If you do this for both img files (the good and the bad one) you should be able to find out what's different. Gerd
Date: Wed, 23 Sep 2015 23:45:05 -0300 From: naoliv@gmail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] Problem with aeroway=aerodrome as a relation
Could somehow mkgmap have an issue with aeroway=aerodrome as a relation? (instead a simple closed way)
For example, this airport http://www.openstreetmap.org/way/90834745 have its internal grasses properly represented like here: http://cocardl.com.br/pv/viracopos.jpg
On the other hand, this airport http://www.openstreetmap.org/relation/3896781 seems to overlap every internal feature (like grasses): http://cocardl.com.br/pv/galeao.jpg
Is mkgmap giving different treatments for aeroway=aerodrome as a closed way and as a relation?
Hi Marcio, yes, I found similar results. Without a typ file, the 0x07 polygon seems to have the higher draw priority. Gerd From: thundercel@gpsinfo.com.br To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 24 Sep 2015 09:35:30 -0300 Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Gerd, assisting Nelson, using the default style we have ever encountered the first problem is the style does not look landuse = grass forcing us to include in inc / landuse_polygons line landuse = grass [0x17 resolution 20]. Using the default style (with grass included) we only have succeeded using the "comment out" in the following polygons lines of "default style": :# aeroway=airport [0x07 resolution 20] # aeroway=aerodrome [0x07 resolution 20] Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 4:32 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Nelson, there is no special java code in mkgmap to treat aeroways. I guess you don't use the default style, so I can't say what goes wrong. A good tool to find out what mkgmap writes to the img file is GPSMapEdit. Use it to open the corresponding img file and double click into the area you want to analyse. It shows you what Garmin type the area has. Press escape to close the dialog box followed by delete to remove that polygon. Repeat this process until GPSMapEdit shows something like "Area of map coverage (0x4b, polygon)" If you do this for both img files (the good and the bad one) you should be able to find out what's different. Gerd
Date: Wed, 23 Sep 2015 23:45:05 -0300 From: naoliv@gmail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] Problem with aeroway=aerodrome as a relation
Could somehow mkgmap have an issue with aeroway=aerodrome as a relation? (instead a simple closed way)
For example, this airport http://www.openstreetmap.org/way/90834745 have its internal grasses properly represented like here:
http://cocardl.com.br/pv/viracopos.jpg
On the other hand, this
airport
http://www.openstreetmap.org/relation/3896781 seems to overlap every internal feature (like grasses): http://cocardl.com.br/pv/galeao.jpg
Is mkgmap giving different treatments for aeroway=aerodrome as a closed way and as a relation?
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Yes Gerd, Without a typ file it has a higher priority, but we use the defaul the Mkgmap TYP and did not intend to date to develop a custom TYP. Have some form of the Mkgmap level make him take that priority polygon used for airport or aerodrome? Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 9:38 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Marcio, yes, I found similar results. Without a typ file, the 0x07 polygon seems to have the higher draw priority. Gerd -------------------------------------------------------------------------------- From: thundercel@gpsinfo.com.br To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 24 Sep 2015 09:35:30 -0300 Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Gerd, assisting Nelson, using the default style we have ever encountered the first problem is the style does not look landuse = grass forcing us to include in inc / landuse_polygons line landuse = grass [0x17 resolution 20]. Using the default style (with grass included) we only have succeeded using the "comment out" in the following polygons lines of "default style": :# aeroway=airport [0x07 resolution 20] # aeroway=aerodrome [0x07 resolution 20] Marcio
Hi Marcio, not sure what you want to do. A possible change would be to render the areoway=* at level 1 and higher. I think the typ file is the better solution. Gerd From: thundercel@gpsinfo.com.br To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 24 Sep 2015 09:58:03 -0300 Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Yes Gerd, Without a typ file it has a higher priority, but we use the defaul the Mkgmap TYP and did not intend to date to develop a custom TYP. Have some form of the Mkgmap level make him take that priority polygon used for airport or aerodrome? Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 9:38 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Marcio, yes, I found similar results. Without a typ file, the 0x07 polygon seems to have the higher draw priority. Gerd From: thundercel@gpsinfo.com.br To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 24 Sep 2015 09:35:30 -0300 Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Gerd, assisting Nelson, using the default style we have ever encountered the first problem is the style does not look landuse = grass forcing us to include in inc / landuse_polygons line landuse = grass [0x17 resolution 20]. Using the default style (with grass included) we only have succeeded using the "comment out" in the following polygons lines of "default style": :# aeroway=airport [0x07 resolution 20] # aeroway=aerodrome [0x07 resolution 20] Marcio _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, undoubtedly a custom TYP file is a solution, but that solution requires the use of custom TYP and prevents the use of TYP default of Mkgmap. Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 10:54 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Marcio, not sure what you want to do. A possible change would be to render the areoway=* at level 1 and higher. I think the typ file is the better solution. Gerd --------------------------------------------------------------------------------
Hi Marcio, I don't understand what you mean with "TYP default of Mkgmap". I am not aware of such a file, means, if you don't provide a typ file the gmapsupp produced with mkgmap doesn't contain a typ file. Gerd From: thundercel@gpsinfo.com.br To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 24 Sep 2015 11:37:48 -0300 Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Gerd, undoubtedly a custom TYP file is a solution, but that solution requires the use of custom TYP and prevents the use of TYP default of Mkgmap. Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 10:54 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Marcio, not sure what you want to do. A possible change would be to render the areoway=* at level 1 and higher. I think the typ file is the better solution. Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, when I refer to TYP default Mkgmap I mean produce the map without the custom TYP file. In this situation the Mkgmap generates a map with the data on himself. Where. I do not know, but generates. Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 11:57 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Marcio, I don't understand what you mean with "TYP default of Mkgmap". I am not aware of such a file, means, if you don't provide a typ file the gmapsupp produced with mkgmap doesn't contain a typ file. Gerd -------------------------------------------------------------------------------- From: thundercel@gpsinfo.com.br To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 24 Sep 2015 11:37:48 -0300 Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Gerd, undoubtedly a custom TYP file is a solution, but that solution requires the use of custom TYP and prevents the use of TYP default of Mkgmap. Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 10:54 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Marcio, not sure what you want to do. A possible change would be to render the areoway=* at level 1 and higher. I think the typ file is the better solution. Gerd
Hi Marcio, no, mkgmap doesn't generate a default typ file. The Garmin devices contain something like a default typ file, which is used for a map without a typ file. My understanding is that the defaults are different for different devices, at least reg. POI. Gerd From: thundercel@gpsinfo.com.br To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 24 Sep 2015 13:06:22 -0300 Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Gerd, when I refer to TYP default Mkgmap I mean produce the map without the custom TYP file. In this situation the Mkgmap generates a map with the data on himself. Where. I do not know, but generates. Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 11:57 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Marcio, I don't understand what you mean with "TYP default of Mkgmap". I am not aware of such a file, means, if you don't provide a typ file the gmapsupp produced with mkgmap doesn't contain a typ file. Gerd From: thundercel@gpsinfo.com.br To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 24 Sep 2015 11:37:48 -0300 Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Gerd, undoubtedly a custom TYP file is a solution, but that solution requires the use of custom TYP and prevents the use of TYP default of Mkgmap. Marcio From: Gerd Petermann Sent: Thursday, September 24, 2015 10:54 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation Hi Marcio, not sure what you want to do. A possible change would be to render the areoway=* at level 1 and higher. I think the typ file is the better solution. Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Thu, Sep 24, Gerd Petermann wrote:
The Garmin devices contain something like a default typ file, which is used for a map without a typ file. My understanding is that the defaults are different for different devices, at least reg. POI.
Correct. And this also means, that you cannot create a default style without typ file, which looks identical in all cases on all devices. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
On Thu, Sep 24, 2015 at 1:20 PM, Gerd Petermann <gpetermann_muenchen@hotmail.com> wrote:
no, mkgmap doesn't generate a default typ file. The Garmin devices contain something like a default typ file, which is used for a map without a typ file. My understanding is that the defaults are different for different devices, at least reg. POI.
So the solution is indeed to use a TYP file to assure the same result across all the devices?
Nelson, to my knowledge, the TYP file links prints to certain objects established by garmin code for each object. In styles of Mkpamap define which codes should be assigned to each object. The garmin code, as I understand it, is displayed on each device garmin according to the characteristics of the device, but this code is one for each object. Different patterns and priorities can be set in the custom TYP file.
From what I gather. in the absence of a custom TYP, the priority is set internally in the device, following the garmin codes of objects.
In the style Mkgmap is the code garmin 0x07 assigned to aeroway = airport and aeroway = aerodrome. We believe that changing this code in style to another (low priority) can solve the problem without the need to create a custom TYP. Marcio -----Mensagem Original----- From: Nelson A. de Oliveira Sent: Thursday, September 24, 2015 1:27 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] Problem with aeroway=aerodrome as a relation On Thu, Sep 24, 2015 at 1:20 PM, Gerd Petermann <gpetermann_muenchen@hotmail.com> wrote:
no, mkgmap doesn't generate a default typ file. The Garmin devices contain something like a default typ file, which is used for a map without a typ file. My understanding is that the defaults are different for different devices, at least reg. POI.
So the solution is indeed to use a TYP file to assure the same result across all the devices?
participants (4)
-
Gerd Petermann -
Nelson A. de Oliveira -
Thorsten Kukuk -
thundercel＠gpsinfo.com.br