[GRASS-dev] Bad map deletion beahviour with external OGR sources

GRASS GRASS developer
1

I Think I found a problem with OGR datasources linked
in using v.external.

If I change into a directory with shapefiles and then
issue the following to link in the data in "myShapefile.shp":

  v.external dsn=. layer=myShapefile output=linked_in

And then change into another directory and issue any command
that wants to work on "linked_in", e.g.:
  
  g.remove vect=linked_in
  v.info linked_in

I get:

  ERROR: Cannot open layer 'myShapefile'

But when I change back into the directoy where I used
to be when running the v.external command, it works.

So I think v.external should take care to always link
to the absolute location of the source in the file
system (if I specify "dsn=" as an absolute path,
things work fine).

Ben

------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.

2

Hi,

2011/1/14 Benjamin Ducke <benjamin.ducke@oxfordarch.co.uk>:

I Think I found a problem with OGR datasources linked
in using v.external.

If I change into a directory with shapefiles and then
issue the following to link in the data in "myShapefile.shp":

v.external dsn=. layer=myShapefile output=linked_in

And then change into another directory and issue any command
that wants to work on "linked_in", e.g.:

g.remove vect=linked_in
v.info linked_in

I get:

ERROR: Cannot open layer 'myShapefile'

But when I change back into the directoy where I used
to be when running the v.external command, it works.

So I think v.external should take care to always link
to the absolute location of the source in the file
system (if I specify "dsn=" as an absolute path,
things work fine).

at least it should print a warning. Please report it on trac. Martin

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa