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
calc_cost_map [2015/09/26 21:02]
admin
calc_cost_map [2021/03/16 14:51] (current)
hermann
Line 7: Line 7:
 ===== Inputs ===== ===== Inputs =====
  
-^ Name ^ Type ^ Description ^ +^ Name  ^ Type  ^ Description ​ 
-Source ​ | [[Map Type|Map]]  | Source feature map. A map of non-null cells representing source features. If null value is not defined, an error will be reported. ​ | +Sources ​ | [[Map Type]] ​ | Source feature map. A map of non-null cells representing source features. If null value is not defined, an error will be reported. ​ | 
-Cost  | [[Map Type|Map]]  | Map expressing the difficulty to cross each cell. Difficulty is proportional to the cell value. An insurmountable cell can be represented by very high value. Null value cells will be passed to the cost map. Friction values must be positive, otherwise an error will be reported. ​ |+Frictions ​ | [[Map Type]] ​ | Map expressing the difficulty to cross each cell. Difficulty is proportional to the cell value. An insurmountable cell can be represented by very high value. Null value cells will be passed to the cost map. Friction values must be positive, otherwise an error will be reported.  | 
 +| Also Calculate Cost Direction Map  | [[Boolean Value Type]] ​ | If true, the cost direction map will also be generated during the cost calculation and placed in the "​Directions"​ output port. Otherwise, that output port will be left empty. Directions are represented using a Moore neighborhood (NONE=0, NW=1, N=2, NE=3, E=4, SE=5, S=6, SW=7, and W=8).  |
  
 ===== Optional Inputs ===== ===== Optional Inputs =====
  
-^ Name ^ Type ^ Description ^ Default Value ^ +^ Name  ^ Type  ^ Description ^ Default Value  
-| Cell Type  | [[Cell Type Type|Cell ​Type]] ​ | Data cell type of the cost map must be compatible to the source feature and friction data cell types, otherwise an error will be reported. ​ | Signed 32 Bit Integer ​ | +| Cell Type  | [[Cell Type Type]] ​ | Data cell type of the cost map must be compatible to the source feature and friction data cell types, otherwise an error will be reported. ​ | Signed 32 Bit Integer ​ | 
-| Null Value  | [[Null Value Type|Null Value]]  | Null value of the cost map. This value cannot be equal to zero because zero value represents source features on the cost map. If it is set to zero, an error will be reported. ​ | Default((Based on the value of the Cell Type input.)) ​ | +| Null Value  | [[Null Value Type]] ​ | Null value of the cost map. This value cannot be equal to zero because zero value represents source features on the cost map. If it is set to zero, an error will be reported. ​ | Default((Based on the value of the Cell Type input.)) ​ | 
-| Diagonals Cost More  | [[Bool Type|Bool]]  | If true, diagonal movements are more expensive than orthogonal movements (horizontal / vertical). In this case, the cost of a diagonal movement is multiplied by 1.414213562. ​ | True  | +| Diagonals Cost More  | [[Boolean Value Type]] ​ | If true, diagonal movements are more expensive than orthogonal movements (horizontal / vertical). In this case, the cost of a diagonal movement is multiplied by 1.414213562. ​ | True  | 
-| Maximum Number Of Passes ​ | [[Non Negative ​Int Type|Non Negative Int]]  | Maximum number of passes that are used to calculate the cost map. The value 0 (zero) indicates that this functor will execute as many steps as needed in order to produce the best cost (optimized) map. Usually two passes are enough to produce optimized cost maps.  | 0  | +| Maximum Number Of Passes ​ | [[Non Negative ​Integer Value Type]] ​ | Maximum number of passes that are used to calculate the cost map. The value 0 (zero) indicates that this functor will execute as many steps as needed in order to produce the best cost (optimized) map. Usually two passes are enough to produce optimized cost maps.  | 0  | 
-Friction Is Relative ​ | [[Bool Type|Bool]]  | If true, the friction values are relative to map resolution and represent friction units per meter. In this case, the friction values are automatically multiplied by the cell resolution (in meters). ​ | False  |+Frictions Are Relative ​ | [[Boolean Value Type]] ​ | If true, the friction values are relative to map resolution and represent friction units per meter. In this case, the friction values are automatically multiplied by the cell resolution (in meters). ​ | False  |
  
 ===== Outputs ===== ===== Outputs =====
  
-^ Name ^ Type ^ Description ^ +^ Name  ^ Type  ^ Description ​ 
-Cost  | [[Map Type|Map]]  | Accumulated cost surface map from each feature source. Output map has the same dimensions of the source feature map. |+Costs  | [[Map Type]] ​ | Accumulated cost surface map from each feature source. Output map has the same dimensions of the source feature map.  | 
 +| Directions ​ | [[Map Type]] ​ | Map showing the directions following the least costly path in the cost map. Directions are represented using Moore neighborhood (NONE=0, NW=1, N=2, NE=3, E=4, SE=5, S=6, SW=7, and W=8).  ​|
  
 ===== Group ===== ===== Group =====