#1856 closed enhancement (wontfix)
Rasql_hierarchical metadata as extra parameters of encode()
Reported by: | Bang Pham Huu | Owned by: | dkamov |
---|---|---|---|
Priority: | major | Milestone: | 10.0 |
Component: | conversion | Version: | development |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
Complexity: | Medium |
Description (last modified by )
Currently, "metadata" as extra parameters in JSON of encode() can be a map of string:string only, e.g:
select encode(c, "tiff", "{ \"metadata\": { \"new_metadata\": \"This is a new added metadata\" }") from mr2 as c
It could be good if "metadata" can support value not only string (current error is: rasdaman error 0: Type is not convertible to string, but a JSON object or JSON array, e.g:
select encode(c, "tiff", "{ \"metadata\": { \"new_metadata\": [\"value1\", \"value2\" }") from mr2 as c
select encode(c, "tiff", "{ \"metadata\": { \"new_metadata\": { \"key1\": \"value1\"} }") from mr2 as c
Change History (4)
comment:1 by , 5 years ago
Cc: | removed |
---|---|
Description: | modified (diff) |
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 5 years ago
comment:3 by , 5 years ago
Owner: | changed from | to
---|
comment:4 by , 5 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
Closing as wontfix as the formats don't support hierarchical metadata anyway (unless proven otherwise .
The user/client should make sure to arrange the metadata as key/value pairs in whatever way they thing it's best.
Version 0, edited 5 years ago by (next)
Note:
See TracTickets
for help on using tickets.
How should this metadata be encoded?
In GDAL only flat key/value pairs is possible as far as I know. Should be similar in netcdf.