cheluna at gmail.com
Mon Nov 2 05:28:26 EST 2009
I'll try... :) I'll let you know... I hope it's not a WinGrass problem.
By the way, can you tell me what software are you using instead of WinGRASS?
Enrico R. Crema wrote:
> Hi Consuelo,
> If you are importing an ESRI created ASCII file use r.in.arc instead
> of r.in.ascii. The headers of ESRI's ASCII file are in fact slightly
> different from the ones created by r.out.ascii, so this might be the
> reason. I'm not using WinGRASS anymore though, so there are remote
> chances that this is a wingrass problem, but worth have a try with
>> Date: Fri, 30 Oct 2009 02:58:42 -0700 (PDT)
>> From: cheluna <cheluna en gmail.com>
>> Subject: [GRASS-windows] r.in.ascii
>> To: grass-windows en lists.osgeo.org
>> Message-ID: <1256896722991-3917960.post en n2.nabble.com>
>> Content-Type: text/plain; charset=us-ascii
>> Hello to everyone!
>> I have a question. I'm not sure if I'm doing something wrong or
>> what. I'm
>> trying to import an ASCII file into WinGrass (using Phyton
>> interface). The
>> file was created with ArcInfo. The file is a 5.3 MB *asc file. But
>> it is
>> taking ages in importing it and after 21 hours, I gave in. Is that
>> Can it take that long? Or did I do something wrong?
>> I'm using Windows Xp Sp3 on a Dell XPS M1210. I have installed Grass
>> OsGeo4W. Anyone has a clue?
>> View this message in context:
>> Sent from the Grass - Win mailing list archive at Nabble.com.
>> grass-windows mailing list
>> grass-windows en lists.osgeo.org
>> End of grass-windows Digest, Vol 38, Issue 8
> grass-windows mailing list
> grass-windows en lists.osgeo.org
View this message in context: http://n2.nabble.com/r-in-ascii-tp3919908p3930959.html
Sent from the Grass - Win mailing list archive at Nabble.com.
More information about the grass-windows