Opened 4 years ago

Closed 3 years ago

#610 closed defect (fixed)

Missing mapping between WCPS and RasQL primitive data types

Reported by: pcampalani Owned by: uadhikari
Priority: major Milestone: 9.0.x
Component: petascope Version: development
Keywords: cast wcps rasql Cc: dmisev, pbaumann
Complexity: Medium

Description (last modified by pcampalani)

Explicit casts in a WCPS query should not be left as-is in the RasQL translation, but instead they should be replaced with the correspondent data type (e.g. WCPS char to RasQL octet).

For details on the different data types specifications, see Table 2 in WCPS standard (OGC08-068r2) against Table 1 in the RasQL guide.

Change History (5)

comment:1 Changed 4 years ago by pcampalani

  • Description modified (diff)

comment:2 Changed 3 years ago by dmisev

  • Owner changed from pcampalani to uadhikari
  • Status changed from new to assigned

Utkrist has done the fix for the boolean type translation, so naturally can take a look at this one as well.

comment:3 Changed 3 years ago by pcampalani

Utkrist: any status update? thx.

comment:4 Changed 3 years ago by uadhikari

I have already found the solution. There are some issues with the test cases which needs to be discussed further. A small addition is needed in current implementation of wcps grammar to support 'unsigned int' and 'int'. As Prof. Baumann pointed out, it must be in par with WCPS 1.5, we can check in that direction too. Perhaps, we can finalise this today.

comment:5 Changed 3 years ago by dmisev

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.