On 11/06/20 13:36, mbrauch...@posteo.de wrote:
Thank you for the explanation! I assumed gsoc version is build upon
i.segment.
Is there any way to include the shape parameters in i.segment? I am very
fond of the gsoc version as it helps surpress segments growing to very
complex geometries
Thank you for the explanation! I assumed gsoc version is build upon i.segment.Is there any way to include the shape parameters in i.segment? I am very fond of the gsoc version as it helps surpress segments growing to very complex geometries (shadows through the forest patches for example). Kind
i.segment.gsoc is the original version developed during GSoC. i.segment is ann
optimized version that was originally based on the GSoC work, but has known
different developments since, including in the way the threshold parameter is
applied.
I would recommend using i.segment.
Moritz
Am 10.
Lennert
Sendt: onsdag 20. november 2019 13:16
Til: Stefan Blumentrath ; GRASS users list
Emne: Re: [GRASS-user] i.segment: band_suffix does not seem to have effect
On 20/11/19 11:19, Stefan Blumentrath wrote:
> Hi,
>
> I thought that if I give the band_suffix option in i.segment it
> pr
On 20/11/19 11:19, Stefan Blumentrath wrote:
Hi,
I thought that if I give the band_suffix option in i.segment it
produces bands with modified band values for all input bands. However,
the option does not seem to have effect (no modified output bands are
produced). Did I do or understand
Hi,
I thought that if I give the band_suffix option in i.segment it produces bands
with modified band values for all input bands. However, the option does not
seem to have effect (no modified output bands are produced). Did I do or
understand something wrong?
Cheers
Stefan
I thought I did a few times, as it also was successful on Tuesday (without
the coefficient of variation and without neighborhood statistics).
After the error from Wed Oct 17 13:55, I reinstalled to be sure and
retried.
Success!! Thanks alot. Now for the next challenge to begin :)
i.segment.stats
On 17/10/18 19:15, Jamille Haarloo wrote:
Yes, I noticed as other modules weren't working either. Stupid..
Just got the results with 7.6 and some "nan" values again.
This shouldn't happen with the current version. Did you reinstall with
'g.extension i.segment.stats' ?
Moritz
Yes, I noticed as other modules weren't working either. Stupid..
Just got the results with 7.6 and some "nan" values again.
Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Creating output vector map...
ERROR: Error while
On 17/10/18 15:39, Jamille Haarloo wrote:
Alright. Just tried, but got an old error back again. Also when
reinstalling r.object.geometry got 'ERROR: File is not a zip file'
i.segment.stats -n map=SegW24IDM4DV4@LUP1
rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
Alright. Just tried, but got an old error back again. Also when
reinstalling r.object.geometry got 'ERROR: File is not a zip file'
i.segment.stats -n map=SegW24IDM4DV4@LUP1 rasters=DV2@LUP1,DV4@LUP1
,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
On 16/10/18 22:20, Jamille Haarloo wrote:
The csv looks ok, but quite extensive and heavy.
Yes, but when dealing with large areas, not going through the vector
fomat actually speeds up the process. You can feed this csv into
v.class.mlR directly.
I reinstalled again and tried with less
The csv looks ok, but quite extensive and heavy.
I reinstalled again and tried with less variables, without the coefficient
of variation and without neighborhood statistics. This time without error.
i.segment.stats map=SegW24IDM4DV4@LUP1 rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1
On 15/10/18 21:00, Jamille Haarloo wrote:
I did with neighborhood statistics and vector, and without.
with neighb. statistics & with vector
i.segment.stats -n --overwrite map=SegW24IDM4DV4@LUP1
rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
I did with neighborhood statistics and vector, and without.
with neighb. statistics & with vector
i.segment.stats -n --overwrite map=SegW24IDM4DV4@LUP1 rasters=DV2@LUP1
,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
On 15/10/18 10:54, Moritz Lennert wrote:
On 15/10/18 10:17, Moritz Lennert wrote:
On 12/10/18 21:10, Jamille Haarloo wrote:
Markus. i.segment finished without giving an error.
Moritz,
I am back at the older error. I've seen this error documented online as
a result of 'unaccepted'
On 15/10/18 10:17, Moritz Lennert wrote:
On 12/10/18 21:10, Jamille Haarloo wrote:
Markus. i.segment finished without giving an error.
Moritz,
I am back at the older error. I've seen this error documented online as
a result of 'unaccepted' column-names. I tried to keep the name of the
input
On 12/10/18 21:10, Jamille Haarloo wrote:
Markus. i.segment finished without giving an error.
Moritz,
I am back at the older error. I've seen this error documented online as
a result of 'unaccepted' column-names. I tried to keep the name of the
input maps for the statistics as short and
Markus. i.segment finished without giving an error.
Moritz,
I am back at the older error. I've seen this error documented online as a
result of 'unaccepted' column-names. I tried to keep the name of the input
maps for the statistics as short and simple possible (without dots etc).
On 11/10/18 19:42, Jamille Haarloo wrote:
Markus, that's great! I will install the latest version and retry. I
will report next Monday.
Thanks Moritz. The spaces and '&' in paths of output files did not give
problems before, but I retried without the spaces and '&' just in case.
Markus, that's great! I will install the latest version and retry. I will
report next Monday.
Thanks Moritz. The spaces and '&' in paths of output files did not give
problems before, but I retried without the spaces and '&' just in case.
i.segment.stats -n --overwrite map=SegmW24IDM4DV4@LUP1
On 09/10/18 17:19, Jamille Haarloo wrote:
first lines of test.csv
cat|area|perimeter|compact_square|compact_circle|fd
1|11876.00|1398.00|0.311808|3.618821|1.543932
2|635805.00|57572.00|0.055400|20.367814|1.640512
3|25898.00|3322.00|0.193773|5.823198|1.595825
On Mon, Oct 8, 2018 at 1:19 PM Jamille Haarloo
wrote:
>
> Thank you Markus,
>
> I just got the i.segment results with Grass 7.6 (64 bit; r73480-35).
>
> This is the output:
> i.segment --overwrite group=DV4@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
output=SegmW24IDM4DV4 threshold=0.25 minsize=5000
first lines of test.csv
cat|area|perimeter|compact_square|compact_circle|fd
1|11876.00|1398.00|0.311808|3.618821|1.543932
2|635805.00|57572.00|0.055400|20.367814|1.640512
3|25898.00|3322.00|0.193773|5.823198|1.595825
4|7767.00|1702.00|0.207122|5.447885|1.661054
On 09/10/18 13:48, Jamille Haarloo wrote:
Hello Moritz,
First a pop-up came about not finding it, so reinstalled it.
g.extension r.object.geometry
WARNING: Extension already installed. Re-installing...
Downloading precompiled GRASS Addons ...
Updating addons metadata file...
Installation of
Hello Moritz,
First a pop-up came about not finding it, so reinstalled it.
g.extension r.object.geometry
WARNING: Extension already installed. Re-installing...
Downloading precompiled GRASS Addons ...
Updating addons metadata file...
Installation of successfully finished
(Mon Oct 08 16:55:04
Am 8. Oktober 2018 20:40:39 MESZ schrieb Jamille Haarloo
:
>Sorry about that Moritz. Possibly I made that mistake, but I tried
>several
>times. I don't think I reproduced the same mistake in all tries.
>These are the i.segment.stats results with Grass 7.6 (64 bit;
>r73480-35). I
>am reading up
Sorry about that Moritz. Possibly I made that mistake, but I tried several
times. I don't think I reproduced the same mistake in all tries.
These are the i.segment.stats results with Grass 7.6 (64 bit; r73480-35). I
am reading up on this error now.
i.segment.stats -n map=SegmW24IDM4DV4@LUP1
Thank you Markus,
I just got the i.segment results with Grass 7.6 (64 bit; r73480-35).
This is the output:
i.segment --overwrite group=DV4@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
output=SegmW24IDM4DV4 threshold=0.25 minsize=5000 memory=1
seeds=SegW24IDM4DV4@LUP1 goodness=SegmW24IDM4DV4_goodn
Maximum
On 04/10/18 17:06, Jamille Haarloo wrote:
i.segment.stats errors:
Please, whenever you report errors, also report the command line used.
ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_7968 (cat
int, area double precision, compact_circle double precision, DV2_mean
double
Can you please try with GRASS 7.6 64 bit [0] and report if the error still
persists or not?
Thanks,
Markus M
[0] https://wingrass.fsv.cvut.cz/grass76/x86_64/
On Thu, Oct 4, 2018 at 5:07 PM Jamille Haarloo
wrote:
>
> Dear Grass community,
>
> I have been experimenting with i.segment,
Dear Grass community,
I have been experimenting with i.segment, i.segment.uspo and
i.segment.stats on relatively small areas of a worldview-2 image.
After some success I tried i.segment and i.segment.stats on the entire area
of 19875 ha, but I kept getting the same errors with i.segment.stats. I
On Mon, Jun 18, 2018 at 4:16 PM, Paul Shapley wrote:
>
> Hi Users,
>
> I am getting an error when i run i.segment on a small subset of an image:-
>
> 'ERROR: Insufficient number of non-NULL cells in current region'
Either the subset is too small (only one cell) or the current region does
not
Hi Users,
I am getting an error when i run i.segment on a small subset of an image:-
'ERROR: Insufficient number of non-NULL cells in current region'
Googled the error and found this (if it helps)
https://gis.stackexchange.com/questions/256431/error-in-grass-using-i-segment-uspo-function
On 30/06/14 12:09, Francesco Nex wrote:
Hi,
My name is Francesco and I'm very new with GRASS.
I tried to use the i.segment command and I got a problem.
The command lines I used are the following:
i.segment -d group=060140_file_OFD output=060140_file_segs_L1 threshold=0.1
i.segment -d
35 matches
Mail list logo
