Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-18 Thread Jamille Haarloo
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 -n --overwrite map=SegW24IDM4DV4@LUP1 rasters=DV2@LUP1
,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
area_measures=compact_circle
csvfile=C:\Users\haarlooj\nStats_SegW24IDM4DV4_17okt18
vectormap=nvSegW24IDM4DV4 processes=2
Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Creating output vector map...
(Wed Oct 17 18:22:33 2018) Command finished (95 min 6 sec)


On Thu, Oct 18, 2018 at 5:12 AM Moritz Lennert 
wrote:

> 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
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-18 Thread Moritz Lennert

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
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-17 Thread Jamille Haarloo
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 executing: 'INSERT INTO segmstat_tmp_vect_8116 VALUES
(2744,
10.574609,0.000657937002497415,100.010348629312,0.0118722,0.0199653,0.037037,0.0532407,0.0149315167004704,-34.81817527835,-0.440972,-0.375,-0.315972,-0.232639,0.0147358775257243,26.7103955510257,0.370735,0.452658,0.53125,0.60625,0.00759147152076699,10.6500844056518,0.75,0.802083,0.875,0.927083,4.16169760046326,52.4687741848501,2,3,5,7,0.200221189871832,35.183683942494,1,1,2,2,8,13.216384625,8.62095260592,0.00227423524743,0.00305950083943,223.15170811,122.713529331,0.01689609075,0.0219202839649,0.022322058,0.0229396651236,0.029157736625,0.0250281412368,0.03936146125,0.0291593758381,0.00809150063926,0.00998894786878,nan,nan,0.000935102375,0.00149429712142,0.00332539875,0.00553672330287,0.0106704025,0.0177514942977,0.0168798225,0.0277037009502,0.0108558662204,0.00624210011282,36.7678730965,22.2897752507,0.29285125,0.180951460467,0.3513889,0.181596981702,0.41656925,0.180382131329,0.485690125,0.1830333289,0.0149007045801,0.018570035777,30.2038217327,26.3183888064,0.5921816125,0.417141476181,0.642181,0.380369094661,0.699914125,0.345038582134,0.744641,0.31679767,194.55742,313.451777334,43.4071398819,21.8790138711,15.0,20.8086520467,20.25,27.6258484033,25.875,34.2798683632,32.375,41.9402476745,164.772935658,278.214855266,39.6227650243,32.7809091847,12.375,19.1307180994,16.25,25.5673131166,21.0,32.3921286735,26.875,40.3622270818)'
Traceback (most recent call last):
  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py", line 371, in 
main()
  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py", line 358, in main
gscript.run_command('db.execute', input=insert_sql,
quiet=True)
  File "C:\Program Files\GRASS GIS
7.6.svn\etc\python\grass\script\core.py", line 423, in
run_command
return handle_errors(returncode, returncode, args,
kwargs)
  File "C:\Program Files\GRASS GIS
7.6.svn\etc\python\grass\script\core.py", line 334, in
handle_errors
returncode=returncode)
grass.exceptions.CalledModuleError: Module run None
['db.execute', '--q', 'input=Z:\\GRASS_GIS\\Cottica_LUP\\LUP
1\\.tmp/unknown\\8116.1'] ended with error
Process ended with non-zero return code 1. See errors in the
(error) output.
(Wed Oct 17 13:55:43 2018) Command finished (90 min 41 sec)



On Wed, Oct 17, 2018 at 1:48 PM Moritz Lennert 
wrote:

> 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
> >
> raster_statistics=variance,coeff_var,first_quart,median,third_quart,perc_90
> > area_measures=compact_circle csvfile=Z:\nStats_SegW24IDM4DV4_17okt18
> > vectormap=nvSegW24IDM4DV4 processes=4
> > Calculating geometry statistics...
> > Traceback (most recent call last):
> >File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> > pts/i.segment.stats.py ", line 371, in
> 
> >  main()
> >File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> > pts/i.segment.stats.py ", line 220, in main
> >  quiet=True)
> >File "C:\PROGRA~1\QGIS21~1.0\apps\grass\grass-7.0.4\etc\py
> > thon\grass\script\core.py", line 395, in run_command
> >  return handle_errors(returncode, returncode, args,
> > kwargs)
> >File "C:\PROGRA~1\QGIS21~1.0\apps\grass\grass-7.0.4\etc\py
> > thon\grass\script\core.py", line 313, in handle_errors
> >  returncode=returncode)
> > grass.exceptions.CalledModuleError: Module run None
> > ['r.object.geometry', '--o', '--q',
> > 'output=Z:\\GRASS_GIS/Cottica_LUP/LUP1/.tmp/unknown/7508.0',
> > 'input=SegW24IDM4DV4@LUP1'] ended with error
> > Process ended with non-zero return code -1073741515. See
> > errors in the (error) output.
> > (Wed Oct 17 10:33:05 2018) Command finished (0 sec)
> >
> > g.extension r.object.geometry
> > WARNING: Extension  already installed.
> Re-installing...
> > Downloading precompiled GRASS Addons ...
> > ERROR: File is not a zip file:
> >
> http://wingrass.fsv.cvut.cz/grass70/x86_64/addons/grass-7.0.4/r.object.geometry.zip
> > (Wed Oct 17 10:32:54 2018) Command finished (1 sec)
>
> You seem to be using a very old version of GRASS: 7.0.4. There are no
> addons available for Windows for that version. The official last release
> of the 7.0 line was 7.0.6 and addons are available for that.
>
> But I would really recommend that you work at least with the current
> stable version 7.4.1 (soon 7.4.2) or even with a newer version.
>
> Moritz
>

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-17 Thread Moritz Lennert

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 
raster_statistics=variance,coeff_var,first_quart,median,third_quart,perc_90 
area_measures=compact_circle csvfile=Z:\nStats_SegW24IDM4DV4_17okt18 
vectormap=nvSegW24IDM4DV4 processes=4

Calculating geometry statistics...
Traceback (most recent call last):
   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py ", line 371, in 
     main()
   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py ", line 220, in main
     quiet=True)
   File "C:\PROGRA~1\QGIS21~1.0\apps\grass\grass-7.0.4\etc\py
thon\grass\script\core.py", line 395, in run_command
     return handle_errors(returncode, returncode, args,
kwargs)
   File "C:\PROGRA~1\QGIS21~1.0\apps\grass\grass-7.0.4\etc\py
thon\grass\script\core.py", line 313, in handle_errors
     returncode=returncode)
grass.exceptions.CalledModuleError: Module run None
['r.object.geometry', '--o', '--q',
'output=Z:\\GRASS_GIS/Cottica_LUP/LUP1/.tmp/unknown/7508.0',
'input=SegW24IDM4DV4@LUP1'] ended with error
Process ended with non-zero return code -1073741515. See
errors in the (error) output.
(Wed Oct 17 10:33:05 2018) Command finished (0 sec)

g.extension r.object.geometry
WARNING: Extension  already installed. Re-installing...
Downloading precompiled GRASS Addons ...
ERROR: File is not a zip file: 
http://wingrass.fsv.cvut.cz/grass70/x86_64/addons/grass-7.0.4/r.object.geometry.zip

(Wed Oct 17 10:32:54 2018) Command finished (1 sec)


You seem to be using a very old version of GRASS: 7.0.4. There are no 
addons available for Windows for that version. The official last release 
of the 7.0 line was 7.0.6 and addons are available for that.


But I would really recommend that you work at least with the current 
stable version 7.4.1 (soon 7.4.2) or even with a newer version.


Moritz
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-17 Thread Jamille Haarloo
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
raster_statistics=variance,coeff_var,first_quart,median,third_quart,perc_90
area_measures=compact_circle csvfile=Z:\nStats_SegW24IDM4DV4_17okt18
vectormap=nvSegW24IDM4DV4 processes=4
Calculating geometry statistics...
Traceback (most recent call last):
  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py", line 371, in 
main()
  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py", line 220, in main
quiet=True)
  File "C:\PROGRA~1\QGIS21~1.0\apps\grass\grass-7.0.4\etc\py
thon\grass\script\core.py", line 395, in run_command
return handle_errors(returncode, returncode, args,
kwargs)
  File "C:\PROGRA~1\QGIS21~1.0\apps\grass\grass-7.0.4\etc\py
thon\grass\script\core.py", line 313, in handle_errors
returncode=returncode)
grass.exceptions.CalledModuleError: Module run None
['r.object.geometry', '--o', '--q',
'output=Z:\\GRASS_GIS/Cottica_LUP/LUP1/.tmp/unknown/7508.0',
'input=SegW24IDM4DV4@LUP1'] ended with error
Process ended with non-zero return code -1073741515. See
errors in the (error) output.
(Wed Oct 17 10:33:05 2018) Command finished (0 sec)

g.extension r.object.geometry

WARNING: Extension  already installed. Re-installing...
Downloading precompiled GRASS Addons ...
ERROR: File is not a zip file:
http://wingrass.fsv.cvut.cz/grass70/x86_64/addons/grass-7.0.4/r.object.geometry.zip
(Wed Oct 17 10:32:54 2018) Command finished (1 sec)

On Wed, Oct 17, 2018 at 4:38 AM Moritz Lennert 
wrote:

> 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 variables, without the
> > coefficient of variation and without neighborhood statistics. This time
> > without error.
>
> Great. I see that the i.segment.stats now has been updated on the addons
> server, so it would be great if you could try again with the
> neighborhood statistics.
>
> Moritz
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-17 Thread Moritz Lennert

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 variables, without the 
coefficient of variation and without neighborhood statistics. This time 
without error.


Great. I see that the i.segment.stats now has been updated on the addons 
server, so it would be great if you could try again with the 
neighborhood statistics.


Moritz
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-16 Thread Jamille Haarloo
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
,IDM4@LUP1,W2@LUP1,W4@LUP1
raster_statistics=variance,first_quart,median,third_quart,perc_90
area_measures=compact_circle
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_16okt18
vectormap=vSegW24IDM4DV4 processes=3
Calculating geometry statistics...
Calculating statistics for raster maps...
Creating output vector map...
(Tue Oct 16 16:31:51 2018) Command finished (94 min 7 sec)



On Tue, Oct 16, 2018 at 1:56 PM Moritz Lennert 
wrote:

> 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
> >
> raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
>
> > area_measures=compact_circle
> > csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_15okt18
> > vectormap=vSegW24IDM4DV4 processes=3
> > Calculating geometry statistics...
> > Calculating statistics for raster maps...
> > Calculating neighborhood statistics...
> > Creating output vector map...
> > DBMI-SQLite driver error:
> > Error in sqlite3_prepare():
> > near "IDM4_third_qu": syntax error
> > ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_10260 (cat
> > int, compact_circle double precision, DV2_mean double precision,
> > DV2_stddev double precision, DV2_variance double precision,
> > DV2_coeff_var double precision, DV2_first_quart double precision,
> > DV2_median double precision, DV2_third_quart double precision,
> > DV2_perc_90 double precision, DV4_mean double precision, DV4_stddev
> [...]
>
> This is not using the new version of i.segment.stats that I committed
> yesterday. I see that the version available at
> https://wingrass.fsv.cvut.cz/grass74/x86_64/addons/latest/ is still the
> one from before my changes.
>
> Martin, any reason this has not been recreated since ?
>
>
> > without neighb. statistics, but with vector
> > (Mon Oct 15 10:54:02 2018)
> > i.segment.stats --overwrite map=SegW24IDM4DV4@LUP1
> > rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
> >
> raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
>
> > area_measures=compact_circle
> > csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_15okt18
> > vectormap=vSegW24IDM4DV4 processes=3
> > Calculating geometry statistics...
> > Calculating statistics for raster maps...
> > Creating output vector map...
> > DBMI-SQLite driver error:
> > Error in sqlite3_prepare():
> > no such column: nan
> > DBMI-SQLite driver error:
> > Error in sqlite3_prepare():
> > no such column: nan
> > ERROR: Error while executing: 'INSERT INTO segmstat_tmp_vect_3516 VALUES
> > (1244,
> >
> 1.128379,0.069477558136,0,0,0,0.069,0.069,0.069,0.069,0,0,0,nan,0,0,0,0,0.53125,0,0,0,0.53125,0.53125,0.53125,0.53125,1,0,0,0,1,1,1,1,3,0,0,0,3,3,3,3,1,0,0,0,1,1,1,1)'
>
> Hmmm, not sure where this 'nan' comes from. If I see correctly it is
> from a coefficient of variation of DV4@LUP1 for an object where both the
> mean and the stddev are 0, leading to a zero division.
>
> I don't know what DV4 is. Is it normal that an object could have mean
> and stddev = 0 ? If yes, then the coefficient of variation might not be
> useful.
>
> Anyhow, I just committed a fix (r73555) which should normally replace
> this 'nan' by its SQL equivalent 'NULL'.
>
> >
> > without neighb. statistics & without vector
> > (Mon Oct 15 14:58:40 2018)
> > i.segment.stats --overwrite map=SegW24IDM4DV4@LUP1
> > rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
> >
> raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
>
> > area_measures=compact_circle
> > csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_15okt18b processes=3
> > Calculating geometry statistics...
> > Calculating statistics for raster maps...
> > (Mon Oct 15 15:15:18 2018) Command finished (16 min 38 sec)
> >
> > with neighb. statistics, but without vector
> > (Mon Oct 15 15:32:39 2018)
> > i.segment.stats -n --overwrite map=SegW24IDM4DV4@LUP1
> > rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
> >
> raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
>
> > area_measures=compact_circle
> > csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_15okt18c processes=3
> > Calculating geometry statistics...
> > Calculating statistics for raster maps...
> > Calculating neighborhood statistics...
> > (Mon Oct 15 15:50:25 2018) Command finished (17 min 46 sec)
>
> These two are normal as your errors are all in the SQL that creates the
> attribute table of the vector. If you do not create a vector map, you
> obvisouly do 

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-16 Thread Moritz Lennert

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 
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90 
area_measures=compact_circle 
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_15okt18 
vectormap=vSegW24IDM4DV4 processes=3

Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Creating output vector map...
DBMI-SQLite driver error:
Error in sqlite3_prepare():
near "IDM4_third_qu": syntax error
ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_10260 (cat 
int, compact_circle double precision, DV2_mean double precision, 
DV2_stddev double precision, DV2_variance double precision, 
DV2_coeff_var double precision, DV2_first_quart double precision, 
DV2_median double precision, DV2_third_quart double precision, 
DV2_perc_90 double precision, DV4_mean double precision, DV4_stddev 

[...]

This is not using the new version of i.segment.stats that I committed 
yesterday. I see that the version available at 
https://wingrass.fsv.cvut.cz/grass74/x86_64/addons/latest/ is still the 
one from before my changes.


Martin, any reason this has not been recreated since ?



without neighb. statistics, but with vector
(Mon Oct 15 10:54:02 2018)
i.segment.stats --overwrite map=SegW24IDM4DV4@LUP1 
rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1 
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90 
area_measures=compact_circle 
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_15okt18 
vectormap=vSegW24IDM4DV4 processes=3

Calculating geometry statistics...
Calculating statistics for raster maps...
Creating output vector map...
DBMI-SQLite driver error:
Error in sqlite3_prepare():
no such column: nan
DBMI-SQLite driver error:
Error in sqlite3_prepare():
no such column: nan
ERROR: Error while executing: 'INSERT INTO segmstat_tmp_vect_3516 VALUES 
(1244, 
1.128379,0.069477558136,0,0,0,0.069,0.069,0.069,0.069,0,0,0,nan,0,0,0,0,0.53125,0,0,0,0.53125,0.53125,0.53125,0.53125,1,0,0,0,1,1,1,1,3,0,0,0,3,3,3,3,1,0,0,0,1,1,1,1)'


Hmmm, not sure where this 'nan' comes from. If I see correctly it is 
from a coefficient of variation of DV4@LUP1 for an object where both the 
mean and the stddev are 0, leading to a zero division.


I don't know what DV4 is. Is it normal that an object could have mean 
and stddev = 0 ? If yes, then the coefficient of variation might not be 
useful.


Anyhow, I just committed a fix (r73555) which should normally replace 
this 'nan' by its SQL equivalent 'NULL'.




without neighb. statistics & without vector
(Mon Oct 15 14:58:40 2018)
i.segment.stats --overwrite map=SegW24IDM4DV4@LUP1 
rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1 
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90 
area_measures=compact_circle 
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_15okt18b processes=3

Calculating geometry statistics...
Calculating statistics for raster maps...
(Mon Oct 15 15:15:18 2018) Command finished (16 min 38 sec)

with neighb. statistics, but without vector
(Mon Oct 15 15:32:39 2018)
i.segment.stats -n --overwrite map=SegW24IDM4DV4@LUP1 
rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1 
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90 
area_measures=compact_circle 
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_15okt18c processes=3

Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
(Mon Oct 15 15:50:25 2018) Command finished (17 min 46 sec)


These two are normal as your errors are all in the SQL that creates the 
attribute table of the vector. If you do not create a vector map, you 
obvisouly do not get the errors.


Does the content of the csv file look correct ?

Moritz
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-15 Thread Jamille Haarloo
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
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
area_measures=compact_circle
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_15okt18
vectormap=vSegW24IDM4DV4 processes=3
Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Creating output vector map...
DBMI-SQLite driver error:
Error in sqlite3_prepare():
near "IDM4_third_qu": syntax error
ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_10260 (cat
int, compact_circle double precision, DV2_mean double precision, DV2_stddev
double precision, DV2_variance double precision, DV2_coeff_var double
precision, DV2_first_quart double precision, DV2_median double precision,
DV2_third_quart double precision, DV2_perc_90 double precision, DV4_mean
double precision, DV4_stddev double precision, DV4_variance double
precision, DV4_coeff_var double precision, DV4_first_quart double
precision, DV4_median double precision, DV4_third_quart double precision,
DV4_perc_90 double precision, IDM2_mean double precision, IDM2_stddev
double precision, IDM2_variance double precision, IDM2_coeff_var double
precision, IDM2_first_quart double precision, IDM2_median double precision,
IDM2_third_quart double precision, IDM2_perc_90 double precision, IDM4_mean
double precision, IDM4_stddev double precision, IDM4_variance double
precision, IDM4_coeff_var double precision, IDM4_first_quart double
precision, IDM4_median double precision, IDM4_third_quart double precision,
IDM4_perc_90 double precision, W2_mean double precision, W2_stddev double
precision, W2_variance double precision, W2_coeff_var double precision,
W2_first_quart double precision, W2_median double precision, W2_third_quart
double precision, W2_perc_90 double precision, W4_mean double precision,
W4_stddev double precision, W4_variance double precision, W4_coeff_var
double precision, W4_first_quart double precision, W4_median double
precision, W4_third_quart double precision, W4_perc_90 double precision,
neighbors_count double precision, compact_circle_nbrmean double precision,
compact_circle_nbrstddev double precision, DV2_mean_nbrmean double
precision, DV2_mean_nbrstddev double precision, DV2_stddev_nbrmean double
precision, DV2_stddev_nbrstddev double precision, DV2_variance_nbrmean
double precision, DV2_variance_nbrstddev double precision,
DV2_coeff_var_nbrmean double precision, DV2_coeff_var_nbrstddev double
precision, DV2_first_quart_nbrmean double precision,
DV2_first_quart_nbrstddev double precision, DV2_median_nbrmean double
precision, DV2_median_nbrstddev double precision, DV2_third_quart_nbrmean
double precision, DV2_third_quart_nbrstddev double precision,
DV2_perc_90_nbrmean double precision, DV2_perc_90_nbrstddev double
precision, DV4_mean_nbrmean double precision, DV4_mean_nbrstddev double
precision, DV4_stddev_nbrmean double precision, DV4_stddev_nbrstddev double
precision, DV4_variance_nbrmean double precision, DV4_variance_nbrstddev
double precision, DV4_coeff_var_nbrmean double precision,
DV4_coeff_var_nbrstddev double precision, DV4_first_quart_nbrmean double
precision, DV4_first_quart_nbrstddev double precision, DV4_median_nbrmean
double precision, DV4_median_nbrstddev double precision,
DV4_third_quart_nbrmean double precision, DV4_third_quart_nbrstddev double
precision, DV4_perc_90_nbrmean double precision, DV4_perc_90_nbrstddev
double precision, IDM2_mean_nbrmean double precision, IDM2_mean_nbrstddev
double precision, IDM2_stddev_nbrmean double precision,
IDM2_stddev_nbrstddev double precision, IDM2_variance_nbrmean double
precision, IDM2_variance_nbrstddev double precision, IDM2_coeff_var_nbrmean
double precision, IDM2_coeff_var_nbrstddev double precision,
IDM2_first_quart_nbrmean double precision, IDM2_first_quart_nbrstddev
double precision, IDM2_median_nbrmean double precision,
IDM2_median_nbrstddev double precision, IDM2_third_quart_nbrmean double
precision, IDM2_third_quart_nbrstddev double precision,
IDM2_perc_90_nbrmean double precision, IDM2_perc_90_nbrstddev double
precision, IDM4_mean_nbrmean double precision, IDM4_mean_nbrstddev double
precision, IDM4_stddev_nbrmean double precision, IDM4_stddev_nbrstddev
double precision, IDM4_variance_nbrmean double precision,
IDM4_variance_nbrstddev double precision, IDM4_coeff_var_nbrmean double
precision, IDM4_coeff_var_nbrstddev double precision,
IDM4_first_quart_nbrmean double precisiDBMI-SQLite driver error:
Error in sqlite3_prepare():
near "IDM4_third_qu": syntax error
on, IDM4_first_quart_nbrstddev double precision, IDM4_median_nbrmean double
precision, IDM4_median_nbrstddev double precision, IDM4_third_qu'
Traceback (most recent call last):
  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py", 

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-15 Thread Moritz Lennert

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' column-names. I tried to keep the name of the
input maps for the statistics as short and simple possible (without dots
etc).

i.segment.stats -n map=SegW24IDM4DV4@LUP1
rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
area_measures=compact_circle
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_11okt18
vectormap=vSegW24IDM4DV4 processes=2
Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Creating output vector map...
DBMI-SQLite driver error:
Error in sqlite3_prepare():
near "IDM4_third_qu": syntax error
ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_12816 (cat
int, compact_circle double precision, DV2_mean double precision,
DV2_stddev double precision, DV2_variance double precision,
DV2_coeff_var double precision, DV2_first_quart double precision,
DV2_median double precision, DV2_third_quart double precision,
DV2_perc_90 double precision, DV4_mean double precision, DV4_stddev
double precision, DV4_variance double precision, DV4_coeff_var double
precision, DV4_first_quart double precision, DV4_median double
precision, DV4_third_quart double precision, DV4_perc_90 double
precision, IDM2_mean double precision, IDM2_stddev double precision,
IDM2_variance double precision, IDM2_coeff_var double precision,
IDM2_first_quart double precision, IDM2_median double precision,
IDM2_third_quart double precision, IDM2_perc_90 double precision,
IDM4_mean double precision, IDM4_stddev double precision, IDM4_variance
double precision, IDM4_coeff_var double precision, IDM4_first_quart
double precision, IDM4_median double precision, IDM4_third_quart double
precision, IDM4_perc_90 double precision, W2_mean double precision,
W2_stddev double precision, W2_variance double precision, W2_coeff_var
double precision, W2_first_quart double precision, W2_median double
precision, W2_third_quart double precision, W2_perc_90 double precision,
W4_mean double precision, W4_stddev double precision, W4_variance double
precision, W4_coeff_var double precision, W4_first_quart double
precision, W4_median double precision, W4_third_quart double precision,
W4_perc_90 double precision, neighbors_count double precision,
compact_circle_nbrmean double precision, compact_circle_nbrstddev double
precision, DV2_mean_nbrmean double precision, DV2_mean_nbrstddev double
precision, DV2_stddev_nbrmean double precision, DV2_stddev_nbrstddev
double precision, DV2_variance_nbrmean double precision,
DV2_variance_nbrstddev double precision, DV2_coeff_var_nbrmean double
precision, DV2_coeff_var_nbrstddev double precision,
DV2_first_quart_nbrmean double precision, DV2_first_quart_nbrstddev
double precision, DV2_median_nbrmean double precision,
DV2_median_nbrstddev double precision, DV2_third_quart_nbrmean double
precision, DV2_third_quart_nbrstddev double precision,
DV2_perc_90_nbrmean double precision, DV2_perc_90_nbrstddev double
precision, DV4_mean_nbrmean double precision, DV4_mean_nbrstddev double
precision, DV4_stddev_nbrmean double precision, DV4_stddev_nbrstddev
double precision, DV4_variance_nbrmean double precision,
DV4_variance_nbrstddev double precision, DV4_coeff_var_nbrmean double
precision, DV4_coeff_var_nbrstddev double precision,
DV4_first_quart_nbrmean double precision, DV4_first_quart_nbrstddev
double precision, DV4_median_nbrmean double precision,
DV4_median_nbrstddev double precision, DV4_third_quart_nbrmean double
precision, DV4_third_quart_nbrstddev double precision,
DV4_perc_90_nbrmean double precision, DV4_perc_90_nbrstddev double
precision, IDM2_mean_nbrmean double precision, IDM2_mean_nbrstddev
double precision, IDM2_stddev_nbrmean double precision,
IDM2_stddev_nbrstddev double precision, IDM2_variance_nbrmean double
precision, IDM2_variance_nbrstddev double precision,
IDM2_coeff_var_nbrmean double precision, IDM2_coeff_var_nbrstddev double
precision, IDM2_first_quart_nbrmean double precision,
IDM2_first_quart_nbrstddev double precision, IDM2_median_nbrmean double
precision, IDM2_median_nbrstddev double precision,
IDM2_third_quart_nbrmean double precision, IDM2_third_quart_nbrstddev
double precision, IDM2_perc_90_nbrmean double precision,
IDM2_perc_90_nbrstddev double precision, IDM4_mean_nbrmean double
precision, IDM4_mean_nbrstddev double precision, IDM4_stddev_nbrmean
double precision, IDM4_stddev_nbrstddev double precision,
IDM4_variance_nbrmean double precision, IDM4_variance_nbrstddev double
precision, IDM4_coeff_var_nbrmean double precision,
IDM4_coeff_var_nbrstddev double precision, IDM4_first_quart_nbrmean
double precisDBMI-SQLite driver error > Error in sqlite3_prepare():

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-15 Thread Moritz Lennert

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 maps for the statistics as short and simple possible (without dots
etc).

i.segment.stats -n map=SegW24IDM4DV4@LUP1
rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
area_measures=compact_circle
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_11okt18
vectormap=vSegW24IDM4DV4 processes=2
Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Creating output vector map...
DBMI-SQLite driver error:
Error in sqlite3_prepare():
near "IDM4_third_qu": syntax error
ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_12816 (cat
int, compact_circle double precision, DV2_mean double precision,
DV2_stddev double precision, DV2_variance double precision,
DV2_coeff_var double precision, DV2_first_quart double precision,
DV2_median double precision, DV2_third_quart double precision,
DV2_perc_90 double precision, DV4_mean double precision, DV4_stddev
double precision, DV4_variance double precision, DV4_coeff_var double
precision, DV4_first_quart double precision, DV4_median double
precision, DV4_third_quart double precision, DV4_perc_90 double
precision, IDM2_mean double precision, IDM2_stddev double precision,
IDM2_variance double precision, IDM2_coeff_var double precision,
IDM2_first_quart double precision, IDM2_median double precision,
IDM2_third_quart double precision, IDM2_perc_90 double precision,
IDM4_mean double precision, IDM4_stddev double precision, IDM4_variance
double precision, IDM4_coeff_var double precision, IDM4_first_quart
double precision, IDM4_median double precision, IDM4_third_quart double
precision, IDM4_perc_90 double precision, W2_mean double precision,
W2_stddev double precision, W2_variance double precision, W2_coeff_var
double precision, W2_first_quart double precision, W2_median double
precision, W2_third_quart double precision, W2_perc_90 double precision,
W4_mean double precision, W4_stddev double precision, W4_variance double
precision, W4_coeff_var double precision, W4_first_quart double
precision, W4_median double precision, W4_third_quart double precision,
W4_perc_90 double precision, neighbors_count double precision,
compact_circle_nbrmean double precision, compact_circle_nbrstddev double
precision, DV2_mean_nbrmean double precision, DV2_mean_nbrstddev double
precision, DV2_stddev_nbrmean double precision, DV2_stddev_nbrstddev
double precision, DV2_variance_nbrmean double precision,
DV2_variance_nbrstddev double precision, DV2_coeff_var_nbrmean double
precision, DV2_coeff_var_nbrstddev double precision,
DV2_first_quart_nbrmean double precision, DV2_first_quart_nbrstddev
double precision, DV2_median_nbrmean double precision,
DV2_median_nbrstddev double precision, DV2_third_quart_nbrmean double
precision, DV2_third_quart_nbrstddev double precision,
DV2_perc_90_nbrmean double precision, DV2_perc_90_nbrstddev double
precision, DV4_mean_nbrmean double precision, DV4_mean_nbrstddev double
precision, DV4_stddev_nbrmean double precision, DV4_stddev_nbrstddev
double precision, DV4_variance_nbrmean double precision,
DV4_variance_nbrstddev double precision, DV4_coeff_var_nbrmean double
precision, DV4_coeff_var_nbrstddev double precision,
DV4_first_quart_nbrmean double precision, DV4_first_quart_nbrstddev
double precision, DV4_median_nbrmean double precision,
DV4_median_nbrstddev double precision, DV4_third_quart_nbrmean double
precision, DV4_third_quart_nbrstddev double precision,
DV4_perc_90_nbrmean double precision, DV4_perc_90_nbrstddev double
precision, IDM2_mean_nbrmean double precision, IDM2_mean_nbrstddev
double precision, IDM2_stddev_nbrmean double precision,
IDM2_stddev_nbrstddev double precision, IDM2_variance_nbrmean double
precision, IDM2_variance_nbrstddev double precision,
IDM2_coeff_var_nbrmean double precision, IDM2_coeff_var_nbrstddev double
precision, IDM2_first_quart_nbrmean double precision,
IDM2_first_quart_nbrstddev double precision, IDM2_median_nbrmean double
precision, IDM2_median_nbrstddev double precision,
IDM2_third_quart_nbrmean double precision, IDM2_third_quart_nbrstddev
double precision, IDM2_perc_90_nbrmean double precision,
IDM2_perc_90_nbrstddev double precision, IDM4_mean_nbrmean double
precision, IDM4_mean_nbrstddev double precision, IDM4_stddev_nbrmean
double precision, IDM4_stddev_nbrstddev double precision,
IDM4_variance_nbrmean double precision, IDM4_variance_nbrstddev double
precision, IDM4_coeff_var_nbrmean double precision,
IDM4_coeff_var_nbrstddev double precision, IDM4_first_quart_nbrmean
double precisDBMI-SQLite driver error > Error in sqlite3_prepare():
near "IDM4_third_qu": syntax error




Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-15 Thread Moritz Lennert

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 simple possible (without dots 
etc).


i.segment.stats -n map=SegW24IDM4DV4@LUP1 
rasters=DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1 
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90 
area_measures=compact_circle 
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_11okt18 
vectormap=vSegW24IDM4DV4 processes=2

Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Creating output vector map...
DBMI-SQLite driver error:
Error in sqlite3_prepare():
near "IDM4_third_qu": syntax error
ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_12816 (cat 
int, compact_circle double precision, DV2_mean double precision, 
DV2_stddev double precision, DV2_variance double precision, 
DV2_coeff_var double precision, DV2_first_quart double precision, 
DV2_median double precision, DV2_third_quart double precision, 
DV2_perc_90 double precision, DV4_mean double precision, DV4_stddev 
double precision, DV4_variance double precision, DV4_coeff_var double 
precision, DV4_first_quart double precision, DV4_median double 
precision, DV4_third_quart double precision, DV4_perc_90 double 
precision, IDM2_mean double precision, IDM2_stddev double precision, 
IDM2_variance double precision, IDM2_coeff_var double precision, 
IDM2_first_quart double precision, IDM2_median double precision, 
IDM2_third_quart double precision, IDM2_perc_90 double precision, 
IDM4_mean double precision, IDM4_stddev double precision, IDM4_variance 
double precision, IDM4_coeff_var double precision, IDM4_first_quart 
double precision, IDM4_median double precision, IDM4_third_quart double 
precision, IDM4_perc_90 double precision, W2_mean double precision, 
W2_stddev double precision, W2_variance double precision, W2_coeff_var 
double precision, W2_first_quart double precision, W2_median double 
precision, W2_third_quart double precision, W2_perc_90 double precision, 
W4_mean double precision, W4_stddev double precision, W4_variance double 
precision, W4_coeff_var double precision, W4_first_quart double 
precision, W4_median double precision, W4_third_quart double precision, 
W4_perc_90 double precision, neighbors_count double precision, 
compact_circle_nbrmean double precision, compact_circle_nbrstddev double 
precision, DV2_mean_nbrmean double precision, DV2_mean_nbrstddev double 
precision, DV2_stddev_nbrmean double precision, DV2_stddev_nbrstddev 
double precision, DV2_variance_nbrmean double precision, 
DV2_variance_nbrstddev double precision, DV2_coeff_var_nbrmean double 
precision, DV2_coeff_var_nbrstddev double precision, 
DV2_first_quart_nbrmean double precision, DV2_first_quart_nbrstddev 
double precision, DV2_median_nbrmean double precision, 
DV2_median_nbrstddev double precision, DV2_third_quart_nbrmean double 
precision, DV2_third_quart_nbrstddev double precision, 
DV2_perc_90_nbrmean double precision, DV2_perc_90_nbrstddev double 
precision, DV4_mean_nbrmean double precision, DV4_mean_nbrstddev double 
precision, DV4_stddev_nbrmean double precision, DV4_stddev_nbrstddev 
double precision, DV4_variance_nbrmean double precision, 
DV4_variance_nbrstddev double precision, DV4_coeff_var_nbrmean double 
precision, DV4_coeff_var_nbrstddev double precision, 
DV4_first_quart_nbrmean double precision, DV4_first_quart_nbrstddev 
double precision, DV4_median_nbrmean double precision, 
DV4_median_nbrstddev double precision, DV4_third_quart_nbrmean double 
precision, DV4_third_quart_nbrstddev double precision, 
DV4_perc_90_nbrmean double precision, DV4_perc_90_nbrstddev double 
precision, IDM2_mean_nbrmean double precision, IDM2_mean_nbrstddev 
double precision, IDM2_stddev_nbrmean double precision, 
IDM2_stddev_nbrstddev double precision, IDM2_variance_nbrmean double 
precision, IDM2_variance_nbrstddev double precision, 
IDM2_coeff_var_nbrmean double precision, IDM2_coeff_var_nbrstddev double 
precision, IDM2_first_quart_nbrmean double precision, 
IDM2_first_quart_nbrstddev double precision, IDM2_median_nbrmean double 
precision, IDM2_median_nbrstddev double precision, 
IDM2_third_quart_nbrmean double precision, IDM2_third_quart_nbrstddev 
double precision, IDM2_perc_90_nbrmean double precision, 
IDM2_perc_90_nbrstddev double precision, IDM4_mean_nbrmean double 
precision, IDM4_mean_nbrstddev double precision, IDM4_stddev_nbrmean 
double precision, IDM4_stddev_nbrstddev double precision, 
IDM4_variance_nbrmean double precision, IDM4_variance_nbrstddev double 
precision, IDM4_coeff_var_nbrmean double precision, 
IDM4_coeff_var_nbrstddev double precision, IDM4_first_quart_nbrmean 
double precisDBMI-SQLite driver error > Error in sqlite3_prepare():

near 

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-12 Thread Jamille Haarloo
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).

i.segment.stats -n map=SegW24IDM4DV4@LUP1 rasters=DV2@LUP1,DV4@LUP1
,IDM2@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
area_measures=compact_circle
csvfile=C:\Users\haarlooj\Stats_SegW24IDM4DV4_11okt18
vectormap=vSegW24IDM4DV4 processes=2
Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Creating output vector map...
DBMI-SQLite driver error:
Error in sqlite3_prepare():
near "IDM4_third_qu": syntax error
ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_12816 (cat
int, compact_circle double precision, DV2_mean double precision, DV2_stddev
double precision, DV2_variance double precision, DV2_coeff_var double
precision, DV2_first_quart double precision, DV2_median double precision,
DV2_third_quart double precision, DV2_perc_90 double precision, DV4_mean
double precision, DV4_stddev double precision, DV4_variance double
precision, DV4_coeff_var double precision, DV4_first_quart double
precision, DV4_median double precision, DV4_third_quart double precision,
DV4_perc_90 double precision, IDM2_mean double precision, IDM2_stddev
double precision, IDM2_variance double precision, IDM2_coeff_var double
precision, IDM2_first_quart double precision, IDM2_median double precision,
IDM2_third_quart double precision, IDM2_perc_90 double precision, IDM4_mean
double precision, IDM4_stddev double precision, IDM4_variance double
precision, IDM4_coeff_var double precision, IDM4_first_quart double
precision, IDM4_median double precision, IDM4_third_quart double precision,
IDM4_perc_90 double precision, W2_mean double precision, W2_stddev double
precision, W2_variance double precision, W2_coeff_var double precision,
W2_first_quart double precision, W2_median double precision, W2_third_quart
double precision, W2_perc_90 double precision, W4_mean double precision,
W4_stddev double precision, W4_variance double precision, W4_coeff_var
double precision, W4_first_quart double precision, W4_median double
precision, W4_third_quart double precision, W4_perc_90 double precision,
neighbors_count double precision, compact_circle_nbrmean double precision,
compact_circle_nbrstddev double precision, DV2_mean_nbrmean double
precision, DV2_mean_nbrstddev double precision, DV2_stddev_nbrmean double
precision, DV2_stddev_nbrstddev double precision, DV2_variance_nbrmean
double precision, DV2_variance_nbrstddev double precision,
DV2_coeff_var_nbrmean double precision, DV2_coeff_var_nbrstddev double
precision, DV2_first_quart_nbrmean double precision,
DV2_first_quart_nbrstddev double precision, DV2_median_nbrmean double
precision, DV2_median_nbrstddev double precision, DV2_third_quart_nbrmean
double precision, DV2_third_quart_nbrstddev double precision,
DV2_perc_90_nbrmean double precision, DV2_perc_90_nbrstddev double
precision, DV4_mean_nbrmean double precision, DV4_mean_nbrstddev double
precision, DV4_stddev_nbrmean double precision, DV4_stddev_nbrstddev double
precision, DV4_variance_nbrmean double precision, DV4_variance_nbrstddev
double precision, DV4_coeff_var_nbrmean double precision,
DV4_coeff_var_nbrstddev double precision, DV4_first_quart_nbrmean double
precision, DV4_first_quart_nbrstddev double precision, DV4_median_nbrmean
double precision, DV4_median_nbrstddev double precision,
DV4_third_quart_nbrmean double precision, DV4_third_quart_nbrstddev double
precision, DV4_perc_90_nbrmean double precision, DV4_perc_90_nbrstddev
double precision, IDM2_mean_nbrmean double precision, IDM2_mean_nbrstddev
double precision, IDM2_stddev_nbrmean double precision,
IDM2_stddev_nbrstddev double precision, IDM2_variance_nbrmean double
precision, IDM2_variance_nbrstddev double precision, IDM2_coeff_var_nbrmean
double precision, IDM2_coeff_var_nbrstddev double precision,
IDM2_first_quart_nbrmean double precision, IDM2_first_quart_nbrstddev
double precision, IDM2_median_nbrmean double precision,
IDM2_median_nbrstddev double precision, IDM2_third_quart_nbrmean double
precision, IDM2_third_quart_nbrstddev double precision,
IDM2_perc_90_nbrmean double precision, IDM2_perc_90_nbrstddev double
precision, IDM4_mean_nbrmean double precision, IDM4_mean_nbrstddev double
precision, IDM4_stddev_nbrmean double precision, IDM4_stddev_nbrstddev
double precision, IDM4_variance_nbrmean double precision,
IDM4_variance_nbrstddev double precision, IDM4_coeff_var_nbrmean double
precision, IDM4_coeff_var_nbrstddev double precision,
IDM4_first_quart_nbrmean double precisDBMI-SQLite driver error:
Error in sqlite3_prepare():
near "IDM4_third_qu": syntax error
ion, IDM4_first_quart_nbrstddev double precision, IDM4_median_nbrmean
double precision, 

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-11 Thread Moritz Lennert

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.
i.segment.stats -n --overwrite map=SegmW24IDM4DV4@LUP1 
rasters=W2@LUP1,W4@LUP1,DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1 
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90 
area_measures=compact_circle 
csvfile=Z:\grass_cmd_output-i.segment.statsSegmWV24IDM4DV4_11okt2018.txt 
vectormap=VSegmWV24IDM4DV4 processes=4

Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Traceback (most recent call last):
   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py ", line 370, in 
     main()
   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py ", line 282, in main
     quiet=True).splitlines()])
   File "C:\Program Files\GRASS GIS
7.6.svn\etc\python\grass\script\core.py", line 478, in
read_command
     return handle_errors(returncode, stdout, args, kwargs)
   File "C:\Program Files\GRASS GIS
7.6.svn\etc\python\grass\script\core.py", line 334, in
handle_errors
     returncode=returncode)
grass.exceptions.CalledModuleError: Module run None
['r.neighborhoodmatrix', '--q', '-d',
'input=SegmW24IDM4DV4@LUP1'] ended with error


Try reinstalling r.neighborhoodmatrix with g.extension.

Moritz
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-11 Thread Jamille Haarloo
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 rasters=W2@LUP1
,W4@LUP1,DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
area_measures=compact_circle
csvfile=Z:\grass_cmd_output-i.segment.statsSegmWV24IDM4DV4_11okt2018.txt
vectormap=VSegmWV24IDM4DV4 processes=4
Calculating geometry statistics...
Calculating statistics for raster maps...
Calculating neighborhood statistics...
Traceback (most recent call last):
  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py", line 370, in 
main()
  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py", line 282, in main
quiet=True).splitlines()])
  File "C:\Program Files\GRASS GIS
7.6.svn\etc\python\grass\script\core.py", line 478, in
read_command
return handle_errors(returncode, stdout, args, kwargs)
  File "C:\Program Files\GRASS GIS
7.6.svn\etc\python\grass\script\core.py", line 334, in
handle_errors
returncode=returncode)
grass.exceptions.CalledModuleError: Module run None
['r.neighborhoodmatrix', '--q', '-d',
'input=SegmW24IDM4DV4@LUP1'] ended with error
Process ended with non-zero return code -1073741515. See
errors in the (error) output.
(Thu Oct 11 13:30:10 2018) Command finished (15 min 56 sec)

Hopefully it works on Monday!

On Wed, Oct 10, 2018 at 5:46 AM Moritz Lennert 
wrote:

> 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
> > 4|7767.00|1702.00|0.207122|5.447885|1.661054
> > 5|13605.00|2200.00|0.212074|5.320696|1.617158
> > 6|442366.00|44230.00|0.060150|18.759495|1.645730
> >
>
> So everything looks alright.
>
> However:
>
> On 08/10/18 20:40, Jamille Haarloo wrote:
>  > i.segment.stats -n map=SegmW24IDM4DV4@LUP1
>  > rasters=W2@LUP1,W4@LUP1,DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1
>  >
> raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
>
>
>  > area_measures=compact_circle csvfile=X:\Projecten\Land-use Planning
>  > Marowijne\GIS en RS\Werkfolder\GRASS &
>  > R\grass_cmd_output-i.segment.statsSegmWV24IDM4DV4_5okt2018.txt
>  > vectormap=VSegmWV24IDM4DV4 processes=4
>
> I'm not sure how well the script can handle a file path with spaces and
> '&' in it. Maybe this causes some error ?
>
>  > Calculating geometry statistics...
>  > Traceback (most recent call last):
>  >File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
>  > pts/i.segment.stats.py ", line 370, in
> 
>  >  main()
>  >File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
>  > pts/i.segment.stats.py ", line 219, in main
>  >  quiet=True)
>  >File "C:\Program Files\GRASS GIS
>  > 7.6.svn\etc\python\grass\script\core.py", line 423, in
>  > run_command
>  >  return handle_errors(returncode, returncode, args,
>  > kwargs)
>  >File "C:\Program Files\GRASS GIS
>  > 7.6.svn\etc\python\grass\script\core.py", line 334, in
>  > handle_errors
>  >  returncode=returncode)
>  > grass.exceptions.CalledModuleError: Module run None
>  > ['r.object.geometry', '--o', '--q', 'output=Z:\\GRASS_GIS\\C
>  > ottica_LUP\\LUP1\\.tmp/unknown\\10956.0',
>  > 'input=SegmW24IDM4DV4@LUP1'] ended with error
>  > Process ended with non-zero return code -1073741515. See
>  > errors in the (error) output.
>
> The error message does not tell us what went wrong with
> r.object.geometry. Have you tried running i.segment.stats since
> reinstalling r.object.geometry ?
>
> Moritz
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-10 Thread Moritz Lennert

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
4|7767.00|1702.00|0.207122|5.447885|1.661054
5|13605.00|2200.00|0.212074|5.320696|1.617158
6|442366.00|44230.00|0.060150|18.759495|1.645730



