Hi,
As far as I can remember from reviewing the code, server side
simplification is enabled on a per-request basis. So it should be
possible to disable it when certain parameters (like $area required)
are met.
Matthias
___
Qgis-developer mailing
On Mon, Jun 23, 2014 at 1:59 PM, Matthias Kuhn matthias.k...@gmx.ch wrote:
Hi,
As far as I can remember from reviewing the code, server side
simplification is enabled on a per-request basis. So it should be
possible to disable it when certain parameters (like $area required)
are met.
Right.
My assumption is, that in this particular case the geometry is used in
the rendering process (hence a simplified version).
It could be checked if an expression used in the rendering process
requires the geometry (or $area and maybe others?) just the way
attributes are only requested for
Apologies for cross-post from qgis-user - I thought -developer only dealt with
QGIS core, rather than also with plugin development.
How do I determine in Python whether each field is hidden? I can't get
editType() to work (and know it is deprecated). Does anyone have an example of
this using
Hi all,
Does anyone have any thoughts about http://hub.qgis.org/issues/8359 -
specifically, is the warning which shows when exporting compositions
containing WMS layers still required? My gut feeling is that it's probably
safest to leave the warning, but thought I'd get a few more opinions before
Hi Tom,
The following example should should print the type for all widgets.
editorWidgetV2ByName( fieldName ) will return Hidden for all hidden
fields, so for checking simply use string comparison.
editorWidgetV2Config can then be used to access further configuration
options for the editor
Hi all.
Thanks mainly to the effort of Juergen and Giovanni, the bugtracker queue is now
being cleaned up considerably, removing issues resolved long ago, duplicates,
and
unverifiables. Keeping the list tidy is crucial to focus the attention on
important
issues: if the list is full of garbage,
Hi Matthias
Many thanks for this. It's not working for me quite yet:
AttributeError: 'QgsVectorLayer' object has no attribute 'editorWidgetV2ByName'
Python version:
2.7.5 (default, May 15 2013, 22:44:16) [MSC v.1500 64 bit (AMD64)]
QGIS version:
2.2.0-Valmiera Valmiera, c3a2817
Any ideas?
Hi Tom,
That works starting from 2.3 (master) / 2.4 (release/stable)
For 2.2 you will have to work with
i.editType( fields.indexFromName(field) )
This will continue to work with 2.4 (And it would be nice if you could
test and report in case there's a difference between 2.2 and 2.3 as
there's
Hi Matthias
Ah, OK. I didn't gather that from the API docs. OK, I can print out the
editType() value now, which is 11 for hidden:
print i.editType(fields.indexFromName(field))
However, I can't test for it:
if i.editType(fields.indexFromName(field)) != 11
SyntaxError: invalid syntax
I've
Did you try to compare to QgsVectorLayer.Hidden?
The list of types is here:
http://qgis.org/api/classQgsVectorLayer.html#a441a8cbb0170c48da6aa7b02dad4b5a3
Regards,
Matthias
On 23.06.2014 15:56, Tom Chadwin wrote:
Hi Matthias
Ah, OK. I didn't gather that from the API docs. OK, I can print
Hi all.
We are thinking about the future of Processing framework. The duplication shown
among
modules is certainly a good thing, as it allows richer analyses and more
control and
verification, but can be intimidating even for skilled GIS users.
We have been discussed this before, but I came up
Hi Paolo,
I agree with you, a cleaner organization of Processing tools is advisable
to reduce the confusion in users.
It's rather difficult to teach them in a clear way too! :)
IMHO this reorganization should consider also the integration of other
sparse analysis/processing tools, like the ones
I've given a look to the list of Processing QGIS geoalgorithms and I've
seen that all the tools from fTools seem to be there. I remembered that
someone was missing, but it seems not to be true anymore. I wonder if it
wouldn't be the case to drop fTools algorithms from Vector menu. It would
help in
Paolo, that sounds good to me
The basic and experimental modules that you propose are the current
simplified and advanced modes. We should work on a normal mode.
Let's discuss it here and maybe create a spreadsheet that we can edit to
select the list of modules to include
Thanks for the
Hi Giovanni,
some time ago not all FTools modules were available via Processing, but we add
at least part of missed modules to it (e.g. Random Points algs were added about
month ago with Faunalia support). Unfortunately if I'm not wrong
several algorithms
still missed (for example Vector Grid).
Getting to the post subject, I feel it would be more natural to distinguish
between generic and specific tools. The experimental section could have
the same categories:
- Generic
- Specific (I'm not sure this is the right word...)
- Experimental
- Generic
- Specific
With specific I
Maybe tagging support will help with this, as same algorithm
may be useful in different domains
2014-06-23 20:33 GMT+03:00 G. Allegri gioha...@gmail.com:
Getting to the post subject, I feel it would be more natural to distinguish
between generic and specific tools. The experimental section
Hi,
On Mon, Jun 23, 2014 at 11:28 AM, Alexander Bruy alexander.b...@gmail.com
wrote:
Hi Giovanni,
some time ago not all FTools modules were available via Processing, but we
add
at least part of missed modules to it (e.g. Random Points algs were added
about
month ago with Faunalia
Hi, I really like the idea to separate well tested modules from
experimentals. I loose lots of time each time testing every module before
finding the good one. Today, I struggled with spline surface interpolation,
some grass 6 modules do run out of memory after 3 hours computing, some saga
modules
On Mon, Jun 23, 2014 at 9:29 AM, Matthias Kuhn matthias.k...@gmx.ch wrote:
My assumption is, that in this particular case the geometry is used in
the rendering process (hence a simplified version).
It could be checked if an expression used in the rendering process
requires the geometry (or
Hi,
Using the raster layer provider's identify() function, I can get the
raster value at the specified location. Are there any convenience
functions to do bilinear or cubic raster sampling as well? Or does
this have to be done manually in the plugin code?
Thanks and best wishes,
Anita
I'm not aware of such functions exposed to QGIS API, and AFAIK there's
nothing useful under Qt neither...
giovanni
2014-06-23 21:25 GMT+02:00 Anita Graser anitagra...@gmx.at:
Hi,
Using the raster layer provider's identify() function, I can get the
raster value at the specified location. Are
On 06/20/2014 01:33 AM, Luca Manganelli wrote:
On Fri, Jun 20, 2014 at 9:43 AM, Martin Dobias wonder...@gmail.com wrote:
I agree with Andreas. Can we postpone the release for a few days?
There is still quite steady flow of new bug reports worth addressing.
I would suggest max. 7 days (without
Hi Developers
Encountered a very serious problem, looks like this issue is there in 2.x
Ways to reproduce;
1. Add a world boundary shp file in wgs84 (you can use other files too)
http://thematicmapping.org/downloads/world_borders.php
2. Open the print composer, add a new map
3. add scale bar
forgot,
using Windows OS
Win 7 Professional x64
Thanks
Ted
On Tue, Jun 24, 2014 at 7:27 AM, Ted tiruchirapa...@gmail.com wrote:
Hi Developers
Encountered a very serious problem, looks like this issue is there in 2.x
Ways to reproduce;
1. Add a world boundary shp file in wgs84 (you
Hi Anita,
There's no such thing in QGIS.
But, you can have such functionality through processing or via plugins
(e.g. Raster Interpolation).
Anyway, that would be an idea to bring such functionality in core!
Cheers,
Denis
On 23.06.2014 21:25, Anita Graser wrote:
Hi,
Using the raster
On Tue, Jun 24, 2014 at 12:31 PM, Denis Rouzaud denis.rouz...@gmail.com wrote:
Hi Anita,
There's no such thing in QGIS.
But, you can have such functionality through processing or via plugins (e.g.
Raster Interpolation).
Anyway, that would be an idea to bring such functionality in core!
28 matches
Mail list logo
