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
I ran into this issue when checking SLD output from LAYER CLASS EXPRESSIONS.
I'd not thoroughly read the logical expression docs and so had been unaware that NOT expressions in MapServer can be represented by != or ne, but not <>.
The following layer parses fine in MapServer, but the <> gets parsed as MS_TOKEN_COMPARISON_LT and MS_TOKEN_COMPARISON_GT in
I ran into this issue when checking SLD output from LAYER CLASS EXPRESSIONS.
I'd not thoroughly read the logical expression docs and so had been unaware that
NOT
expressions in MapServer can be represented by!=
orne
, but not<>
.The following layer parses fine in MapServer, but the
<>
gets parsed asMS_TOKEN_COMPARISON_LT
andMS_TOKEN_COMPARISON_GT
inMapServer/src/maplayer.c
Line 679 in 24d36f8
This probably causes strange issues when rendering data, but is more noticeable when generating SLD as it returns:
Ideally I think the MapServer expression parser should throw an error when reading the Mapfile (or we attempt to support
<>
in expressions).The text was updated successfully, but these errors were encountered: