New answers tagged

1

Working Model: I likely have this more complicated than it needs to be, but it's working. To get around the geometry type difference (line segments and points), I interpolated midpoints and merged them together, then used field calculator to calculate the offset_azimuth as desired. Now this model works, take a single boundary layer input and wind direction. ...


3

You can do this by just setting the input field to an already existing one. You can either type it by hand or use a model input: or Here is an alternative, I personally prefer: Use "refactor fields" instead of "field calculator". This tool has some advantages: You can use input-variables in your expression (in field calculator you can ...


1

If you want to use a field of the attribute table for buffering, you can choose buffer by variable distance as the tool you're using, this allows you to write down the field name. Or when using the plain buffer tool as you currently do, you can click data defined override (as you already did in your second screenshot) and then click edit. Enter here the ...


4

Yes, you can use "Point"-Input in your model: It expects a user given point by clicking on the canvas and return x,y [EPSG:xxxx] e.g. -0.12,12.4 [EPSG:4326]. You can turn this into a geometry-point by using regular expressions like make_point( array_get(string_to_array((regexp_substr(to_string('-0.12,12.4 [EPSG:4326]'),'[^\\s]*'))),0), array_get(...


1

Normally you should be able to use it as a variable @Coefficient, (originally used inputname without whitespaces and an @ at first sign) e.g. 99 * @Coefficient + 123, but in my experience this sometimes does not work using the processing tool field calculator in graphical model. However, you can simply use refactor fields instead. It offers pretty much the ...


3

A pretty dirty solution to this is to use the "String concatenation" tool to generate an expression that you feed into the field calculator.


0

I have just encountered this issue myself. My workflow is to run 5 PostgreSQL Execute and Load algorithms, use the rename algorithm to rename each, and then use Package to join them into one Geopackage. I found that though the rename layer algorithm does not seem to output it doesn't matter. I could package the output of the five 'PostgreSQL Execute and Load'...


1

I have created a model you can download here from my github repo. Thats how it looks: Where: r is the input raster NClasses is a numerical input greater 0 (the amount of classes you wish to have) And: you need to set a dependency for "Reclassy by table", because "Raster layer statistics" needs to execute first you need to insert a ...


0

Well, it seems, the output layers need to be .gpkg. On shp, every output layer comes with zero featurees. Problem solved. By defaulting on the modeler the output path with gpkg extension. The main problem was the v.clean (break) function, that return zero features after run, so all the output afterward were empty.


1

Try to execute this code on pyqgis console and look if the algorithm dock appears. It could appear over the mainWindow. from processing.modeler.ModelerDialog import ModelerDialog [dock.setVisible(True) for dock in ModelerDialog().findChildren(QgsDockWidget)]


Top 50 recent answers are included