Re: [Geoserver-users] interesting CSS styler issue
On Thu, Sep 9, 2010 at 6:21 AM, Justin Deoliveira wrote: > FYI, I just created a CSS component in jira, so folks can start filing bugs > against it. And they will go straight to david :P Thanks but it went Andrea by default :-) Ian -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] interesting CSS styler issue
FYI, I just created a CSS component in jira, so folks can start filing bugs
against it. And they will go straight to david :P
http://jira.codehaus.org/browse/GEOS/component/14527
On Thu, Sep 9, 2010 at 1:32 AM, David Winslow wrote:
> bug. definitely bug. While selector order in HTML/CSS is significant, it
> doesn't matter at all in GeoServer CSS (because HTML/CSS uses order to
> represent nesting of HTML elements, but there's no sensible analog to nested
> HTML elements in GeoServer's simple feature model).
>
> I am fairly busy with FOSS4G activities this week, but I will try to look
> into this further next week (or maybe the following, depending on jet lag :)
> ). For now, I hope the workaround you have discovered will be sufficient.
>
> --
> David Winslow
> OpenGeo - http://opengeo.org/
>
> ps: By way of explanation, the CSS module does a lot of work enumerating
> all possible combinations of CSS-rules and combining their filters rules to
> generate an equivalent set of mutually exclusive SLD rules. Since there are
> a *lot* of such combinations (for those counting, a number that grows *
> exponentially* with the number of rules in the original CSS stylesheet), I
> try to identify unsatisfiable combinations (such as "[a=1] [a=2]") as early
> as possible, and avoid investigating further combinations based on
> unsatisfiable filter combinations. Bugs like this usually indicate a
> false-positive in the code that evaluates CSS-rule combinations to identify
> whether they should be thrown out due to not matching any features.
>
> On Wed, Sep 8, 2010 at 7:47 AM, Ian Turton wrote:
>
>> I'm not sure if this is a bug, a feature or that I don't fully
>> understand what is going on. If I create a style like:
>>
>> /* @title Residential Road*/
>> [...@scale < 10] [highway='residential'],
>> [...@scale < 10] [highway='unclassified'] {
>> stroke: grey, white;
>> stroke-width: 3px, 1px;
>> stroke-z-index: 0, 6;
>> }
>>
>> The unclassified roads are not drawn but if I do
>>
>> /* @title Residential Road*/
>> [...@scale < 10] [highway='residential'],
>> [highway='unclassified'] [...@scale < 10] {
>> stroke: grey, white;
>> stroke-width: 3px, 1px;
>> stroke-z-index: 0, 6;
>> }
>>
>> then they are drawn.
>>
>> Any ideas?
>>
>> Ian
>>
>>
>> --
>> Ian Turton
>>
>>
>> --
>> This SF.net Dev2Dev email is sponsored by:
>>
>> Show off your parallel programming skills.
>> Enter the Intel(R) Threading Challenge 2010.
>> http://p.sf.net/sfu/intel-thread-sfd
>> ___
>> Geoserver-users mailing list
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>
>
>
> --
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] interesting CSS styler issue
bug. definitely bug. While selector order in HTML/CSS is significant, it
doesn't matter at all in GeoServer CSS (because HTML/CSS uses order to
represent nesting of HTML elements, but there's no sensible analog to nested
HTML elements in GeoServer's simple feature model).
I am fairly busy with FOSS4G activities this week, but I will try to look
into this further next week (or maybe the following, depending on jet lag :)
). For now, I hope the workaround you have discovered will be sufficient.
--
David Winslow
OpenGeo - http://opengeo.org/
ps: By way of explanation, the CSS module does a lot of work enumerating all
possible combinations of CSS-rules and combining their filters rules to
generate an equivalent set of mutually exclusive SLD rules. Since there are
a *lot* of such combinations (for those counting, a number that grows *
exponentially* with the number of rules in the original CSS stylesheet), I
try to identify unsatisfiable combinations (such as "[a=1] [a=2]") as early
as possible, and avoid investigating further combinations based on
unsatisfiable filter combinations. Bugs like this usually indicate a
false-positive in the code that evaluates CSS-rule combinations to identify
whether they should be thrown out due to not matching any features.
On Wed, Sep 8, 2010 at 7:47 AM, Ian Turton wrote:
> I'm not sure if this is a bug, a feature or that I don't fully
> understand what is going on. If I create a style like:
>
> /* @title Residential Road*/
> [...@scale < 10] [highway='residential'],
> [...@scale < 10] [highway='unclassified'] {
> stroke: grey, white;
> stroke-width: 3px, 1px;
> stroke-z-index: 0, 6;
> }
>
> The unclassified roads are not drawn but if I do
>
> /* @title Residential Road*/
> [...@scale < 10] [highway='residential'],
> [highway='unclassified'] [...@scale < 10] {
> stroke: grey, white;
> stroke-width: 3px, 1px;
> stroke-z-index: 0, 6;
> }
>
> then they are drawn.
>
> Any ideas?
>
> Ian
>
>
> --
> Ian Turton
>
>
> --
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] interesting CSS styler issue
I'm not sure if this is a bug, a feature or that I don't fully
understand what is going on. If I create a style like:
/* @title Residential Road*/
[...@scale < 10] [highway='residential'],
[...@scale < 10] [highway='unclassified'] {
stroke: grey, white;
stroke-width: 3px, 1px;
stroke-z-index: 0, 6;
}
The unclassified roads are not drawn but if I do
/* @title Residential Road*/
[...@scale < 10] [highway='residential'],
[highway='unclassified'] [...@scale < 10] {
stroke: grey, white;
stroke-width: 3px, 1px;
stroke-z-index: 0, 6;
}
then they are drawn.
Any ideas?
Ian
--
Ian Turton
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
