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?