PostGIS: Difference between revisions
Jump to navigation
Jump to search
(link to Tutorial by Micha Silver) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
See also [[Working with external data in GRASS 7]] | |||
__TOC__ | |||
== Help pages == | |||
* GRASS {{cmd|databaseintro}} help page | * GRASS {{cmd|databaseintro}} help page | ||
| Line 7: | Line 9: | ||
* {{cmd|grass-odbc}} help page | * {{cmd|grass-odbc}} help page | ||
== Link to external dataset == | |||
* {{cmd|v.external}} | * {{cmd|v.external}} | ||
== Import into GRASS == | |||
# {{cmd|v.in.ogr}} (import only geometry column from postgresql/postgis) | # {{cmd|v.in.ogr}} (import only geometry column from postgresql/postgis) | ||
# {{cmd|v.clean}} | # {{cmd|v.clean}} | ||
| Line 26: | Line 29: | ||
== See also == | == See also == | ||
* [http://www.surfaces.co.il/?p=645 Tutorial by Micha Silver] | * [http://www.surfaces.co.il/?p=645 Tutorial by Micha Silver] | ||
[[Category: FAQ]] | [[Category: FAQ]] | ||
Revision as of 12:58, 27 February 2011
See also Working with external data in GRASS 7
Help pages
- GRASS databaseintro help page
- GRASS sql help page
- grass-pg help page
- grass-odbc help page
Link to external dataset
Import into GRASS
There is a fundamental difference between the PostGIS format which is non-topological and the internal GRASS format which is topological and which, thus, does not really allow for overlapping polygons. You can digitize them, but they are not really useful...
You cannot directly process a PostGIS table in GRASS. GRASS has its own internal vector format.
You can link a GRASS layer to a PostgreSQL attribute table, though. v.db.connect