Version 44 (modified by 15 years ago) ( diff ) | ,
---|
Vector library in GRASS 7
Table of Contents
See:
File-based spatial index
OGR interface
Direct OGR read access
Capability to read OGR layers directly without linking them via v.external
. Example:
v.info map=~/shapefiles/@OGR layer=busstopsall v.extract input=PG:dbname=nc_spm_08@OGR layer=busstopsall where="STREET_1 = 'William Moore Dr.'" output=b1
List of modules which supports direct OGR read access ((*) indicates work in progress):
v.info
- r39161v.db.connect
- r39538v.extract
- r39621v.db.select
- r39556v.buffer
- r39809v.category
- r39812v.class
- r39813v.clean
- r39814v.delaunay
- r39821v.dissolve
- r39822v.distance
- r39823v.drape
- r39826v.extrude
- r39827v.generalize
- r39828v.hull
- r39829v.kcv
- r39832v.neighbors
- r39834v.normal
- r39839v.out.ascii
- r39881v.out.dxf
- r39882v.out.ogr
- r39883v.out.pov
- r39884v.out.svg
- r39885v.overlay
- r39895v.parallel
- r39896
Direct OGR write access
Capability to write OGR layers directly without need to store data in the native vector format and then exporting data using v.out.ogr
. E.g.
# input: GRASS data # output: PostGIS database v.extract map=obce where="NAZEV = Solany" output=PG:dbname=gisdb@OGR olayer=obce # input: PostGIS layer, ESRI Shapefile # output: PostGIS database v.select ainput=PG:dbname=gisdb@OGR alayer=zeleznice \ binput=shps@OGR blayer=obce operator=intersects \ output=PG:dbname=gisdb@OGR olayer=obce_zelez
Redesign support structures
Reduce memory requirements particularly for points and lines. See ticket:542.
TODO
3D vector data support
TODO
See also:
Note:
See TracWiki
for help on using the wiki.