WCS_GetCoverage in GML fix sequenceRule element

[Bang Pham Huu]

The sequenceRule element currently follows the CRS axes order, e.g: if 3D coverage with crs: EPSG:4326 (lat (+1), long (+2) order)&time (+3) imported from 4 geotiff files (latitude: 18 pixels, longitude: 36 pixels) with regular time recipe, in rasql it has this sdom: [0:35,0:17,0:3] with grid axes order: long, lat, time).

The result of this GetCoverage request

http://localhost:8080/rasdaman/ows?&SERVICE=WCS&VERSION=2.0.1&REQUEST=GetCoverage&COVERAGEID=test_AverageTemperature&FORMAT=application/gml+xml

returns

GridFunction>
<sequenceRule axisOrder="+2 +1 +3">Linear</sequenceRule>
<startPoint>0 0 0</startPoint>
</GridFunction>

which is incorrect as it just follows the CRS orders. However, it should follow the way the JSON encode in rasql does (loop from outer time axis [0:3], to lat axis [0:17] then inner long axis [0:35]). Hence, the correct sequenceRule is "+3 +1 +2".

[Bang Pham Huu]

Also updated petascope on ​http://conformance.rasdaman.com/ows and ​http://ows.rasdaman.org/rasdaman/ows.