Hi Pierre,
If you would turn this into a add-on module it could eventually became the
portable way to do that... Having this functionality makes sense.
Vaclav
On Mon, Sep 17, 2018 at 3:28 PM Stefan Blumentrath <
stefan.blumentr...@nina.no> wrote:
> r.colors manual says color ramps are saved
r.colors manual says color ramps are saved in:
$GISBASE/etc/colors/, so values could be read from there, I guess.
And the parser can give you GUI access to the rules names with the
G_OPT_M_COLR option:
https://grass.osgeo.org/grass77/manuals/parser_standard_options.html
Cheers
Stefan
On Mon, Sep 17, 2018 at 4:17 AM Pierre Roudier wrote:
>
> Hi all,
>
> I am trying to write a little Python extension wrapping r.color to use
> different kind of strecthes,
>
> It should be pretty simple, basically just builkding rules on-the-fly
> and pass them to r.color. But I can't quite seem
On Mon, Sep 17, 2018 at 3:39 PM Moritz Lennert
wrote:
>
> Markus,
>
> Could you explain this ? Does this mean that the memory parameter in
> r.in.gdal is now automagic ? Or why doesn't it make sens to let the user
> define in r.import the memory size ?
Markus N and me were discussing this
#3648: Error when using WMS on Windows
-+-
Reporter: annakrat | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.6.0
Component: Python |Version: unspecified
Keywords:
Markus,
Could you explain this ? Does this mean that the memory parameter in
r.in.gdal is now automagic ? Or why doesn't it make sens to let the user
define in r.import the memory size ?
Moritz
On 17/09/18 15:30, svn_gr...@osgeo.org wrote:
Author: neteler
Date: 2018-09-17 06:30:25 -0700
#613: clean_temp: not safe for concurrent use
--+--
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.6.0
Component: Startup |Version: 6.4.0 RCs
