On 22 November 2017 at 21:21, Andreas Neumann wrote:
> Hi,
>
> Is it possible to query the value of a QGIS variable in Python code? E.g.
> I'd like to find out in my code the full storage path to the folder of my
> current QGIS project, which would be available in the
On 23 November 2017 at 22:35, Andreas Neumann wrote:
> BTW: refactor fields isn't such a bad name in my opinion. Perhaps we could
> introduce aliases for algorithms - so that they could be found more easily?
Algorithms have support for "tags", which I think covers the alias
Plugin Processing Workflows approval by zimbogisgeek.
The plugin version "[638] Processing Workflows 1.2.2" is now approved
Link: http://plugins.qgis.org/plugins/processing_workflow/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List
Older versions can read enough of the project files to be functional,
however. At some point someone will need to use an older version to
resolve a bug in a newer version.
On 24/11/17 17:14, Nyall Dawson wrote:
On 24 November 2017 at 14:10, Patrick Dunford wrote:
On 24 November 2017 at 14:10, Patrick Dunford wrote:
> As of the moment I'm finding that 2.18 has difficulty correctly detecting
> the CRS from a project file saved from the latest master. Generally
> EPSG:3857 is detected as EPSG:4326
>
> Given the master is still a
As of the moment I'm finding that 2.18 has difficulty correctly
detecting the CRS from a project file saved from the latest master.
Generally EPSG:3857 is detected as EPSG:4326
Given the master is still a development version is this considered a bug
in 2.18 or is there still a process of
Is it normal for an r.walk over an area of 10,500 acres to use up 12GB of HD
space and want more? That's using up every bit of space I have left, so it's
crashing out. I tried setting the maximum cost to 10 and I think 1 also, but
the algorithm keeps running for a long time making these really
On 23-11-17 16:46, Arnaud Morvan wrote:
> @Mathias :
>
> Yes after taking a look, WMS dimensions is exactly the idea I have in mind.
Mmm,
I think Dimensions is a different case, as Dimensions are tied to WMS-T
[0] and the query parameter is defined as
=...,...
=...
etc
OR elevation:
=
Happy Thanksgiving Everyone!
Who's very familiar with GRASS r.walk? I'm finding some tutorials and man
pages with examples but having trouble applying what I've found. I'm trying
to create mobility models for use with lost person analytics.
Does is matter what format the input layers are
@Patrick :
Yes, I know that it is possible to use FILTER in request, but I'm not
sure all layers will have the same field name for "floor".
So I would prefer to define a filter in each layer definition in the
project file using a common variable name.
And I would like to have the same
You could do that using the filter parameter with something like that:
FILTER=layer_name:"floor" = 3
On Thu, Nov 23, 2017 at 2:38 PM, Matthias Kuhn wrote:
> Like WMS dimension?
>
> http://mapserver.org/ogc/wms_dimension.html
>
> Matthias
>
>
> On 11/23/17 2:11 PM, Arnaud
Like WMS dimension?
http://mapserver.org/ogc/wms_dimension.html
Matthias
On 11/23/17 2:11 PM, Arnaud Morvan wrote:
> Hello,
>
> I would like GetMap and GetFeature request extra parameters to be
> accessible as variables in server.
>
> So we could define, in QGIS project, a variable "floor",
Hello,
I would like GetMap and GetFeature request extra parameters to be
accessible as variables in server.
So we could define, in QGIS project, a variable "floor", used to filter
layers.
On desktop side, we could have a desktop plugin named FloorSlider to
change the "floor" value.
And
2017-11-23 13:35 GMT+01:00 Andreas Neumann :
> Hi Régis,
>
> I agree - it would be good to brainstorm what's missing to have an
> FME-like ETL environment.
>
> I see that you are coming to the Madeira dev meeting. Would be a good
> opportunity for such discussions and then
2017-11-23 13:35 GMT+01:00 Andreas Neumann :
> Hi Régis,
>
> I agree - it would be good to brainstorm what's missing to have an
> FME-like ETL environment.
>
> I see that you are coming to the Madeira dev meeting. Would be a good
> opportunity for such discussions and then
Hi,
this is awesome and something I have been trying to push towards at a
lot of meetings over the last year.
It reminds me a lot of this proposal by Arnaud Morvan, with the
technical details that are required to get all your wishes working:
Hi Régis,
I agree - it would be good to brainstorm what's missing to have an
FME-like ETL environment.
I see that you are coming to the Madeira dev meeting. Would be a good
opportunity for such discussions and then open the QEP in parallel (or
open it before and work on it).
BTW: refactor
Hi,
for me it wasn't just the build dir, but actually the source dir
rm -rf python/plugins/processing/algs/grass7/
git checkout -- python/plugins/processing/algs/grass7/
did the trick
Matthias
On 11/09/2017 11:00 PM, Tim Sutton wrote:
> Hi
>
> Thanks Médéric - cleaning out my build dir fixed
You could potentially use a model to save refactor fields settings. That
said, there's currently a problem (see issue
https://issues.qgis.org/issues/17421) preventing this algorithm from being
used in a model.
M
On Thu, Nov 23, 2017 at 3:01 PM, Andreas Neumann
wrote:
> Hi,
Hi Andreas,
I don't have any answer to that particular question, but in many project we
are working for, it becomes clear that we need to push processing to become
an ETL, and the field mapping component is clearly a key feature.
What do you think about opening a QEP and store in there all what's
Hi,
The refactor fields algorithm is potentially very powerful.
However, I do miss a way to save and load the configuration (or maybe I
just haven't found it). I have layers with many fields and I am adding
additional fields with expressions.
Every time I run it, I have to do the
21 matches
Mail list logo