#9556 closed enhancement (fixed)
Add "natural and landuse of the same type should not cross each other "
| Reported by: | mkoniecz | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | 14.01 |
| Component: | Core validator | Version: | |
| Keywords: | Cc: | simon04 |
Description
as explained in #9507 natural and landuse may cross each other but on the other hand landuse=forest should not cross other landuse=forest (also landuse=residential with landuse=residential) etc.
Attachments (0)
Change History (6)
comment:1 by , 12 years ago
| Summary: | Add "natural and landuse of the same type shuld not cross each other " → Add "natural and landuse of the same type should not cross each other " |
|---|
comment:2 by , 12 years ago
| Cc: | added |
|---|
comment:4 by , 12 years ago
The current spatial selectors are evaluated from right to left. The right one is considered to be the parent object (this naming originates from normal child/parent selectors). Thus, using parent_tag on the left part gives access to corresponding tag of the right object. {0.key} is not known to the MapCSS part, but is only inserted after a successful match by the tag checking part.
comment:5 by , 12 years ago
Ok thanks :) this syntax is awesome, need just some time to master it :)
comment:6 by , 12 years ago
| Milestone: | → 14.01 |
|---|



I tried this but it doesn't work, is there a way to implement this with current syntax or do we need another evolution ?