[Geoserver-devel] [jira] (GEOS-6821) Rule order issue in CSS

GeoServer GeoServer Developer
1

Andrea Aime created an issue

GeoServer / BugGEOS-6821

Rule order issue in CSS

Issue Type:

BugBug

Assignee:

Andrea Aime

Components:

CSS

Created:

08/Jan/15 3:35 AM

Priority:

MajorMajor

Reporter:

Andrea Aime

From a user report:

When used with another simple stroke, the cased line is drawn as a simple line on the second bigger scale rule.

@mode "Exclusive";

tasmania_roads [TYPE='road'] [@scale<=10000000] [@scale>4000000] {
   stroke: #6699FF;
   stroke-width: 8px;
   stroke-linecap: round;
}

tasmania_roads [TYPE='road'] [@scale<=4000000] [@scale>1000] {
   stroke: #aaaaaa, #FF99aa;
   stroke-width: 5px, 3px;
   stroke-linecap: round;
   z-index: 0, 1;
}

Regards,
Torsten

PS: OK, I just found out why. If the rules are reordered (first the one with z-index then the other one) it works. Is this behavior intended? The doc says the order should not matter: “The order of these rules does not matter since the scales denominated in each rule do not overlap.” http://docs.geoserver.org/latest/en/user/extensions/css/cookbook/line.html#id24

Add Comment

Add Comment

This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)

Atlassian logo