Opened 7 years ago
Closed 7 years ago
#1578 closed enhancement (fixed)
Make sure we use JSON and not CSV encode in petascope, raswct, etc. — at Version 3
| Reported by: | Dimitar Misev | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | major | Milestone: | 9.5 |
| Component: | petascope | Version: | development |
| Keywords: | Cc: | Peter Baumann, Vlad Merticariu | |
| Complexity: | Medium |
Description (last modified by )
Our CSV encode is not very standard for 3D+ and using JSON would be much better.
Petascope, raswct, and any other client code that relies on encoding to CSV should be updated to use JSON. This is straightforward, the '{' and '}' handling should be simply changed to '[' and ']'.
There are 2 things need to change:
+ Petascope with GetCoverage in GML+XML using JSON format internally.
+ Raswct supports parsing value from JSON beside CSV.
Change History (3)
comment:1 by , 7 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 7 years ago
comment:3 by , 7 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
definitely a good move! Should save some trouble in the future.