Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
interimage:examples:example2 [2011/08/11 19:30] rsilva |
interimage:examples:example2 [2011/08/11 20:32] rsilva |
||
---|---|---|---|
Line 18: | Line 18: | ||
* tijuca.tif | * tijuca.tif | ||
* quadras.shp (city blocks) | * quadras.shp (city blocks) | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
Line 56: | Line 62: | ||
* Collapse the //Blocks// node. Once it's collapsed, select an object and see its attributes in the //Object Information// widget. Note that each block turned into a separate object and that the //CODIGO// attribute was successfully imported by the operator. | * Collapse the //Blocks// node. Once it's collapsed, select an object and see its attributes in the //Object Information// widget. Note that each block turned into a separate object and that the //CODIGO// attribute was successfully imported by the operator. | ||
{{interimage:examples:example2_12.png|Blocks node collapsed}} -> {{interimage:examples:example2_13.png|Select an object}} -> {{interimage:examples:example2_14.png|Object Information widget}} | {{interimage:examples:example2_12.png|Blocks node collapsed}} -> {{interimage:examples:example2_13.png|Select an object}} -> {{interimage:examples:example2_14.png|Object Information widget}} | ||
- | * Expand back the //Blocks// node. Now, select the //Blocks// node and click the //TopDown Decision Rule// button. | + | * Expand back the //Blocks// node, select it and click the //TopDown Decision Rule// button. |
{{interimage:examples:example2_15.png|Top-down decision rule}} | {{interimage:examples:example2_15.png|Top-down decision rule}} | ||
* In the dialog that comes up click the //Class// button and select the //Blocks// class. Click OK. Make sure that the //Merge All// option is selected and click OK again. | * In the dialog that comes up click the //Class// button and select the //Blocks// class. Click OK. Make sure that the //Merge All// option is selected and click OK again. | ||
- | {{interimage:examples:example2_16.png|Decision Rule for Blocks}} -> {{interimage:examples:example2_17.png|Insert Class}} | + | {{interimage:examples:example2_16.png|Decision Rule dialog}} -> {{interimage:examples:example2_17.png|Insert Class}} |
* Save the project and re-execute the interpretation. | * Save the project and re-execute the interpretation. | ||
- | * Once the analysis is ready, collapse the //Blocks// node. Select an object and see its attributes in the //Object Information// widget. You should note that all blocks were merged into a single object. That's what the //Merge All/ feature does. The previous behavior can be accomplished again by selecting //No Merge// in the //TopDown Decision Rule// dialog. | + | * Once the analysis is ready, collapse the //Blocks// node. Select an object and see its attributes in the //Object Information// widget. You should note that all blocks were merged into a single object. That's what the //Merge All// feature does. |
+ | {{interimage:examples:example2_18.png|Blocks merged into a single object}} | ||
+ | * The previous behavior can be achieved again by selecting //No Merge// in the //TopDown Decision Rule// dialog. | ||
+ | * Add a //Roads// node to the semantic net: | ||
+ | {{interimage:examples:example2_19.png|Semantic Net}} | ||
+ | * Save the project and re-execute the interpretation. The result is explained by the default operator associated to the //Roads// node: //Dummy Top-Down//. It produces a hypothesis of //Roads// over the entire scene, so what's not //Blocks// (the gaps in the previous result) will automatically be classified as //Roads//. | ||
+ | {{interimage:examples:example2_20.png|Gaps are classified as Roads}} | ||
+ | * The result can be better viewed if the //Blocks// node is collapsed. |