If a layer is not given, the available layers are printed and the module exits.
The optional spatial parameter defines spatial query extents. This parameter allows to restrict the region to a spatial subset while importing the data. All vector completely or partially falling into this rectangle subregion are imported.
Topology cleaning on areas is automatically performed, but may fail in special cases (then use v.clean).
Further available drivers such as UK .NTF, SDTS, TIGER, IHO S-57 (ENC), DGN, GML, AVCBin, REC, Memory, OGDI, and PostgreSQL depend on the local installation (OGR library), for details see OGR web site.
If the user wishes to ignore the difference between the apparent coordinate system of the source data and the current location, they may pass the -o flag to override the projection check.
If the user wishes to import the data with the full projection definition, it is possible to have v.in.ogr automatically create a new location based on the projection and extents of the file being read. This is accomplished by passing the name to be used for the new location via the location parameter. Upon completion of the command, a new location will have been created (with only a PERMANENT mapset), and the vector map will have been imported with the indicated output name into the PERMANENT mapset.
Support of database schema:
First v.database has to be used to set a default schema for the new vector table(s). In db.* modules the schema name must be always specified if used. Example:
v.database driver=pg database=test schema=user1
v.in.ogr dsn=./ layer=river output=river # -> table user1.river
db.select table=user1.river
The user can ignore schemas, if desired:
v.database driver=pg database=test
v.in.ogr dsn=./ layer=river output=river # -> table public.river
db.select table=river
[A-Za-z][A-Za-z0-9_]*That means that SQL neither supports '.' (dots) nor '-' (minus) nor '#' in table column names. Also a table name must start with a character, not a number.
Last changed: $Date: 2005/01/24 01:38:20 $