[GRASSLIST:5277] Re: ARCViewImport too slow

[Nick Cahill]

Baylor University is currently experiencing E-mail problems.  We cannot assure that your message will be delivered in a timely manner.  You do not neeed to re-send your message, it has been safely recieved by our system for eventual delivery to the recipient.  We intend to have our system fully restored by Monday, Jaunary 13. 
-------------- next part --------------
Try exporting your DEM as a GRID from ArcView; then import the grid 
using r.in.gdal. When you export the grid you'll get a series of files 
like:


w001001x.adf
w001001.adf
sta.adf
log
dblbnd.adf
hdr.adf


In r.in.gdal, select the largest file (in the case above, w001001.adf, 
which is 13.3 MB). It should import fine. This has worked for me. 
Shapefiles are vector files, which aren't really appropriate for a DEM.

Good luck,

Nick Cahill



On Friday, January 3, 2003, at 12:25  PM, javier garcia wrote:

> Hello all and happy new year!
>
> I'm working with someone who uses ArcView and I need a dem that is 
> stored in
> his ArcView. We are having serious problem importing it. In fact we 
> can't do
> it.
> We have export it as a shape file from ArcView. And I'm using 
> r.in.shape to
> import it. The translation into a ascii file is slow but a file is 
> obtained
> (A 4.5 millions of lines one!), but r.in.poly is dispiriting slow.
> After 14 hours it is in the third pass of 26.
> I've stopped it because this is clearly not a good method to operate.
> Has anyone made this kind of ArcView export-GRASS import with 
> distributed
> data as a dem with success?
>
> Thanks and regards
>
> -- 
> A. Javier Garc?a
> Water and Soil Conservation Department
> CEBAS-CSIC
> Apartado 4195
> 30080 Murcia
> Spain
>
> Tel.: +34 968 39 63 90
> Fax: +34 968 39 62 13
>