PostGIS: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
mNo edit summary
Line 8: Line 8:
* {{cmd|grass-pg|desc=PostgreSQL DB driver in GRASS}} help page
* {{cmd|grass-pg|desc=PostgreSQL DB driver in GRASS}} help page
* {{cmd|grass-odbc|desc=ODBC DB driver in GRASS}} help page
* {{cmd|grass-odbc|desc=ODBC DB driver in GRASS}} help page
== Link to external dataset ==
* input maps: {{cmd|v.external|version=70}}
**in GRASS 6 the map links created by {{cmd|v.external}} are ''read only''
**GRASS 7 supports also write access to the map links, see [[Working with external data in GRASS 7#Vector data|working with external data in GRASS 7]] for details
* output maps: {{cmd|v.external.out|version=70}} (GRASS 7 only)


== Import into GRASS ==
== Import into GRASS ==
Line 31: Line 24:


== Link to GRASS ==
== Link to GRASS ==
* input maps: {{cmd|v.external|version=70}}
**in GRASS 6 the map links created by {{cmd|v.external}} are ''read only''
**GRASS 7 supports also write access to the map links, see [[Working with external data in GRASS 7#Vector data|working with external data in GRASS 7]] for details
* output maps: {{cmd|v.external.out|version=70}} (GRASS 7 only)


You can register a PostGIS layer into GRASS using {{cmd|v.external}}, eg. PostGIS layer 'lakes' from database 'pgis_nc'
You can register a PostGIS layer into GRASS using {{cmd|v.external}}, eg. PostGIS layer 'lakes' from database 'pgis_nc'

Revision as of 14:07, 27 November 2012

See also working with external data in GRASS 7.

Help pages

Import into GRASS

  1. v.in.ogr - imports geometry data from PostGIS into native GRASS vector format, attributes are stored using default DB settings (see db.connect for details)
  2. v.clean - clean up data after import

Note 1: There is a fundamental difference between the PostGIS format which is non-topological (OGC simple feature-based) 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...

Note 2: GRASS 7 allows reading and writing topological PostGIS data (see PostGIS Topology for details).


Load video
YouTube
Importing PostGIS layers into GRASS

Link to GRASS

You can register a PostGIS layer into GRASS using v.external, eg. PostGIS layer 'lakes' from database 'pgis_nc' 

v.external dsn=PG:dbname=pgis_nc layer=lakes

It will create in the current mapset new vector map 'lakes', the module also builds pseudo-topology for this map,

To link a PostGIS layer from non-public schema 

v.external dsn=PG:<connection sting> layer=<schema>.<layer> output=<layer>

Important note: In GRASS 6 this link is read-only, in GRASS 7 it's possible to modify linked layers directly via OGR library, see working with external data in GRASS 7.

You can also link a GRASS layer to a PostgreSQL attribute table, though v.db.connect.


Load video
YouTube
Link PostGIS layers as GRASS vector maps

Export to PostGIS

To export GRASS vector map layer to PostGIS layer use v.out.ogr, eg. 

v.out.ogr in=lakes@PERMANENT dsn=PG:dbname=pgis_nc format=PostgreSQL type=area

Note that exporting data can be quite time-consuming task, especially when input vector map attributes are stored in DBF format. It's recommended to store attribute data in SQLite format rather then in old-fashioned DBF format. For example when exporting vector map 'lakes' from North Carolina sample dataset.

  • Attributes in DBF format
real    1m15.072s
user    1m6.160s
sys     0m3.824s
  • Attributes in SQLite format
real    0m11.796s
user    0m5.564s
sys     0m4.148s


Load video
YouTube
Creating model which exports all GRASS vector maps from given mapset to PostGIS database
Load video
YouTube
Creating model which exports all GRASS vector maps from given mapset to PostGIS database (including schema)

1) create schema with name of input mapset

2) copy vector maps from selected mapset to the current and stores their attributes in SQLite database

3) exports GRASS vector maps to the selected PostGIS database

See also wxGUI Modeler.

Direct access to PostGIS data

Important note: Direct read/write access is implemented only in GRASS 7.

Direct read access

GRASS 7 enables the users to access PostGIS layers directly via virtual mapset 'OGR' and modules parameters map=OGR_datasource@OGR and layer=OGR_layer, eg. to access PostGIS layer 'lakes' from database 'pgis_nc' 

v.info map=PG:dbname=pgis_nc@OGR layer=lakes

The direct read access avoids need of creating a link via v.external and accessing PostGIS data directly without creating any data elements in the current mapset. The main drawback of direct read access is that the pseudo-topology is built each time when accessing the data.

Direct write access

Note: direct write access via OGR library is currently under development (GRASS 7 only).

GRASS 7 allows to write output vector map directly via OGR library. For defining output vector data format is designed v.external.out module. For example 

v.external.out dsn=PG:dbname=pgis_nc format=PostgreSQL

causes that every newly created vector map will be stored as PostGIS layer in database 'pgis_nc' without any data elements created in the current mapset. Such PostGIS layer can be linked afterwards via v.external or accessed directly as described in the section above. For example 

v.extract input=lakes out=reservoir where="FTYPE = 'RESERVOIR'"
v.info map=PG:dbname=pgis_nc@OGR layer=reservoir

To switch back to GRASS native format enter 

v.external.out -r

See also

Retrieved from "https://grasswiki.osgeo.org/w/index.php?title=PostGIS&oldid=17028"