w.
> I think this will be a more robust way to have the editing & data
> management facilities, & the apparent single table/column that you
> require.
>
> Brent Wood
>
>
> --- On Mon, 12/17/12, Astrid Emde wrote:
>
>
> From: Astrid Emde
> Subject: [Qgis-u
ngle database view. I think this
will be a more robust way to have the editing & data management facilities, &
the apparent single table/column that you require.
Brent Wood
--- On Mon, 12/17/12, Astrid Emde wrote:
From: Astrid Emde
Subject: [Qgis-user] How to digitze points, linestrings, p
Hi Astrid,
On Mon, 17. Dec 2012 at 09:22:13 +0100, Astrid Emde wrote:
> in a project I want to handle in one PostgreSQl/PostGIS table different
> geometrytypes (POINT, LINESTRING, POLYGON or even MULTI-objects) in a
> single geometrycolumn.
> Then I would like to digitize with QGIS new objects.
Hello Astrid,
> in a project I want to handle in one PostgreSQl/PostGIS table different
> geometrytypes (POINT, LINESTRING, POLYGON or even MULTI-objects) in a
> single geometrycolumn.
It is possible though really not recommanded.
> Then I would like to digitize with QGIS new objects. Is this po
Hi Astrid,
AFAIK QGIS can only handle one geometry type per layer (how should it be
displayed by default?) and only (Multi)points, -lines and -polygons.
So there are IMHO two workarounds, both with views:
1) create three different tables ((Multi)point, (Multi)linestring and
(Multi)polygon) for
Hello,
in a project I want to handle in one PostgreSQl/PostGIS table different
geometrytypes (POINT, LINESTRING, POLYGON or even MULTI-objects) in a
single geometrycolumn.
Then I would like to digitize with QGIS new objects. Is this possible?
I tried it already but in QGIS it is not possible to
