Alex Mandel wrote:
I'm a little lost here, in my experience a vector layer becomes a table,
not multiple tables and all the geometries are stored in a blob column
no matter what type it is.
That's what I'm curious about. Each vector is becoming a table
unto itself. That's not proper normal
Peter,
What tool did you use to import the layer into POSTGIS?
Quantum GIS.
My guess is you actually used the SPIT plugin, which is a C++ plugin
included with QGIS, and is a gui frontend to shp2pgsql...
Carson
___
Qgis-user mailing list
Yes, that is correct.
Are there any other 'shp ingesters' for use with QGIS?
AFAIK the PostGIS manager plugin is also able to load shapefiles into
PostGIS, and this is a nice simple way to manage your database directly
from within QGIS.
I am thinking that my complaint regarding proper
On Thu, Apr 9, 2009 at 7:53 PM, Peter Willis pet...@borstad.com wrote:
Carson Farmer wrote:
Peter,
What tool did you use to import the layer into POSTGIS?
Quantum GIS.
My guess is you actually used the SPIT plugin, which is a C++ plugin
included with QGIS, and is a gui frontend to
On Thu, Apr 9, 2009 at 7:53 PM, Peter Willis pet...@borstad.com wrote:
Carson Farmer wrote:
Peter,
What tool did you use to import the layer into POSTGIS?
Quantum GIS.
My guess is you actually used the SPIT plugin, which is a C++ plugin
included with
Hello,
I just ingested a MULTIPOLYGON vector into a PostGIS enabled
database and realized that each vector becomes a unique TABLE
in the database.
Is this really necessary?
Why not use proper relational database techniques and have
all vectors of a specific type go into a single table
with a
I'm a little lost here, in my experience a vector layer becomes a table,
not multiple tables and all the geometries are stored in a blob column
no matter what type it is.
Of course if you have multiple vector types in the same table this can
cause issues with various spatial operations, so you
