#306: v.in.ogr GUI is missing --o and --v
---+
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: major | Milestone: 6.4.0
#307: v.in.dxf: output name should be required
--+-
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: trivial | Milestone
Hi,
2008/9/10 Moritz Lennert <[EMAIL PROTECTED]>:
> I just noticed that the wxgui vdigit uses a default of 0 for the first cat
> value to be assigned to a newly digitized element. Is this desirable ? In
> previous version of v.digit it always was 1. Don't know if this really makes
> any differenc
#307: v.in.dxf: output name should be required
--+-
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: major| Milestone
#306: v.in.ogr GUI is missing --o and --v
--+-
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: minor| Milestone: 6.
#306: v.in.ogr GUI is missing --o and --v
---+
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: major | Milestone: 6.4.0
Hi,
currently you can choose from two components of vector digitizer --
vedit and vdigit. Vedit calls directly v.edit command which slows down
every action, Vdigit uses C++ extension. Vedit component has been part
of the development. It this moment I would suggest to drop this
component. At the en
#308: Compiler error while building python swig
--+-
Reporter: cgsbob | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major
#306: v.in.ogr GUI is missing --o and --v
---+
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: major | Milestone: 6.4.0
#308: Compiler error while building python swig
--+-
Reporter: cgsbob | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major
#308: Compiler error while building python swig
--+-
Reporter: cgsbob | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major
#308: Compiler error while building python swig
--+-
Reporter: cgsbob | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major
#308: Compiler error while building python swig
--+-
Reporter: cgsbob | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major
#306: v.in.ogr GUI is missing --o and --v
---+
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: major | Milestone: 6.4.0
Росен Матев wrote:
> Thanks for pointing out all that. Strangely, I don't get those
> warnings here, probably command line switches...
this is what I use:
CFLAGS="-g -Wall -Werror-implicit-function-declaration" ./configure \
...
For debugging do not use -O for optimization and do not strip th
#306: v.in.ogr GUI is missing --o and --v
---+
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: major | Milestone: 6.4.0
#308: Compiler error while building python swig
-+--
Reporter: cgsbob | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major
Hi
Is anyone from the GRASS community interested in doing a demo session
of GRASS at the upcoming FOSS4G2008 conference in Cape Town? If so
please drop me a note so we can book a time slot for you. More info
can be found here:
http://wiki.osgeo.org/wiki/FOSS4G2008_Demos
Best regards
--
Tim S
Hi,
Thanks for pointing out all that. Strangely, I don't get those
warnings here, probably command line switches... I think they are
fixed now.
I don't seem to have problems with centroids. Can you show me a map,
on which that occurs?
And again, please help with the busroute11 test, cause it's beh
#306: v.in.ogr GUI is missing --o and --v
---+
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: major | Milestone: 6.4.0
#306: v.in.ogr GUI is missing --o and --v
---+
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: major | Milestone: 6.4.0
Hello,
I just noticed that the wxgui vdigit uses a default of 0 for the first
cat value to be assigned to a newly digitized element. Is this desirable
? In previous version of v.digit it always was 1. Don't know if this
really makes any difference, though.
Moritz
___
On Wed, Sep 10, 2008 at 2:37 PM, Hamish <[EMAIL PROTECTED]> wrote:
> Rainer:
>> I want to use the wildfire modules, and they are either EXTREMELY slow
>> (even on the demodataset) or there is something wrong with them,
>> because they seem to hang at 0% cells visited.
>
> It is endlessly stuck in a
Rainer:
> I want to use the wildfire modules, and they are either EXTREMELY slow
> (even on the demodataset) or there is something wrong with them,
> because they seem to hang at 0% cells visited.
It is endlessly stuck in a while loop.
It's the second loop in r.spread/replaceHa.c, because the loop
#64: ps.map: patch to set customized scalebar units
--+-
Reporter: alf | Owner: hamish
Type: enhancement | Status: closed
Priority: minor| Milestone: 6.4.0
Component: p
On Wed, Sep 10, 2008 at 11:53 AM, Martin Landa <[EMAIL PROTECTED]> wrote:
> hi,
>
> 2008/9/10 Rainer M Krug <[EMAIL PROTECTED]>:
>> Therefore I want to compile them with #define DEBUG enabled. At the
>> moment, I am compiling the grass completely - but there must be a way
>> of compiling only the w
hi,
2008/9/10 Rainer M Krug <[EMAIL PROTECTED]>:
> Therefore I want to compile them with #define DEBUG enabled. At the
> moment, I am compiling the grass completely - but there must be a way
> of compiling only the wildfire modules (or even only r.spread)?
you don't need that, just define DEBUG v
Hi
I want to use the wildfire modules, and they are either EXTREMELY slow
(even on the demodataset) or there is something wrong with them,
because they seem to hang at 0% cells visited.
Therefore I want to compile them with #define DEBUG enabled. At the
moment, I am compiling the grass completely
I've removed the C99 calls.
On Wed, Sep 10, 2008 at 3:23 AM, Glynn Clements
<[EMAIL PROTECTED]> wrote:
>
> Martin Landa wrote:
>
>> > My mentor Wolf and I are experiencing problems with the new buffer
>> > module. For some certain input it works well on my system but doesn't
>> > finish at all on
#306: v.in.ogr GUI is missing --o and --v
---+
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: major | Milestone: 6.4.0
30 matches
Mail list logo
