On Mon, Dec 2, 2013 at 4:21 AM, Martin Landa wrote:
> Hi Markus,
>
> 2013/11/30 Markus Metz :
>
>> How did you discover that bug in Vect_merge_lines()? To my knowledge
>> all modules calling Vect_merge_lines() set the correct type (lines
>> and/or boundaries).
>
> by `v.clean tool=snap -c`, see [1
On Tue, Dec 3, 2013 at 1:05 AM, Nikos Alexandris
wrote:
> Nikos Alexandris wrote:
> ..
>
>> I've tested this with at least three different similar cases. All work fine
>> without the seed map! All fail with a seed map supplied. I guess, the only
>> real difference is time for the processes to comp
Nikos Alexandris wrote:
> > I've tested this with at least three different similar cases. All work
> > fine without the seed map! All fail with a seed map supplied. I guess, the
> > only real difference is time for the processes to complete, right?
> OK, I've just discovered that I mixed 8-bit (
Nikos Alexandris wrote:
..
> I've tested this with at least three different similar cases. All work fine
> without the seed map! All fail with a seed map supplied. I guess, the only
> real difference is time for the processes to complete, right?
OK, I've just discovered that I mixed 8-bit (the P
Nikos Alexandris wrote:
> I am trying to (re-)segment a group of high resolution multi-spectral bands
> (QuickBird2). I work with
>
> version=7.0.svn
> date=2013
> revision=58327M
> build_date=2013-11-29
>
> and use a seed map (result from the Panchromatic band) and, unfortunately, I
> got twice
Hi,
I am trying to (re-)segment a group of high resolution multi-spectral bands
(QuickBird2). I work with
version=7.0.svn
date=2013
revision=58327M
build_date=2013-11-29
and use a seed map (result from the Panchromatic band) and, unfortunately, I
got twice the same error message
--%<---
i.seg
