WCPS1.5_Use http://..../def/crs/OGC/0/IndexND instead of CRS:1

[Bang Pham Huu]

In WCPS 1.0, it uses CRS:1 as a indicator to know that this is a grid CRS. However, it will need to be changed to use with formal CRS such as

http://www.opengis.net/def/crs/OGC/0/Index2D/

if coverage is grid and has 2D (e.g: mr) or Index3D (irr_cube_1).

Then each WCPS query which need to use grid axis need to use this CRS, e.g:

for c in ( mr ), d in (eobstest)
return encode (scale( c[i(20:150), j(20:150)],
imageCrsDomain(d[t(0),Long:"http://opengis.net/def/crs/OGC/0/Index1D/"(10:200),Lat:"http://opengis.net/def/crs/OGC/0/Index1D/"(10:200)]) )
, "png")

@Prof. Peter: I've some waiting patches which is used CRS:1 instead of Index1D, it is not really convenient to fix it in each patch. Can you accept these existing patch and I will make a patch later to change all CRS:1 to use Index1D in WCPS 1.5? Thanks.

[Dimitar Misev]

Note in your example it should be ​http://opengis.net/def/crs/OGC/0/Index2D, not 1D

[Bang Pham Huu]

The CRS:1 and IndexND is not interchangeable as pointed out in ​http://rasdaman.org/ticket/1362, close as invalid.

[Peter Baumann]

For documentation purposes: indeed CRS:1 and InexND refer to the same thing (image CRS), but cannot be used interchangeably as Index1D, for example, contains more info (1D). It is true, though, that in future IndexND should be used, but this is a matter of using standards and should be independent from implementation.

Except - please check - that petascope possibly internally generates such URLs as query results; in this case, an action is needed indeed to generate IndexND in future.