[mkgmap-dev] [PATCH v1] Support relation destination_sign
From Henning Scholland osm at aighes.de on Fri Apr 19 08:51:48 BST 2013
Am 18.04.2013 22:30, schrieb WanMil: >> Am 18.04.2013 20:15, schrieb WanMil: >>> Hi Henning, >>> >>> that's already possible: >>> >>> type=route & route=bicyle { apply role=forward { set foo=bar } } >>> >>> >> Oh...I missed it. But then it shouldn't be necessary to use special >> code, because you can manage it via style, or am I wrong? >> >> Henning >> > Maybe. > > Can you implement these rules? It should be in relation-file: type=destination_sign { apply role=to { set foobar:destination=='$(foobar:destination),${destination}' | '${destination}' } } Now every to-way is tagged with destination-Tags of all relations seperated by , In lines-file you would need something like: highway!=*_link { delete foobar:destination } Maybe you would like to merge foobar:destination with an existing desination, but I don't know if this is a good idea. Henning > The destination tag is copied from the relation if the "to" member is a > link and does not already have a destination tag. > The same happens with the ref/destination_ref/destination:ref tags. They > are set as destination:ref tag in case the "to" way does not already > have a ref tag. > > WanMil > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >
- Previous message: [mkgmap-dev] [PATCH v1] Support relation destination_sign
- Next message: [mkgmap-dev] [PATCH v1] Support relation destination_sign
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list