Hi WanMil,

what is the benefit of the new handling?

There are many benefits: 1. Thight integration of process-exits and process-destination. You can decide via style file what happens if a link is part of an exit and contains a destination tag. 2. Each destination tag is taken into account. Think of a big motorway junction. It is possible that you have to follow several independent destinations within the same junction. Now you will see each destination on the Garmin at the right place. 3. process-destination often does not work on big motorway junctions. An easy example is the common cloverleaf design of junctions. The destinations of the inner links was not handled by process-destination because the resulting motorway is not unique. With the new handling you will get the destination hint within the cloverleaf. 4. You will get destination hints on the motorway entries. This should also be handled by the process-destination but on my Garmins but I think it is done better now.

Is it possible to distinguish between motorway-exits and motorway junctions?

No.

Up to now I only used process-dest and not process-exits because process-exits overruled the destination logic at motorway junctions.

That's a problem that should be fixed with this patch.

Chris

_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Okay, thanks, I will test it.

Hi, I'm not discovering a big difference to the old logic but agree that it is the cleaner and more consistent solution. So for me it's ok to commit. Chris