going back to your original question, if you use --overwrite
with the master script, it should be set for everything called
by the master script as the GRASS_OVERWRITE enviro var will
be set by the parser. You can test to see if it is set with:
import os
if "GRASS_OVERWRITE" in os.environ:
Hmmm. This should have worked. But...
The options (copied from another script) are written as...
#%option G_OPT_R_INPUT
#% key: ms3
#% description: Input raster map for red channel
#%end
So there is no way to add "new" unless I redo the options section. This way of
doing the interface is new,
Thanks. I'll try one of these methods.
Michael
On Jun 27, 2012, at 5:06 PM, Glynn Clements wrote:
>
> Michael Barton wrote:
>
>> I thought from reading past mail posts that -o and --o and --overwrite
>> all set the overwrite flag.
>
> The last two do; the first one is just a normal flag.
>
>
Thanks much!
Michael
On Jun 27, 2012, at 2:55 PM, Martin Landa wrote:
> 2012/6/27 Michael Barton :
>> Yes
>
> so it's done (just check revisions I already noted)
>
> --
> Martin Landa * http://geo.fsv.cvut.cz/~landa
_
C. Michael Barton
Visiting Scientist, Integrated Scie
Michael Barton wrote:
> I thought from reading past mail posts that -o and --o and --overwrite
> all set the overwrite flag.
The last two do; the first one is just a normal flag.
Historically, modules used -o for overwrite, but that is deprecated in
favour of the --o/--overwrite option which is
Michael wrote:
> A couple months ago, we discovered and fixed a bug that kept
> people from using the attribute table manager in GRASS 6. This
> could not be fixed in the GRASS 6.4.2 code because it is frozen.
> But the recommendation was to have binary maintainers fix it in
> their distributions.
Martin wrote:
> I would like to suggest to replace `r.in.wms` module
> available in trunk by the new python module `r.in.wms2`
> (which i currently available from addons [1]).
I haven't tested it, but in general this sounds like a good
idea to me.
Note the OnEarth WMS server in the examples page
2012/6/27 Michael Barton :
> Yes
so it's done (just check revisions I already noted)
--
Martin Landa * http://geo.fsv.cvut.cz/~landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
I thought from reading past mail posts that -o and --o and --overwrite all set
the overwrite flag.
I test for overwrite with grass.overwrite()
But how do I include a check box for the overwrite flag in the GUI specs (for
g.parser)?
Putting in an "o" flag does not seem to set the overwrite flag
Yes
Michael
On Jun 27, 2012, at 12:25 PM, Martin Landa wrote:
> 2012/6/27 Michael Barton :
>> Thanks. I thought you were only referring to the help information, not the
>> source compiling dependencies.
>
> by that you mean REQUIREMENT.html file?
>
> Martin
>
> --
> Martin Landa * http://g
2012/6/27 Michael Barton :
> Thanks. I thought you were only referring to the help information, not the
> source compiling dependencies.
by that you mean REQUIREMENT.html file?
Martin
--
Martin Landa * http://geo.fsv.cvut.cz/~landa
___
grass-dev mai
Thanks. I thought you were only referring to the help information, not the
source compiling dependencies.
Michael
On Jun 27, 2012, at 12:22 PM, Martin Landa wrote:
> 2012/6/27 Michael Barton :
>> In upcoming releases, we need to include PIL in the dependencies list and
>> make sure that it goes
2012/6/27 Michael Barton :
> In upcoming releases, we need to include PIL in the dependencies list and
> make sure that it goes into the binaries, since the cartography module is an
> integral part of GRASS now.
already done (as I noted in previous mail).
Martin
--
Martin Landa * http://geo.fs
2012/6/27 G. Allegri :
> Ok, I see [1], but I didn't know PIL was somehow involved. Is it?
just for generating previews (ie. run ps.map on background and convert
generated ps file into png) [1]
Martin
[1] http://grass.osgeo.org/wiki/WxGUI_Cartographic_Composer#Video_tutorial
--
Martin Landa *
I agree with getting 6.4.3 out the door fast.
Michael
On Jun 27, 2012, at 11:31 AM, Martin Landa wrote:
> Hi Micheal,
>
> 2012/6/27 Michael Barton :
>> A couple months ago, we discovered and fixed a bug that kept people from
>> using the attribute table manager in GRASS 6. This could not be fix
Thanks!
Michael
On Jun 27, 2012, at 12:17 PM, Martin Landa wrote:
> 2012/6/27 Michael Barton :
>> Yes. That's is. It requires PIL. It would be good to include this in the
>> help file.
>
> already done - r52243 & r52245
>
> Martin
>
> --
> Martin Landa * http://geo.fsv.cvut.cz/~landa
_
In upcoming releases, we need to include PIL in the dependencies list and make
sure that it goes into the binaries, since the cartography module is an
integral part of GRASS now.
Michael
On Jun 27, 2012, at 12:04 PM, G. Allegri wrote:
> Ok, I see [1], but I didn't know PIL was somehow involved
I was confused. It was a digitizer issue that was fixed. We all (including you)
fixed it in the binary. The table manager is a different issue.
Michael
On Jun 27, 2012, at 11:31 AM, Martin Landa wrote:
> Hi Micheal,
>
> 2012/6/27 Michael Barton :
>> A couple months ago, we discovered and fixed
2012/6/27 Michael Barton :
> Yes. That's is. It requires PIL. It would be good to include this in the
> help file.
already done - r52243 & r52245
Martin
--
Martin Landa * http://geo.fsv.cvut.cz/~landa
___
grass-dev mailing list
grass-dev@lists.osgeo.
Has anyone run into this? We're unable to save a map to an image file in GRASS
6.4.2 from a Windows XP machine. Saving works in GRASS 7. Is this a bug for all
of Windows in 6.4.2 or just XP...or just something on the Windows XP machine
here?
Michael
_
C. Michael Barton
Visit
Hi all,
I would like to suggest to replace `r.in.wms` module available in
trunk by the new python module `r.in.wms2` (which is currently
available from addons [1]). This module has been recently developed by
Stepan Turek within his bachelor thesis. The module `r.in.wms` (in
trunk) is just pythoniz
Yes. That's is. It requires PIL. It would be good to include this in the help
file.
Michael
On Jun 27, 2012, at 12:04 PM, G. Allegri wrote:
> Ok, I see [1], but I didn't know PIL was somehow involved. Is it?
> I'ma PIL lover :)
>
> giovanni
>
> http://trac.osgeo.org/grass/browser/grass/tags/r
Ok, I see [1], but I didn't know PIL was somehow involved. Is it?
I'ma PIL lover :)
giovanni
http://trac.osgeo.org/grass/browser/grass/tags/release_20120219_grass_6_4_2/gui/wxpython/gui_modules/psmap.py
2012/6/27 Martin Landa
> Hi,
>
> 2012/6/27 G. Allegri :
> > Just a curiosity: what/where i
Hi,
2012/6/27 G. Allegri :
> Just a curiosity: what/where is the "python cartography module"?
> A long time away from GRASS made me miss lot of things...
we are speaking about GUI front-end for ps.map, check GRASS 6.4.2+ [1]
Martin
[1] http://grass.osgeo.org/grass64/manuals/html64_user/wxGUI.Ps
Just a curiosity: what/where is the "python cartography module"?
A long time away from GRASS made me miss lot of things...
2012/6/27 Martin Landa
> 2012/6/27 Michael Barton :
> > There is a python module needed to do previews. I forget what it is
> called.
> > Can anyone remind me?
>
> Python Im
2012/6/27 Michael Barton :
> There is a python module needed to do previews. I forget what it is called.
> Can anyone remind me?
Python Imaging Library [1]
Martin
[1]
http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/psmap/utils.py#L23
--
Martin Landa * http://geo.fsv.cvut.cz/~lan
Hi Micheal,
2012/6/27 Michael Barton :
> A couple months ago, we discovered and fixed a bug that kept people from
> using the attribute table manager in GRASS 6. This could not be fixed in the
> GRASS 6.4.2 code because it is frozen. But the recommendation was to have
> binary maintainers fix it i
There is a python module needed to do previews. I forget what it is called. Can
anyone remind me?
Michael
_
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Corporation for Atmospheric Research
303-497-2889
A couple months ago, we discovered and fixed a bug that kept people from using
the attribute table manager in GRASS 6. This could not be fixed in the GRASS
6.4.2 code because it is frozen. But the recommendation was to have binary
maintainers fix it in their distributions. William and I fixed it
[Addendum]
Hamish:
> > (not talking about pan-sharpening, but in general,)
> > how about the situation where you have a map data
> > which is loudly dominated by a signal, and you want to try and remove that
> > loud signal so that you can look at the subtle variations caused by a
> > different s
30 matches
Mail list logo