Hi,
Issue solved - turned out that the layer in the project file was renamed
(by a colleague) and hence processing could not find the feature source.
All works fine now. Silly me!
However, the processing error message was really misleading and had no
indication that it could not find the layer.
Plugin Coordtransform approval by pcav.
The plugin version "[1280] Coordtransform 1.1" is now approved
Link: http://plugins.qgis.org/plugins/Coordtransform/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org
Plugin Kortforsyningen approval by pcav.
The plugin version "[1037] Kortforsyningen 1.4" is now approved
Link: http://plugins.qgis.org/plugins/Kortforsyningen/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.
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
Plugin Frame Pixels approval by pcav.
The plugin version "[1443] Frame Pixels 0.2 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/FramePixels/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osg
Plugin iso4app approval by pcav.
The plugin version "[1409] iso4app 0.4 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/iso4app/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman
+1
Thanks,
On 2018-04-26 07:40, Paolo Cavallini wrote:
Hi all,
Il 26/04/2018 05:08, Nyall Dawson ha scritto:
I'm VERY interested in seeing this resurrected. I'm available to
mentor this task if someone else wants to take ownership of the plugin
and do the port, OR alternatively I'd be happy
Hello Germán
Note that I've already fixed some related problems with
https://github.com/qgis/QGIS/pull/4964
Calling deleteLater should delete the dialog on next events processing.
Do dialog and child widgets signals should be correctly disconnected.
Arnaud
Le 25/04/2018 à 16:55, Germán Carr
Hi devs,
I found some broken SAGA algorithms (just the name of the parameters).
Just one simple question: are the SAGA tests resurrected? I see the test
file is available again:
https://github.com/qgis/QGIS/commit/41a27f700ff7806cfe29490a757959adfd4f324b#diff-c567084a3d3994247ea380ed2549
is
Hi Arnaud,
the videos I included in the first message of this thread were recorded
using QGIS master. So, probably the PR you mentioned (which was merged in
2017) didn't fully fix it, since this specific dialog is still showing up
when closing the project.
Regards,
Germán
2018-04-26 3:58 GMT-
As a long-time R spatial developer and QGIS user I'll be glad to help out -
but time-poor at work for now. "Helping out" may be more like "making
unreasonable suggestions" and "finding annoying bugs".
For example, can we find a more efficient way to transfer data from QGIS to
R? Can the new `sf`
Where do I find the format for the parameters of the processing description
files. I have figured out some of them, but for
QgsProcessingParameterRasterDestination I would like to set it as optional
and to skip it by default. This is the string that I have.
QgsProcessingParameterRasterDestination
Hi all,
Both yesterday and today, the macOS build failed due to missing CMake
INCLUDE specifications.
MacOS puts each framework in a separate directory while Linux merges
everything into /usr/local. Thus, Linux commits will compile when a new
dependency is added as long as some other depende
Hi Tom,
Sorry to hear that. In the past we had macOS continuous integration
tests in place but had to disable them, because the package manager used
there (homebrew) was breaking dependencies unpredictably (I don't think
that's unexpected news for you if you are building on mac though ;) )
There
spam the log and reduce a lot the rendering time... it takes seconds for
few polygons. ç
cheers
Luigi Pirelli
**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stacke
On 27 April 2018 at 03:58, Tom Elwertowski wrote:
> Hi all,
>
> Both yesterday and today, the macOS build failed due to missing CMake
> INCLUDE specifications.
Should be fixed in master now.
Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.os
On 27 April 2018 at 06:27, Luigi Pirelli wrote:
> spam the log and reduce a lot the rendering time... it takes seconds for few
> polygons. ç
True...
Not sure what a good solution is here. Those geos warnings are often
very handy to see and for users to be aware of.
Got any ideas?
Nyall
>
>
On 26 April 2018 at 20:32, matteo wrote:
> Hi devs,
>
> I found some broken SAGA algorithms (just the name of the parameters).
> Just one simple question: are the SAGA tests resurrected? I see the test
> file is available again:
>
> https://github.com/qgis/QGIS/commit/41a27f700ff7806cfe29490a75795
On 27 April 2018 at 01:26, C Hamilton wrote:
> Where do I find the format for the parameters of the processing description
> files. I have figured out some of them, but for
> QgsProcessingParameterRasterDestination I would like to set it as optional
> and to skip it by default. This is the string
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
On 26 April 2018 at 22:10, Barry Rowlingson
wrote:
> As a long-time R spatial developer and QGIS user I'll be glad to help out -
> but time-poor at work for now. "Helping out" may be more like "making
> unreasonable suggestions" and "finding annoying bugs".
Don't undersell yourself... these woul
On 26 April 2018 at 17:14, Andreas Neumann wrote:
> Hi,
>
> Issue solved - turned out that the layer in the project file was renamed (by
> a colleague) and hence processing could not find the feature source. All
> works fine now. Silly me!
>
> However, the processing error message was really misle
22 matches
Mail list logo
