I've noticed that using avcimport (which converts .e00 files to binary coverages) greatly speeds up import of .e00 files when you use ogr2ogr. So v.in.ogr probably uses avcimport for this reason.
Bob Moskovitz Research Analyst I Seismic Hazard Evaluation Project California Geological Survey http://gmw.consrv.ca.gov/shmp CONFIDENTIALITY NOTICE: This communication is intended only for the use of the individual or entity to which it is addressed. This message contains information from the State of California, California Geological Survey, which may be privileged, confidential and exempt from disclosure under applicable law, including the Electronic Communications Privacy Act. If the reader of this communication is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. > -----Original Message----- > From: [email protected] > [mailto:[email protected]]on Behalf Of Rich Shepard > Sent: Tuesday, November 17, 2009 4:51 PM > To: [email protected] > Subject: [GRASS-user] v.in.e00 vs. v.in.ogr > > > Looking for the v.in.ogr man page I was reminded that > there is a v.in.e00. > Should I use the latter rather than the former? > > Tried running v.in.e00. After entering the .e00 file name > and specifying > 'area' for the type I and saw this fatal error message: > > ERROR: 'avcimport' program not found. Install it first. > > The source file is an ASCII .e00, not compressed and not needing > comversion from ARC/Info binary to exchange format. > > What have I missed here? > > Rich > _______________________________________________ > grass-user mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-user > _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
