Peter Wendorff wrote:
Hi Sebastian.
I'm not sure if there is something in current MapCSS ideas against the
functionality "inherited" from classical CSS.
In CSS I would suggest a cascading scheme for the labelling fallbacks
(the @ indicates an attribute - ignore it, if that's not MapCSS syntax),
but I hope, you get what I mean:
building[@addr:housenumber] {
text: @addr:housenumber;
}
building[@addr:housename] {
text: @addr:housename;
}
building[@name] {
text: @name;
}
building[@name:de] {
text: @name:de;
}
The value of text is calculated cascadingly: apply all definitions
consecutively, overwriting properties, if applied again.
If there is a Tag name:de at a building, it would be applied in my
example, as it's the last statement applied.
Yes, I guess this would work well. The remaining question is how to put static strings. E.g. the manual way to derive a tag value would be
xx: eval(tag("addr:housenumber"));
but what is xx?
Sebastian
_______________________________________________
Mapcss mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/mapcss
