aboutsummaryrefslogtreecommitdiff
path: root/docs/source/operations/transformations
diff options
context:
space:
mode:
authorKristian Evers <kristianevers@gmail.com>2019-02-14 12:00:45 +0100
committerKristian Evers <kristianevers@gmail.com>2019-02-14 12:00:45 +0100
commit29a59cadb9d1371479477af517f3431784e880f9 (patch)
tree040806680521072ffdc1e5b68a2c34d82646c857 /docs/source/operations/transformations
parent15a225b0d80281b80c536e7b5dde334d12c406c6 (diff)
downloadPROJ-29a59cadb9d1371479477af517f3431784e880f9.tar.gz
PROJ-29a59cadb9d1371479477af517f3431784e880f9.zip
Reverse direction of deformation operations/transformations/deformation
Changed the direction of dt-calculation to follow the same convention as helmert. Changed from dt = t_c - t_obs to dt = t_obs - t_c, which effectively reverses the direction of the operation. Existing projstrings using deformation can simply reverse the direction of the operation to achieve the same results as before this commit.
Diffstat (limited to 'docs/source/operations/transformations')
-rw-r--r--docs/source/operations/transformations/deformation.rst20
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/source/operations/transformations/deformation.rst b/docs/source/operations/transformations/deformation.rst
index 87b08453..0a772547 100644
--- a/docs/source/operations/transformations/deformation.rst
+++ b/docs/source/operations/transformations/deformation.rst
@@ -127,7 +127,7 @@ Mathematically speaking, application of a deformation model is simple. The defor
represented as a grid of velocities in three dimensions. Coordinate corrections are
applied in cartesian space. For a given coordinate, :math:`(X, Y, Z)`, velocities
:math:`(V_X, V_Y, V_Z)` can be interpolated from the gridded model. The time span
-between :math:`t_c` and :math:`t_{obs}` determine the magnitude of the coordinate
+between :math:`t_{obs}` and :math:`t_c` determine the magnitude of the coordinate
correcton as seen in eq. :eq:`apply_velocity` below.
.. math::
@@ -144,7 +144,7 @@ correcton as seen in eq. :eq:`apply_velocity` below.
Y \\
Z \\
\end{pmatrix}_A +
- (t_c - t_{obs})
+ (t_{obs} - t_c)
\begin{pmatrix}
V_X \\
V_Y \\
@@ -154,14 +154,14 @@ correcton as seen in eq. :eq:`apply_velocity` below.
Corrections are done in cartesian space.
-Coordinates of the gridded model are in ENU (east, north, up) space because it would
-otherwise require an enormous 3 dimensional grid to handle the corrections in cartesian
-space. Keeping the correction in lat/long space reduces the complexity of the grid
-significantly. Consequently though, the input coordinates needs to be converted to
-lat/long space when searching for corrections in the grid. This is done with the *cart*
-operation. The converted grid corrections can then be applied to the input coordinates
-in cartesian space. The conversion from ENU space to cartesian space is done in the
-following way:
+Coordinates of the gridded model are in ENU (east, north, up) space because it
+would otherwise require an enormous 3 dimensional grid to handle the corrections
+in cartesian space. Keeping the correction in lat/long space reduces the
+complexity of the grid significantly. Consequently though, the input coordinates
+needs to be converted to lat/long space when searching for corrections in the
+grid. This is done with the :ref:`cart<cart>` operation. The converted grid
+corrections can then be applied to the input coordinates in cartesian space. The
+conversion from ENU space to cartesian space is done in the following way:
.. math::
:label: enu2xyz