You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our mapcss only supports "single element"-rules. Rules with e.g. parent/child/link selectors (e.g. way[x] > node[y]), containment selectors (e.g. node[x] ∈ area[y]), connection pseudo-classes (e.g. :unconnected) or parent/child-expressions (e.g. parent_tag(...)) are all ignored at the moment.
It would be great to also support them in Osmose. Most likely this'll have to be via SQL queries.
The biggest challenges I'd expect:
efficiency
connection with class selectors (which may also be shared with single-element rules, e.g.
Currently our mapcss only supports "single element"-rules. Rules with e.g. parent/child/link selectors (e.g.
way[x] > node[y]
), containment selectors (e.g.node[x] ∈ area[y]
), connection pseudo-classes (e.g.:unconnected
) or parent/child-expressions (e.g.parent_tag(...)
) are all ignored at the moment.It would be great to also support them in Osmose. Most likely this'll have to be via SQL queries.
The biggest challenges I'd expect:
Just filing this issue to also have it on the issue tracker.
The text was updated successfully, but these errors were encountered: