Differences

This shows you the differences between two versions of the page.

--- lesson_1 [2013/08/05 18:44]
admin
+++ lesson_1 [2019/08/30 16:44]
argemiro
@@ Line 1: / Line 1: @@
-===== Data structures and formats =====
+{{ :logo_guidebook1.jpg?400 |}}
+\\
+=====LESSON 1: Dinamica EGO data structures and file format=====
+\\
+\\
 ==== What will you learn? ====
@@ Line 8: / Line 10: @@
   * Dinamica EGO file formats
-Dinamica EGO handles data in several formats, including raster maps or images, tables, matrices, and a Weights of Evidence coefficient file.[{{ :tutorial:cube_raster_dataset.jpg| A cube raster dataset}}]\\
+Dinamica EGO handles data in several formats, including raster maps or images, tables, matrices, and a Weights of Evidence coefficient file.\\
-For spatial data, Dinamica only supports raster datasets. Therefore you will need to prepare your dataset in a GIS package and then export the maps in one of the three formats specified below. Although geo-referencing is supported and needed, all raster dataset in a model must have the same number of columns and rows. Moreover they must be tied to the same coordinate space and registration point (Fig.3).\\
+For spatial data, Dinamica only supports raster datasets. Therefore you will need to prepare your dataset in a GIS package and then export the maps in one of the three formats specified below. Although geo-referencing is supported and needed, all raster dataset in a model must have the same number of columns and rows. Moreover they must be tied to the same coordinate space and registration point.\\
 Dinamica EGO reads and writes raster data in many ways: check all the [[:supported_map_formats|Supported Map Formats]]\\
@@ Line 20: / Line 22: @@
 <note important>In map algebra, the null concept is very important to obtain an intelligible result from a model execution. Null means absence of data. Thus a map containing an irregular geographic area of interest, which does not completely cover the geographic plane, must contain a representation for null cell. The value reserved for null cell representation may vary depending on the data cell type, i.e. the size in terms of bits used to store the cell values of a map. Dinamica EGO supports data cell types as follows: {{ :tutorial:data_cell_types.jpg |}}\\ Usually, the lowest negative value is used to represent the null value. For example -32768 for Signed 16 Bit Integer. Always choose a data cell type able to embrace the range of values contained in a variable. For example: elevation, varying from -10 meters to 4000 meters, must be represented as Signed 16 Bit Integer or IEEE 754 32 Bit Real.</note>
-<note warning> You may need (and must) in some cases to define the null value when loading a Geotiff dataset, which lacks this definition (highly advised). Learn in [[tutorial:building_a_simple_model|Building a simple model Lesson]] how to do this.</note>\\
+<note warning> You may need (and must) in some cases to define the null value when loading a Geotiff and some other dataset, which lacks this definition (highly advised). Learn in [[tutorial:building_a_simple_model|Building a simple model Lesson]] how to do this.</note>\\
-**Tables** are a convenient way to represent attribute data, usually pertaining to a certain geographic zone, for example: country, state or counties. Dinamica EGO can read data in Comma Separated Value format, in which the first column represents the key and the second, the value, as follows.
+Tables are a convenient way to represent attribute data, usually pertaining to a certain geographic zone, for example: country, state or counties. Dinamica EGO can read data in Comma Separated Value format, as follows. Basically, it is possible to use two different kinds of tables: [[:table type|tables]] and [[:lookup table type|lookup tables]].
+//Table//
-^ Key  ^ Value  ^
+^ Key*  ^ Key2*  ^ Value  ^ Value2  ^
+| 1  | 2  | 10  | 60  |
+| 2  | 6  | 30  | 40  |
+| 3  | 9  | 15  | 20  |
+//Lookup Table//
+^ Key  ^ Value  ^
 | 1  | 10  |
 | 2  | 30  |
 | 3  | 15  |
-The first line of the table must contain the columns titles “Key” and the variable name, such as population, countries, etc.
+The first line of the lookup table must contain the columns titles “Key” and the variable name, such as population, countries, etc.
-Transition matrix is also stored using this format; the only difference is that the key employs a composite algorism to represent a transition as follows:
+Transition matrix is also stored using this format as follows:
+^ To*  ^ From*  ^ Rate  ^
-^ Key  ^ Value  ^
+| 1  | 2  | 0.223567  |
-| 1.002  | 0.223567  |
+| 1  | 3  | 0.223567  |
-| 1.003  | 0.223567  |
+| 2  | 1  | 0.024841  |
-| 2.001  | 0.024841  |
+| 2  | 3  | 0.030573  |
-| 2.003  | 0.030573  |
+| 3  | 2  | 0.000348  |
-| 3.002  | 0.000348  |
 Thus the previous table is equivalent to the following transition matrix: Note that the diagonal values do not need to be filled in, nor are necessary the transitions equal to zero.
-|   ^ 1  ^ 2  ^ 3  ^
+|    ^ 1  ^ 2  ^ 3  ^
 ^ 1  | -  | 0.223567  | 0.379618  |
 ^ 2  | 0.024841  | -  | 0.030573  |
 ^ 3  | 0  | 0  | -  |
 Another supported format is the Weights of Evidence file - a text file containing the Weights of Evidence coefficients. This file is obtained through the Weights of Evidence method used in the calibration process