Hi Stefan,
We have recently updated the user manual to reflect this new
great feature.
Can you test the example that is given there (also includes
two processing algorithms)?
https://docs.qgis.org/testing/en/docs/user_manual/processing/scripts.html#the-alg-decorator
Håvard
On 12.04.2019 08:28,
The tabs reappear when new log messages come in.
No need to restart QGIS.
Håvard
On 11. feb. 2019 11:55, Groene Bij wrote:
Hi,
Using qgis 3.4.4 and opening the log messages panel, I accidentally
deleted one of the tabs, but I don’t know which one.
Do they automatically re-appear after resta
getting lost when
dealing as desired value. Although the OR part needs more Discussion. For
consistency that has to be nodata as well. What about nodata OR 0? In my
opinion nodata always needs a discrete treatment to avoid generating fallcious
information.
Cheers
Stefan
Havard Tveite hat
nodata + 1 = nodata
nodata * 1 = nodata
nodata AND 1 = nodata
nodata OR 1 = 1
Håvard
On 11. feb. 2019 03:11, Nyall Dawson wrote:
Hey all,
I'm seeking some feedback on whether our current handling of nodata
pixels in the raster calculator is correct, or (my suspicion) annoying
and limiting.
Cu
Hi Beatriz,
Documentation for QGIS 3 can currently be found at:
https://docs.qgis.org/testing/en/docs/
Documentation for QGIS 3 is far from complete, so you may
find that there are parts that still reflect QGIS 2 behaviour.
Håvard
On 29. jan. 2019 12:10, Beatriz Woods wrote:
Hi,
I just down
ulti-geometries, I
agree it sounds like a valid tool to have, but I am a bit concerned of
the clutter to benefit ratio. Does anyone have an idea how often this
would be useful in reality?
Thanks
Matthias
On 1/8/19 9:02 AM, Havard Tveite wrote:
I agree that disabling the vertex tool for point la
I agree that disabling the vertex tool for point layers is a good
idea. It will improve consistency and avoid confusion.
A separate tool for moving a part of a multi-geometry would be
useful.
Håvard
On 08. jan. 2019 07:53, Bernhard Ströbl wrote:
Hi Saber,
Delete a single point (part) in a mul
Assuming that the point layer has an attribute that identifies
the district, I suggest that you first create Voronoi polygons
for the point layer, and then dissolve the Voronoi polygons based
on the attribute that identifies the district.
Both these functions can be found in the Processing toolbox
You probably need to use an "Action" (of type Python) and some
Python code. You can define actions in Layers properties-> Actions.
(https://docs.qgis.org/2.18/en/docs/training_manual/create_vector_data/actions.html)
Håvard
On 04. okt. 2018 12:42, Henrique Duarte Vieira wrote:
Hello to all,
I
Hi Reginald,
Python (Processing) scripts in QGIS 3 are much more complicated
than in QGIS 2. I recently learned that you will get an example
script by choosing "Create new script from template..." under
the "Scripts" icon that is located at the top of the Processing
Toolbox.
Use that script as a
On Ubuntu
~/.local/share/QGIS/QGIS3/profiles/default
Håvard
On 09. juli 2018 08:31, Patrick Dunford wrote:
Good day all
Where are the config settigns for Qgis stored on Linux editions
On my existing desktop running 3.0 there are two different locations used:
* ~/.config/QGIS
* ~/.qgisX
Th
Hi,
I would like to use a processing algorithm in a plugin,
and run it as a QgsTask to avoid user interface "freeze".
I have tested with QGIS 3 (3.0.2) using the "native.buffer"
algorithm and a line vector layer:
context = QgsProcessingContext()
alg=QgsApplication.processingRegistry().algorit
QgsApplication.processingRegistry().algorithms() does not
list grass7:v.to.rast.value (but grass7:v.to.rast is
there).
In QGIS 3, the following seems to work:
myres = processing.run("qgis:union", {'INPUT': "my_input", 'OVERLAY':
"my_overlay", 'OUTPUT': "my_result"}, feedback=None)['OUTPUT']
p
You could use the GRASS function r.null (available in
Processing).
Håvard
On 30. des. 2016 11:35, Raymond Nijssen wrote:
I'd like to reclass a raster that contains just cells with values nodata
and 1. (I created it by rasterizing a polygon layer.)
Now I want to change all nodata values to 0, b
MMQGIS does not seem to accept the same layer as source and
destination.
The NNJoin plugin will calculate the distance to the nearest
neighbour and will identify it through its attribute values,
but will not help you with the plotting.
Håvard
On 29. nov. 2016 20:10, Ricardo Thompson wrote:
Good
In recent versions you can change this in
Project properties, General, Coordinate display.
Håvard
On 17. okt. 2016 12:43, McDonaldR wrote:
Hello list
I have user with a project with a number of layers (both shapefile and
PostGIS). Project CRS is EPSG:27700 and layer CRS is EPSG:27700 (Britis
There is now a QGIS plugin that you can test
http://plugins.qgis.org/plugins/SDEllipse/
Håvard
On 19. mai 2016 15:02, Josefine Petrenz wrote:
Hi all,
is there a tool or a plugin in qgis, that is similar to the arcgis-tool
"Directional Distribution (Standard Deviational Ellipse)?
Many Thanks in
Whenever I change the visibility of a layer in the map legend
(show or hide layer), "On the fly" CRS transformation (OTF)
gets enabled. This is kind of irritating.
I have a few layers in the map legend, and they have different
CRSs.
Same behaviour for QGIS 2.8.9 and 2.14.2 on Ubuntu 14.04.
Is
Since QGIS Processing Dissolve (mentioned in the issue)
accepts joined fields for the Unique ID field, the result
should contain that field.
So it seems most logical to include joined fields in the
result.
Håvard
On 11. april 2016 11:46, Alexander Bruy wrote:
Hi all,
and sorry for cross-postin
I was also confused by this.
Having Map units as the default for "Display coordinates" seems
logical to me, so I suggest that the default is changed.
Could this be considered a bug (change of behaviour) and fixed
for 2.14.x?
Håvard
On 11. mars 2016 12:37, Claas Leiner wrote:
Hi,
There ist a
If you are going to use GRASS r.to.vect (for instance through QGIS
Processing), you will need a binary skeleton image.
You could get one by using the raster calculator to extract
your single colour as a binary image, and then GRASS r.thin
(available in QGIS Processing) to get the skeleton.
Håvard
, I get problems
with some line-polygon intersects and polygon-polygon
unions.
Håvard
On 8/29/2012 10:39 AM, Havard Tveite wrote:
After moving to QGIS version 1.8.0 (from 1.7.4), I am having
trouble with overlay (intersection, union).
The intersect function (Vector-> Geoprocessing Tools->
After moving to QGIS version 1.8.0 (from 1.7.4), I am having
trouble with overlay (intersection, union).
The intersect function (Vector-> Geoprocessing Tools-> Intersect)
gives the following warning:
* Warnings:
* Feature geometry error: One or more output features ignored due to invalid
geometr
23 matches
Mail list logo
