Differences

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

--- interimage:operators_documentation [2010/06/16 14:56]
hermann
+++ interimage:operators_documentation [2010/09/06 16:24]
tkorting
@@ Line 1: / Line 1: @@
 [[interimage:|InterIMAGE wiki]]
 ====== TerraAIDA Operators Documentation ======
 Operators reference version: 1.0.5
+InterIMAGE is a multi-platform framework, written in C++, currently with implementations for LINUX and Windows operational systems. Moreover, InterIMAGE provides support for the integration of image processing operators in the interpretation process and, as such operators are treated as external programs by its control mechanism, they can be coded in any computer language, and even in proprietary programs. The InterIMAGE framework offers, nonetheless, a repository of operators, called TerraAIDA ([[http://www.dpi.inpe.br/terraaida]]), assembled with software classes and functions supplied by the [[http://www.terralib.org/|TerraLib]] library.
 ===== TerraAIDA Arithmetic =====
@@ Line 25: / Line 27: @@
 **Multi-Class support**
-Yes. If you select //true// in the "Top Down Multi-Class" option, you must create another node in the same level with a corresponding opposite name, with prefix "n-". For example, if this class name is "MyClass" the opposite class name will be "n-MyClass". Hypothesis discarded by this operator will be classified as "n-MyClass".
+Yes. If you select //true// in the "Top Down Multi-Class" option, you must create another node in the same level with a corresponding opposite name, with prefix "n-". For example, if this class name is "MyClass" the opposite class name will be "n-MyClass". Hypothesis discarded by this operator will be classified as "n-MyClass". Alternatively, you can define a new node name in the input parameter named **Non Class Name**.
 [[interimage:example_supervised_c45|Example of using Multi-Class support.]]
@@ Line 52: / Line 54: @@
 | Decision Rule | Decision Rule | Decision rule applied to the generated hypothesis. | | Leave blank to accept all generated hypothesis. |
 | Node Weight     | Floating point | This node weight (higher priority will be given to nodes with higher weights in cases where there are geographic overlays).  | [0.0, 1.0] |  |
+| Non Class Name  | String | If Multi-Class support is active, the discarded hypothesis will fall in the node named by this parameter. | One string with the name of some node in the tree, in the same level. | |
 ===== TerraAIDA Baatz Segmenter =====
@@ Line 165: / Line 168: @@
 ^ Parameter Name  ^ Type            ^ Description               ^   Valid Values      ^   Note   ^
 | a) Training Set File | * .shp | Training shape file name.   | A valid shape file name.  | The shapefile must be composed by polygons, their respective attributes and particularly one attribute called "class".  |
-| b) Input Shape File | *.shp | Shape file name of the file to be classified. | A valid shape file name. | The shapefile must be composed by polygons, and the *same set of attributes* in the training shape file. |
+| b) Input Shape File | *.shp | Shape file name of the file to be classified. | A valid shape file name. | The shapefile must be composed by polygons, and the **same set of attributes** in the training shape file. |
-One example of this operator can be found [[interimage:example_supervised_c45|here]].
+Note: The generated decision tree will be placed in a //.txt// file, located in the **same place as your input shape file**, with the same name as your input file.
+One example of this operator can be found [[interimage:examples:supervised_c45|here]].
 ===== TerraAIDA Checkerboard Segmenter =====
@@ Line 224: / Line 229: @@
 **Multi-Class support**
-Yes. If you select //true// in the "Top Down Multi-Class" option, you must create another node in the same level with a corresponding opposite name, with prefix "n-". For example, if this class name is "MyClass" the opposite class name will be "n-MyClass". Hypothesis discarded by this operator will be classified as "n-MyClass".
+Yes. If you select //true// in the "Top Down Multi-Class" option, you must create another node in the same level with a corresponding opposite name, with prefix "n-". For example, if this class name is "MyClass" the opposite class name will be "n-MyClass". Hypothesis discarded by this operator will be classified as "n-MyClass". Alternatively, you can define a new node name in the input parameter named **Non Class Name**.
 [[interimage:example_supervised_c45|Example of using Multi-Class support.]]
@@ Line 249: / Line 254: @@
 | Decision Rule | Decision Rule | Decision rule applied to the generated hypothesis. | | Leave blank to accept all generated hypothesis. |
 | Node Weight | Floating point | This node weight (higher priority will be given to nodes with higher weights in cases where there are geographic overlays). | [0.0, 1.0] |  |
+| Non Class Name  | String | If Multi-Class support is active, the discarded hypothesis will fall in the node named by this parameter. | One string with the name of some node in the tree, in the same level. | |
 ===== TerraAIDA Region Growing Segmenter =====
@@ Line 327: / Line 333: @@
 Shape file attributes with the the following names will not be imported: REGION, CLASS, ID, GEOWEST, GEONORTH, GEOEAST, GEOSOUTH, FILE_GEOWEST, FILE_GEONORTH, FILE_GEOEAST, FILE_GEOSOUTH, P, FILE, LLX, LLY, URX, URY.
+**Processing sequence**
+  -Read user input shape file.
+  -Generates the intersection between the loaded shape file polygons and the operator execution area.
+  -Apply the user decision rule (using the supplied training set) over the intersection  polygons.
+  -Generate the output hypothesis.
 **Input parameters**
@@ Line 361: / Line 374: @@
 **Multi-Class support**
-Yes. If you select //true// in the "Top Down Multi-Class" option, you must create another node in the same level with a corresponding opposite name, with prefix "n-". For example, if this class name is "MyClass" the opposite class name will be "n-MyClass". Hypothesis discarded by this operator will be classified as "n-MyClass".
+Yes. If you select //true// in the "Top Down Multi-Class" option, you must create another node in the same level with a corresponding opposite name, with prefix "n-". For example, if this class name is "MyClass" the opposite class name will be "n-MyClass". Hypothesis discarded by this operator will be classified as "n-MyClass". Alternatively, you can define a new node name in the input parameter named **Non Class Name**.
 [[interimage:example_supervised_c45|Example of using Multi-Class support.]]
+**Processing sequence**
+  -Read user input shape file.
+  -Generates the intersection between the loaded shape file polygons and the operator execution area.
+  -Using the intersection result generates a set of intermediate hypothesis of "MyClass" and the opposite class "n-MyClass", as describe above.
+  -Apply the user decision rule (using the supplied training set) over the intermediate hypothesis set.
+  -Generate the output hypothesis from the decision rule result.
 **Input parameters**
@@ Line 375: / Line 396: @@
 | Decision Rule | Decision Rule | Decision rule applied to the generated hypothesis. | | Leave blank to accept all generated hypothesis. |
 | Node Weight | Floating point | This node weight (higher priority will be given to nodes with higher weights in cases where there are geographic overlays).  | [0.0, 1.0] |  |
+| Non Class Name  | String | If Multi-Class support is active, the discarded hypothesis will fall in the node named by this parameter. | One string with the name of some node in the tree, in the same level. | |
 {{ :interimage:shape_file_intersection_example.png }}

Trace:

Differences

Navigation

Search