Missing mapping between WCPS and RasQL primitive data types

[Piero Campalani]

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.

[Dimitar Misev]

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

[Piero Campalani]

Utkrist: any status update? thx.

[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.

[Dimitar Misev]

changeset:0778878c62747608d2b8ee8fdfaaa215cdc32cbc