2016-06-28 13:34 GMT+02:00 Tom Chadwin :
> I'm sorry to keep asking about this. I'm now getting this error on Travis,
> against nightly (http://qgis.org/debian-nightly):
>
> Traceback (most recent call last):
> File "/home/travis/build/tomchadwin/qgis2web/olwriter.py",
-1 for Disqus. How about an easy step in this direction: have a field for a
Twitter account. Authors could decide whether to populate with their own or
create an account dedicated to their plugin.
--
View this message in context:
On 20-07-16 09:29, Yves Jacolin wrote:
> Matthias, Harrissou,
>
> On Wednesday, July 20, 2016 9:12:17 Matthias Kuhn wrote:
>> Hi Harrissou
>>
>> On 07/20/2016 08:47 AM, DelazJ wrote:
>> [..]
>>
>>> So questions:
>>> - Will we have a 2.18 (if ever) documentation?
>>
>> I think it would be good to
On Wed, Jul 20, 2016 at 6:17 PM, Even Rouault
wrote:
> The issues were with multiple layer joins with GeoServer in some
> circumstances not very
> clearly understood ( I don't want to particularly point fingers at
> GeoServer, as server side joins is a pretty advanced
On 20/07/16 18:17, Even Rouault wrote:
>> True... Although we could replace the features in the cache instead of
>> dropping the new ones for a tiny improvement.
> That would indeed help for the next feature request
>
>> There might be less complicated examples but this is the one I managed to
> True... Although we could replace the features in the cache instead of
> dropping the new ones for a tiny improvement.
That would indeed help for the next feature request
>
> Question: *is **there anybody using WFS with this option unchecked?*
> And if yes, for what reason?
> >>>
On 20/07/16 17:51, Even Rouault wrote:
>> In which case does that help? Isn't every cached feature downloaded
>> again (with potentially more up to date information) anyway?
> You get the feeling of a more responsive UI when you can reuse already
> downloaded features, but that's true that if
> In which case does that help? Isn't every cached feature downloaded
> again (with potentially more up to date information) anyway?
You get the feeling of a more responsive UI when you can reuse already
downloaded features, but that's true that if the server content has changed in
between, you
On 20/07/16 17:35, Even Rouault wrote:
> Hi,
>
>> I am a bit confused by the WFS option *"Only request features
>> overlapping the view extent"*.
>>
>> In general, that's what every provider does by default and is a safe
>> strategy to use. If this option is unchecked, QGIS will just start
>>
Hi,
I am a bit confused by the WFS option *"Only request features
overlapping the view extent"*.
In general, that's what every provider does by default and is a safe
strategy to use. If this option is unchecked, QGIS will just start
downloading features randomly until it hits a server limit (or
There is a ticket related here https://hub.qgis.org/issues/6478. We had a
discussion whether we should have the feedbacks on our side or usea 3rd
party plugin such as disqus, but it did not go much further than that.
Cheers
On Wed, Jul 20, 2016 at 4:45 PM, Paolo Cavallini
Il 20/07/2016 16:40, C Hamilton ha scritto:
> I don't know if it is possible, but it would be really nice if there
> were a way to get feedback on what a user likes or especially what the
> user dislikes when they vote on a QGIS plugin. If they give it a 1, 2,
Hi,
agreed, this would be a very
I don't know if it is possible, but it would be really nice if there were a
way to get feedback on what a user likes or especially what the user
dislikes when they vote on a QGIS plugin. If they give it a 1, 2, or 3 star
vote I would really like to know why. I would take the steps to try and fix
Hi,
You can submit it as non-experimental right away, if you think it is
already mature enough. I think this flag is self-declared - up to the
developer to decide. Paolo, who checks new plugins may suggest to the
plugin author to mark it as experimental if he thinks it is not yet
mature enough.
Hi Calvin,
Il 20/07/2016 16:22, C Hamilton ha scritto:
> I am planning on submitting a new D3 plugin to the QGIS plugins repo.
> This generates a circular heatmap D3 web page that has some similarities
> to the ArcGIS data clock. This is the github link.
>
>
I am planning on submitting a new D3 plugin to the QGIS plugins repo. This
generates a circular heatmap D3 web page that has some similarities to the
ArcGIS data clock. This is the github link.
https://github.com/NationalSecurityAgency/qgis-d3datavis-plugin
I have done a write up that shows what
Thanks again, Even:
QgsDataSourceURI(layer.dataProvider().dataSourceUri())
Tom
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/QgsMapLayer-source-for-a-WFS-now-returns-a-different-string-tp5277278p5277353.html
Sent from the Quantum GIS - Developer mailing list archive at
Even Rouault-2 wrote
> You can use QgsDataSourceURI.param("url") to retrieve the url parameter.
> You
> 'll need to augment it with SERVICE, VERSION and REQUEST parameters to
> form a
> valid GetFeature request.
Many apologies, but how do I retrieve the QgsDataSourceURI of a layer? I'm
not
Le mercredi 20 juillet 2016 15:21:57, Tom Chadwin a écrit :
> Even Rouault-2 wrote
>
> > You can use QgsDataSourceURI.param("url") to retrieve the url parameter.
> > You
> > 'll need to augment it with SERVICE, VERSION and REQUEST parameters to
> > form a
> > valid GetFeature request.
>
> Many
On 20/07/16 14:26, Nathan Woodrow wrote:
> Not sure we can? 2.14 is bug fix only. Given it's Python though you
> could just patch their copy.
>
Same thinking here, in general a release should receive bugfixes, not
features.
In the past we played with shipping updates through the plugin manager
Hi René-Luc,
There are no new features in past versions - only bug fixes. This also
applies to LT releases.
Sometimes it is a bit of a discussion if something qualifies as bug fix
or a feature, e.g. if something really essential is missing. So if you
can sell it as a "bug fix" it may get in.
Not sure we can? 2.14 is bug fix only. Given it's Python though you could
just patch their copy.
On Wed, Jul 20, 2016 at 10:25 PM, René-Luc Dhont wrote:
> Hi devs,
>
> I just made a Pull-Request to add a feature to DB manager.
> https://github.com/qgis/QGIS/pull/3322
> Add
Hi devs,
I just made a Pull-Request to add a feature to DB manager.
https://github.com/qgis/QGIS/pull/3322
Add the ability to update SQL Layer (to tweak the query)
I'd like to know what is the official ways adding features to QGIS LTR
core plugins ?
My customer will be happy to see it in
Le mercredi 20 juillet 2016 11:57:19, Tom Chadwin a écrit :
> I was retrieving the URL of a WFS layer, and formatting it for Leaflet as
> follows:
>
> layerSource = layer.source()
> layerSource += "=text%2Fjavascript&"
> layerSource += "format_options=callback%3AmyCallback"
> wfsVars += ('' %
I was retrieving the URL of a WFS layer, and formatting it for Leaflet as
follows:
layerSource = layer.source()
layerSource += "=text%2Fjavascript&"
layerSource += "format_options=callback%3AmyCallback"
wfsVars += ('' % layerSource)
This no longer works, because source() on a WFS layer now (2.16
Hi guys,
any news on this error?
tried to change the repo with those for the 2.14 and I'm not
experiencing the same error..
Thanks
Matteo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info:
On 20/07/16 09:31, Radim Blazek wrote:
> On Tue, Jul 19, 2016 at 10:07 PM, Radim Blazek wrote:
>> 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.
On Tue, Jul 19, 2016 at 10:07 PM, Radim Blazek wrote:
> 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
Matthias, Harrissou,
On Wednesday, July 20, 2016 9:12:17 Matthias Kuhn wrote:
> Hi Harrissou
>
> On 07/20/2016 08:47 AM, DelazJ wrote:
> [..]
>
> > So questions:
> > - Will we have a 2.18 (if ever) documentation?
>
> I think it would be good to plan 2.18 in general. Triggering the release
>
Hi Harrissou
On 07/20/2016 08:47 AM, DelazJ wrote:
> Hi folks,
> (sorry for the cross-posting)
being sorry doesn't make it any better ;)
honestly, I think in 99% of the cases it's fine to just target one or
the other.
> A few days ago, 2.14 doc has been released and the issues for 2.16 are
>
Hi Harrissou,
I would say 99% of the new features in the 2.x branch should also land
in the 3.x branch - otherwise it would be a waste ... in the opposite
direction it will be less, since new features that depend on an API
break can't be present in the 2.x. branch.
It is also very likely that
Hi folks,
(sorry for the cross-posting)
A few days ago, 2.14 doc has been released and the issues for 2.16 are
being addressed now.
Thanks to the automatic [feature] webhook, we are able to build the list of
changes in doc as soon as features land. BUT but... Currently, the webhook
is set to tag
32 matches
Mail list logo