wcst_import - wrong constraint for default_null_values

[Bang Pham Huu]

wcst_import has a wrong constraint for default_null_values, number of null values must match with number of coverage's bands:

Default null values must be a list containing 1 null value
for all bands or N individual null values for N bands.

e.g: if coverage has 1 band (TIFF file with tag NoData Value=-3.4028234663852886e+38), then, default_null_values can only have 1 value, not with multiple values (according to ​http://doc.rasdaman.org/04_ql-guide.html?highlight=null%20values#set-types for setting null values for a set type), such as:

"default_null_values": [0, -3.4028234663852886e+38]

Also, petascope has problem with parsing multiple null values from GML, e.g:

 <swe:nilValues>
           <swe:NilValues>
                    <swe:nilValue reason="">
                        0
                    </swe:nilValue>
                    <swe:nilValue reason="">
                        -3.4028234663852886e+38
                    </swe:nilValue>
           </swe:NilValues>
</swe:nilValues>

[Dimitar Misev]

Can you write what should be done to fix this ticket? The explanation is fuzzy so I'm not entirely clear about the expected outcome.

[Bang Pham Huu]

Replying to dmisev:

Can you write what should be done to fix this ticket? The explanation is fuzzy so I'm not entirely clear about the expected outcome.

The fixes come from the listed problems. It means removing the constraint in WCST_Import and fixing the parsing problem for multiple null values in Petascope from GML.