So everything looks alright.

However:

On 08/10/18 20:40, Jamille Haarloo wrote:
> i.segment.stats -n map=SegmW24IDM4DV4@LUP1
> rasters=W2@LUP1,W4@LUP1,DV2@LUP1,DV4@LUP1,IDM2@LUP1,IDM4@LUP1
> 
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90 


> area_measures=compact_circle csvfile=X:\Projecten\Land-use Planning
> Marowijne\GIS en RS\Werkfolder\GRASS &
> R\grass_cmd_output-i.segment.statsSegmWV24IDM4DV4_5okt2018.txt
> vectormap=VSegmWV24IDM4DV4 processes=4

I'm not sure how well the script can handle a file path with spaces and 
'&' in it. Maybe this causes some error ?


> Calculating geometry statistics...
> Traceback (most recent call last):
>File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> pts/i.segment.stats.py ", line 370, in 


>  main()
>File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> pts/i.segment.stats.py ", line 219, in main
>  quiet=True)
>File "C:\Program Files\GRASS GIS
> 7.6.svn\etc\python\grass\script\core.py", line 423, in
> run_command
>  return handle_errors(returncode, returncode, args,
> kwargs)
>File "C:\Program Files\GRASS GIS
> 7.6.svn\etc\python\grass\script\core.py", line 334, in
> handle_errors
>  returncode=returncode)
> grass.exceptions.CalledModuleError: Module run None
> ['r.object.geometry', '--o', '--q', 'output=Z:\\GRASS_GIS\\C
> ottica_LUP\\LUP1\\.tmp/unknown\\10956.0',
> 'input=SegmW24IDM4DV4@LUP1'] ended with error
> Process ended with non-zero return code -1073741515. See
> errors in the (error) output.

