[GRASS-dev] Handling of Python scripts on MS Windows

[Enrico Gallo]

Dear list,

in my very limited experience, the same Python script for GRASS always
runs without problems inside QGIS-GRASS Processing Plugin but
sometimes fails in GRASS Enviroment, if other Python are installed on
the PC (Stand alone, ARCGIS)
Could be QGIS-GRASS Processing Initialization investigated?

regards

enrico gallo
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.profile limits in Windows 7

[Hamish]

Hamish wrote:
>> what we should do is explicitly look for "profile=-" for
>> reading from stdin, to make it more clear that it exists. another
>> more GUI friendly way is to add a new option for an input file, which
>> would be mutually exclusive with the profile=[east,north[,east,north,...]
>> method of using the module.

Vaclav:
> I agree with more GUI friendly way.

Actually it was the only way, since profile= expects comma separated
pairs, and the parser (if it was working!) refuses to accept just
one "-" for the option.

So now in trunk r59033 profile= only accepts sets of coord pairs,
and for stdin you have to use coordinate_file="-".

> Once done in r.profile, this functionality will be instantly
> available for MS Windows users (using only GUI).

fwiw both  Note that currently when you forget to fill `profile` in GUI and
> press Run, you will get strange behavior.

Now it should be better, you have to leave profile= blank and also
add "-" to the coordinate_file= option. Still possible to get stuck waiting for 
stdin to close, but much
less probable.


Hamish

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.profile limits in Windows 7

[Helmut Kudrnovsky]

> note WinGRASS binaries are still 32 bit,

actually there is OSGeo4W-64bit ready for testing
(http://trac.osgeo.org/osgeo4w/):

(1) Download the  32bit or  64bit OSGeo4W network installer (previous 32bit
only installer) 

winGRASS6.4.3.-64bit is included.



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/r-profile-limits-in-Windows-7-tp5103303p5103782.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] 7th Bolsena Hacking Event open for registration! - June 1 to 7 2014

[Jeroen Ticheler]

Dear all,I'm proud to invite you for the seventh Bolsena Hacking Event this year from 1 to 7 June 2014. The code sprint focusses collaboration between open source software developers. People can share experiences and come up with creative new ideas and collaborations. The week allows developers to actively work together and get their hands dirty coding great new stuff.You are welcome to sign up and join the group. There is limited space (25 beds with only 13 beds remaining) so please book your place as soon as possible to guarantee your place. Full boarding for the week, including food, is 550 Euro (excl VAT) per person, the same as last years.Sign up and read more at: Bolsena Hacking Event 2014 ( http://wiki.osgeo.org/wiki/Bolsena_Code_Sprint_2014 )Hope to see a good crowd again this year! Ciao,Jeroen
GeoCat introduces Bridge© An extension to ArcGIS© to instantly publish data and metadata on GeoServer and GeoNetwork.See http://geocat.net for more details. Jeroen TichelerGeoCat bvVeenderweg 136721 WD BennekomThe NetherlandsTel: +31 (0)6 81286572http://geocat.netPlease consider the environment before printing this email.



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New GRASS for Mac binaries

[Yann]

Hi Michael,

thanks to Stefano Cavallari (not on the GRASS lists) the bug for other users 
has a temporary solution:

LANG=en_UK.UTF-8 '/Applications/GRASS/GRASS-7.0.app/Contents/MacOS/grass.sh’

This will launch GRASS properly from other users than the main one.
Yann


On Feb 13, 2014, at 1:24, Michael Barton  wrote:

> I still don’t know what has been happening with my attempts to run my own 
> binaries. But following up on thoughts from William and Vaclav, I’m chalking 
> it up to dropbox incomplete syncing. I’ve gone ahead and posted new versions 
> for GRASS 7, GRASS 6.5, and GRASS 6.4 to the web site 
> . If anyone cares to try them and let 
> me know, I’d appreciate it. I’m heading out of town but will see if I can 
> test sometime during the trip.
> 
> Michael
> 
> __
> C. Michael Barton 
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
> Tempe, AZ  85287-2402
> USA
> 
> voice: 
> 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax:  480-965-7671(SHESC), 480-727-0709 (CSDC)
> www: 
> http://csdc.asu.edu, http://shesc.asu.edu
> http://www.public.asu.edu/~cmbarton
> 
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.profile limits in Windows 7

[Enrico Gallo]

2014-02-14 10:10 GMT+01:00 Hamish :
> Hamish wrote:

>> Once done in r.profile, this functionality will be instantly
>> available for MS Windows users (using only GUI).
>
> fwiw both  the same way on MS Windows as in Mac and UNIX. That the MS Windows
> users are not currently getting a command line dos box from the
> default desktop icon is debatably a mis-feature (there's a long
> discussion in a trac ticket about that).

in very truth, I need r.profile in a Python script and 
option value is given using a string variable
I think "
>
>> Note that currently when you forget to fill `profile` in GUI and
>> press Run, you will get strange behavior.
>
> Now it should be better, you have to leave profile= blank and also
> add "-" to the coordinate_file= option. Still possible to get stuck waiting 
> for stdin to close, but much
> less probable.
>
>
> Hamish
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.profile limits in Windows 7

[Vaclav Petras]

On Fri, Feb 14, 2014 at 8:08 AM, Enrico Gallo wrote:

> I think "___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] r.profile interface changes

[Vaclav Petras]

Hi,

Hamish and I did some changes in r.profile. X monitors-related parts of
documentation removed, standard options introduced and most notably, Hamish
added `coordinate_file` option to enable file input and make clear end
checkable when standard input is used.

I'm just unsure about names `coordinate_file` and `profile`. Predefined
name for G_OPT_M_COORDS standard option is `coordinates`, so it will be
good if `profile` would be renamed to `coordinates`. It would also improve
r.profile call syntax from my point of view:

- r.profile input=... profile=
+r.profile input=... coordinates=

Moreover, profile is the output of r.profile, not the input. So, do you
agree with rename of `profile` to `coordinates`?

I'm not sure about `coordinate_file` versus `coordinates_file`. What is
more correct English here?

Note that Grass7/NewFeatures page was not updated yet.

And what about d.where and d.profile linked in r.profile manual? What they
were doing at X monitors? What is their replacement in `g.gui` and `d.mon
wx*`? Do we want for them something like what was recently implemented for
d.out.file? Note that there is currently no way to run wxGUI profile tool
from command line.

Vaclav


[r59031] https://trac.osgeo.org/grass/changeset/59031
[r59033] https://trac.osgeo.org/grass/changeset/59033
[r59052] https://trac.osgeo.org/grass/changeset/59052
[Grass7/NewFeatures] https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures
[r.profile] http://grass.osgeo.org/grass70/manuals/r.profile.html
[d.where] http://grass.osgeo.org/grass70/manuals/d.where.html
[d.profile] http://grass.osgeo.org/grass70/manuals/d.profile.html
[GRASS-dev] r.profile limits in Windows 7
http://lists.osgeo.org/pipermail/grass-dev/2014-February/067354.html
[GRASS-dev] d.out.file
http://lists.osgeo.org/pipermail/grass-dev/2014-February/067362.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.profile interface changes

[Moritz Lennert]

On 14/02/14 17:02, Vaclav Petras wrote:

Hi,

Hamish and I did some changes in r.profile. X monitors-related parts of
documentation removed, standard options introduced and most notably,
Hamish added `coordinate_file` option to enable file input and make
clear end checkable when standard input is used.

I'm just unsure about names `coordinate_file` and `profile`. Predefined
name for G_OPT_M_COORDS standard option is `coordinates`, so it will be
good if `profile` would be renamed to `coordinates`. It would also
improve r.profile call syntax from my point of view:

- r.profile input=... profile=
+r.profile input=... coordinates=

Moreover, profile is the output of r.profile, not the input. So, do you
agree with rename of `profile` to `coordinates`?


+1


Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New GRASS for Mac binaries

[Michael Barton]

Interesting. Thanks.

But in my case, I AM the main user and owner. I THINK it was a problem with my 
Dropbox syncing.

Michael Barton
School of Human Evolution &Social Change
Center for Social Dynamics & Complexity
Arizona State University

...Sent from my iPad

On Feb 14, 2014, at 1:54 AM, "Yann" 
mailto:yche...@gmail.com>> wrote:

Hi Michael,

thanks to Stefano Cavallari (not on the GRASS lists) the bug for other users 
has a temporary solution:

LANG=en_UK.UTF-8 '/Applications/GRASS/GRASS-7.0.app/Contents/MacOS/grass.sh’

This will launch GRASS properly from other users than the main one.
Yann


On Feb 13, 2014, at 1:24, Michael Barton 
mailto:michael.bar...@asu.edu>> wrote:

I still don’t know what has been happening with my attempts to run my own 
binaries. But following up on thoughts from William and Vaclav, I’m chalking it 
up to dropbox incomplete syncing. I’ve gone ahead and posted new versions for 
GRASS 7, GRASS 6.5, and GRASS 6.4 to the web site 
. If anyone cares to try them and let me 
know, I’d appreciate it. I’m heading out of town but will see if I can test 
sometime during the trip.

Michael

__
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
Tempe, AZ  85287-2402
USA

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax:  480-965-7671(SHESC), 480-727-0709 (CSDC)
www:  http://csdc.asu.edu, 
http://shesc.asu.edu
http://www.public.asu.edu/~cmbarton

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New GRASS for Mac binaries

[Vaclav Petras]

On Fri, Feb 14, 2014 at 11:21 AM, Michael Barton wrote:

> I THINK it was a problem with my Dropbox syncing.


Perhaps, it would be safer to sync tar (tar.gz, zip, ...) and add
compression and decompression to your workflow. I'm not sure how Dropbox
handles changes of large amount of strange files.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New GRASS for Mac binaries

[Michael Barton]

That was what I used to do, but have switched to doing this all on DropBox so I 
can work back and forth across different computers. Part of this is a dropbox 
issue, part has to do with connection speeds, and part involves changing some 
of my workflows.

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax:  480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu













On Feb 14, 2014, at 9:40 AM, Vaclav Petras 
mailto:wenzesl...@gmail.com>> wrote:


On Fri, Feb 14, 2014 at 11:21 AM, Michael Barton 
mailto:michael.bar...@asu.edu>> wrote:
I THINK it was a problem with my Dropbox syncing.

Perhaps, it would be safer to sync tar (tar.gz, zip, ...) and add compression 
and decompression to your workflow. I'm not sure how Dropbox handles changes of 
large amount of strange files.

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1983: wingrass: permission denied to open grass70.py

[GRASS GIS]

#1983: wingrass: permission denied to open grass70.py
-+--
 Reporter:  mmetz|   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  7.0.0
Component:  Installation | Version:  svn-trunk
 Keywords:  wingrass, installer  |Platform:  MSWindows 7  
  Cpu:  All  |  
-+--

Comment(by marisn):

 Today I got hit by the same error on XP machines with SVN nightly
 WinGRASS-7.0.svn-r59013M-869

 As I had to start a lab work, I fixed all machines by granting "execute"
 rights on whole GRASS folder in "Program Files" (with all child files and
 folders!) and thus don't have exact error message any more but it was just
 something printed in the terminal like "Permission denied, error 13"

 Afterwards issue was fixed, still every time GRASS 7 was thinking that it
 has been lunched for the first time and asked to set up GISDBASE =>
 somewhere else some permission is still missing? (Just a question if
 somebody has solved it)

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.profile interface changes

[Hamish]

Vaclav wrote:

> Hamish and I did some changes in r.profile. X monitors-related parts
> of documentation removed, standard options introduced and most
> notably, Hamish added `coordinate_file` option to enable file input
> and make clear end checkable when standard input is used.
> 
> I'm just unsure about names `coordinate_file` and `profile`.
> Predefined name for G_OPT_M_COORDS standard option is `coordinates`,
> so it will be good if `profile` would be renamed to `coordinates`. It
> would also improve r.profile call syntax from my point of view:
>
> - r.profile input=... profile= 
> +r.profile input=... coordinates= 
> 
> Moreover, profile is the output of r.profile, not the input. So,
> do you agree with rename of `profile` to `coordinates`?

sure, done in svn.


> I'm not sure about `coordinate_file` versus `coordinates_file`.
> What is more correct English here?

I renamed it to file=. If you are using the command line having
both coordinates= and coordinate(s)_file= means you have to type
the whole word, which is really annoying. (yes, there's the c_f=
trick, but it's not widely known.

> Note that Grass7/NewFeatures page was not updated yet.

todo.

> And what about d.where and d.profile linked in r.profile manual? What
> they were doing at X monitors?

Both now removed from the G7 help page. d.where lets you click on the
map canvas and it prints the coord as text on the terminal. From
there you could redirect them to a file or as in the commented out
example in the r.profile help page, pipe it directly into r.profile
for a do-it-yourself interactive input & profile tool.

d.profile is an interactive tool similar to the wxGUI profile tool,
and is replaced by it.

> Note that there is currently no way to run wxGUI profile tool
> from command line.

See also r.transect by the way, which is an alternate front-end to
r.profile.


regards,
Hamish
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.profile limits in Windows 7

[Hamish]

Hamish:
> >>  note WinGRASS binaries are still 32 bit,

Helmut wrote:
> actually there is OSGeo4W-64bit ready for testing
> (http://trac.osgeo.org/osgeo4w/):
> 
> (1) Download the  32bit or  64bit OSGeo4W network installer (previous 32bit
> only installer) 
> 
> winGRASS6.4.3.-64bit is included.

great news! Has anyone tested with big data? 


Hamish

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev