Each Control feature should be a single line segment, which is a vector representing the direction and distance from a point on the Observed feature to its corresponding point after warping. Any format is available if it supports storing line geometries.

---

Each Control feature should be a single line segment, which is a vector representing the direction and distance from a point on the Observed feature to its corresponding point after warping. Any format is available if it supports storing line geometries.

@mark2atsafe Low hanging fruit: Adding this reply by @takashi to the AffineWarper Documentation will make it easier to understand.

---

@mark2atsafe Low hanging fruit: Adding this reply by @takashi to the AffineWarper Documentation will make it easier to understand.

The current documentation says...

Each Control feature represents a control vector whose start point is at some location in the original Observed data space, and whose end point is at the corresponding location in the desired output data space. The control vector represents the correction required to go from the observed vertex to the desired vertex. (Control vectors with only one point are interpreted as a requirement that this location not change from the observed dataset to the reference dataset. This is often referred to as a tie point.)

I can maybe make a suggestion to edit it. Perhaps to this...?

Each Control feature represents a control vector (a 2-point line feature) whose start point is at some location in the original Observed data space, and whose end point is at the corresponding location in the desired output data space. Each control vector represents the correction required to go from the observed vertex to the desired vertex, in terms of direction and distance. Control vectors with only one point are interpreted as a requirement that this location not change from the observed dataset to the reference dataset. This is often referred to as a tie point.Control vectors can be stored in a dataset of any format and read into FME, or generated directly in an FME workspace, which is often the case when the vectors are not known in advance and must be generated from incoming data.

Does that sound better?

---

The current documentation says...

Each Control feature represents a control vector whose start point is at some location in the original Observed data space, and whose end point is at the corresponding location in the desired output data space. The control vector represents the correction required to go from the observed vertex to the desired vertex. (Control vectors with only one point are interpreted as a requirement that this location not change from the observed dataset to the reference dataset. This is often referred to as a tie point.)

I can maybe make a suggestion to edit it. Perhaps to this...?

Each Control feature represents a control vector (a 2-point line feature) whose start point is at some location in the original Observed data space, and whose end point is at the corresponding location in the desired output data space. Each control vector represents the correction required to go from the observed vertex to the desired vertex, in terms of direction and distance. Control vectors with only one point are interpreted as a requirement that this location not change from the observed dataset to the reference dataset. This is often referred to as a tie point.Control vectors can be stored in a dataset of any format and read into FME, or generated directly in an FME workspace, which is often the case when the vectors are not known in advance and must be generated from incoming data.

Does that sound better?

Exactly. Vector is the correct term but when I read "single line segment" it was instantly clear to me how this should work. Thanks for the quick follow up.

---