Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm having some difficulty when using a Logical OR in a WFS query to get multiple postcodes. This code works fine when it's only 1 PropertyIsEqualTo filter, but when I wrap the OR around more than one PropertyIsEqualTo filter I get an exception.

User-Agent: Fiddler
Content-Type: text/xml
Content-Length: 1875
Expect: 100-continue

<wfs:GetFeature service="WFS" version="1.1.0" xmlns:xsi="" xmlns:wfs="" xmlns:ogc="" xmlns:gml="" xmlns:ncc="" xsi:schemaLocation="">
<wfs:Query typeName="ncc:OSCodepoint_15KM">

This is the Error message I get.

<?xml version="1.0" encoding="UTF-8"?>
<ows:ExceptionReport version="1.0.0" xsi:schemaLocation=""  xmlns:xsi="" xmlns:ows="">
  <ows:Exception exceptionCode="NoApplicableCode">
    <ows:ExceptionText>Error occurred getting features Invalid fid filter provides, has no fids inside Invalid fid filter provides, has no fids inside</ows:ExceptionText>

I'm using GeoServer to process the query.

Any help is much appreciated.

share|improve this question
up vote 4 down vote accepted

Use a capitalized Or instead of all-caps OR to wrap your criteria:

        <!-- Criteria -->

I can't find any definitive answers about case sensitivity in filters, but the XML schema on the OGC site uses "Or" instead of "OR".

share|improve this answer
Thanks very much, my hair is still intact. The mistake was using Mapserver for the examples where they use CAPITALS and then implementing it with GeoServer where they don't. – Tom Styles Jan 6 '12 at 8:25
XML is case sensitive and it should be Or – iant Jan 6 '12 at 13:49

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.