Seb wrote: > I traced one of the problems with my attempts to import vector > and associated attribute tables. I found that if some rows > contain null values for at least one column, then v.in.ascii > cannot parse the table correctly.
I don't think it's related, but FYI outstanding v.in.ascii bug: http://trac.osgeo.org/grass/ticket/198 Hamish _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
