Opened 21 months ago

Last modified 3 months ago

#1095 assigned defect

WCS-T doesn't support CInt16

Reported by: dmisev Owned by: dmisev
Priority: major Milestone: Future
Component: petascope Version: development
Keywords: Cc: vmerticariu, pbaumann
Complexity: Medium

Description (last modified by dmisev)

While importing Sentinel 1 SLC data with wcst_import.sh:

Service Call: http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=InsertCoverage&coverageRef=file:///tmp/ce86a214_1004_4b81_875a_6c7813ae6727.gml&tiling=ALIGNED [0:1023, 0:1023]&pixelDataType=CInt16&useId=existing
Error Code: InvalidParameterValue
Error Text: <?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="InvalidParameterValue">
        <ows:ExceptionText>Pixel data type CInt16 unknown.</ows:ExceptionText>
    </ows:Exception>

</ows:ExceptionReport>

Attached is a sample tiff file.

Rasdaman supports only 64 and 128 bit complex numbers (floating point only). We should extend this, best to match the GDAL complex number types (we are missing CInt16 and CInt32): http://www.gdal.org/gdal_8h.html#a22e22ce0a55036a96f652765793fb7a4

Attachments (1)

sample.tif (459.1 KB) - added by dmisev 21 months ago.

Download all attachments as: .zip

Change History (11)

Changed 21 months ago by dmisev

comment:1 Changed 21 months ago by vmerticariu

We could map that to r_Complex, but the problem is that r_Complex is 64 bit (which is the smallest complex type rasdaman supports).

Gdal supports from 16 to 64 bit complex types: http://www.gdal.org/gdal_8h.html#a22e22ce0a55036a96f652765793fb7a4

comment:2 Changed 21 months ago by dmisev

  • Cc pbaumann added

I guess it's time to add more complex types in rasdaman?

comment:3 Changed 21 months ago by pbaumann

a valid request indeed - Sentinel is important. Hope we can find resources - maybe someone from the community would like embark on this...

comment:4 Changed 21 months ago by dmisev

  • Owner changed from mdumitru to vzamfir
  • Status changed from new to assigned

comment:5 Changed 21 months ago by dmisev

  • Description modified (diff)

comment:6 Changed 21 months ago by dmisev

  • Description modified (diff)

comment:7 Changed 21 months ago by dmisev

Question: how should these complex types of 16 and 32 bit (signed int) be called?

Currently we have complex = float, and complexd = double.
Any suggestion for the new type names? complexShort/complexLong? complexInt16/complexInt32?

comment:8 Changed 21 months ago by dmisev

Btw, can't we map this to a struct { re, im }?

comment:9 Changed 7 months ago by dmisev

  • Milestone changed from 9.2 to 9.4
  • Owner changed from vzamfir to dmisev

comment:10 Changed 3 months ago by dmisev

  • Milestone changed from 9.4 to Future

@Vlad did you come across the same Sentinel 1 data? How did import work out?

Note: See TracTickets for help on using tickets.