Hi Matthias,
On Wed, 03. Dec 2014 at 16:46:11 +0100, Matthias Kuhn wrote:
I didn't look at it in detail and just based this recommendation on the
one from the QtXml documentation linked at the end of the original message.
Is there something in particular you think we will be missing? If so, it
On 4 December 2014 at 19:25, Jürgen E. j...@norbit.de wrote:
Hi Matthias,
On Wed, 03. Dec 2014 at 16:46:11 +0100, Matthias Kuhn wrote:
I didn't look at it in detail and just based this recommendation on the
one from the QtXml documentation linked at the end of the original message.
Is there
Thank you Jürgen and Nyall,
On 04.12.2014 09:44, Nyall Dawson wrote:
On 4 December 2014 at 19:25, Jürgen E. j...@norbit.de wrote:
We could just keep using it and fork it if need be. Any idea why it was
discontinued?
This link [1] suggests that it hasn't been discontinued, it's just
QtXml is really, damn slow. PyQt with QtXml is worst then lxml, just to
make a comparison. Switching to a streamlined xml parser would be
advisable, but I know it would a deep refactoring for a lot of QGIS's code.
Maybe it should be considered within the next big refactorings (geometry,
composer,
On Thu, Dec 4, 2014 at 10:04 AM, G. Allegri gioha...@gmail.com wrote:
QtXml is really, damn slow. PyQt with QtXml is worst then lxml, just to make
a comparison. Switching to a streamlined xml parser would be advisable, but
I know it would a deep refactoring for a lot of QGIS's code.
Maybe it
On 04.12.2014 10:04, G. Allegri wrote:
QtXml is really, damn slow. PyQt with QtXml is worst then lxml, just to
make a comparison. Switching to a streamlined xml parser would be
advisable, but I know it would a deep refactoring for a lot of QGIS's code.
Maybe it should be considered within the
Considering a sponsor: it might be packaged in a proposal of a native
project file format that also supports storing layers.
You could potentially consider using a GeoPackage container as a base for that
:
- http://www.geopackage.org/spec/
- http://www.gdal.org/drv_geopackage.html
It would
Hi,
agreed it's awfully slow on large project save (about 1 min sometimes for
about 200 layers)
+1 for refactoring qgs into a container able to store layers. That would
give us a storing solution for memory layers, discussed previously.
Cheers
Régis
--
View this message in context:
Hi,
I've nearly the same problem on master since this week-end (I believe) :
Couldn't load PyQGIS.
Python support will be disabled.
Traceback (most recent call last):
File , line 1, in
File /home/etienne/apps/share/qgis/python/qgis/__init__.py, line 36, in
from qgis.core import
It's also worth noting that QtXml is very
slow, which is noticeable on project load/save.
Is it really the xml parsing which is slow? I would have expected that
xml parsing only is fast and the things QGIS is doing on project load
are slow (e.g. restoring connections, creating print
Hello Nyall,
Thank you for your answer.
I'm really ashamed : It was just a stupid path problem.
I had already tried to import new composers created with QGIS 2.6, but
trying again put me on the path to the solution.
Thank you and really sorry for the noise.
Vincent
---
On Thu, Dec 4, 2014 at 1:44 PM, Marco Hugentobler
marco.hugentob...@sourcepole.ch wrote:
Is it really the xml parsing which is slow? I would have expected that xml
parsing only is fast and the things QGIS is doing on project load are slow
(e.g. restoring connections, creating print composers,
Hi.
I'm just wondering if the weekly release of QGIS for Windows has been stopped?
I haven't seen a new release since November 17.
Regards, Casper
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
(aka LISP ALL THE THINGS)
Just posted something that I thought a few people might be interested in
http://nathanw.net/2014/12/04/using-hy-a-dialect-of-lisp-for-python-with-qgis/
- Nathan
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
Hi,
I was wondering if the scripts built in the processing toolbox support the
use of the multiprocessing python module? I have a few standalone ArcGIS
scripts that use that module and therefore are quicker and would love to
see if I can implement them within QGIS.
Cheers,
Bjorn
Slowness is painfull also on project save, and I guess this is mainly the xml
issue there.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/QtXml-is-no-longer-maintained-in-Qt5-tp5176248p5176498.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
I was able to fix it by defining LD_LIBRARY_PATH to point to development
libs.
like export LD_LIBRARY_PATH=/home/misha/opt/qgis-dev/lib
Aparently there qgis tries to load libs from other places; in my case
it is probably
because I have qgis installed from repository.
Mikhail
On
Hi all,
I've pushed a second step of support for rotation in raster renderer
but I'm missing something about the placement and scaling of it
as the raster gets bigger and offsetted when rotated.
Size is good at 0,90,180,270 but offset is still wrong in a way that's
probably due to only carring
Can anyone help with this?
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Retrieve-field-name-used-as-label-tp5176293p5176544.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer
Here is my problem:
I am trying to develop a mobile application using Qt and QGIS. I am
trying to implement zoom action on qgsmapcanvas. Right now, I have a
qgsmapcanvas and a qwidget. I have developed the code for zoom action on the
qwidget. And I am considering to overlap the qgsmapcanvas
Both should work:
QgsLabel(layer.pendingFields()).fields()[0].name()
layer.customProperty(labeling/fieldName)
Best Regards,
-SL
--
Sent from my mobile phone
Il 04/Dic/2014 23:00 Tom Chadwin tom.chad...@nnpa.org.uk ha scritto:
Can anyone help with this?
--
View this message in context:
QgsLabel(layer.pendingFields()).fields()[0].name()
That doesn't work - it gives the field at position 0, not the labelling
field.
layer.customProperty(labeling/fieldName)
But this does work perfectly. Thank you so much.
Tom
--
View this message in context:
Don't use QgsLabel it is the old label engine and will be removed in the
future.
- Nathan
On Fri Dec 05 2014 at 9:27:14 AM Tom Chadwin tom.chad...@nnpa.org.uk
wrote:
QgsLabel(layer.pendingFields()).fields()[0].name()
That doesn't work - it gives the field at position 0, not the labelling
Noted. Thanks, Nathan.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Retrieve-field-name-used-as-label-tp5176293p5176558.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing
Is there a python version of qTuio? qTuio is implemented in C++. However, I
am currently trying to use pyqgis due to problems with C++ environment (I
cannot even create a raster layer).
Any help is appreciated.
--
View this message in context:
25 matches
Mail list logo