The error message does not tell us what went wrong with 
r.object.geometry. Have you tried running i.segment.stats since 
reinstalling r.object.geometry ?


Moritz
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-09 Thread Markus Metz
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 memory=1
seeds=SegW24IDM4DV4@LUP1 goodness=SegmW24IDM4DV4_goodn
> Maximum number of iterations set to 50
> Loading input bands...
> Loading seeds from raster map ...
> Processing pass 1...
> Processing pass 2...
> Processing pass 3...
> Processing pass 4...
> Processing pass 5...
> Processing pass 6...
> Processing pass 7...
> Processing pass 8...
> Processing pass 9...
> Segmentation converged after 9 iterations
> Assigning region IDs to remaining single-cell regions...
> Merging segments smaller than 5000 cells...
> Writing out segment IDs...
> Writing out goodness of fit
> ERROR: Region of size 635805 should be in search tree

This error is now fixed in trunk, relbr76, and relbr74 (r73512-4)

Markus M

>
> On Thu, Oct 4, 2018 at 4:07 PM Markus Metz 
wrote:
>>
>> 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, 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 started using a mask to eliminate most of the matrix, to see if that
helped. It did not, so I started the process again in i.segment but with
the previous segmentation output as seed to reduce processing. This time I
also got an error with i.segment in 2 attempts with different parameters. I
looked for documentation, but I couldn't find any solutions and I rather
not mess with the scripts. I do get a raster-output which looks ok, but
i.segment.stats fails to create an attribute table for further analyses. My
questions are: Is the area too big (too much pixels)? Are there too many
segments? The count of the last output is 9054 segments. Or should I start
the process again form the beginning without the seed assuming the Mask is
not the problem? The processing might take several weeks though.
>> >
>> >  i.segment error:
>> > ERROR: Region of size 501508 should be in search tree
>> >
>> > i.segment.stats errors:
>> > ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_7968
(cat int, area double precision, compact_circle double precision, DV2_mean
double precision, DV2_stddev double precision, DV2_variance double
precision, DV2_coeff_var double precision, DV2_first_quart double
precision, DV2_median double precision, DV2_third_quart double precision,
DV2_perc_90 double precision, DV4_mean double precision, DV4_stddev double
precision, DV4_variance double precision, DV4_coeff_var double precision,
DV4_first_quart double precision, DV4_median double precision,
DV4_third_quart double precision, DV4_perc_90 double precision, IDM2_mean
double precision, IDM2_stddev double precision, IDM2_variance double
precision, IDM2_coeff_var double precision, IDM2_first_quart double
precision, IDM2_median double precision, IDM2_third_quart double precision,
IDM2_perc_90 double precision, IDM4_mean double precision, IDM4_stddev
double precision, IDM4_variance double precision, IDM4_coeff_var double
precision, IDM4_first_quart double precision, IDM4_median double precision,
IDM4_third_quart double precision, IDM4_perc_90 double precision, W2_mean
double precision, W2_stddev double precision, W2_variance double precision,
W2_coeff_var double precision, W2_first_quart double precision, W2_median
double precision, W2_third_quart double precision, W2_perc_90 double
precision, DV4_mean double precision, DV4_stddev double precision,
DV4_variance double precision, DV4_coeff_var double precision,
DV4_first_quart double precision, DV4_median double precision,
DV4_third_quart double precision, DV4_perc_90 double precision,
neighbors_count double precision, area_nbrmean double precision,
area_nbrstddev double precision, compact_circle_nbrmean double precision,
compact_circle_nbrstddev double precision, DV2_mean_nbrmean double
precision, DV2_mean_nbrstddev double precision, DV2_stddev_nbrmean double
precision, DV2_stddev_nbrstddev double precision, DV2_variance_nbrmean
double precision, DV2_variance_nbrstddeGRASS_INFO_ERROR(7020,1):
>> > Traceback (most recent call last):
>> >   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
>> > pts/i.segment.stats.py", line 370, in 
>> > main()
>> >   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
>> > pts/i.segment.stats.py", line 357, in main
>> > gscript.run_command('db.execute', input=insert_sql,
>> > quiet=True)
>> >   File "C:\Program Files\GRASS GIS
>> > 

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-09 Thread Jamille Haarloo
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
5|13605.00|2200.00|0.212074|5.320696|1.617158
6|442366.00|44230.00|0.060150|18.759495|1.645730

--
Windows 7
Dell
Proc. Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
RAM: 16 GB
--
Could the "ju" be caused my the Mask?
--
I used uspo on 3 regions to decide on parameters. 0.24 as treshold and
minsize 3500 looked to be the best combination of parameters studying all
the results in the output file.
Summary:
regions=regionAB@LUP1,regionD@LUP1,regionRM@LUP1
segmentation_method=region_growing threshold_start=0.18 threshold_stop=0.25
threshold_step=0.02 minsize_start=3000 minsize_stop=6000 minsize_step=500
optimization_function=f number_best=2 memory=8000 processes=4
Working on region regionAB@LUP1
Working on region regionD@LUP1
Working on region regionRM@LUP1
Best values:
Region Thresh Minsize Optimization
regionRM@LUP1 0.24 3500 0.7951456323
regionRM@LUP1 0.24 3000 0.765849594003
regionAB@LUP1 0.24 4000 0.630706501774
regionAB@LUP1 0.24 3500 0.472619083853
regionD@LUP1 0.2 3000 0.802618475115
regionD@LUP1 0.22 3000 0.77939730321

I also had other uspo runs but with less useful results.

The map with segments was created (0.24 treshold minsize 3500). But after
the errors with i.segment.stats I reasoned the number of segments (18685)
was too much to handle as it failed to create the attribute table. To
reduce the number of segments, I used this map as seed to create a new
segmentation map with the parameters 0.25 and 5000 and a mask to eliminate
the matrix.
But now I see the number of segments shouldn't have been a problem in this
case.

On Tue, Oct 9, 2018 at 9:35 AM Moritz Lennert 
wrote:

> 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  successfully finished
> > (Mon Oct 08 16:55:04 2018) Command finished (4 sec)
> > (Mon Oct 08 16:55:53 2018)
> > r.object.geometry SegmW24IDM4DV4 output=test.csv
> > Calculating statistics
> > Writing output
> > (Mon Oct 08 16:56:14 2018) Command finished (21 sec)
>
> Could you provide the first lines of content of test.csv ?
>
> >
> > g.region -p
> > projection: 1 (UTM)
> > zone:   21
> > datum:  wgs84
> > ellipsoid:  wgs84
> > north:  634826.41313284
> > south:  611477.61329757
> > west:   775494.11663193
> > east:   793630.22784822
> > nsres:  0.5642
> > ewres:  0.5307
> > rows:   46697
> > cols:   36272
> > cells:  1693793584
>
>
> So you have over 1.5 billion cells. That's quite big, but not impossible
> to handle. Depends on your machine.
>
> >
> > r.info  SegmW24IDM4DV4
> >
>  
> ++
> >   | Map:  SegmW24IDM4DV4 Date: Fri Oct 05 23:46:04
> > 2018|
> >   | Mapset:   LUP1   Login of Creator: haarlooj
> >|
> >   | Location: Cottica_LUP
> >|
> >   | DataBase: Z:\GRASS_GIS
> > |
> >   | Title:
> > |
> >   | Timestamp: none
> >|
> >
>  
> ||
> >   |
> >|
> >   |   Type of Map:  raster   Number of Categories: 0
> > |
> >   |   Data Type:CELL
> > |
> >   |   Rows: 46697
> >|
> >   |   Columns:  36272
> >|
> >   |   Total Cells:  ju
>
>
> This 'ju' is weird, here.
>
>
> > |
> >   |Projection: UTM (zone 21)
> > |
> >   |N: 634826.41313284S: 611477.61329757   Res:
> > 0.5642  |
> >   |E: 793630.22784822W: 775494.11663193   Res:
> > 0.5307  |
> >   |   Range of data:min = 1  max = 12901
> > |
> >   |
> >|
> >   |   Data Description:
> >|
> >   |generated by i.segment
> >|
> >   |
> >|
> >   |   Comments:
> >|
> >   |i.segment --overwrite group="DV4@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1"
> > out\   |
> >   |put="SegmW24IDM4DV4" threshold=0.25 radius=1.5
> > method="region_growin\   |
> >   |g" similarity="euclidean" minsize=5000 memory=1
> > seeds="SegW24IDM\   |
> >   |4DV4@LUP1" goodness="SegmW24IDM4DV4_goodn"
>
>
> You only have 12901 segments, so an average size of 32822m2 per segment.
> Is this what you aimed for ? As you asked for a minsize of 5000 pixels I
> guess this is deliberate.
>
> You threshold of 0.25 is also very high...
>
> Moritz
>
___

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-09 Thread Moritz Lennert

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  successfully finished
(Mon Oct 08 16:55:04 2018) Command finished (4 sec)
(Mon Oct 08 16:55:53 2018)
r.object.geometry SegmW24IDM4DV4 output=test.csv
Calculating statistics
Writing output
(Mon Oct 08 16:56:14 2018) Command finished (21 sec)


Could you provide the first lines of content of test.csv ?



g.region -p
projection: 1 (UTM)
zone:       21
datum:      wgs84
ellipsoid:  wgs84
north:      634826.41313284
south:      611477.61329757
west:       775494.11663193
east:       793630.22784822
nsres:      0.5642
ewres:      0.5307
rows:       46697
cols:       36272
cells:      1693793584



So you have over 1.5 billion cells. That's quite big, but not impossible 
to handle. Depends on your machine.




r.info  SegmW24IDM4DV4
  ++
  | Map:      SegmW24IDM4DV4                 Date: Fri Oct 05 23:46:04 
2018    |
  | Mapset:   LUP1                           Login of Creator: haarlooj  
       |
  | Location: Cottica_LUP
       |
  | DataBase: Z:\GRASS_GIS  
        |
  | Title:  
        |
  | Timestamp: none  
       |

  ||
  |  
       |
  |   Type of Map:  raster               Number of Categories: 0
        |
  |   Data Type:    CELL
        |
  |   Rows:         46697
       |
  |   Columns:      36272
       |
  |   Total Cells:  ju   



This 'ju' is weird, here.



        |
  |        Projection: UTM (zone 21)
        |
  |            N: 634826.41313284    S: 611477.61329757   Res: 
0.5642      |
  |            E: 793630.22784822    W: 775494.11663193   Res: 
0.5307      |
  |   Range of data:    min = 1  max = 12901
        |
  |  
       |
  |   Data Description:  
       |
  |    generated by i.segment
       |
  |  
       |
  |   Comments:  
       |
  |    i.segment --overwrite group="DV4@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1" 
out\   |
  |    put="SegmW24IDM4DV4" threshold=0.25 radius=1.5 
method="region_growin\   |
  |    g" similarity="euclidean" minsize=5000 memory=1 
seeds="SegW24IDM\   |

  |    4DV4@LUP1" goodness="SegmW24IDM4DV4_goodn"



You only have 12901 segments, so an average size of 32822m2 per segment. 
Is this what you aimed for ? As you asked for a minsize of 5000 pixels I 
guess this is deliberate.


You threshold of 0.25 is also very high...

Moritz
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-09 Thread Jamille Haarloo
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 2018) Command finished (4 sec)

