On Wed, Aug 4, 2010 at 12:28 PM, Arnd Wippermann arnd.wipperm...@web.de wrote:
Hi
Why is it not possible to use '.' (point for singleChar) in a
OpenLayers.Filter.Comparison.LIKE?
What do you mean exactly?
The Comparision filter 'like' seems not to work as expected.
It's not possible to
expect '2' or 'adadas2', but not '2klkölk'
Many thanks
Arnd
-Ursprüngliche Nachricht-
Von: Eric Lemoine [mailto:eric.lemo...@camptocamp.com]
Gesendet: Donnerstag, 5. August 2010 09:20
An: Arnd Wippermann
Cc: users@openlayers.org
Betreff: Re: [OpenLayers-Users
On Thu, Aug 5, 2010 at 2:28 PM, Arnd Wippermann arnd.wipperm...@web.de wrote:
Hi Eric,
thanks for the reply and the hint. It's a more complex situation.
It's not a problem with the filter, but with OpenLayers.Format.SLD().read:
I create a SLD and apply it to a vector layer
var formatSLD =
Hi,
Eric's patch won't solve the problem, because the input to the filter will then
be 0.2 instead of .2.
Arnd, can you please create a ticket? This behavior was introduced by
http://trac.openlayers.org/changeset/8927, and I think it would be better to
cast in filter.evaluate rather than in
On Thu, Aug 5, 2010 at 11:38 AM, Andreas Hocevar ahoce...@opengeo.org wrote:
Hi,
Eric's patch won't solve the problem, because the input to the filter will
then be 0.2 instead of .2.
Arnd, can you please create a ticket? This behavior was introduced by
Hi,
The patch resolves the problem in parts.
ogc:Filter xmlns:ogc=http://www.opengis.net/ogc;
ogc:PropertyIsLike wildCard=* singleChar=. escape=!
ogc:PropertyNameindice/ogc:PropertyName
ogc:Literal.2/ogc:Literal
/ogc:PropertyIsLike
/ogc:Filter
The SLD will be created and the WFS GetFeature
Another solution is to use a character other than . for the single
character wildcard so that it no longer looks like a number to the
parser. Try
ogc:Filter xmlns:ogc=http://www.opengis.net/ogc;
ogc:PropertyIsLike wildCard=* singleChar=# escape=!
ogc:PropertyNameindice/ogc:PropertyName
@openlayers.org
Betreff: Re: [OpenLayers-Users] OpenLayers.Filter.Comparison.LIKE and
singleChar
Hi,
Eric's patch won't solve the problem, because the input to the filter will
then be 0.2 instead of .2.
Arnd, can you please create a ticket? This behavior was introduced by
http://trac.openlayers.org
. August 2010 18:53
An: Arnd Wippermann
Cc: users@openlayers.org
Betreff: Re: [OpenLayers-Users] OpenLayers.Filter.Comparison.LIKE and
singleChar
Another solution is to use a character other than . for the single character
wildcard so that it no longer looks like a number to the parser. Try
ogc:Filter
On Thu, Aug 5, 2010 at 1:08 PM, Arnd Wippermann arnd.wipperm...@web.de wrote:
Thanks Ian,
I have tried this, to test, if the SLD reader principal works. But I
wouldn't like this approach, because you have to remember, that you changed
the value for singleChar.
I suspect that this filter will
this approach, because you have to remember, that you changed
the value for singleChar.
Arnd
-Ursprüngliche Nachricht-
Von: Ian Turton [mailto:ijtur...@gmail.com]
Gesendet: Donnerstag, 5. August 2010 18:53
An: Arnd Wippermann
Cc: users@openlayers.org
Betreff: Re: [OpenLayers-Users
: [OpenLayers-Users] OpenLayers.Filter.Comparison.LIKE and
singleChar
Another solution is to use a character other than . for the single
character wildcard so that it no longer looks like a number to the
parser. Try
ogc:Filter xmlns:ogc=http://www.opengis.net/ogc;
ogc:PropertyIsLike
Hi
Why is it not possible to use '.' (point for singleChar) in a
OpenLayers.Filter.Comparison.LIKE?
The Comparision filter 'like' seems not to work as expected.
It's not possible to use an expression only with a point for a single char
(.2) or a static string (22).
It causes an error
13 matches
Mail list logo
