Opened 9 years ago

Last modified 6 years ago

#950 closed enhancement

Null value must be an integer or integer interval — at Initial Version

Reported by: olcl Owned by: Dimitar Misev
Priority: major Milestone: 9.7
Component: qlparser Version: development
Keywords: Cc: Peter Baumann, Bang Pham Huu, Vlad Merticariu
Complexity: Hard

Description

Currently the Null value when ingesting using wcst must be an integer or integer interval (we are on enterprise).

The vast majority of our netcdf files are datatype float so this feature does not work.

The error we receive is :

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ows:ExceptionReport version="2.0.0"
    xsd:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd"
    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">
    <ows:Exception exceptionCode="InvalidPropertyValue">
        <ows:ExceptionText>Nil value 9.96920996839e+36 not supported. Only integer, or integer interval (written as "integer:integer") values are supported.</ows:ExceptionText>
    </ows:Exception>

</ows:ExceptionReport>

Change History (0)

Note: See TracTickets for help on using tickets.