(Mon Oct 08 16:55:53 2018)

r.object.geometry SegmW24IDM4DV4 output=test.csv

Calculating statistics
Writing output
(Mon Oct 08 16:56:14 2018) Command finished (21 sec)

g.region -p

projection: 1 (UTM)
zone:   21
datum:  wgs84
ellipsoid:  wgs84
north:  634826.41313284
south:  611477.61329757
west:   775494.11663193
east:   793630.22784822
nsres:  0.5642
ewres:  0.5307
rows:   46697
cols:   36272
cells:  1693793584

r.info SegmW24IDM4DV4

 ++
 | Map:  SegmW24IDM4DV4 Date: Fri Oct 05 23:46:04 2018
  |
 | Mapset:   LUP1   Login of Creator: haarlooj
  |
 | Location: Cottica_LUP
  |
 | DataBase: Z:\GRASS_GIS
   |
 | Title:
   |
 | Timestamp: none
  |
 ||
 |
  |
 |   Type of Map:  raster   Number of Categories: 0
   |
 |   Data Type:CELL
   |
 |   Rows: 46697
  |
 |   Columns:  36272
  |
 |   Total Cells:  ju
   |
 |Projection: UTM (zone 21)
   |
 |N: 634826.41313284S: 611477.61329757   Res: 0.5642
  |
 |E: 793630.22784822W: 775494.11663193   Res: 0.5307
  |
 |   Range of data:min = 1  max = 12901
   |
 |
  |
 |   Data Description:
  |
 |generated by i.segment
  |
 |
  |
 |   Comments:
  |
 |i.segment --overwrite group="DV4@LUP1,IDM4@LUP1,W2@LUP1,W4@LUP1"
out\   |
 |put="SegmW24IDM4DV4" threshold=0.25 radius=1.5
method="region_growin\   |
 |g" similarity="euclidean" minsize=5000 memory=1
seeds="SegW24IDM\   |
 |4DV4@LUP1" goodness="SegmW24IDM4DV4_goodn"

On Mon, Oct 8, 2018 at 4:27 PM Moritz Lennert 
wrote:

