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?