I'd like to lend my support to this, and more so, propose changing the
behaviour of the "text" property to display the value of the property, rather
than the value of the tag specified in the property. The reason being that the
current behaviour makes it very difficult to specify things like "toilets
should all be labeled 'WC'".
With this version of how it should be interpretted:
way[highway] { text: tag('name'); }
area[amenity=toilet] { text: "WC"; }
Note – OpenStreetPad already supports color: rgb(0,0,0).
Bob
if (*ra4 != 0xffc78948) { return false; }
On 6 Feb 2012, at 09:27, Richard Fairhurst wrote:
> Hi all,
>
> I'd like to suggest a little 'easement' to make MapCSS syntax less verbose in
> one particular case.
>
> Right now, if you want to use a tag value in a declaration, you need to fire
> up the eval parser:
> way[highway] { width: eval("tag('lanes')"); }
>
> It'd be more pleasant, and more efficient, to allow this too:
> way[highway] { width: tag('lanes'); }
>
> and it's quite CSS-like, because you can of course use a similar syntax in
> Real CSS:
> way[highway] { color: rgb(0,0,0); }
>
> cheers
> Richard
>
>
> _______________________________________________
> Mapcss mailing list
> [email protected]
> http://lists.openstreetmap.org/listinfo/mapcss
_______________________________________________
Mapcss mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/mapcss