>
>
> Am 8. Oktober 2018 20:40:39 MESZ schrieb Jamille Haarloo <
> j.r.haar...@gmail.com>:
> >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
> >rasters=W2@LUP1,W4@LUP1,DV2@LUP1
> >,DV4@LUP1,IDM2@LUP1,IDM4@LUP1
>
> >raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
> >area_measures=compact_circle csvfile=X:\Projecten\Land-use Planning
> >Marowijne\GIS en RS\Werkfolder\GRASS &
> >R\grass_cmd_output-i.segment.statsSegmWV24IDM4DV4_5okt2018.txt
> >vectormap=VSegmWV24IDM4DV4 processes=4
> >Calculating geometry statistics...
> >Traceback (most recent call last):
> >  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> >pts/i.segment.stats.py", line 370, in 
> >main()
> >  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> >pts/i.segment.stats.py", line 219, in main
> >quiet=True)
> >  File "C:\Program Files\GRASS GIS
> >7.6.svn\etc\python\grass\script\core.py", line 423, in
> >run_command
> >return handle_errors(returncode, returncode, args,
> >kwargs)
> >  File "C:\Program Files\GRASS GIS
> >7.6.svn\etc\python\grass\script\core.py", line 334, in
> >handle_errors
> >returncode=returncode)
> >grass.exceptions.CalledModuleError: Module run None
> >['r.object.geometry', '--o', '--q', 'output=Z:\\GRASS_GIS\\C
> >ottica_LUP\\LUP1\\.tmp/unknown\\10956.0',
> >'input=SegmW24IDM4DV4@LUP1'] ended with error
>
>
> Could you directly run r.object.geometry:
>
> r.object.geometry SegmW24IDM4DV4 output=test.csv
>
> and tell us what you get ?
>
> And what is your computational region (g.region -p)  and the output of
> r.info SegmW24IDM4DV4 ?
>
> Moritz
>
> >Process ended with non-zero return code -1073741515. See
> >errors in the (error) output.
> >
> >On Mon, Oct 8, 2018 at 10:06 AM Moritz Lennert
> >
> >wrote:
> >
> >> 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 precision, DV2_stddev double precision, DV2_variance double
> >> > precision, DV2_coeff_var double precision, DV2_first_quart double
> >> > precision, DV2_median double precision, DV2_third_quart double
> >> > precision, DV2_perc_90 double precision, DV4_mean double precision,
> >> > DV4_stddev double precision, DV4_variance double precision,
> >> > DV4_coeff_var double precision, DV4_first_quart double precision,
> >> > DV4_median double precision, DV4_third_quart double 

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-08 Thread Moritz Lennert


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 on this error now.
>
>i.segment.stats -n map=SegmW24IDM4DV4@LUP1
>rasters=W2@LUP1,W4@LUP1,DV2@LUP1
>,DV4@LUP1,IDM2@LUP1,IDM4@LUP1
>raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
>area_measures=compact_circle csvfile=X:\Projecten\Land-use Planning
>Marowijne\GIS en RS\Werkfolder\GRASS &
>R\grass_cmd_output-i.segment.statsSegmWV24IDM4DV4_5okt2018.txt
>vectormap=VSegmWV24IDM4DV4 processes=4
>Calculating geometry statistics...
>Traceback (most recent call last):
>  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
>pts/i.segment.stats.py", line 370, in 
>main()
>  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
>pts/i.segment.stats.py", line 219, in main
>quiet=True)
>  File "C:\Program Files\GRASS GIS
>7.6.svn\etc\python\grass\script\core.py", line 423, in
>run_command
>return handle_errors(returncode, returncode, args,
>kwargs)
>  File "C:\Program Files\GRASS GIS
>7.6.svn\etc\python\grass\script\core.py", line 334, in
>handle_errors
>returncode=returncode)
>grass.exceptions.CalledModuleError: Module run None
>['r.object.geometry', '--o', '--q', 'output=Z:\\GRASS_GIS\\C
>ottica_LUP\\LUP1\\.tmp/unknown\\10956.0',
>'input=SegmW24IDM4DV4@LUP1'] ended with error


Could you directly run r.object.geometry:

r.object.geometry SegmW24IDM4DV4 output=test.csv

and tell us what you get ?

And what is your computational region (g.region -p)  and the output of r.info 
SegmW24IDM4DV4 ?

Moritz

>Process ended with non-zero return code -1073741515. See
>errors in the (error) output.
>
>On Mon, Oct 8, 2018 at 10:06 AM Moritz Lennert
>
>wrote:
>
>> 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 precision, DV2_stddev double precision, DV2_variance double
>> > precision, DV2_coeff_var double precision, DV2_first_quart double
>> > precision, DV2_median double precision, DV2_third_quart double
>> > precision, DV2_perc_90 double precision, DV4_mean double precision,
>> > DV4_stddev double precision, DV4_variance double precision,
>> > DV4_coeff_var double precision, DV4_first_quart double precision,
>> > DV4_median double precision, DV4_third_quart double precision,
>> > DV4_perc_90 double precision, IDM2_mean double precision,
>IDM2_stddev
>> > double precision, IDM2_variance double precision, IDM2_coeff_var
>double
>> > precision, IDM2_first_quart double precision, IDM2_median double
>> > precision, IDM2_third_quart double precision, IDM2_perc_90 double
>> > precision, IDM4_mean double precision, IDM4_stddev double
>precision,
>> > IDM4_variance double precision, IDM4_coeff_var double precision,
>> > IDM4_first_quart double precision, IDM4_median double precision,
>> > IDM4_third_quart double precision, IDM4_perc_90 double precision,
>> > W2_mean double precision, W2_stddev double precision, W2_variance
>double
>> > precision, W2_coeff_var double precision, W2_first_quart double
>> > precision, W2_median double precision, W2_third_quart double
>precision,
>> > W2_perc_90 double precision, DV4_mean double precision, DV4_stddev
>> > double precision, DV4_variance double precision, DV4_coeff_var
>double
>> > precision, DV4_first_quart double precision, DV4_median double
>> > precision, DV4_third_quart double precision, DV4_perc_90 double
>> > precision, neighbors_count double precision, area_nbrmean double
>> > precision, area_nbrstddev double precision, compact_circle_nbrmean
>> > double precision, compact_circle_nbrstddev double precision,
>> > DV2_mean_nbrmean double precision, DV2_mean_nbrstddev double
>precision,
>> > DV2_stddev_nbrmean double precision, DV2_stddev_nbrstddev double
>> > precision, DV2_variance_nbrmean double precision,
>> > DV2_variance_nbrstddeGRASS_INFO_ERROR(7020,1):
>>
>> The DV2 and DV4 maps seem to be there twice and so there are
>duplicate
>> column names, leading to a failure in the CREATE TABLE call.
>>
>> In the call to i.segment.stats, did you maybe add these map names
>twice
>> to the 'rasters' parameter by accident ?
>>
>> Moritz
>>
>>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-08 Thread 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 on this error now.

i.segment.stats -n map=SegmW24IDM4DV4@LUP1 rasters=W2@LUP1,W4@LUP1,DV2@LUP1
,DV4@LUP1,IDM2@LUP1,IDM4@LUP1
raster_statistics=mean,stddev,variance,coeff_var,first_quart,median,third_quart,perc_90
area_measures=compact_circle csvfile=X:\Projecten\Land-use Planning
Marowijne\GIS en RS\Werkfolder\GRASS &
R\grass_cmd_output-i.segment.statsSegmWV24IDM4DV4_5okt2018.txt
vectormap=VSegmWV24IDM4DV4 processes=4
Calculating geometry statistics...
Traceback (most recent call last):
  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py", line 370, in 
main()
  File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
pts/i.segment.stats.py", line 219, in main
quiet=True)
  File "C:\Program Files\GRASS GIS
7.6.svn\etc\python\grass\script\core.py", line 423, in
run_command
return handle_errors(returncode, returncode, args,
kwargs)
  File "C:\Program Files\GRASS GIS
7.6.svn\etc\python\grass\script\core.py", line 334, in
handle_errors
returncode=returncode)
grass.exceptions.CalledModuleError: Module run None
['r.object.geometry', '--o', '--q', 'output=Z:\\GRASS_GIS\\C
ottica_LUP\\LUP1\\.tmp/unknown\\10956.0',
'input=SegmW24IDM4DV4@LUP1'] ended with error
Process ended with non-zero return code -1073741515. See
errors in the (error) output.

On Mon, Oct 8, 2018 at 10:06 AM Moritz Lennert 
wrote:

> 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 precision, DV2_stddev double precision, DV2_variance double
> > precision, DV2_coeff_var double precision, DV2_first_quart double
> > precision, DV2_median double precision, DV2_third_quart double
> > precision, DV2_perc_90 double precision, DV4_mean double precision,
> > DV4_stddev double precision, DV4_variance double precision,
> > DV4_coeff_var double precision, DV4_first_quart double precision,
> > DV4_median double precision, DV4_third_quart double precision,
> > DV4_perc_90 double precision, IDM2_mean double precision, IDM2_stddev
> > double precision, IDM2_variance double precision, IDM2_coeff_var double
> > precision, IDM2_first_quart double precision, IDM2_median double
> > precision, IDM2_third_quart double precision, IDM2_perc_90 double
> > precision, IDM4_mean double precision, IDM4_stddev double precision,
> > IDM4_variance double precision, IDM4_coeff_var double precision,
> > IDM4_first_quart double precision, IDM4_median double precision,
> > IDM4_third_quart double precision, IDM4_perc_90 double precision,
> > W2_mean double precision, W2_stddev double precision, W2_variance double
> > precision, W2_coeff_var double precision, W2_first_quart double
> > precision, W2_median double precision, W2_third_quart double precision,
> > W2_perc_90 double precision, DV4_mean double precision, DV4_stddev
> > double precision, DV4_variance double precision, DV4_coeff_var double
> > precision, DV4_first_quart double precision, DV4_median double
> > precision, DV4_third_quart double precision, DV4_perc_90 double
> > precision, neighbors_count double precision, area_nbrmean double
> > precision, area_nbrstddev double precision, compact_circle_nbrmean
> > double precision, compact_circle_nbrstddev double precision,
> > DV2_mean_nbrmean double precision, DV2_mean_nbrstddev double precision,
> > DV2_stddev_nbrmean double precision, DV2_stddev_nbrstddev double
> > precision, DV2_variance_nbrmean double precision,
> > DV2_variance_nbrstddeGRASS_INFO_ERROR(7020,1):
>
> The DV2 and DV4 maps seem to be there twice and so there are duplicate
> column names, leading to a failure in the CREATE TABLE call.
>
> In the call to i.segment.stats, did you maybe add these map names twice
> to the 'rasters' parameter by accident ?
>
> Moritz
>
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-08 Thread Jamille Haarloo
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 number of iterations set to 50
Loading input bands...
Loading seeds from raster map ...
Processing pass 1...
Processing pass 2...
Processing pass 3...
Processing pass 4...
Processing pass 5...
Processing pass 6...
Processing pass 7...
Processing pass 8...
Processing pass 9...
Segmentation converged after 9 iterations
Assigning region IDs to remaining single-cell regions...
Merging segments smaller than 5000 cells...
Writing out segment IDs...
Writing out goodness of fit
ERROR: Region of size 635805 should be in search tree

