Opened 9 years ago

Closed 9 years ago

#2518 closed defect (worksforme)

v.in.ogr

Reported by: baharmon Owned by: grass-dev@…
Priority: normal Milestone:
Component: Vector Version: svn-releasebranch70
Keywords: v.in.ogr Cc:
CPU: OSX/Intel Platform: MacOSX

Description

v.in.ogr did not find any layers for shapefiles. I tried both source type file and directory. This was with the daily build from Dec 22nd - GRASS 7.0.0svn(r63776).

I checked and it worked fine with an older installation of GRASS 7.1svn (r62255).

Change History (4)

comment:1 by helena, 9 years ago

Platform: MSWindows 8MacOSX

I can confirm issues with shape file import - I was trying to create a new location using shape file - the shape file was recognized and the location was created but when I answered yes on importing the file I got error stating that the format is not recognized. I am running this with GRASS7.0.0.svn r61585M compiled by Anna on Yosemite (it is really nice). We did not get the sqlite working but I am not sure it is related to the shape import issues. I was able to import the file using v.in.ogr from command line without the table. Perhaps this is something already fixed in 7.1 which needs backporting (or was just backported by Martin?)

comment:2 by annakrat, 9 years ago

Keywords: v.in.ogr added

I tested v.in.ogr when creating new location based on a shapefile and it's working on Ubuntu with the most recent versions of 70 and trunk. It would be good to test it on the newest versions and see if you are describing the same problem and if it depends on shape file data.

comment:3 by helena, 9 years ago

It works for Michaels binaries with GRASS7.0.0.beta4, so I think it was our problem with selfcompiled GRASS7. Anna, if you think it is OK, please close it.

in reply to:  3 comment:4 by annakrat, 9 years ago

Resolution: worksforme
Status: newclosed

Replying to helena:

It works for Michaels binaries with GRASS7.0.0.beta4, so I think it was our problem with selfcompiled GRASS7. Anna, if you think it is OK, please close it.

The original issue was on Windows, but I will assume it was resolved. Please reopen if needed.

Note: See TracTickets for help on using tickets.