Just found the problem with PostgreSQL-import:
If the postGIS-layer has multiple geometries (in my case, centroid and
polygon), it will be viewed with "db.tables -p", but not imported
through "v.in.ogr". Error is misleading as it says "Layer not
available". Workaround, was a copy of the layer with only one geometry.
Would be great to be able to select though, e.g. as done in QGIS.
patrick
Message: 4
Date: Wed, 14 Mar 2012 10:50:57 +0100
From: "Patrick S."<[email protected]>
Subject: [GRASS-user] postgreSQL import
To: grass mailing list<[email protected]>
Message-ID:<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
I try to import various files from PostgreSQL to GRASS in GRASS70.
/
db.connect driver=pg
database='host=<server>,dbname=<database>,schema=<schamename>'
db.login user="sustaincity" pass="+++"
db.connect -p
db.tables -p |less
for i in {1..3};
do
v.in.ogr dsn='PG:host=<servername> dbname=<dbname>
user=<username>' layer=schema.layer output=layer$i
type=boundary,centroid -o --o;
done/
This does only work for few layers. Some layers have many items inside
and these are not recognized, although I can view them through db.tables
-p.:
/ERROR: Layer<schema.layername> not available/
any ideas?
_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user