On Thu, Oct 4, 2018 at 4:07 PM Markus Metz 
wrote:

> 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, 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 started using a mask to eliminate most of the matrix, to see if that
> helped. It did not, so I started the process again in i.segment but with
> the previous segmentation output as seed to reduce processing. This time I
> also got an error with i.segment in 2 attempts with different parameters. I
> looked for documentation, but I couldn't find any solutions and I rather
> not mess with the scripts. I do get a raster-output which looks ok, but
> i.segment.stats fails to create an attribute table for further analyses. My
> questions are: Is the area too big (too much pixels)? Are there too many
> segments? The count of the last output is 9054 segments. Or should I start
> the process again form the beginning without the seed assuming the Mask is
> not the problem? The processing might take several weeks though.
> >
> >  i.segment error:
> > ERROR: Region of size 501508 should be in search tree
> >
> > i.segment.stats errors:
> > ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_7968 (cat
> int, area double precision, compact_circle double precision, DV2_mean
> double precision, DV2_stddev double precision, DV2_variance double
> precision, DV2_coeff_var double precision, DV2_first_quart double
> precision, DV2_median double precision, DV2_third_quart double precision,
> DV2_perc_90 double precision, DV4_mean double precision, DV4_stddev double
> precision, DV4_variance double precision, DV4_coeff_var double precision,
> DV4_first_quart double precision, DV4_median double precision,
> DV4_third_quart double precision, DV4_perc_90 double precision, IDM2_mean
> double precision, IDM2_stddev double precision, IDM2_variance double
> precision, IDM2_coeff_var double precision, IDM2_first_quart double
> precision, IDM2_median double precision, IDM2_third_quart double precision,
> IDM2_perc_90 double precision, IDM4_mean double precision, IDM4_stddev
> double precision, IDM4_variance double precision, IDM4_coeff_var double
> precision, IDM4_first_quart double precision, IDM4_median double precision,
> IDM4_third_quart double precision, IDM4_perc_90 double precision, W2_mean
> double precision, W2_stddev double precision, W2_variance double precision,
> W2_coeff_var double precision, W2_first_quart double precision, W2_median
> double precision, W2_third_quart double precision, W2_perc_90 double
> precision, DV4_mean double precision, DV4_stddev double precision,
> DV4_variance double precision, DV4_coeff_var double precision,
> DV4_first_quart double precision, DV4_median double precision,
> DV4_third_quart double precision, DV4_perc_90 double precision,
> neighbors_count double precision, area_nbrmean double precision,
> area_nbrstddev double precision, compact_circle_nbrmean double precision,
> compact_circle_nbrstddev double precision, DV2_mean_nbrmean double
> precision, DV2_mean_nbrstddev double precision, DV2_stddev_nbrmean double
> precision, DV2_stddev_nbrstddev double precision, DV2_variance_nbrmean
> double precision, DV2_variance_nbrstddeGRASS_INFO_ERROR(7020,1):
> > Traceback (most recent call last):
> >   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> > pts/i.segment.stats.py", line 370, in 
> > main()
> >   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> > pts/i.segment.stats.py", line 357, in main
> > gscript.run_command('db.execute', input=insert_sql,
> > quiet=True)
> >   File "C:\Program Files\GRASS GIS
> > 7.4.0\etc\python\grass\script\core.py", line 421, in
> > run_command
> > return handle_errors(returncode, returncode, args,
> > 

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-08 Thread Moritz Lennert

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 precision, DV2_stddev double precision, DV2_variance double 
precision, DV2_coeff_var double precision, DV2_first_quart double 
precision, DV2_median double precision, DV2_third_quart double 
precision, DV2_perc_90 double precision, DV4_mean double precision, 
DV4_stddev double precision, DV4_variance double precision, 
DV4_coeff_var double precision, DV4_first_quart double precision, 
DV4_median double precision, DV4_third_quart double precision, 
DV4_perc_90 double precision, IDM2_mean double precision, IDM2_stddev 
double precision, IDM2_variance double precision, IDM2_coeff_var double 
precision, IDM2_first_quart double precision, IDM2_median double 
precision, IDM2_third_quart double precision, IDM2_perc_90 double 
precision, IDM4_mean double precision, IDM4_stddev double precision, 
IDM4_variance double precision, IDM4_coeff_var double precision, 
IDM4_first_quart double precision, IDM4_median double precision, 
IDM4_third_quart double precision, IDM4_perc_90 double precision, 
W2_mean double precision, W2_stddev double precision, W2_variance double 
precision, W2_coeff_var double precision, W2_first_quart double 
precision, W2_median double precision, W2_third_quart double precision, 
W2_perc_90 double precision, DV4_mean double precision, DV4_stddev 
double precision, DV4_variance double precision, DV4_coeff_var double 
precision, DV4_first_quart double precision, DV4_median double 
precision, DV4_third_quart double precision, DV4_perc_90 double 
precision, neighbors_count double precision, area_nbrmean double 
precision, area_nbrstddev double precision, compact_circle_nbrmean 
double precision, compact_circle_nbrstddev double precision, 
DV2_mean_nbrmean double precision, DV2_mean_nbrstddev double precision, 
DV2_stddev_nbrmean double precision, DV2_stddev_nbrstddev double 
precision, DV2_variance_nbrmean double precision, 
DV2_variance_nbrstddeGRASS_INFO_ERROR(7020,1):


The DV2 and DV4 maps seem to be there twice and so there are duplicate 
column names, leading to a failure in the CREATE TABLE call.


In the call to i.segment.stats, did you maybe add these map names twice 
to the 'rasters' parameter by accident ?


Moritz

___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.segment and i.segment.stats errors

2018-10-04 Thread Markus Metz
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, 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 started using a mask to eliminate most of the matrix, to see if that
helped. It did not, so I started the process again in i.segment but with
the previous segmentation output as seed to reduce processing. This time I
also got an error with i.segment in 2 attempts with different parameters. I
looked for documentation, but I couldn't find any solutions and I rather
not mess with the scripts. I do get a raster-output which looks ok, but
i.segment.stats fails to create an attribute table for further analyses. My
questions are: Is the area too big (too much pixels)? Are there too many
segments? The count of the last output is 9054 segments. Or should I start
the process again form the beginning without the seed assuming the Mask is
not the problem? The processing might take several weeks though.
>
>  i.segment error:
> ERROR: Region of size 501508 should be in search tree
>
> i.segment.stats errors:
> ERROR: Error while executing: 'CREATE TABLE segmstat_tmp_vect_7968 (cat
int, area double precision, compact_circle double precision, DV2_mean
double precision, DV2_stddev double precision, DV2_variance double
precision, DV2_coeff_var double precision, DV2_first_quart double
precision, DV2_median double precision, DV2_third_quart double precision,
DV2_perc_90 double precision, DV4_mean double precision, DV4_stddev double
precision, DV4_variance double precision, DV4_coeff_var double precision,
DV4_first_quart double precision, DV4_median double precision,
DV4_third_quart double precision, DV4_perc_90 double precision, IDM2_mean
double precision, IDM2_stddev double precision, IDM2_variance double
precision, IDM2_coeff_var double precision, IDM2_first_quart double
precision, IDM2_median double precision, IDM2_third_quart double precision,
IDM2_perc_90 double precision, IDM4_mean double precision, IDM4_stddev
double precision, IDM4_variance double precision, IDM4_coeff_var double
precision, IDM4_first_quart double precision, IDM4_median double precision,
IDM4_third_quart double precision, IDM4_perc_90 double precision, W2_mean
double precision, W2_stddev double precision, W2_variance double precision,
W2_coeff_var double precision, W2_first_quart double precision, W2_median
double precision, W2_third_quart double precision, W2_perc_90 double
precision, DV4_mean double precision, DV4_stddev double precision,
DV4_variance double precision, DV4_coeff_var double precision,
DV4_first_quart double precision, DV4_median double precision,
DV4_third_quart double precision, DV4_perc_90 double precision,
neighbors_count double precision, area_nbrmean double precision,
area_nbrstddev double precision, compact_circle_nbrmean double precision,
compact_circle_nbrstddev double precision, DV2_mean_nbrmean double
precision, DV2_mean_nbrstddev double precision, DV2_stddev_nbrmean double
precision, DV2_stddev_nbrstddev double precision, DV2_variance_nbrmean
double precision, DV2_variance_nbrstddeGRASS_INFO_ERROR(7020,1):
> Traceback (most recent call last):
>   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> pts/i.segment.stats.py", line 370, in 
> main()
>   File "C:\Users\haarlooj\AppData\Roaming\GRASS7\addons/scri
> pts/i.segment.stats.py", line 357, in main
> gscript.run_command('db.execute', input=insert_sql,
> quiet=True)
>   File "C:\Program Files\GRASS GIS
> 7.4.0\etc\python\grass\script\core.py", line 421, in
> run_command
> return handle_errors(returncode, returncode, args,
> kwargs)
>   File "C:\Program Files\GRASS GIS
> 7.4.0\etc\python\grass\script\core.py", line 332, in
> handle_errors
> returncode=returncode)
> grass.exceptions.CalledModuleError: Module run None
> ['db.execute', '--q', 'input=Z:\\GRASS_GIS\\Cottica_LUP\\LUP
> 1\\.tmp/unknown\\7968.1'] ended with error
> Process ended with non-zero return code 1. See errors in the
> (error) output.
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user