[Geoserver-users] matchCase

GeoServer GeoServer User
1

Hi there,

I’m trying to use the attribute “matchCase” with filter PropertyIsEqualTo in a WFS GetFeature request.

In the body of the WFS request :

<ogc:PropertyIsEqualTo matchCase=“false”>

I get this exception :

java.lang.RuntimeException: Parsing failed for PropertyIsEqualTo: java.lang.classCastException: java.lang.String cannot be cast to java.lang.Boolean

I tried without quotes, with single quotes, on 2.14, 2.17 to no avail

The request works without the attribute matchCase but, I’d like to perform case insensitive requests.

Thanks

···

Envoyé à partir d’Outlook

2

I have generated the xml from Openlayers for a WFS getfeature request with the matchCase option set to true. It looks like this:

ROUTE_ID

50927952

Hopefully this helps, admittedly it does not have any alpha characters, but it works

Cheers,

Graham

···

From: Olivier Gagnon mcnolii@anonymised.com
Sent: Thursday, 20 January 2022 2:56 AM
To: GeoServer Users geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] matchCase

Hi there,

I’m trying to use the attribute “matchCase” with filter PropertyIsEqualTo in a WFS GetFeature request.

In the body of the WFS request :

<ogc:PropertyIsEqualTo matchCase=“false”>

I get this exception :

java.lang.RuntimeException: Parsing failed for PropertyIsEqualTo: java.lang.classCastException: java.lang.String cannot be cast to java.lang.Boolean

I tried without quotes, with single quotes, on 2.14, 2.17 to no avail

The request works without the attribute matchCase but, I’d like to perform case insensitive requests.

Thanks

Envoyé à partir d’Outlook

3

Currently supported GeoServer versions are 2.19.x and 2.20.x. I don’t remember if there was any change
related to PropertyIsEqualTo parsing in earlier versions, you might want to try a more recent one.

From the error, maybe you are trying to use matchCase on a version of WFS that does not
support it? WFS 1.0 uses Filter 1.0, which does not have a matchCase attribute. It was introduced in WFS 1.1

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail

4

Andrea,

you are right : changing WFS version to 1.1.0 did the trick.

Thank you very much for your help.

···

Envoyé à partir d’Outlook

De : Andrea Aime andrea.aime@anonymised.com
Envoyé : 20 janvier 2022 03:46
À : Olivier Gagnon mcnolii@anonymised.com
Cc : GeoServer Users geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] matchCase

Currently supported GeoServer versions are 2.19.x and 2.20.x. I don’t remember if there was any change
related to PropertyIsEqualTo parsing in earlier versions, you might want to try a more recent one.

From the error, maybe you are trying to use matchCase on a version of WFS that does not
support it? WFS 1.0 uses Filter 1.0, which does not have a matchCase attribute. It was introduced in WFS 1.1

Cheers
Andrea

On Wed, Jan 19, 2022 at 4:58 PM Olivier Gagnon <mcnolii@anonymised.com> wrote:

Hi there,

I’m trying to use the attribute “matchCase” with filter PropertyIsEqualTo in a WFS GetFeature request.

In the body of the WFS request :

<ogc:PropertyIsEqualTo matchCase=“false”>

I get this exception :

java.lang.RuntimeException: Parsing failed for PropertyIsEqualTo: java.lang.classCastException: java.lang.String cannot be cast to java.lang.Boolean

I tried without quotes, with single quotes, on 2.14, 2.17 to no avail

The request works without the attribute matchCase but, I’d like to perform case insensitive requests.

Thanks

Envoyé à partir d’Outlook

Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail