Opened 6 years ago
Last modified 6 years ago
#1910 closed enhancement
Petascope_Clip()'s new parameter WITH COORDINATES — at Version 3
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 9.7 |
Component: | petascope | Version: | development |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
Complexity: | Medium |
Description (last modified by )
When clipping and encoding as CSV/JSON
, the result of clipping with new parameter WITH COORDINATES
will have this format with grid axes and a value attached to its grid coordinates, e.g:
for c in (test_irr_cube_2) return encode( clip(c, LineStringZ(75042.7273594 5094865.55794 "2008-01-01T02:01:20.000Z", 705042.727359 5454865.55794 "2008-01-08T00:02:58.000Z")) WITH COORDINATES, "json") returns ["grid_coord_1 grid_coord_2... value1 value2 ...", "grid_coord_1 grid_coord_2... value1 value2 ...", ...]
Petascope will parse the returned result, and convert the axis1 axis2… grid coordinates to corresponding geo coordinates. This needs to be done carefully with respect to the axis order in rasdaman. So the final result will be
["geo_coord_1 geo_coord_2... value1 value2 ...", "geo_coord_1 geo_coord_2... value1 value2 ...", ...]
Petascope should preserve these characters (+ whitespace) as they appear in the json/csv result from rasdaman:
{ } [ ] " ,
Change History (3)
comment:1 by , 6 years ago
Description: | modified (diff) |
---|
comment:2 by , 6 years ago
Description: | modified (diff) |
---|
comment:3 by , 6 years ago
Component: | undecided → petascope |
---|---|
Description: | modified (diff) |
Note:
See TracTickets
for help on using tickets.