Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
image_virtualization [2026/07/22 04:02] hermann [See Also] |
image_virtualization [2026/08/08 02:02] (current) hermann |
||
|---|---|---|---|
| Line 23: | Line 23: | ||
| Older versions of Dinamica could only manipulate maps with the same number of lines and columns. Additional information such as registration coordinates, resolution, etc., was not treated uniformly by all functors, and many of them simply ignored this information in the input maps. | Older versions of Dinamica could only manipulate maps with the same number of lines and columns. Additional information such as registration coordinates, resolution, etc., was not treated uniformly by all functors, and many of them simply ignored this information in the input maps. | ||
| - | Dinamica handles map extents and resolution in a very uniform way. Basically, when a set of maps is given to a functor, they are first analyzed to determine the minimum extent and resolution an input map should have to best cover all necessary cells. Then, each input map is wrapped in a virtual version of itself with this new resolution and extent. The functor receives those virtual versions and uses them to perform the computation. By using this virtualization process, Dinamica ensures that all maps given to a functor have the same number of lines and columns, resolution, and extents. It is also worth noting that the same map might have different virtual representations depending on the original set of maps given to a particular functor. | + | Dinamica handles map extents and resolution in a very uniform way. Basically, when a set of maps is given to a functor, they are first analyzed to determine the minimum extent and the highest resolution an input map should have to best cover all necessary cells. Then, each input map is wrapped in a virtual version of itself with this new resolution and extent. The functor receives those virtual versions and uses them to perform the computation. By using this virtualization process, Dinamica ensures that all maps given to a functor have the same number of lines and columns, resolution, and extents. It is also worth noting that the same map might have different virtual representations depending on the original set of maps given to a particular functor. |
| {{reference_book:imagevirtualization4.png?direct&800|}} | {{reference_book:imagevirtualization4.png?direct&800|}} | ||
| - | The virtual resolution of the resulting virtual maps is always the smallest resolution among all maps involved in the virtualization process. This minimizes the number of cells that need to be analyzed when determining which original cell a given virtual cell corresponds to. | + | The virtual resolution of the resulting virtual maps is always the highest resolution (smallest cell size) among all maps involved in the virtualization process. This minimizes the number of cells that need to be analyzed when determining which original cell a given virtual cell corresponds to. |
| {{reference_book:imagevirtualization6.png?direct&800|}} | {{reference_book:imagevirtualization6.png?direct&800|}} | ||