Opened 9 years ago
Last modified 8 years ago
#1315 closed defect
WCPS1.5_Use http://..../def/crs/OGC/0/IndexND instead of CRS:1 — at Version 2
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 10.0 |
Component: | petascope | Version: | development |
Keywords: | Cc: | Peter Baumann, Dimitar Misev | |
Complexity: | Easy |
Description (last modified by )
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.
Change History (2)
comment:1 by , 9 years ago
comment:2 by , 8 years ago
Description: | modified (diff) |
---|---|
Summary: | WCPS1.5_Use http://..../def/crs/OGC/0/Index1D instead of CRS:1 → WCPS1.5_Use http://..../def/crs/OGC/0/IndexND instead of CRS:1 |
Note:
See TracTickets
for help on using tickets.
Note in your example it should be http://opengis.net/def/crs/OGC/0/Index2D, not 1D