Helmert Transform Coordinate Rotation Applier

Description

Apply a static small-angle seven-parameter Helmert transform with an explicit rotation-sign convention.

Geodesy distinguishes a mathematical reference ellipsoid, a realized coordinate datum and the physical gravity field. Geodetic latitude follows the ellipsoid normal; geocentric latitude follows a radius from the center. Ellipsoidal height, orthometric height and geoid undulation are separate signed quantities. Keep the declared ellipsoid, coordinate axes, angular units and time scale with a result.

Apply a static small-angle seven-parameter Helmert transform with an explicit rotation-sign convention.

A three-dimensional Helmert transform acts on Cartesian coordinates. Position-vector and coordinate-frame rotations use opposite signs; translations are meters, rotations arcseconds and the scale increment parts per million.^[1]

When to use this tool

Use this tool when you need to apply a static small-angle seven-parameter Helmert transform with an explicit rotation-sign convention.

How to use the tool and how it works

Enter ecefMeters, translationMeters, rotationArcseconds, scalePpm, convention using the definitions below.
Run the operation. Resolve input-format errors before interpreting an output.
Read result.ecefMeters, using the stated boundary, ordering, sign and absence conventions.

Require three-element [X,Y,Z] coordinates, translations and rotations. Convert arcseconds to radians with positive signs for position-vector and negative signs for coordinate-frame. Return t+(1+ppm×10⁻⁶) times the small-angle rotated Cartesian vector.^[2]

Input field	Meaning and units	Accepted input
ecefMeters	Three-element [X,Y,Z] geocentric Cartesian meter vector; individual magnitudes≤10⁹ and any radius restrictions stated above apply.	Dense list of at most 128 finite numbers, under the stated integer/range rules.
translationMeters	Three translations [dX,dY,dZ] in meters; Molodensky limits each to ±10,000.	Dense list of at most 128 finite numbers, under the stated integer/range rules.
rotationArcseconds	Three small rotations [rx,ry,rz] in arcseconds, each within ±60, under convention.	Dense list of at most 128 finite numbers, under the stated integer/range rules.
scalePpm	Signed scale increment in parts per million, magnitude≤1000; factor is 1+ppm×10⁻⁶.	Finite numeric value satisfying the stated comparisons.
convention	Exact rotation-sign selector position-vector or coordinate-frame.	Text, at most 8,192 UTF-16 code units; narrower grammar/range rules also apply.

Output field	Interpretation
result	Object containing the fields below.
result.ecefMeters	Three Cartesian [X,Y,Z] coordinates in meters, in the stated frame.

json

{
  "input": {
    "ecefMeters": [
      1,
      2,
      3
    ],
    "translationMeters": [
      1,
      1,
      1
    ],
    "rotationArcseconds": [
      0,
      0,
      0
    ],
    "scalePpm": 0,
    "convention": "position-vector"
  },
  "output": {
    "result": {
      "ecefMeters": [
        2,
        3,
        4
      ]
    }
  }
}

Limitations and assumptions

Convention is exactly position-vector or coordinate-frame, rotation magnitudes≤60 arcseconds, scale within ±1000 ppm, and vector entries within ±10⁹. This is a static first-order seven-parameter transform, without epoch/rate terms or exact finite rotations.
All quantities are finite and retain the units stated for this operation. Ellipsoid-parameter tools use semi-major axis 1–10⁸ m and dimensionless flattening 0–0.02; explicit-axis tools use 0.9a≤b≤a unless a tighter bound is stated. These tools do not fetch datums, geoid grids, satellite observations or Earth-orientation updates.
Every declared outer field is required and unknown outer fields are rejected. Strings and JSON text have size limits, lists are bounded to 128 entries, and JSON nesting/node counts are bounded. Tighter operation-specific bounds stated above take precedence.
Numeric results must be finite. Large physical magnitudes are allowed by the output evidence checks, while integer fields and source schemas retain their exactness rules. Source indexes are zero-based. Floating-point residues can remain even where an ideal formula gives an exact zero.

Alternative or Complementary methods

Use a coordinate transform for a change of representation and explicit datum parameters for a change of reference frame. Preserve model and convergence metadata, and use observation and datum information appropriate to a real survey before interpreting a computed tolerance as accuracy.

References

Similar or alternative tools

Scale Factor ppm Correction in Helmert Applier
Apply a signed parts-per-million scale increment and expose its additive coordinate correction.
Molodensky Datum Shift Simplified A-B-Delta Converter
Apply first-order Molodensky coordinate shifts using explicit translations and ellipsoid changes.