Table2D is a
direct subtype of Table with functions Table2D Functions, keys Table2D keys and example object Tbl2DNum that represents a two-dimensional orthogonal array of data indexed by coordinates along two axes, which are in fixed order and may be referred to as "first" and "second".
In regular format, one or more of the left columns are reserved for holding the coordinates along the first axis and one or more of the top rows for the coordinates along the second axis.
In transposed format, this correspondence is reversed and the left column holds the second axis coordinates, whereas the top row holds the first axis coordinates.
A Table2D displayed in transposed format is not considered different than its untransposed form with regard to its data contents.
In other words, the relationship between data and coordinates is not affected by switching between regular and transposed formats.
The top/left table cell may contain anything or nothing at all.
If it contains text prefixed with [X] or [XY], where X,Y stand for special letters described below, then the following interpretation holds:
In the [X] case, if X equals R or r, then the table is presented in "Regular" format, meaning the left column(s) holds the coordinates along the first axis, whereas the top row(s) contain the coordinates along the second axis.
If X equals T or t, then the table is presented in "Transposed" format, meaning left column(s) <-> second axis and top row(s) <-> first axis.
In the [XY] case, the second letter Y indicates the type of the table's inner values.
The text following the [XY] - if any - is optional and may be used only if at least one dimension has single array coordinates, i.e. coordinates that occupy a single column or row.
It indicates the title or titles of the respective coordinate column and/or row.
If both dimensions have single array coordinates, then both titles must be specified as #X_Title_Name and #Y_Title_Name, where X_Title_Name, Y_Title_Name can be any text.

Any of these titles may also include a unit specifier from the list
Value Unit at its end enclosed in parentheses, such as #Strike(%), which then applies only on the respective column.
Optionally a unit specifier may be also defined for the table's values. It must be included in parentheses and positioned before the coordinate titles but after the letter code described above.
Y can only be one of {B,D,I,NUL,N,O,S,T,V} (case not important) indicating respectively the types "Boolean" , "Date" , "Integer" , "Null" , "Number" , "Object" , "Step" , "Text" , "Variant".
V (=Variant) means the type of the table entries is not explicitly provided, but it is implied by the entries themselves.
N (=Number) means the table entries (but not necessarily the coordinates too) must be all numbers.
In this case, blank cells are interpreted as numerical entries of which the value gets implied by the adjucent non-blank cells through 2-dimensional linear interpolation and flat extrapolation.
If no letter X is provided, then "Regular" format is assumed.
If no letter Y is provided, then V (=Variant) is assumed for the type of the table's inner values.
Objects of this type are treated by Deriscope exceptionally in that the array data - rather than the surrounding key/value pairs - are immediatelly displayed whenever they are encountered.