blob: 2c6d264aecf1582b6b814b801cc3d35318e0ae07 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
.. _pop:
================================================================================
Pop coordinate value to pipeline stack
================================================================================
.. versionadded:: 6.0.0
Retrieve components of a coordinate that was saved in a previous pipeline step.
+---------------------+--------------------------------------------------------+
| **Alias** | pop |
+---------------------+--------------------------------------------------------+
| **Domain** | 4D |
+---------------------+--------------------------------------------------------+
| **Input type** | Any |
+---------------------+--------------------------------------------------------+
| **Output type** | Any |
+---------------------+--------------------------------------------------------+
This operations makes it possible to retrieve coordinate components that was
saved in previous pipeline steps. A retrieved coordinate component is loaded,
or *popped*, from a memory stack that is part of a :ref:`pipeline<pipeline>`.
The pipeline coordinate stack is inspired by the stack data structure that is
commonly used in computer science. There's four stacks available: One four each
coordinate dimension. The dimensions, or coordinate components, are numbered
1--4. It is only possible to move data to and from the stack within the same
coordinate component number. Values can be saved to the stack by using the
:ref:`push operation<push>`.
If the pop operation is used by itself, e.g. not in a pipeline, it will
function as a no-operation that passes the coordinate through unchanged.
Similarly, if no coordinate component is available on the stack to be popped
the operation does nothing.
Examples
################################################################################
A common use of the :ref:`push<push>` and pop operations is in 3D
:ref:`Helmert<helmert>` transformations where only the horizontal components
are needed. This is often the case when combining heights from a legacy
vertical reference with a modern geocentric reference. Below is a an example of
such a transformation, where the horizontal part is transformed with a Helmert
operation but the vertical part is kept exactly as the input was.
::
$ echo 12 56 12.3 2020 | cct +proj=pipeline \
+step +proj=push +v_3 \
+step +proj=cart +ellps=GRS80 \
+step +proj=helmert +x=3000 +y=1000 +z=2000 \
+step +proj=cart +ellps=GRS80 +inv \
+step +proj=pop +v_3 \
12.0056753463 55.9866540552 12.3000 2000.0000
Note that the third coordinate component in the output is the same as the input.
The same transformation without the push and pop operations would look like this::
$ echo 12 56 12.3 2020 | cct +proj=pipeline \
+step +proj=cart +ellps=GRS80 \
+step +proj=helmert +x=3000 +y=1000 +z=2000 \
+step +proj=cart +ellps=GRS80 +inv \
12.0057 55.9867 3427.7404 2000.0000
Here the vertical component is adjusted significantly.
Parameters
################################################################################
.. option:: +v_1
Retrieves the first coordinate component from the pipeline stack
.. option:: +v_2
Retrieves the second coordinate component from the pipeline stack
.. option:: +v_3
Retrieves the third coordinate component from the pipeline stack
.. option:: +v_4
Retrieves the fourth coordinate component from the pipeline stack
Further reading
################################################################################
#. `Stack data structure on Wikipedia <https://en.wikipedia.org/wiki/Stack_(abstract_data_type)>`_
|
