Send grass-windows mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.osgeo.org/mailman/listinfo/grass-windows
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of grass-windows digest..."


Today's Topics:

   1. No such file or directory (Peter Brooks)
   2. Re: No such file or directory (Markus Neteler)
   3. Re: No such file or directory (Peter Brooks)
   4. Re: No such file or directory (Markus Neteler)
   5. Re: No such file or directory (Peter Brooks)
   6. Re: No such file or directory (Markus Neteler)


----------------------------------------------------------------------

Message: 1
Date: Fri, 14 Aug 2009 11:53:24 +0100
From: "Peter Brooks" <[email protected]>
Subject: [GRASS-windows] No such file or directory
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII

Hi, I've downloaded the 'ncexternal' data from the grassbook website -
  I created a 'ncexternal' mapset folder and copied the files into 
there.

Whenever I try the examples that access import or process these files 
I get an error message in GRASS. For example on p62

r.in.poly in=newfacility.txt out=new_facility_1m

gives

newfacility.txt: No such file or directory

although the file is there. I have tried adding the folder to the 
Windows path, but that doesn't solve it.

I am probably doing something stupid or have missed (or skipped :) 
something obvious... I would be grateful for any help.

Many thanks
Peter


------------------------------

Message: 2
Date: Fri, 14 Aug 2009 13:44:26 +0200
From: Markus Neteler <[email protected]>
Subject: Re: [GRASS-windows] No such file or directory
To: Peter Brooks <[email protected]>
Cc: [email protected]
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Aug 14, 2009 at 12:53 PM, Peter Brooks<[email protected]> wrote:
> Hi, I've downloaded the 'ncexternal' data from the grassbook website -
>  I created a 'ncexternal' mapset folder and copied the files into
> there.
>
> Whenever I try the examples that access import or process these files
> I get an error message in GRASS. For example on p62
>
> r.in.poly in=newfacility.txt out=new_facility_1m
>
> gives
>
> newfacility.txt: No such file or directory
>
> although the file is there. I have tried adding the folder to the
> Windows path, but that doesn't solve it.

Peter - two ideas:

- does it work when you use the GUI (i.e., launch r.in.poly without
  parameters)?
- does the path to newfacility.txt contain white space? We are still
   hunting down those cases where it fails

best
Markus


------------------------------

Message: 3
Date: Fri, 14 Aug 2009 13:58:36 +0100
From: "Peter Brooks" <[email protected]>
Subject: Re: [GRASS-windows] No such file or directory
To: Markus Neteler <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

Hi Markus, 

 - yes it works using the GUI (should have thought to try this)

 - yes, the path contains whitespaces. Using speech or quote marks 
around the full path + filename sorts it.  Falls over without. A path 
without whitespace works but requires unix style forward slashes.


(I stupidly thought that by creating a mapset and saving the data 
into that folder GRASS would be able to find it... didn't think I 
would need the full path. Will now move the data to a c:\ncexternal 
folder to reduce typing :-)

Many thanks
Peter


On 14 Aug 2009 at 13:44, Markus Neteler wrote:

On Fri, Aug 14, 2009 at 12:53 PM, Peter Brooks<[email protected]>
wrote: > Hi, I've downloaded the 'ncexternal' data from the grassbook
website - >  I created a 'ncexternal' mapset folder and copied the
files into > there. > > Whenever I try the examples that access 
import
or process these files > I get an error message in GRASS. For example
on p62 > > r.in.poly in=newfacility.txt out=new_facility_1m > > gives
> > newfacility.txt: No such file or directory > > although the file
is there. I have tried adding the folder to the > Windows path, but
that doesn't solve it.

Peter - two ideas:

- does it work when you use the GUI (i.e., launch r.in.poly without
  parameters)?
- does the path to newfacility.txt contain white space? We are still
   hunting down those cases where it fails

best
Markus


------------------------------

Message: 4
Date: Fri, 14 Aug 2009 15:14:17 +0200
From: Markus Neteler <[email protected]>
Subject: Re: [GRASS-windows] No such file or directory
To: Peter Brooks <[email protected]>
Cc: [email protected]
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

hi Peter,

On Fri, Aug 14, 2009 at 2:58 PM, Peter Brooks<[email protected]> wrote:
> Hi Markus,
>
>  - yes it works using the GUI (should have thought to try this)

ok, good.

>  - yes, the path contains whitespaces. Using speech or quote marks
> around the full path + filename sorts it.  Falls over without. A path
> without whitespace works but requires unix style forward slashes.

I darkly remember that we added some Windows-magic for that
elsewhere but I don't remember how.


> (I stupidly thought that by creating a mapset and saving the data
> into that folder GRASS would be able to find it...

It does so on non-Windows and it should "learn" it also on Windows!

I tried:

GRASS 6.4.0svn (nc_spm_08): > r.in.poly in=/tmp/dd\ dd/newfacility.txt
out=new_facility_1m
Writing raster map...
 100%

GRASS 6.4.0svn (nc_spm_08): > cd /tmp/dd\ dd/
GRASS 6.4.0svn (nc_spm_08):/tmp/dd dd > r.in.poly in=./newfacility.txt
out=new_facility_1m --o
Writing raster map...
 100%

Works. So it may be rather the slash stuff than white space?

> didn't think I
> would need the full path. Will now move the data to a c:\ncexternal
> folder to reduce typing :-)

Yes, for now - we hope to figure out the problem.

Please consider to open a bug report with these findings.

best
Markus


------------------------------

Message: 5
Date: Fri, 14 Aug 2009 14:52:55 +0100
From: "Peter Brooks" <[email protected]>
Subject: Re: [GRASS-windows] No such file or directory
To: Markus Neteler <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

No, I think it is whitespace...  I'm trying to use the 'cmd >' field 
in the 'GRASS GIS Layer Manager' (the new wxPython GUI).  I guess 
this is what a Windows user would try to do :-)

I tried adding a space to the folder name (= 'c:\nc external'), 
forward slashes don't help but speech or quote marks do.

(I think the same thing happens with all r.in commands if they are 
looking for external files - is this to be expected?)


Using the GRASS Command line utility (DOS shell type interface):

GRASS 6.4.0svn (North-Carolina)> cd c:/nc external
The system cannot find the path specified.

GRASS 6.4.0svn (North-Carolina)> cd c:\nc external
(works ok)


Thanks
Peter


On 14 Aug 2009 at 15:14, Markus Neteler wrote:

hi Peter,

On Fri, Aug 14, 2009 at 2:58 PM, Peter Brooks<[email protected]>
wrote: > Hi Markus, > >  - yes it works using the GUI (should have
thought to try this)

ok, good.

>  - yes, the path contains whitespaces. Using speech or quote marks
> around the full path + filename sorts it.  Falls over without. A
> path without whitespace works but requires unix style forward
> slashes.

I darkly remember that we added some Windows-magic for that
elsewhere but I don't remember how.


> (I stupidly thought that by creating a mapset and saving the data
> into that folder GRASS would be able to find it...

It does so on non-Windows and it should "learn" it also on Windows!

I tried:

GRASS 6.4.0svn (nc_spm_08): > r.in.poly in=/tmp/dd\ 
dd/newfacility.txt
out=new_facility_1m Writing raster map...
 100%

GRASS 6.4.0svn (nc_spm_08): > cd /tmp/dd\ dd/
GRASS 6.4.0svn (nc_spm_08):/tmp/dd dd > r.in.poly 
in=./newfacility.txt
out=new_facility_1m --o Writing raster map...
 100%

Works. So it may be rather the slash stuff than white space?

> didn't think I
> would need the full path. Will now move the data to a c:\ncexternal
> folder to reduce typing :-)

Yes, for now - we hope to figure out the problem.

Please consider to open a bug report with these findings.

best
Markus


------------------------------

Message: 6
Date: Fri, 14 Aug 2009 16:01:44 +0200
From: Markus Neteler <[email protected]>
Subject: Re: [GRASS-windows] No such file or directory
To: Peter Brooks <[email protected]>
Cc: GRASS developers list <[email protected]>,
        [email protected]
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

(cc grass-dev)

[r.in.poly fails to read text input file on Windows/CMD line]

On Fri, Aug 14, 2009 at 3:52 PM, Peter Brooks<[email protected]> wrote:
> No, I think it is whitespace...  I'm trying to use the 'cmd >' field
> in the 'GRASS GIS Layer Manager' (the new wxPython GUI).  I guess
> this is what a Windows user would try to do :-)
>
> I tried adding a space to the folder name (= 'c:\nc external'),
> forward slashes don't help but speech or quote marks do.
>
> (I think the same thing happens with all r.in commands if they are
> looking for external files - is this to be expected?)
>
> Using the GRASS Command line utility (DOS shell type interface):
>
> GRASS 6.4.0svn (North-Carolina)> cd c:/nc external
> The system cannot find the path specified.
>
> GRASS 6.4.0svn (North-Carolina)> cd c:\nc external
> (works ok)

@devs:
Perhaps we need some more G_convert_dirseps_*() magic?

Markus


------------------------------

_______________________________________________
grass-windows mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-windows


End of grass-windows Digest, Vol 36, Issue 6
********************************************

Reply via email to