Opened 2 years ago

Last modified 13 months ago

#950 new enhancement

Null value must be an integer or integer interval

Reported by: olcl Owned by: dmisev
Priority: major Milestone: 10.0
Component: qlparser Version: development
Keywords: Cc: pbaumann, mdumitru, vmerticariu
Complexity: Hard

Description (last modified by dmisev)

Currently the Null value when ingesting using wcst must be an integer or integer interval.

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 (2)

comment:1 Changed 2 years ago by dmisev

  • Cc pbaumann mdumitru vmerticariu added
  • Complexity changed from Medium to Hard
  • Component changed from undecided to qlparser
  • Description modified (diff)
  • Milestone set to 10.0
  • Type changed from defect to enhancement

comment:2 Changed 13 months ago by bphamhuu

with the current netcdf recipe, it supports an option to set Null value, by setting (i.e: "nilValue": "-99999" as ingredient http://rasdaman.org/wiki/WCSTImportGuide/GeneralRecipe, this is a solution with WCST_Import (if someone find this ticket for the same problem).

Note: See TracTickets for help on using tickets.