Opened 8 years ago

Closed 3 years ago

#1258 closed defect (wontfix)

Trouble with external OGR sources and relative paths (v.external)

Reported by: benducke Owned by: grass-dev@…
Priority: normal Milestone: 7.0.5
Component: Vector Version: svn-trunk
Keywords: v.external, OGR Cc:
CPU: Unspecified Platform: Linux

Description

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).

Change History (3)

comment:1 Changed 8 years ago by martinl

Milestone: 6.4.17.0.0

comment:2 Changed 3 years ago by martinl

Milestone: 7.0.07.0.5

comment:3 Changed 3 years ago by martinl

Resolution: wontfix
Status: newclosed

You need to use full path. Relative path will behave like this. There is nothing to be fixed, it's a "feature".

Note: See TracTickets for help on using tickets.