Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Last revision Both sides next revision
lesson_1 [2019/09/04 13:29]
britaldo 		lesson_1 [2020/02/13 15:48]
danilo
Line 10: Line 10:
 \\ \\
 Dinamica EGO handles data in several formats, including raster maps or images, tables, matrices, and a Weights of Evidence coefficient file.\\ 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 EGO supports raster datasets for most analyses, but vector can also be input and then transformed into raster or used in Python or R hybrid EGO operators. Geo-referencing is mandatory, same projection and datum. Dinamica EGO virtualization machine can process maps with different spatial resolution and tie point.
 \\ \\
 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. 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]]    * Dinamica EGO reads and writes raster data in many ways: check all the [[:​supported_map_formats|Supported Map Formats]]
-   * Dinamica EGO supports ​all the affine ​coordinate systems ​wich includes most of the projections and data used.+   * Dinamica EGO supports ​most of the coordinate systems.
 \\ \\
 <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 the null cell. The value reserved for null cell representation may vary depending on the data cell type, i.e. the size in bits used to store the cell values of a map. Dinamica EGO supports data cell types as follows: <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 the null cell. The value reserved for null cell representation may vary depending on the data cell type, i.e. the size in bits used to store the cell values of a map. Dinamica EGO supports data cell types as follows:
Line 21: Line 22:
 {{ :​tutorial:​data_cell_types.jpg |}} {{ :​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>​+Usually, the lowest negative value is used to represent the null value. For example -32768 for Signed 16 Bit Integer. ​Choose ​a data cell type able to encompass ​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. If there is more than one choice, choose always the most economical data format in number of bits</​note>​
 <note tip> You may need to define the null value when loading a Geotiff and some other dataset, which lacks this definition. Learn in [[tutorial:​building_a_simple_model|Building a simple model Lesson]] how to do this.</​note>​ <note tip> You may need to define the null value when loading a Geotiff and some other dataset, which lacks this definition. Learn in [[tutorial:​building_a_simple_model|Building a simple model Lesson]] how to do this.</​note>​
 \\ \\
Line 66: Line 67:
 \\ \\
 <note tip> <note tip>
-TIP: You can edit this file directly on a text editor or using the Weights of Evidence graphical editor linked to [[:​load_weights|Load Weights Functor]].+You can edit this file directly on a text editor or using the Weights of Evidence graphical editor linked to [[:​load_weights|Load Weights Functor]].
 </​note>​ </​note>​
 \\ \\