Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#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 Dimitar Misev)

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 Dimitar Misev, 5 years ago

Cc: bbell removed
Description: modified (diff)
Owner: changed from Dimitar Misev to apercov
Status: newassigned

comment:2 by Dimitar Misev, 5 years ago

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.

comment:3 by Dimitar Misev, 5 years ago

Owner: changed from apercov to dkamov

comment:4 by Dimitar Misev, 5 years ago

Resolution: wontfix
Status: assignedclosed

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 Dimitar Misev (next)
Note: See TracTickets for help on using tickets.