you can have that a lot easier: tourism=alpine_hut { name '${name} ${ele}' | '${name}' | '${ele}' | 'Berghütte' } [0x4803 resolution 23] if ele is not there the 1st naming will be skipped and so on. but: separating something like tourism=alpine_hut and amenity=restaurant into 2 pois would be great - why not with an option file that contains all the key=value pairs that should not occur together in one node. using continue in such a case makes the style really messy (and pretty unpredictable too) in my opinion. Am 06.02.2012 13:06, schrieb toc-rox:
Splitting is a bit misleading - it's more a doubling.
And here is an example where continue doesn't do the job or leads to a complex logic:
tourism = alpine_hut& name = *& ele = * {name '${name} (${ele}) (Berghütte)'} [0x4803 resolution 23] tourism = alpine_hut& name = * {name '${name} (Berghütte)'} [0x4803 resolution 23] tourism = alpine_hut& ele = * {name 'Berghütte (${ele})'} [0x4803 resolution 23] tourism = alpine_hut {name 'Berghütte'} [0x4803 resolution 23]
The criterion for a doubling could be: the node contains more than one POI
BTW: I think we have to deal in the future with more and more complex tags.
Klaus
-- View this message in context: http://gis.19327.n5.nabble.com/Idea-for-a-split-pois-option-tp5459785p545994... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev