logo separator

[mkgmap-dev] How to make a scale-dependent TYP style?

From Ticker Berkin rwb-mkgmap at jagit.co.uk on Sun Apr 5 10:13:40 BST 2020


Without an override from a TYP file, Garmin devices have their own,
inbuilt, rules about how to render each object (point/line/polygon) and
these vary from device to device, so no, there isn't and cannot be a
tool to do what you asked.

If you are making a map just for your particular device, the best thing
to do is generate a map without a TYP and see how it looks, then tweak
just the minimum with specific TYP [_xxx] entries.

For my eTrex HCx, not having a TYP works really well for points and

My eTrex 30x doesn't show some non-road lines, or shows them in white
which was almost impossible to see, so I have these in my TYP.

There are problems in the way they renders overlapping polygon and the
order in which they overwrite each other as the device is finding them,
but this is another topic.

For both, apart from the above, I much prefer their default rendering
rather than, say, {distribution}/examples/typ-files/mapnik.txt which
also slows down the devices to an almost unusable speed. 


On Sat, 2020-04-04 at 21:24 +0200, Niccolo Rigacci wrote:
> On Sat, Apr 04, 2020 at 07:05:09PM +0100, Ticker Berkin wrote:
> > 
> > mkgmap doesn't have a default TYP, but there are a couple of
> > examples
> > in {distribution}/examples/typ-files 
> > 
> > I find it best not to have any highway _lines in my personal TYP
> > file
> > for the reasons you are seeing - it looks much better on my device
> > to
> > let it represent them using its default mechanism.
> So, if I understand well what are you saying, the default 
> mechanism used by mkgmap is not based on TYP rules, but on 
> algorithmic procedures.
> Is it possible to browse the native rendering types known by 
> mkgmap? Something like TYPViewer. So that I can use them instead 
> of creating new ones via TYP files.

More information about the mkgmap-dev mailing list