Ambiguity in JSON representation of multi-dimensional arrays #269
Description
The description of JSON output when multi-dimensional fields are used is ambiguous. The 1-d case is provided in the example, but there is no mention of how multi-dimensional arrays should be handled. For example, when size=[3,4] the record could look like:
...
["2010-001T12:01:00Z",0,[[0.1,0.2,0.3,0.4],[0.5,0.6,0.7,0.8],[0.9,1.0,1.1,1.2]]],
...
or
...
["2010-001T12:01:00Z",0,[0.1,0.2,0.3,0.4,0.5,0.6,0.7,0.8,0.9,1.0,1.1,1.2]],
...
It looks like the only server which has this is the CDAWeb server, and in this case Nand chose the first. I'd suggest we just make this explicit.
The counter argument is that this is redundant, since the size=[3,4] asserts the shape. Also, performance will be reduced because many more data structures are needed to represent and parse this.
Last, both options could be accepted, and it would be left to the client to properly form the arrays.