The destination tag is copied from the relation if the "to" member 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.
Afterwards the ways are processed by the common --process-destination algorithm.
Sounds great espacially because the number of destination_sign relations is growing quite well.
But: the effect of the patch is quite small. I have compiled a map of germany. Destination_sign relations: 3677 Destination tags copied to _link ways: 121 Destination:ref tags copied to _link ways: 41 Examples:http://www.openstreetmap.org/browse/way/213248346 gets a destination:ref tag.
http://www.openstreetmap.org/browse/way/194845924 gets a destination tag.Most of copied destination tags are the name of exits. (I didn't measure the values but a small sample showed this).
Anyhow try yourself with your data and let me know if it should be commited. WanMil
destination_sign_v1.patch
Description: application/download
_______________________________________________ mkgmap-dev mailing list [email protected] http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
