Description
Construct a literal translation transform, not a matrix applied to caller state.
A planar affine transform combines a linear map and translation. This family stores [a,b,c,d,e,f], mapping [x,y] to [a×x+c×y+e,b×x+d×y+f]. Positions include translation; displacements use only the linear block, and normal covectors use its inverse transpose. Composition order changes the result.
Construct a literal translation transform, not a matrix applied to caller state.
When to use this tool
Use this tool to construct a literal translation transform, not a matrix applied to caller state.
How to use the tool and how it works
- Enter x, y using the input definitions below.
- Run the operation. Resolve malformed-input errors before interpreting the result.
- Read result.matrix. Interpret signs, units, ordering and null values using the rules below.
Return [1,0,0,1,x,y], giving x′=xInput+x and y′=yInput+y.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| x | x translation distance, scale factor or shear coefficient as stated for this constructor. | Finite number satisfying the stated comparisons. |
| y | y translation distance, scale factor or shear coefficient as stated for this constructor. | Finite number satisfying the stated comparisons. |
| Output field | Interpretation |
|---|---|
| result | Object containing the fields below. |
| result.matrix | Resulting six coefficients [a,b,c,d,e,f] under the stated map and composition order. |
{
"input": {
"x": 4,
"y": 5
},
"output": {
"result": {
"matrix": [
1,
0,
0,
1,
4,
5
]
}
}
}Limitations and assumptions
- This constructs a translation record without applying it to any document, canvas or existing matrix.
- Matrices have six finite coefficients. Point/vector inputs have two components within ±1,000,000,000; rectangle bounds are likewise bounded and ordered. Coordinate units and axis directions are caller-defined. No conditioning threshold is inferred for inversion.
- Every declared top-level input is required and unknown fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and within the absolute safe-integer magnitude; exact larger integers use decimal text. Source positions are zero-based UTF-16 offsets and span ends are exclusive unless a different convention is explicitly stated.
Alternative or Complementary methods
Check coefficient layout and application order when exchanging matrices. Use point, displacement or normal operations according to the quantity being transformed, and a separate conditioning analysis for numerically sensitive inverses.
References
Similar or alternative tools
- Affine Translation Component Replacement
Replace only translation components, preserving the full original linear block.
- Affine Matrix About Anchor Transform
Move the linear transform’s origin to an explicit anchor, preserving existing translation.