#3167: db.connect: connection to remote database does not work
--+---
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.5
Component: Database |
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
On 26/09/16 23:50, Vaclav Petras wrote:
On Mon, Sep 26, 2016 at 5:24 PM, Veronica Andreo > wrote:
I'm with MaDi in that if I see a very long list of flags and
parameters in the terminal when using --h, i just go to the
manual... I
On Fri, Sep 23, 2016 at 5:22 PM, Markus Neteler wrote:
> * various commands: "Use the low-memory version" - also more advanced
I guess this is a typical example where we need to be careful. I can
imagine a situation when a beginner has a lot of data and low-end hardware.
By
On Fri, Sep 23, 2016 at 5:22 PM, Markus Neteler wrote:
> Maybe not hide then but at least group the parameters and flags rather
> than alpha-order or random mix.
>
This is something which can be done right now. The options and flags are
presented in the order as they are
On Mon, Sep 26, 2016 at 5:24 PM, Veronica Andreo
wrote:
> I'm with MaDi in that if I see a very long list of flags and parameters in
> the terminal when using --h, i just go to the manual... I just use --h in
> CLI for a quick recalling of flags/options... A reduced list of
Hello
I'm with MaDi in that if I see a very long list of flags and parameters in
the terminal when using --h, i just go to the manual... I just use --h in
CLI for a quick recalling of flags/options... A reduced list of most
commonly used flags would be nice, but still keep the possibility to get
#3153: g.gui.animation freezes when trying to add decorations
--+-
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.2.0
Component: wxGUI|
#3166: Parallelization with tiling for grass.script
--+--
Reporter: wenzeslaus | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.4.0
Component: Python |Version:
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
#3166: Parallelization with tiling for grass.script
--+--
Reporter: wenzeslaus | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.4.0
Component: Python |Version:
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
#3057: Problems with Numpy and matplotlib after updating through OSGeo4W
--+-
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone: 7.0.5
Component: Python |
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
#3167: db.connect: connection to remote database does not work
--+---
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.5
Component: Database |
#3167: db.connect: connection to remote database does not work
--+---
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.5
Component: Database |
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
#3167: db.connect: connection to remote database does not work
--+---
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.5
Component: Database |
#3167: db.connect: connection to remote database does not work
--+---
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.5
Component: Database |
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
On 26/09/16 14:59, Moritz Lennert wrote:
On 26/09/16 14:41, Moritz Lennert wrote:
On 24/09/16 12:36, Martin Landa wrote:
Hi,
2016-09-18 16:21 GMT+02:00 Martin Landa :
cool, count with my support please. Ma
since RC2 has been released on Sunday 18/9, the final
#3167: db.connect: connection to remote database does not work
---+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker| Milestone: 7.0.5
On 26/09/16 14:41, Moritz Lennert wrote:
On 24/09/16 12:36, Martin Landa wrote:
Hi,
2016-09-18 16:21 GMT+02:00 Martin Landa :
cool, count with my support please. Ma
since RC2 has been released on Sunday 18/9, the final release 7.0.5
should be out ~tomorrow. Any
On 24/09/16 12:36, Martin Landa wrote:
Hi,
2016-09-18 16:21 GMT+02:00 Martin Landa :
cool, count with my support please. Ma
since RC2 has been released on Sunday 18/9, the final release 7.0.5
should be out ~tomorrow. Any objections?
It would be great to see
#3057: Problems with Numpy and matplotlib after updating through OSGeo4W
--+-
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone: 7.0.5
Component: Python |
#2848: g.gui.vdigit: snapping distance seems to only be defined in map units,
not
screen pixels
--+-
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone:
#3166: Parallelization with tiling for grass.script
--+--
Reporter: wenzeslaus | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.4.0
Component: Python |Version:
#2318: G7: t.* modules unclear -s flag
--+-
Reporter: neteler | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone: 7.2.0
Component: Temporal |Version:
#2902: i.segment.hierarchical: Execution of subprocesses was not successful
-+-
Reporter: mlennert| Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.0.5
Hi,
On Fri, Sep 23, 2016 at 12:00 AM, Markus Neteler wrote:
> Hi,
>
> in order to not hinder the addition of important new flags/parameters
> to modules while keeping things optionally easy it would be good to
> implement some expert mode to the parser.
>
> The flags and
#3166: Parallelization with tiling for grass.script
--+--
Reporter: wenzeslaus | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.4.0
Component: Python |Version:
Hi,
I have been struggling with similar issues and solved them by writing a
GRASS_BATCH_JOB script that I execute in parallel in different mapsets.
Thus, the approach Markus and Sören sketch looks very useful to me (even for
people who are not on HPC).
Do you have more options / flags in mind
On Sat, Sep 24, 2016 at 12:36 PM, Martin Landa wrote:
> Hi,
>
> 2016-09-18 16:21 GMT+02:00 Martin Landa :
>> cool, count with my support please. Ma
>
> since RC2 has been released on Sunday 18/9, the final release 7.0.5
> should be out ~tomorrow.
36 matches
Mail list logo