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 have a question about whether the wildCard, singleChar, and escapeChar attributes of PropertyIsLike should be restricted to single character strings.
wildCard specifies the pattern character which matches any sequence of zero or more string characters
singleChar specifies the pattern character which matches any single string character
escapeChar specifies the escape character which can be used to escape the pattern characters
I realize that the user can choose to use a single character. But I wonder if there is value in restricting these attributes to a single character, to prevent incompatibility between the SLD document and systems that use SLD (to prevent the creation of a SCISYS-only SLD document)
The text was updated successfully, but these errors were encountered:
It's a bit of tricky one in that the GUI only reflects what GeoTools tells it, and unfortunately it defines the single character as a string. I'll have look to see if I can intercept it and restrict to a single character.
I have a question about whether the wildCard, singleChar, and escapeChar attributes of PropertyIsLike should be restricted to single character strings.
The schema (http://schemas.opengis.net/filter/1.1.0/filter.xsd) doesn't make any such restriction, and the Implementation Spec doesn't mention PropertyIsLike.
However, the following sources seem to assume a single character restriction:
http://docs.geotools.org/latest/javadocs/org/opengis/filter/PropertyIsLike.html
http://docs.geoserver.org/latest/en/user/filter/filter_reference.html
I realize that the user can choose to use a single character. But I wonder if there is value in restricting these attributes to a single character, to prevent incompatibility between the SLD document and systems that use SLD (to prevent the creation of a SCISYS-only SLD document)
The text was updated successfully, but these errors were encountered: