[mkgmap-dev] tag values of relations and tag values of its members

Fri Sep 10 21:12:22 BST 2010

On Fri, Sep 10, 2010 at 07:01:55PM +0200, Torsten Leistikow wrote:
>I think this wouldn't solve my problem. What I want to achieve is, that 
>multiple relations can add information to a single way.

I implemented the $(variable_name) syntax some time ago, to get bus 
route relations translated properly. An excerpt from --style=routes:

[relations file]
type=route & ... {
   apply { set mkgmap:route='$(mkgmap:route),${ref}' | '${ref}' }
}
[lines file]
highway=* & mkgmap:route=* { name '${mkgmap:route}' } [0x1d resolution 16]

Note that in the apply rule, the $(mkgmap:route) is referring to an 
attribute of the relation member, and the ${ref} is referring to an 
attribute of the relation.

What I would like to see is "apply" sorted by some criterion, and the 
possibility to filter out duplicates, for example, when the same way is 
part of opposite-direction bus route relations. (Opposing bus routes of 
the same line can consist of oneway segments as well as shared 
non-oneway segments. Now I will see "742,742" on the non-oneways and 
just "742" on the oneways.)

I'd also like to have mkgmap generate multiple map layers in one go, so 
that for type=route relations, different values of route=* would go to 
different layers. You normally might want to see only one of route=road, 
route=bicycle, route=bus at a time (by selecting visible map layers on 
the device).

Do we have a bug tracking system or a wiki page for tracking this kind 
of long-term, hard-to-implement feature requests?

	Marko