On 26 April 2018 at 17:31, Benjamin Ducke wrote:
>
>
> In the case of GRASS, this is a more complicated matter.
> GRASS uses a fully topological vector format and all
> input data will go through rigorous topology testing
> by default. The more intermediate steps, the higher
> the risk that data w
Hi,
On 26/04/18 08:53, Nyall Dawson wrote:
> On 26 April 2018 at 16:42, matteo wrote:
>> Hi Nyall,
>>
>>> No - neither SAGA nor GRASS have any concept of QGIS memory layers.
>>> You need to give them a disk-based file path to save their outputs to.
That's not quite accurate. Even if they did hav
On 26 April 2018 at 16:42, matteo wrote:
> Hi Nyall,
>
>> No - neither SAGA nor GRASS have any concept of QGIS memory layers.
>> You need to give them a disk-based file path to save their outputs to.
>
> ok, clear now why this was not working
>
>
>> If you use a memory layer as an input to these a
Hi Nyall,
> No - neither SAGA nor GRASS have any concept of QGIS memory layers.
> You need to give them a disk-based file path to save their outputs to.
ok, clear now why this was not working
> If you use a memory layer as an input to these algs it will also have
> to save it out to a disk base
On 23 April 2018 at 19:59, matteo wrote:
> Hi devs,
>
> sorry if I missed something on this topic, but it seems that it is not
> possible using memory layer when running algorithms from the console.
>
> A simple example should explain everything:
>
> # QGIS
> parameters = {
> 'INPUT' : 'big',
Hi devs,
sorry if I missed something on this topic, but it seems that it is not
possible using memory layer when running algorithms from the console.
A simple example should explain everything:
# QGIS
parameters = {
'INPUT' : 'big',
'OVERLAY': 'small',
'OUTPUT':'memory:'
}
result =
