Plugin Processing BEAM and SNAP algorithm Provider approval by pcav.
The plugin version "[618] Processing BEAM and SNAP algorithm Provider 1.3.1" is
now approved
Link: http://plugins.qgis.org/plugins/processing_gpf/
___
Qgis-developer mailing list
On 16.07.2016 01:20, Nyall Dawson wrote:
On 15 July 2016 at 03:40, Tim Sutton wrote:
Hi All
It seems like something broke in QgsComposition (in 2.16 and master) - we have
some code like this:
logo = self.composition.getComposerItemById('logo')
On Tue, Jul 19, 2016 at 7:11 PM, Radim Blazek wrote:
> This is failing https://travis-ci.org/qgis/QGIS/jobs/145868490 with
> Timeout 60.05 sec.
>
> Any idea why? I have merged pull request with just GRASS config files
> (xml) and 2 python scripts which are not called from
Hi All,
just to let you know that I created an issue in the QGIS issue Tracking
with this problem:
http://hub.qgis.org/issues/15311
Regards,
Germán
2016-07-15 12:26 GMT-05:00 Germán Carrillo :
> Hi All,
>
> I've discovered an issue with QgsVectorLayerUndoCommand
This is failing https://travis-ci.org/qgis/QGIS/jobs/145868490 with
Timeout 60.05 sec.
Any idea why? I have merged pull request with just GRASS config files
(xml) and 2 python scripts which are not called from tests.
Radim
___
Qgis-developer mailing
On 19-07-16 14:50, Anita Graser wrote:
> On Tue, Jul 19, 2016 at 2:25 PM, Richard Duivenvoorde
> > wrote:
>
> On 19-07-16 14:20, Anita Graser wrote:
> > Hi,
> >
> > The latest posts on http://planet.qgis.org/planet/ are from May. Is
On Tue, Jul 19, 2016 at 2:25 PM, Richard Duivenvoorde
wrote:
> On 19-07-16 14:20, Anita Graser wrote:
> > Hi,
> >
> > The latest posts on http://planet.qgis.org/planet/ are from May. Is
> > Planet affected by recent full disk issues on our servers? Or are there
> > other
On 19-07-16 14:20, Anita Graser wrote:
> Hi,
>
> The latest posts on http://planet.qgis.org/planet/ are from May. Is
> Planet affected by recent full disk issues on our servers? Or are there
> other things going on?
Something else, I forwarded some info earlier to people I hope can fix it:
Hi,
The latest posts on http://planet.qgis.org/planet/ are from May. Is Planet
affected by recent full disk issues on our servers? Or are there other
things going on?
Best wishes,
Anita
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
On Tuesday, July 19, 2016 9:49:34 Vincent Schut wrote:
> On Tuesday, July 19, 2016 08:32:55 AM Nyall Dawson wrote:
> > On 18 July 2016 at 23:56, Vincent Schut
>
> wrote:
> > > Ha, we did the same thing at the same time :-) I was just finished git
> > > bisecting and found
Hi Patrick
On Tue, Jul 19, 2016 at 11:30 AM, Patrick Valsecchi
wrote:
>
> So yes, my per function numbers are not very accurate, but they are a very
> good indication of where time is spent. But, I still have the global numbers
> with a RELEASE build to see if
On Tue, Jul 19, 2016 at 11:38 AM, Even Rouault
wrote:
> I'm not sure to have followed your computation, but it is wrong somewhere
> (must be a km vs m confusion).
>
Yes indeed. Shame on me. The earth circumference is 40'000km, not 40'000m.
> I was a bit sceptical, so I did a quick computation. A 32 bit float allows
> an accuracy of 3mm with WGS84 for coordinates around 180°:
> 180 takes 8 bits out of the 23 bits of fraction. The remaining 15 bits can
> split the earth circumference into chunks of 3mm (4/(2^15)). I'm maybe
> off
Hi Martin,
On Tue, Jul 19, 2016 at 10:52 AM, Martin Dobias wrote:
> Just curious - what did you use for profiling? Release or Debug build?
>
When trying to optimize code like QGIS server, I tend to do that:
1. Take a scenario that matches the realworld, run it with a
Hi Nyall,
On Tue, Jul 19, 2016 at 10:25 AM, Nyall Dawson
wrote:
> See https://github.com/qgis/qgis3.0_api/issues/15
>
>
Cool, that would force us to use the coordinates directly instead of the
WKB.
> We can't use a QPolygonF, as it uses qreal for storage. For certain
>
Hi Patrick
On Tue, Jul 19, 2016 at 9:58 AM, Patrick Valsecchi
wrote:
> Hi,
>
> I was looking at the perfs of qgis server and I did a small profiling of a
> GetMap on a road layer (linestring) with QGIS configured with defaults. We
> spend a lot of time
On 19 July 2016 at 17:58, Patrick Valsecchi
wrote:
> Hi,
>
> I was looking at the perfs of qgis server and I did a small profiling of a
> GetMap on a road layer (linestring) with QGIS configured with defaults. We
> spend a lot of time converting to and from WKB.
Hi to everybody,
I tried the script from Kartoza (and that from the first comment):
http://kartoza.com/how-to-create-a-qgis-pdf-report-with-a-few-lines-of-python/
using a simple project with one postgres layer and a simple qpt print
template (consisting of one map composer item), it produces a
Hi,
I was looking at the perfs of qgis server and I did a small profiling of a
GetMap on a road layer (linestring) with QGIS configured with defaults. We
spend a lot of time converting to and from WKB. For example, for rending
67k features (3 GetMaps), we do this for each feature:
- When
On Tuesday, July 19, 2016 08:32:55 AM Nyall Dawson wrote:
> On 18 July 2016 at 23:56, Vincent Schut
wrote:
> > Ha, we did the same thing at the same time :-) I was just finished git
> > bisecting and found the same offending commit, was just about to
email.
>
> Should
Plugin Isogeo approval by pcav.
The plugin version "[1066] Isogeo 0.1a2 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/isogeo_search_engine/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info:
On Tue, Jul 19, 2016 at 8:53 AM, Paolo Cavallini
wrote:
> https://hub.qgis.org/issues/
> returns Internal error. It happened already a few days ago, can we take
> care of this?
>
Looks fine here.
Best wishes,
Anita
___
On 19-07-16 08:53, Paolo Cavallini wrote:
> https://hub.qgis.org/issues/
> returns Internal error. It happened already a few days ago, can we take
> care of this?
Fixed by Juergen, disk full
Regards,
Richard
___
Qgis-developer mailing list
On 19-07-16 00:32, Nyall Dawson wrote:
> On 18 July 2016 at 23:56, Vincent Schut wrote:
>> Ha, we did the same thing at the same time :-) I was just finished git
>> bisecting and found the same offending commit, was just about to email.
>>
>
> Should be fixed now - can
https://hub.qgis.org/issues/
returns Internal error. It happened already a few days ago, can we take
care of this?
Thanks.
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
Qgis-developer mailing list
25 matches
Mail list logo