Hi Richard -
There seems to be some kind of version conflict between the different GIS
software on how to use the OGC definitions for "geometry_columns" - whether
to use the column name "type" og "geometry_type".
And under any circumstances, QGIS is *not* the guilty part.
IMHO ,The Geoserver
On 11/05/2019 19.44, Bo Victor Thomsen wrote:
>
> Retrying the WFS describefeature request on the sql server layers now
> gives the equivalent result as with Postgres:
>
> * ... name="ogr_geometry" nillable="true"
> type="*gml:MultiSurfacePropertyType*"/>...
>
>
> There
Hi all -
(for the impatient, read the last part of this mail)
I've been digging a little bit further into my own setup - essentially
doing the same operations as Richard
I examined the 4 layers i GeoServer
* groenreg:bykerne: *SqlServer* based layer *with* rows.
Geometry column defined
On Fri, May 10, 2019 at 5:04 PM Richard Duivenvoorde
wrote:
> Hi,
>
> Just tried with a Geoserver (2.15) I have running here.
>
> Moved a shp file with 1 feature in a postgis db, created a wfs service
> for it and loaded in QGIS, styled it etc: fine.
>
> Removed the (one) feature from the table,
Hi,
Just tried with a Geoserver (2.15) I have running here.
Moved a shp file with 1 feature in a postgis db, created a wfs service
for it and loaded in QGIS, styled it etc: fine.
Removed the (one) feature from the table, retarted Geoserver, and had a
look into the requests QGIS is firing [0].
Hi Lars and other members of this list..
I feel somewhat obligated to help Lars since it's a problem he has
inherited from me. (Sorry about that...)
To sum it up:
If QGIS connects to a WFS based layer from Geoserver using an existing
project with styled layers and one or more layers
Hi developers.
I asked this question on the user's list, so far without any answers, but have
been advised to ask here as well.
I'm working with a number of projects, which statically open a fixed number of
layers. All layers are fetched using WFS / WFS-T.
Each layer has an extensive rule
