[GRASS-user] v.in.ogr problem

GRASS GRASS user
, ,
1

Hi you all!

I’m having problems with v.in.ogr. This command fails and stops in the middle of the process (I’m working on the http://www.ing.unitn.it/~grass/docs/tutorial_62_en tutorial). The output tab of this tool says it’s “Importing map 1755 features…” but nothing happens (and terminal don’t show me the prompt). When I close v.in.org and ask to display the “imported” vector, it just shows an insignificant part of the vector (compared to the picture on tutorial). And the output to d.vect says that “coor files of vector contours is larger than it should be (239 bytes excess)” and "cannot display areas, topology not available’. What should that mean?

I’ve searched on the mailing list and someone told in a similar situation that it’s probably due to trying to import a big dataset, but I don’t think that’s the case because the data is from a tutorial and have been tested.

I’ve tried others gdal tools and it worked fine: the OGR Vector Converter in QGIS (I’ve tested converting shp->kml) and the gdal_translate and gdalwarp on terminal.

I’m working in Ubuntu 8.10 and I’ve installed GRASS through apt. Any guess of what’s wrong (or what I’m doing wrong)?

Thanks

Rafael

2

Hello Maris, Hello all!

Problem solved (I have to put this on topic?)

I’m not sure if the file I’ve tested is so big to GRASS, but I left the v.in.ogr working for a hole afternoon and nothing. So I tried a smaller data and still nothing. Then I did some search on the net and I found a tip that solved my problem. At QGIS forum I found a topic discussing the same problem (http://forum.qgis.org/viewtopic.php?f=2&t=4451#p7490). A post there send me to a Jachym Cepicky’s post at another forum (http://n2.nabble.com/grass-gdal-ubuntu-issue-solved-(-)-td2352498.html) with the solution.

Well, I reintalled GRASS by Jachim’s repository, and the v.in.ogr worked fine. I have also tested this tool in QGIS (grass plugin) and there was no problem. By the way, grass imported that “big data” in a glimpse! : )

Cheers!

Rafael

Hello.
How many vector features are in that file? Could it be that v.in.ogr
is still processing input file? On some files it may take looooong
time to import vector data.

Maris.