Table Transpose with Labels
Transpose a rectangular numeric table together with explicit row and column labels; label identities remain unchanged.
Description
Transpose a rectangular numeric table together with explicit row and column labels; label identities remain unchanged.
Transposing a labeled numeric table swaps row and column roles as well as values.
When to use this tool
Transpose a rectangular numeric table together with explicit row and column labels; label identities remain unchanged.
- Prepare the supplied table, rowLabels, columnLabels fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter table, rowLabels, columnLabels. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.table, result.rowLabels, result.columnLabels. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require rowLabels length equal table rows and each row length equal columnLabels length. Return column-wise data as new rows, with rowLabels and columnLabels exchanged.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| table | table. | Numeric rows; at most 128 rows and 128 values per row |
| rowLabels | row labels. | List of strings; at most 128 entries |
| columnLabels | column labels. | List of strings; at most 128 entries |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.table | The table list in the ordering and representation described above. |
| result.rowLabels | The row labels list in the ordering and representation described above. |
| result.columnLabels | The column labels list in the ordering and representation described above. |
{
"input": {
"table": [
[
1,
2
],
[
3,
4
]
],
"rowLabels": [
"a",
"b"
],
"columnLabels": [
"x",
"y"
]
},
"output": {
"result": {
"table": [
[
1,
3
],
[
2,
4
]
],
"rowLabels": [
"x",
"y"
],
"columnLabels": [
"a",
"b"
]
}
}
} Limitations and assumptions
- Labels need not be unique. No matrix arithmetic, sorting or external spreadsheet update occurs.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Choose the exact text grammar before combining serializers and parsers. UTF-16 record lengths, raw separators and custom backslash escapes differ from byte framing, CSV, Markdown and spreadsheet semantics.
References
Similar or alternative tools
- Fixed Width Layout Overlap Check
Audit positive overlap between half-open fixed-width text layout spans; touching and zero-width spans do not overlap.
- Fixed Width Record Padder
Pad caller cells into explicit UTF-16 fixed-width fields; overflow is rejected instead of silently truncated.