Coregistration module

This section explains coregistration module in demcompare.

In the following image, we can find the classes that take part in demcompare’s coregistration step, along with their relationship.

Coregistration step architecture

The coregistration_class and transformation_class handle the API for the dem coregistration. The Demcompare pipeline module creates a coregistration_class object. The coregistration_class creates a transformation_class object when the coregistration offsets are obtained.

The transformation_class object is in charge of storing the offsets and applying them to the secondary dem.

../../_images/schema_coregistration_class.png

Fig. 14 Coregistration classes relationship.

Coregistration

The coregistration class in demcompare has the following structure:

A Coregistration object is in charge of computing the offsets between two DEMs that have the same resolution and size, giving as an output a Transformation object, along with the two reprojected and coregistered dems.

It is to be noticed that to compute the offsets between two DEMs, they need to have the same resolution and size. For this reason, the coregistration module perfoms a reprojection using the Dem Tools modules API.

One can find here the full list of API functions available in the coregistration_class, as well as their description and input and output parameters: Coregistration API

For information on how to create a new coregistration class, please see New coregistration class implementation.

Transformation

The Transformation class stores the offsets obtained during the coregistration step. It also has the API to apply the offsets to an input DEM. It is created by the Coregistration class and given as an output.

One can find here the full list of API functions available in the transformation_class, as well as their description and input and output parameters: Transformation API