I've just seen the related issue: http://hub.qgis.org/issues/11968
2015-03-26 18:24 GMT+01:00 G. Allegri :
> Ok, thanks Marco,
> I'll write your answer to the qgis-user thread.
>
> 2015-03-26 18:17 GMT+01:00 Marco Hugentobler <
> marco.hugentob...@sourcepole.ch>:
>
>> Hi Giovanni
>>
>> Uncheckin
Ok, thanks Marco,
I'll write your answer to the qgis-user thread.
2015-03-26 18:17 GMT+01:00 Marco Hugentobler <
marco.hugentob...@sourcepole.ch>:
> Hi Giovanni
>
> Unchecking the option 'cache features' did exactly that (first fetch based
> on current view extent and refetching of new parts whe
Hi Giovanni
Unchecking the option 'cache features' did exactly that (first fetch
based on current view extent and refetching of new parts when panning).
This seems broken now (maybe since the multithreaded rendering?).
Another (not so convenient) method is to create an ogc filter by double
c
Hi,
you probably read the question from Peter on qgis-user [1].
Five years ago Marco said that this behaviour should have been changed
(first fetch based on current view extent) but AFAICS the WFS provider
still behaves the old way.
Was this proposal discarded for some reason?
Giovanni
[1]http://
Hi Christian,
On Thu, 26. Mar 2015 at 13:47:07 +, Boehnke, Christian wrote:
> Our Team of software developers at Fugro Consult are currently developing an
> extension for QGIS. One function of our plugin is to load MS Access Databases
> into QGIS, both .mdb and .accdb. When working with a 64-b
Il 26/03/2015 14:53, Charles Shapiro ha scritto:
> Has anyone else had this difficulty?
I remember others had the same problem, but cannot recall how they
solved it: anyone?
All the best, and thanks for your reply.
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia
Dear QGIS Development Team,
Our Team of software developers at Fugro Consult are currently developing an
extension for QGIS. One function of our plugin is to load MS Access Databases
into QGIS, both .mdb and .accdb. When working with a 64-bit version of QGIS the
MS Access Databases are not rego
Thanks all for pointing things out!
My view did have a unique id, it is just a sub set of another table. So
by selecting it everything is solved.
On 26-03-15 11:45, Matthias Kuhn wrote:
Hi Raymond,
The feature shown in the identify result is the one queried with the
geographic location.
Fo
2015-03-26 11:48 GMT+01:00 Tom Kralidis :
>
> On Thu, 26 Mar 2015, Paolo Cavallini wrote:
>
>> Il 26/03/2015 10:48, Tom Kralidis ha scritto:
>>
>>> plugins (Metatools, QSphere, etc.). Having said this, I think the silver
>>> bullet here would be giving the Metadata section of the Layer Properties
On Thu, 26 Mar 2015, Paolo Cavallini wrote:
Il 26/03/2015 10:48, Tom Kralidis ha scritto:
plugins (Metatools, QSphere, etc.). Having said this, I think the silver
bullet here would be giving the Metadata section of the Layer Properties
window an update to support vanilla ISO 19115/19139 (thi
Hi Raymond,
The feature shown in the identify result is the one queried with the
geographic location.
For some reason the feature shown in the feature form is not a copy of
the identified data (feature) but queried again with its feature id.
For the views on pg databases I have here, the primary
To add my 2 cents worth, I now habitually add a default INTEGER field to my
PostGIS views to provide QGIS with a unique identifier. I label this field
‘qid’ so as not to confuse it with potentially other unique keys that may
already exist in the underlying data.
For example:
CREATE OR REPLA
choose gid field as key, and check if it is really unique in
>>>> postgis?
>>>>
>>>> Cheers
>>>> Régis
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://osgeo-org.1560.x6.nabble.c
ist
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
__ Information from ESET Mail Security, version of virus
signature database 11379 (20150326) __
The message was checked by ESET Mail Security.
http://www.eset.com
__
ormation from ESET Mail Security, version of virus
signature database 11379 (20150326) __
The message was checked by ESET Mail Security.
http://www.eset.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.or
l
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
__ Information from ESET Mail Security, version of virus signature
database
Il 26/03/2015 10:48, Tom Kralidis ha scritto:
> plugins (Metatools, QSphere, etc.). Having said this, I think the silver
> bullet here would be giving the Metadata section of the Layer Properties
> window an update to support vanilla ISO 19115/19139 (this is worthy of a
> QEP
> all by itself), an
Thanks Regis, that was exactly the issue. The (boolean!) field
'inonderzoek' was used as a key. When I change that to 'gid' in the Add
PostGIS Table dialog, everything works correctly.
Can anyone tell me why QGIS picks that boolean field for most of my
tables? Can I change that behaviour by ch
On Wed, 25 Mar 2015, Paolo Cavallini wrote:
Date: Wed, 25 Mar 2015 15:52:49 +0100
From: Paolo Cavallini
To: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] QGIS & PyCSW
Il 25/03/2015 15:24, Angelos Tzotsos ha scritto:
This idea is excellent: we discussed something similar some
Hi, I have seen such troubles when the choosen primary key from qgis side is
not unique .
Symptoms: selecting one feature select severals unrelated features of the
same layer. relation with attributes is broken also.
Can you check in your layer's definition (general tab of layer properties)
if
When I use the Feature info tool with the "Auto open form" option
selected, the form shows different values compared to the identify
results. The Identify results are correct.
Here's a screenshot:
http://terglobo.nl/downloads/qgis_attribute_form_bug.png
I am using QGIS Testing (just updated) o
21 matches
Mail list logo
