Yes, this is a know limitation. With the current architecture I think it would be rather challenging to add that, since we would need to add some external state to the matching routines to track modification of tags. (Basically we would need a hash-map that stores for each object which tags where overwritten)
Things that would be needed to do for this to work:
Extent the grammar to handle the new syntax
Add an unordered_map for ways, nodes, relations to src/server/stylesheet.cpp
Modify Selector interface (src/server/selectors/*) to take the unordered_map as parameter
Add code to src/server/selectors/apply_selector.cpp to add overrides to unordered_map
Fix each Selector to check for an override before using the actual values from "tags" unordered_map
Important keyword 'set' is not supported in declarations and classes.
http://wiki.openstreetmap.org/wiki/MapCSS/0.2#Declarations
e.g.
{ set tag=value; }
or
{ set .minor_road; }
produce an error:
[WARN] [mapcss-parser] Unsupported attribute 'set' was ignored!
0[ERROR] [parser] Parsing of file "mapcss\mymap.mapcss" failed:
[ERROR] [parser] Illegal syntax! Expected valid ":"!
[ERROR] [parser] In line 102 column 9:
[ERROR] [parser] ' set .minor_road;'
[ERROR] [parser] ^-here
The text was updated successfully, but these errors were encountered: