Changes between Version 2 and Version 3 of Ticket #2081
- Timestamp:
- Apr 25, 2019, 6:41:14 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2081
- Property Component undecided → petascope
- Property Type enhancement → defect
- Property Summary wcst_import should accept nan as default null value → petascope should accept nan as null value
-
Ticket #2081 – Description
v2 v3 1 Currently, wcst_import does not accept:1 Petascope should allow '''NaN''' as null value from WCST_Import, e.g: 2 2 3 "default_null_values": [NaN]4 3 5 or 4 {{{ 5 "default_null_values": [NaN] 6 or 7 "default_null_values": ["nan"] 8 }}} 6 9 7 "default_null_values": [ "nan" ]8 10 9 Since rasdaman supports that, wcst_import and petascope should allow them, and pass them further to rasql. 11 12 Error: 13 14 15 {{{ 16 <ows:ExceptionReport version="2.0.1" 17 xsi:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd" 18 xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink"> 19 <ows:Exception exceptionCode="InvalidPropertyValue"> 20 <ows:ExceptionText>Nil value must be a number, given 'nan'.</ows:ExceptionText> 21 </ows:Exception> 22 </ows:ExceptionReport> 23 }}} 24