pyqgis processing, grass: --overwrite does not workQGIS 2.10.1 GRASS Processing algorithms not workingQGIS Processing GRASS7 output is not created in custom application on Mac | LinuxRun time error in QGISError using grass v.clean: “ 'utf-8' codec can't decode byte… ”pyqgis processing: running multiple tools in a single algorithmOutput layer from PyQGIS 3 processing script is emptyDEM File “not found” Error when running r.watershed with Processing Toolbox in QGIS 3.4.2 with GRASSError whilsted using QGIS 3.4.4 r.series batch processingPyQGIS Processing: “memory: not found”PyQGIS processing: Overwrite not possible
Why didn't Boeing produce its own regional jet?
Is it logically or scientifically possible to artificially send energy to the body?
Unlock My Phone! February 2018
Is this a hacking script in function.php?
Different meanings of こわい
Am I breaking OOP practice with this architecture?
Detention in 1997
Arrow those variables!
Avoiding the "not like other girls" trope?
Running Low on Limestone
Bullying boss launched a smear campaign and made me unemployable
Ambiguity in the definition of entropy
How do I deal with an unproductive colleague in a small company?
Why is it a bad idea to hire a hitman to eliminate most corrupt politicians?
Why would the Red Woman birth a shadow if she worshipped the Lord of the Light?
Is there an expression that means doing something right before you will need it rather than doing it in case you might need it?
Do UK voters know if their MP will be the Speaker of the House?
What is the most common color to indicate the input-field is disabled?
Why can't we play rap on piano?
What mechanic is there to disable a threat instead of killing it?
Why do bosons tend to occupy the same state?
CAST throwing error when run in stored procedure but not when run as raw query
How seriously should I take size and weight limits of hand luggage?
Can compressed videos be decoded back to their uncompresed original format?
pyqgis processing, grass: --overwrite does not work
QGIS 2.10.1 GRASS Processing algorithms not workingQGIS Processing GRASS7 output is not created in custom application on Mac | LinuxRun time error in QGISError using grass v.clean: “ 'utf-8' codec can't decode byte… ”pyqgis processing: running multiple tools in a single algorithmOutput layer from PyQGIS 3 processing script is emptyDEM File “not found” Error when running r.watershed with Processing Toolbox in QGIS 3.4.2 with GRASSError whilsted using QGIS 3.4.4 r.series batch processingPyQGIS Processing: “memory: not found”PyQGIS processing: Overwrite not possible
I have a QGIS plugin that tries to call the v.clean
algorithm multiple times in a row and use the same output file each time the algorithm runs through. But even though I set the --overwrite
parameter to true (as found in the grass manual), the output can't be overwritten and instead I get the error
ERROR 1: A file system object called 'C:Users...Desktopoutput.gpkg' already exists.
in the QGIS log. I can still run the plugin, but only the snap
algorithm of the following code will be applied to my line layer:
output = self.dlg.directory.text()
params_snap =
'input' : input_2,
'type' : 1,
'tool' : 1,
'threshold' : 0.000095,
'output': output,
'error' : 'memory:',
'GRASS_OUTPUT_TYPE_PARAMETER': 2
processing.run('grass7:v.clean', params_snap)
params_break =
'input': input_2,
'type': 1,
'tool': 0,
'threshold': 0.1,
'-c': True,
'output': output,
'error': 'memory:',
'--overwrite': True,
'GRASS_OUTPUT_TYPE_PARAMETER': 2
processing.runAndLoadResults('grass7:v.clean', params_break)
The path and name of the ouput are from a QFileDialog. If the information is needed: The input file is a temporary file.
If I set a different output file for each part of the processing the code runs fine and without errors, but since I will use more than only two algorithms creating and deleting files over and over again will just slow the plugin down.
I use the current QGIS LTR 3.4.
pyqgis qgis-plugins grass qgis-processing
add a comment |
I have a QGIS plugin that tries to call the v.clean
algorithm multiple times in a row and use the same output file each time the algorithm runs through. But even though I set the --overwrite
parameter to true (as found in the grass manual), the output can't be overwritten and instead I get the error
ERROR 1: A file system object called 'C:Users...Desktopoutput.gpkg' already exists.
in the QGIS log. I can still run the plugin, but only the snap
algorithm of the following code will be applied to my line layer:
output = self.dlg.directory.text()
params_snap =
'input' : input_2,
'type' : 1,
'tool' : 1,
'threshold' : 0.000095,
'output': output,
'error' : 'memory:',
'GRASS_OUTPUT_TYPE_PARAMETER': 2
processing.run('grass7:v.clean', params_snap)
params_break =
'input': input_2,
'type': 1,
'tool': 0,
'threshold': 0.1,
'-c': True,
'output': output,
'error': 'memory:',
'--overwrite': True,
'GRASS_OUTPUT_TYPE_PARAMETER': 2
processing.runAndLoadResults('grass7:v.clean', params_break)
The path and name of the ouput are from a QFileDialog. If the information is needed: The input file is a temporary file.
If I set a different output file for each part of the processing the code runs fine and without errors, but since I will use more than only two algorithms creating and deleting files over and over again will just slow the plugin down.
I use the current QGIS LTR 3.4.
pyqgis qgis-plugins grass qgis-processing
the grass manual can diverge from the way QGis uses the tool. I cannot test right now, but i suspect that QGis uses another keyword for--overwrite
. I suggest running this tool once using the QGis interface and then looking at the processing history to find out exactly how QGis runs this tool
– xlDias
Mar 25 at 14:48
The GUI version of the GRASS 7 tool in QGIS 2.18 doesn't have an option to specify overwriting. Does it in QGIS 3.4?
– Paulo Raposo
Mar 31 at 7:01
@PauloRaposo it does not, but you can choose consecutive processes with the same output file. In the log grass uses--ouverwrite
and-o
at the same time, but neither of them, nor both of them work.
– gHupf
yesterday
add a comment |
I have a QGIS plugin that tries to call the v.clean
algorithm multiple times in a row and use the same output file each time the algorithm runs through. But even though I set the --overwrite
parameter to true (as found in the grass manual), the output can't be overwritten and instead I get the error
ERROR 1: A file system object called 'C:Users...Desktopoutput.gpkg' already exists.
in the QGIS log. I can still run the plugin, but only the snap
algorithm of the following code will be applied to my line layer:
output = self.dlg.directory.text()
params_snap =
'input' : input_2,
'type' : 1,
'tool' : 1,
'threshold' : 0.000095,
'output': output,
'error' : 'memory:',
'GRASS_OUTPUT_TYPE_PARAMETER': 2
processing.run('grass7:v.clean', params_snap)
params_break =
'input': input_2,
'type': 1,
'tool': 0,
'threshold': 0.1,
'-c': True,
'output': output,
'error': 'memory:',
'--overwrite': True,
'GRASS_OUTPUT_TYPE_PARAMETER': 2
processing.runAndLoadResults('grass7:v.clean', params_break)
The path and name of the ouput are from a QFileDialog. If the information is needed: The input file is a temporary file.
If I set a different output file for each part of the processing the code runs fine and without errors, but since I will use more than only two algorithms creating and deleting files over and over again will just slow the plugin down.
I use the current QGIS LTR 3.4.
pyqgis qgis-plugins grass qgis-processing
I have a QGIS plugin that tries to call the v.clean
algorithm multiple times in a row and use the same output file each time the algorithm runs through. But even though I set the --overwrite
parameter to true (as found in the grass manual), the output can't be overwritten and instead I get the error
ERROR 1: A file system object called 'C:Users...Desktopoutput.gpkg' already exists.
in the QGIS log. I can still run the plugin, but only the snap
algorithm of the following code will be applied to my line layer:
output = self.dlg.directory.text()
params_snap =
'input' : input_2,
'type' : 1,
'tool' : 1,
'threshold' : 0.000095,
'output': output,
'error' : 'memory:',
'GRASS_OUTPUT_TYPE_PARAMETER': 2
processing.run('grass7:v.clean', params_snap)
params_break =
'input': input_2,
'type': 1,
'tool': 0,
'threshold': 0.1,
'-c': True,
'output': output,
'error': 'memory:',
'--overwrite': True,
'GRASS_OUTPUT_TYPE_PARAMETER': 2
processing.runAndLoadResults('grass7:v.clean', params_break)
The path and name of the ouput are from a QFileDialog. If the information is needed: The input file is a temporary file.
If I set a different output file for each part of the processing the code runs fine and without errors, but since I will use more than only two algorithms creating and deleting files over and over again will just slow the plugin down.
I use the current QGIS LTR 3.4.
pyqgis qgis-plugins grass qgis-processing
pyqgis qgis-plugins grass qgis-processing
edited Mar 25 at 9:33
gHupf
asked Mar 23 at 13:18
gHupfgHupf
265115
265115
the grass manual can diverge from the way QGis uses the tool. I cannot test right now, but i suspect that QGis uses another keyword for--overwrite
. I suggest running this tool once using the QGis interface and then looking at the processing history to find out exactly how QGis runs this tool
– xlDias
Mar 25 at 14:48
The GUI version of the GRASS 7 tool in QGIS 2.18 doesn't have an option to specify overwriting. Does it in QGIS 3.4?
– Paulo Raposo
Mar 31 at 7:01
@PauloRaposo it does not, but you can choose consecutive processes with the same output file. In the log grass uses--ouverwrite
and-o
at the same time, but neither of them, nor both of them work.
– gHupf
yesterday
add a comment |
the grass manual can diverge from the way QGis uses the tool. I cannot test right now, but i suspect that QGis uses another keyword for--overwrite
. I suggest running this tool once using the QGis interface and then looking at the processing history to find out exactly how QGis runs this tool
– xlDias
Mar 25 at 14:48
The GUI version of the GRASS 7 tool in QGIS 2.18 doesn't have an option to specify overwriting. Does it in QGIS 3.4?
– Paulo Raposo
Mar 31 at 7:01
@PauloRaposo it does not, but you can choose consecutive processes with the same output file. In the log grass uses--ouverwrite
and-o
at the same time, but neither of them, nor both of them work.
– gHupf
yesterday
the grass manual can diverge from the way QGis uses the tool. I cannot test right now, but i suspect that QGis uses another keyword for
--overwrite
. I suggest running this tool once using the QGis interface and then looking at the processing history to find out exactly how QGis runs this tool– xlDias
Mar 25 at 14:48
the grass manual can diverge from the way QGis uses the tool. I cannot test right now, but i suspect that QGis uses another keyword for
--overwrite
. I suggest running this tool once using the QGis interface and then looking at the processing history to find out exactly how QGis runs this tool– xlDias
Mar 25 at 14:48
The GUI version of the GRASS 7 tool in QGIS 2.18 doesn't have an option to specify overwriting. Does it in QGIS 3.4?
– Paulo Raposo
Mar 31 at 7:01
The GUI version of the GRASS 7 tool in QGIS 2.18 doesn't have an option to specify overwriting. Does it in QGIS 3.4?
– Paulo Raposo
Mar 31 at 7:01
@PauloRaposo it does not, but you can choose consecutive processes with the same output file. In the log grass uses
--ouverwrite
and -o
at the same time, but neither of them, nor both of them work.– gHupf
yesterday
@PauloRaposo it does not, but you can choose consecutive processes with the same output file. In the log grass uses
--ouverwrite
and -o
at the same time, but neither of them, nor both of them work.– gHupf
yesterday
add a comment |
1 Answer
1
active
oldest
votes
but since I will use more than only two algorithms creating and
deleting files over and over again will just slow the plugin down.
Anyway files are created and deleted whether you want it or not (see your ERROR 1 message), so if --overwrite
parameter do not work - as workaround you can manually check if file exist and delete it before starting grass7:v.clean
.
Here is the code:
import os
if os.path.exists(output):
os.remove(output)
Another workaround is to use subprocess
module to call cmd variant of the command. Here is example:
import subprocess
clipper = r'D:sourcents_index_250k.shp'
tiles = '117D 117A 116O 116P'.split()
for tile in tiles:
warp = '''gdalwarp -cutline clipper -cwhere "'TILE_NAME' = 'tile'" infile outfile'''.format(clipper=clipper,
tile=tile,
infile=infile,
outfile=tile + infile
)
subprocess.call(warp)
EDIT 1:
If you execute this code: print(processing.algorithmHelp('grass7:v.clean'))
with QGIS Python console, you may notice that --overwrite
is absent in parameters description.
But if you run the same tool using QGIS interface and check for Log
tab you may notice that --overwrite
parameter is used somehow. That is because you may run every grass tool using cmd/shell (avoiding pyQgis API).
Here is v.clean log results: picture
EDIT 2:
Also you may try to insert string --overwrite
in these paramaters:
GRASS_VECTOR_DSCO: v.out.ogr output data source options (dsco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
GRASS_VECTOR_LCO: v.out.ogr output layer options (lco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
I do not really know how the second solution works. Could you explain the benefits of it compared to the first solution? If I try the first solution I get aWinError 32
, the process cannot access the file because it is used by another process. I do not useRunAndLoadResults
, so QGIS does not load the output of the first time v.clean runs through. Any idea how to solve this?
– gHupf
yesterday
@gHupf See update
– Mr. Che
17 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "79"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f316449%2fpyqgis-processing-grass-overwrite-does-not-work%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
but since I will use more than only two algorithms creating and
deleting files over and over again will just slow the plugin down.
Anyway files are created and deleted whether you want it or not (see your ERROR 1 message), so if --overwrite
parameter do not work - as workaround you can manually check if file exist and delete it before starting grass7:v.clean
.
Here is the code:
import os
if os.path.exists(output):
os.remove(output)
Another workaround is to use subprocess
module to call cmd variant of the command. Here is example:
import subprocess
clipper = r'D:sourcents_index_250k.shp'
tiles = '117D 117A 116O 116P'.split()
for tile in tiles:
warp = '''gdalwarp -cutline clipper -cwhere "'TILE_NAME' = 'tile'" infile outfile'''.format(clipper=clipper,
tile=tile,
infile=infile,
outfile=tile + infile
)
subprocess.call(warp)
EDIT 1:
If you execute this code: print(processing.algorithmHelp('grass7:v.clean'))
with QGIS Python console, you may notice that --overwrite
is absent in parameters description.
But if you run the same tool using QGIS interface and check for Log
tab you may notice that --overwrite
parameter is used somehow. That is because you may run every grass tool using cmd/shell (avoiding pyQgis API).
Here is v.clean log results: picture
EDIT 2:
Also you may try to insert string --overwrite
in these paramaters:
GRASS_VECTOR_DSCO: v.out.ogr output data source options (dsco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
GRASS_VECTOR_LCO: v.out.ogr output layer options (lco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
I do not really know how the second solution works. Could you explain the benefits of it compared to the first solution? If I try the first solution I get aWinError 32
, the process cannot access the file because it is used by another process. I do not useRunAndLoadResults
, so QGIS does not load the output of the first time v.clean runs through. Any idea how to solve this?
– gHupf
yesterday
@gHupf See update
– Mr. Che
17 hours ago
add a comment |
but since I will use more than only two algorithms creating and
deleting files over and over again will just slow the plugin down.
Anyway files are created and deleted whether you want it or not (see your ERROR 1 message), so if --overwrite
parameter do not work - as workaround you can manually check if file exist and delete it before starting grass7:v.clean
.
Here is the code:
import os
if os.path.exists(output):
os.remove(output)
Another workaround is to use subprocess
module to call cmd variant of the command. Here is example:
import subprocess
clipper = r'D:sourcents_index_250k.shp'
tiles = '117D 117A 116O 116P'.split()
for tile in tiles:
warp = '''gdalwarp -cutline clipper -cwhere "'TILE_NAME' = 'tile'" infile outfile'''.format(clipper=clipper,
tile=tile,
infile=infile,
outfile=tile + infile
)
subprocess.call(warp)
EDIT 1:
If you execute this code: print(processing.algorithmHelp('grass7:v.clean'))
with QGIS Python console, you may notice that --overwrite
is absent in parameters description.
But if you run the same tool using QGIS interface and check for Log
tab you may notice that --overwrite
parameter is used somehow. That is because you may run every grass tool using cmd/shell (avoiding pyQgis API).
Here is v.clean log results: picture
EDIT 2:
Also you may try to insert string --overwrite
in these paramaters:
GRASS_VECTOR_DSCO: v.out.ogr output data source options (dsco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
GRASS_VECTOR_LCO: v.out.ogr output layer options (lco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
I do not really know how the second solution works. Could you explain the benefits of it compared to the first solution? If I try the first solution I get aWinError 32
, the process cannot access the file because it is used by another process. I do not useRunAndLoadResults
, so QGIS does not load the output of the first time v.clean runs through. Any idea how to solve this?
– gHupf
yesterday
@gHupf See update
– Mr. Che
17 hours ago
add a comment |
but since I will use more than only two algorithms creating and
deleting files over and over again will just slow the plugin down.
Anyway files are created and deleted whether you want it or not (see your ERROR 1 message), so if --overwrite
parameter do not work - as workaround you can manually check if file exist and delete it before starting grass7:v.clean
.
Here is the code:
import os
if os.path.exists(output):
os.remove(output)
Another workaround is to use subprocess
module to call cmd variant of the command. Here is example:
import subprocess
clipper = r'D:sourcents_index_250k.shp'
tiles = '117D 117A 116O 116P'.split()
for tile in tiles:
warp = '''gdalwarp -cutline clipper -cwhere "'TILE_NAME' = 'tile'" infile outfile'''.format(clipper=clipper,
tile=tile,
infile=infile,
outfile=tile + infile
)
subprocess.call(warp)
EDIT 1:
If you execute this code: print(processing.algorithmHelp('grass7:v.clean'))
with QGIS Python console, you may notice that --overwrite
is absent in parameters description.
But if you run the same tool using QGIS interface and check for Log
tab you may notice that --overwrite
parameter is used somehow. That is because you may run every grass tool using cmd/shell (avoiding pyQgis API).
Here is v.clean log results: picture
EDIT 2:
Also you may try to insert string --overwrite
in these paramaters:
GRASS_VECTOR_DSCO: v.out.ogr output data source options (dsco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
GRASS_VECTOR_LCO: v.out.ogr output layer options (lco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
but since I will use more than only two algorithms creating and
deleting files over and over again will just slow the plugin down.
Anyway files are created and deleted whether you want it or not (see your ERROR 1 message), so if --overwrite
parameter do not work - as workaround you can manually check if file exist and delete it before starting grass7:v.clean
.
Here is the code:
import os
if os.path.exists(output):
os.remove(output)
Another workaround is to use subprocess
module to call cmd variant of the command. Here is example:
import subprocess
clipper = r'D:sourcents_index_250k.shp'
tiles = '117D 117A 116O 116P'.split()
for tile in tiles:
warp = '''gdalwarp -cutline clipper -cwhere "'TILE_NAME' = 'tile'" infile outfile'''.format(clipper=clipper,
tile=tile,
infile=infile,
outfile=tile + infile
)
subprocess.call(warp)
EDIT 1:
If you execute this code: print(processing.algorithmHelp('grass7:v.clean'))
with QGIS Python console, you may notice that --overwrite
is absent in parameters description.
But if you run the same tool using QGIS interface and check for Log
tab you may notice that --overwrite
parameter is used somehow. That is because you may run every grass tool using cmd/shell (avoiding pyQgis API).
Here is v.clean log results: picture
EDIT 2:
Also you may try to insert string --overwrite
in these paramaters:
GRASS_VECTOR_DSCO: v.out.ogr output data source options (dsco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
GRASS_VECTOR_LCO: v.out.ogr output layer options (lco)
Parameter type: QgsProcessingParameterString
Accepted data types:
- str
- QgsProperty
edited 16 hours ago
answered 2 days ago
Mr. CheMr. Che
1,569528
1,569528
I do not really know how the second solution works. Could you explain the benefits of it compared to the first solution? If I try the first solution I get aWinError 32
, the process cannot access the file because it is used by another process. I do not useRunAndLoadResults
, so QGIS does not load the output of the first time v.clean runs through. Any idea how to solve this?
– gHupf
yesterday
@gHupf See update
– Mr. Che
17 hours ago
add a comment |
I do not really know how the second solution works. Could you explain the benefits of it compared to the first solution? If I try the first solution I get aWinError 32
, the process cannot access the file because it is used by another process. I do not useRunAndLoadResults
, so QGIS does not load the output of the first time v.clean runs through. Any idea how to solve this?
– gHupf
yesterday
@gHupf See update
– Mr. Che
17 hours ago
I do not really know how the second solution works. Could you explain the benefits of it compared to the first solution? If I try the first solution I get a
WinError 32
, the process cannot access the file because it is used by another process. I do not use RunAndLoadResults
, so QGIS does not load the output of the first time v.clean runs through. Any idea how to solve this?– gHupf
yesterday
I do not really know how the second solution works. Could you explain the benefits of it compared to the first solution? If I try the first solution I get a
WinError 32
, the process cannot access the file because it is used by another process. I do not use RunAndLoadResults
, so QGIS does not load the output of the first time v.clean runs through. Any idea how to solve this?– gHupf
yesterday
@gHupf See update
– Mr. Che
17 hours ago
@gHupf See update
– Mr. Che
17 hours ago
add a comment |
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f316449%2fpyqgis-processing-grass-overwrite-does-not-work%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
the grass manual can diverge from the way QGis uses the tool. I cannot test right now, but i suspect that QGis uses another keyword for
--overwrite
. I suggest running this tool once using the QGis interface and then looking at the processing history to find out exactly how QGis runs this tool– xlDias
Mar 25 at 14:48
The GUI version of the GRASS 7 tool in QGIS 2.18 doesn't have an option to specify overwriting. Does it in QGIS 3.4?
– Paulo Raposo
Mar 31 at 7:01
@PauloRaposo it does not, but you can choose consecutive processes with the same output file. In the log grass uses
--ouverwrite
and-o
at the same time, but neither of them, nor both of them work.– gHupf
yesterday