Hi Richard,
The situation improved, the server does not only indicate, that it's
running, but serves real pages.
However, when I type http://planet.qgis.org into my address bar I
expect it to open the planet and not the new QGIS Web Application, I
think a simple redirect to /planet/ would do
On Mon, Apr 7, 2014 at 2:36 AM, Mathieu Pellerin nirvn.a...@gmail.com wrote:
May I suggest a small improvement? You should calculate the time it took, in
ms, to render canvas and deduce that ms value from the animationFrameLength
ms value in your singleShot call:
Good point. I thought of it,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry I didn't follow the discussion accurately: what is the final decision
about
filing tickets about Processing?
Currently I see there are two instances:
http://hub.qgis.org/projects/quantum-gis/issues?category_id=94
Hi Stefan,
I'm answering the first question.
Le 05/04/2014 12:25, Stefan Keller a écrit :
Hi Devs,
Tobias and I are working on the ArcGIS REST API Connector Plugin
which reads WFS- and WMTS-alike services (called Feature Service and
Map Service) from ArcGIS Online or ArcGIS Server 10.x.
Hi Anita
On Sat, Apr 5, 2014 at 5:10 PM, Anita Graser anitagra...@gmx.at wrote:
Hi,
Are there plans to let plugins (which are not working well with
multi-threaded rendering) deactivate the feature when needed?
No there are no plans to allow deactivation of rendering in
background. I think it
Hi Anita
On Sun, Apr 6, 2014 at 6:08 PM, Anita Graser anitagra...@gmx.at wrote:
I need the painter from the renderComplete signal? Could you help me with
the correct syntax?
I have:
self.iface.mapCanvas().renderComplete.connect(self.waitAfterRenderComplete)
and
def
Martin,
Both those signals are the same and work the same. The newer .connect
method is the better way.
- Nathan
On Mon, Apr 7, 2014 at 7:31 PM, Martin Dobias wonder...@gmail.com wrote:
Hi Anita
On Sun, Apr 6, 2014 at 6:08 PM, Anita Graser anitagra...@gmx.at wrote:
I need the painter
Hi Nathan,
On Mon, 07. Apr 2014 at 19:37:35 +1000, Nathan Woodrow wrote:
Both those signals are the same and work the same. The newer .connect method
is the better way.
Maybe that was to rule out something else.
Apropos does either connect actually return True?
Jürgen
--
Jürgen E. Fischer
Hi Jürgen
On Mon, Apr 7, 2014 at 11:42 AM, Jürgen E. j...@norbit.de wrote:
Hi Nathan,
On Mon, 07. Apr 2014 at 19:37:35 +1000, Nathan Woodrow wrote:
Both those signals are the same and work the same. The newer .connect method
is the better way.
Maybe that was to rule out something else.
On 7 April 2014 18:15, Vincent Picavet vincent...@oslandia.com wrote:
A good solution though would be to remove google layers and only use OSM and
mapbox layers, which begin to be on par in terms of quality.
I'm pretty sure this is against MapBox's terms of service too, unless
users were made
Also, when it comes to OSM, IMO proper TMS support should be what is
(eventually) offered as implemented feature to users. That'd allow for OSM
basemaps to also export properly in qgis composer. OpenLayer' layers not
exporting well in qgis composer is a pretty big limitation.
Maybe a simple UI to
Hello,
Le lundi 7 avril 2014 12:05:05, Nyall Dawson a écrit :
On 7 April 2014 18:15, Vincent Picavet vincent...@oslandia.com wrote:
A good solution though would be to remove google layers and only use OSM
and mapbox layers, which begin to be on par in terms of quality.
I'm pretty sure
Hi all,
I've just sent through a pull request which implements interactive
preview modes to the composer. These allow you to instantly see what
your composition would look like in grayscale, bw, or for color blind
people. The pull request is here:
https://github.com/qgis/QGIS/pull/1294
HOWEVER -
Not with the field calculator, but you can use the advanced python one
also in Processing.
Here is some more info:
http://anitagraser.com/2013/04/20/advanced-python-field-calculator/
2014-04-06 22:30 GMT+02:00 Yves Jacolin yjaco...@free.fr:
Hello,
Is there a way to process area for each
Hi list!
I'm happy to announce the first release of opeNoise (v.0.1), an experimental
QGIS plugin that allows to compute the noise level generated by road traffic at
fixed receiver points and buildings.
I hope it can be useful and you want to test it and give me some feedback.
You can
Hi Paolo,
now Processing is as subproject of QGIS (thanks to Alex Mandel).
All Processing tickets now should be visible in QGIS bugtracker, also
you can use custom query on the right panel [0] to filter only Processing
tickets.
If you need to create new ticket for Processing, you need to use its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 07/04/2014 15:30, Alexander Bruy ha scritto:
now Processing is as subproject of QGIS (thanks to Alex Mandel).
All Processing tickets now should be visible in QGIS bugtracker, also
you can use custom query on the right panel [0] to filter only
If I understand correctly, this is redmine limitation. Alex can
clarify this better then me
There is also another option — move all Processing tickets
into main QGIS tracker. But in this case we will lose all ticket
groups and will have only one group called Processing.
2014-04-07 16:35
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 07/04/2014 15:38, Alexander Bruy ha scritto:
If I understand correctly, this is redmine limitation. Alex can
clarify this better then me
There is also another option — move all Processing tickets
into main QGIS tracker. But in this case we
Since the OpenLayers plugin does not (currently) work with master, perhaps
we can replace it with TMS-based layers, wither through a plugin or as a
native (GDAL-based) provider?
Is there anything in OpenLayers that could not work with GDAL TMS
mini-driver [1] ?
On Mon, Apr 7, 2014 at 7:22 AM,
Since the OpenLayers plugin does not (currently) work with master, perhaps
we can replace it with TMS-based layers, either through a plugin or as a
native (GDAL-based) provider?
Is there anything in OpenLayers plugin that could not work with GDAL TMS
mini-driver [1] ?
[1]
Thanks for the links. Most of this information is also available at [1].
I am preparing a simple plugin to load these layers as raster layers, will
keep you updated on this.
[1] http://www.gdal.org/frmt_wms.html
On Mon, Apr 7, 2014 at 2:32 PM, kimaidou kimai...@gmail.com wrote:
Hi List
Hi !
I agree with those saying it's better to integrate the features of
top-plugin in the core, if we find the features are worth it, and if
someone has the time to do so, rather than shipping dozens of preinstalled
plugin.
I don't like the impression it gives to have a brand new software
Ok. cracked it. But in the process ended up upgrading to Mavericks to
install Xcode 5+.
A few tips for those building on OSX.
- The homebrew installers are helpful for the dependencies
- use make rather than make -j# on the main build
--
View this message in context:
Am 07.04.2014, 11:57 Uhr, schrieb Martin Dobias wonder...@gmail.com:
Yeah, anyway I checked again and even original Anita's statement
worked for me. This is what I did in python console:
from PyQt4.QtCore import *
class A(QObject):
def __init__(self): QObject.__init__(self)
def f(self,
I actually do not see the difference between a core plugin a something
implemented directly in the core c++ code. Other than the extra time
it might take to develop it. The user doesn't have to know it is a
plugin, and it should be easy to actually remove a core plugin from
the plugin manager
Hi Victor
For me, core features (and not core plugins) are much more integrated into
QGIS ui and dialogs. For example, tablemanager plugins adds some nice
features , but they should be integrated in the Fields tab of the vector
layer properties. Having the features separated in a plugin (core or
I agree, each plugin is a different world. It's true that core
development can bring further integration, but maybe moving plugins to
core is a good moment to rethink how plugins can integrate in the QGIS
interface and allow new ways of interacting (for instance, making it
easy for a plugin to add
I have put together a simple plugin to load a number of TMS layers using
the GDAL TMS mini-driver [1]. I see it as a simple alternative to the more
complete OpenLayers plugin.
Code is at github for now [2]. Any suggestions are welcome (including
plugin name). Also if you have any other working
Nice, few comments (based on my previous uses of the GDAL TMS mini-driver):
- your plugin should make sure the loaded layer is assigned the proper
projection (mostly pseudo-mercator); failing to do so will leave must users
unable to understand why the TMS rendering fails
- that would also switch
Hi,
If you are using Homebrew, consider adding the OSGeo4Mac tap [0], and
trying out the qgis-22 formula. The tap is still in a 'beta' state. If you
find any issues, please post them to the site's tracker.
[0] https://github.com/OSGeo/homebrew-osgeo4mac
Regards,
Larry Shaffer
Dakota
Matthieu,
Thanks for your input!
I will change the project CRS by default but make it optional.
Do you have a xml file for the TMS of the Global Forest Change, or any info
on what server it uses or at least the path?
While working on it I realized the power of the caching - I am taking
32 matches
Mail list logo
