New answers tagged

1

If you have a partitioned drive you can make your life easy by working from the "D"-drive or whatever, as paths originating from there don´t contain your username.


3

Ensure the identifier field in both files are the same type. That is make sure they're both text or both numeric.


0

I remember that I tried to change the directory for r-scipts in QGIS. I changed it into a location on an external hard drive. I ran QGIS without the hard drive linked to my PC and QGIS produced the same error like yours, Zach. After connecting the hard drive again, QGIS produced no error while starting and I could change the directory to the old path again: ...


1

If run grass7.0.3 standalone nviz module works, and in grass7.0.3/bin there isn't nviz and/or nviz7 binary file!? Seems that nviz7 command is moved in the ./qgis/python/plugins/processing/algs/grass7/nviz7.py.


0

Hmm @GermánCarrillo's solution also worked for me. If you want to use ras1 and ras2 as input parameters then you can try the following: import processing ras1 = "H:/pyQGIS/DATA_U6/mdt_483.tif" ras2 = "H:/pyQGIS/DATA_U6/mdt_508.tif" merj = processing.runalg("gdalogr:merge", ras1 + ";" + ras2, False, False, 4,"H:/pyQGIS/DATA_U6/mdt_mosaico.tif")


2

The algorithm expects (in the first argument) the input raster paths using a semicolon as separator. Don't add any blank space after the semicolon. Your script could be just 2 lines long now: import processing merj = processing.runalg('gdalogr:merge','H:/pyQGIS/DATA_U6/mdt_483.tif;H:/pyQGIS/DATA_U6/mdt_508.tif', False, False, ...


2

Use the corrected script Bug report #14608: Processing: Kriging rscripts/Kriging.rsx Automap problem and correction, accepted in the master (Kriging.rsx) It is not a problem of QGIS, it is a problem with you R packages installation. 1) Processing use the Python subprocess module to execute directly the R commands 2) it use an intermediate file named ...


2

Memory upgrades are always good, especially in a 64 bit system. 4GB on a 64 bit system leaves a lot to be desired. I would also clear out my temp folder, and any unnecessary files frequently. (I am really old school about this, I do this at least twice a week.) Your video processor will have a great deal (almost everything) to do with rendering speed, and ...


3

Loading in the first place depends a lot on the HDD/SSD and not the RAM. Drawing depends a lot on your CPU or Graphic-Card, which is done after loading or manipulating something in the map (like zoom or pan). Qgis can be set to use multiple cores to draw features. This you can find in the Options. Maybe its faster then. Then you can just open the ...


0

When running scripts, a good idea is to unload all the modules that were imported and remove any dependencies. This seemed to be what was causing your scripts to not work the way they should. Probably the easiest method to achieve the above is to simply restart QGIS.


1

This was a bug in version 2.14. It will be fixed when 2.14.2 is released.


1

When you execute an algorithm in the Processing Toolbox, the result is recorded in the file /.../.qgis2/processing/processing.log With the command Nviz7, the result in the processing.log file is processing.runalg("grass70:nviz7","/path_to/dem.tif",None,None,"202086.577,205625.414407,88411.048,90534.3504441",0) The Python processing module of QGIS uses ...


0

It requires an object that implements the Progress interface. Either do your own (implement setInfo and whatever else is required) or use a shipped one like processing.gui.MessageBarProgress.MessageBarProgress. from processing.gui.MessageBarProgress import MessageBarProgress mp = MessageBarProgress() GdalUtils.runGdal(command, mp)



Top 50 recent answers are included