Feature #6049
Use extent tools for extent configuration
| Status: | Closed | Start Date: | 07/16/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Patch supplied: | No |
Description
Some tools like SAGA TIN allow to define the extent of the output raster with the extent of an existing layer or by drawing a rectangle on the canvas, these options should also be available in SEXTANTE configuration to avoid typing the coordinates directly to define the region of interest.
History
Updated by Victor Olaya 10 months ago
- Status changed from New to Feedback
I do not know if I understand what you mean. Extents can be defined from a layer of by drawing on the canvas. Just click on the button on the right hand-side of the extent parameter to access those options.
Updated by Paolo Cavallini 7 months ago
- Status changed from Feedback to Closed
Closing for lack of feedback. Reopen if necessary
Updated by Jean-Roc Morreale 7 months ago
Hi, sorry for the late feedback. What I meant is that it would be great to add a "region" component in the sextante modeler which could be used to pass extent/resolution information to an analysis component without user interaction :
Input Raster A -> Select Vector B's extent -> Kriging
Input Vector B
Updated by Paolo Cavallini 7 months ago
- Status changed from Closed to New
Not sure I've got it, but I reopen it anyway.
Updated by Jean-Roc Morreale 7 months ago
I want to be able to create a analysis model where the user just has to define an input of points (A) and an input of a polygon (B) and click OK to get a interpolated raster based on the value of A but on the extent of B, to avoid the calculation of unnecessary data.
You can see it like an automated g.region where I define in the model that it must takes its extent from B and use a defined resolution, this way the user just has to think about his input layers.
Updated by Jean-Roc Morreale 16 days ago
- Status changed from New to Closed
I'm closing this ticket, the modeler has an extent entry (I've not figured how it works yet but it's there)