WCPS1.5_Throw correct exception when interval is not valid

[Bang Pham Huu]

WCPS query

for c in (eobstest) return encode( (c[ t("1950-01-02":"1950-01-01"), Long(35.5:35.5), Lat(10:15)]), "tiff", "nodata=0")

In WCPS 1.0 it returns an meaningful exception

<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" version="2.0.0" xsd:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd">
<ows:Exception exceptionCode="InvalidSubsetting">
<ows:ExceptionText>
t axis: lower bound 1950-01-02 is greater then the upper bound 1950-01-01
</ows:ExceptionText>
</ows:Exception>
<ows:Exception exceptionCode="InvalidSubsetting">
<ows:ExceptionText>
t axis: lower bound 1950-01-02 is greater then the upper bound 1950-01-01
</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>

In WCPS 1.5, it is not really meaningful

<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" version="2.0.0" xsd:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd">
<ows:Exception exceptionCode="RuntimeError">
<ows:ExceptionText>Runtime error while processing request</ows:ExceptionText>
</ows:Exception>
<ows:Exception exceptionCode="RuntimeError">
<ows:ExceptionText>
petascope.wcps2.error.managed.processing.UnorderedSubsetException :
 Invalid subsetting coordinates: 1950-01-02:1950-01-01 for axis t.
</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>

[Bang Pham Huu]

Patch was accepted, close ticket.