Temporal filter PropertyIsLessThan is not working with date values

[dstenger]

When following request is sent:

• POST https://cite.deegree.org:443/deegree-webservices-3.4.30/services/wfs200

<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs/2.0" count="10" service="WFS"
                version="2.0.0">
   <wfs:Query xmlns:ns79="urn:x-inspire:specification:gmlas:ProtectedSites:3.0"
              typeNames="ns79:ProtectedSite">
      <Filter xmlns="http://www.opengis.net/fes/2.0">
         <PropertyIsLessThan matchAction="All" matchCase="true">
            <Literal>2012-05-13T00:00:00</Literal>
            <ValueReference xmlns:tns="urn:x-inspire:specification:gmlas:ProtectedSites:3.0">tns:legalFoundationDate</ValueReference>
         </PropertyIsLessThan>
      </Filter>
   </wfs:Query>
</wfs:GetFeature>

no features are returned.

However, when sending the same request without filter

<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs/2.0" count="20" service="WFS"
                version="2.0.0">
   <wfs:Query xmlns:ns79="urn:x-inspire:specification:gmlas:ProtectedSites:3.0"
              typeNames="ns79:ProtectedSite">
   </wfs:Query>
</wfs:GetFeature>

features are returned which should match the filter:

• <ps:legalFoundationDate>2012-05-11T00:00:00</ps:legalFoundationDate>

Please also see opengeospatial/ets-wfs20#240.

[dstenger]

I did some research in the specs and my conclusion is that PropertyIsLessThan should not work for temporal values.

This topic is also discussed in opengeospatial/ets-wfs20#240. I propose to wait for the conclusion in that issue and to handle this issue accordingly.

[dstenger]

Feedback from SWG: opengeospatial/ets-wfs20#224 (comment)

It is pointed out that this case is not 100% clear. However, they do not see a reason why PropertyIsLessThan should not be usable with temporal values.
Thus, this reported issue is still valid and should be reviewed by the TMC.

[JohannaOtt]

Additionally (and related IMO), a request using a "property is less than" filter with temporal values also returns features which have a nil value in the requested property.
According to this comment, this should not be the case.

[dstenger]

@JohannaOtt The deegree TMC decided to move your reported problem into a separate issue which you can find here: #1440