[GRASS-dev] GSoC weekly report 2006_0619_yb

[Yang, Bo (yangb2)]

Hi all,

Please see the link below for GSoC_2016_Additional_segmentation_algorithms week 
4 report.

https://trac.osgeo.org/grass/wiki/GSoC/2016/Additional_segmentation_algorithms/weekly_report#a12June--19Juneweek4:

Best,
Bo Yang
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC weekly report 2006_0612_yb

[Yang, Bo (yangb2)]

Hi Markus, Maris,

Thanks! It is a very useful tools for me. 
That "random bug" has been fixed for the time being (an input threshold 
parameter was too large previously). But I will learn to use Valgrind and let 
you know if I have further questions. 

Best,
Bo yang

> -Original Message-
> From: neteler.os...@gmail.com [mailto:neteler.os...@gmail.com] On Behalf
> Of Markus Neteler
> Sent: Wednesday, June 15, 2016 5:11 AM
> To: Maris Nartiss <maris....@gmail.com>
> Cc: Yang, Bo (yangb2) <yan...@mail.uc.edu>; GRASS developers list  d...@lists.osgeo.org>
> Subject: Re: [GRASS-dev] GSoC weekly report 2006_0612_yb
> 
> On Wed, Jun 15, 2016 at 9:30 AM, Maris Nartiss <maris@gmail.com> wrote:
> > Hello,
> > you are mentioning some kind of "random bug". To hunt it down, please,
> > run failing command under valgrind, as in most of cases it indicates
> > on an erroneous code that should be tracked down sooner than later as
> > memory corruption quite often is hard to catch.
> >
> > Running under valgrind is easy - just install it and execute "valgrind
> > my_command with all parameters".
> 
> See also here:
> https://grasswiki.osgeo.org/wiki/GRASS_Debugging#Using_Valgrind
> 
> > If you have trouble understanding its
> > output, you can ask any of us to help you.
> >
> > WBR,
> > Māris.
> 
> best,
> Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC weekly report 2006_0612_yb

[Yang, Bo (yangb2)]

Dear all,

Please see the link below for GSoC_2016_Additional_segmentation_algorithms week 
3 report.

https://trac.osgeo.org/grass/wiki/GSoC/2016/Additional_segmentation_algorithms/weekly_report#a4June--11Juneweek3:implementmean-shiftimagesegmentationalgorithm

Best,
Bo Yang
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] i.segment week 2 report 2016_06_05

[Yang, Bo (yangb2)]

Hi All ,

Please see the link below for the week 2 report of GRASS GSoC 2016 Additional 
Image Segmentation Algorithms for i.segment.

https://trac.osgeo.org/grass/wiki/GSoC/2016/Additional_segmentation_algorithms/weekly_report#a30May--4Juneweek2:implementmean-shiftimagesegmentationalgorithm


Best,
Bo Yang
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS GSoC 2016 Additional Image Segmentation Algorithms for i.segment weekly report 0 and 1

[Yang, Bo (yangb2)]

Dear All,



Please see my weekly report 0 and 1 for GRASS GSoC 2016 Additional Image 
Segmentation Algorithms:

[0] 
https://trac.osgeo.org/grass/wiki/GSoC/2016/Additional_segmentation_algorithms/weekly_report



Thanks,

Bo Yang


___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question

[Yang, Bo (yangb2)]

Hi Moritz

> > 4. Then run grass71svn, it reported 3 dll files are missing
> > respectively: "libintl-8.dll/ libsystre-0/ libiconv-2 is missing from
> > your computer";  each time it report one dll missing, I copy this file
> > from "C:\msys64\mingw64\bin" to " C:\OSGeo4W64\bin". I don't know
> why
> > still come dll missing. I installed all the components required in [0]
> >
> > 5. Afterward GRASS can be started in both text mode and g.gui mode.
> 
> And you can run i.segment and other modules ?

Yes, I can run i.segment in text mode and i.segment --ui in GUI mode. I also 
tried i.cluster and i.cluster --ui and they both works. 

> > Do you know will it be anything wrong in the future if commenting this line?
> 
> This line creates the HTML manual page of your module. So, it won't keep
> your module from running, but you won't have the complete manual page.
> 
> Out of curiosity, could you:
> 
> - start grass in text mode, navigate to your i.segment folder and run 'make'

C:\msys64\usr\src\grass_trunk\imagery\i.segment>make
'make' is not recognized as an internal or external command,
operable program or batch file.
Previously I run 'make' in mingw and it works, seems using OSgeo4w cmd can't 
run 'make'

> - in text mode run 'g.gisenv' and send us the output
> 
C:\>g.gisenv
LOCATION_NAME=demolocation
GISDBASE=C:\Users\Bo\Documents\grassdata
MAPSET=PERMANENT
GUI=text
PID=6024

Best,
Bo Yang
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question

[Yang, Bo (yangb2)]

Hi Helmut,

Thanks for the prompt reply. Now I am able to compile and start GRASS, but 
still have a small issue. Below are my procedures:

1. I changed back to 64bit packages because I can't go through in the 32bit 
environmental follow the tutorial [0] (I think might because my OS is 64bit).

2. Thanks for your advice, after deleted:
https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/osgeo4w/package.sh#L178
there no lidar error reported (r.in.lidar, r3.in.lidar, v.out.lidar, 
v.in.lidar). GRASS can be built successfully.

3. As mentioned in the previous threads, the C:\OSGeo4W64\bin\grass71svn#L8 
need to be changed to e.g. "SET OSGEO4W_ROOT= C:\OSGeo4W64"

4. Then run grass71svn, it reported 3 dll files are missing respectively: 
"libintl-8.dll/ libsystre-0/ libiconv-2 is missing from your computer";  each 
time it report one dll missing, I copy this file from "C:\msys64\mingw64\bin" 
to " C:\OSGeo4W64\bin". I don't know why still come dll missing. I installed 
all the components required in [0]

5. Afterward GRASS can be started in both text mode and g.gui mode.

6. I change to i.segment folder and run 'make'. It reported:
$ make
if [ "/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin/i.segment.exe" != "" ] ; 
then GISRC=/usr/src/grass_trunk/dist.x86_64-w64-mingw32/demolocation/.grassrc71 
GISBASE=C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32 
PATH="/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/usr/src/grass_trunk/dist.x86_64-w64-mingw32/scripts:$PATH"
 
PYTHONPATH="C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/etc/python;C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/gui/wxpython;$PYTHONPATH"
 
PATH="/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/usr/src/grass_trunk/dist.x86_64-w64-mingw32/scripts:/usr/src/grass_trunk/dist.x86_64-w64-mingw32/lib:/usr/src/grass_trunk/dist.x86_64-w64-mingw32/lib:/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/c/ProgramData/Oracle/Java/javapath:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program
 Files (x86)/Skype/Phone" LC_ALL=C 
/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin/i.segment.exe 
--html-description < /dev/null | grep -v '\|' > 
i.segment.tmp.html ; fi
C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin/i.segment.exe: error 
while loading shared libraries: libgrass_imagery.7.1.svn.dll: cannot open 
shared object file: No such file or directory
../../include/Make/Html.make:14: recipe for target 'i.segment.tmp.html' failed
make: *** [i.segment.tmp.html] Error 1
rm i.segment.tmp.html

This error appeared previous, I go to 
C:\msys64\usr\src\grass_trunk\include\Make\ Html.make#14 and comment line14:
#   if [ "$(HTMLSRC)" != "" ] ; then $(call htmldesc,$<,$@) ; fi
Then run make in this folder, no error reported, and i.segment can be start via 
GRASS GUI or i.segment --ui itself.

Do you know will it be anything wrong in the future if commenting this line? 
Thanks again for the help.

Best,
Bo Yang

[0] https://trac.osgeo.org/grass/wiki/CompileOnWindows

-Original Message-
From: Helmut Kudrnovsky [mailto:hel...@web.de] 
Sent: Thursday, May 19, 2016 3:15 AM
To: grass-dev@lists.osgeo.org
Subject: Re: [GRASS-dev] Seeking advices for image segmentation algorithms and 
windows compile question

>3. I checked out codes from trunk and build it:
>svn checkout https://svn.osgeo.org/grass/grass/trunk grass_trunk 
>PACKAGE_POSTFIX=-daily ./mswindows/osgeo4w/package.sh
>
>After built it reported:
>Started compilation: Thu May 19 00:45:39 EDT 2016
>--
>Errors in:
>/usr/src/grass_trunk/raster/r.in.lidar
>/usr/src/grass_trunk/raster3d/r3.in.lidar
>/usr/src/grass_trunk/vector/v.out.lidar
>/usr/src/grass_trunk/vector/v.in.lidar
>--
>In case of errors please change into the directory with error and run
'make'.
>If you get multiple errors, you need to deal with them in the order 
>they appear in the error log. If you get an error building a library, 
>you will also get errors from anything which uses the library.

as already mentioned in an earlier reply, please delete

https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/osgeo4w/package.sh#L178

i.e. 

--with-liblas=$PWD/mswindows/osgeo4w/liblas-config \

from your local package.sh




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Seeking-advices-for-image-segmentation-algorithms-and-windows-compile-question-tp5264642p5267138.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question

[Yang, Bo (yangb2)]

Hi All,

Markus, thanks for your reply, I will notice the length of error report. 
Although one of my computer(win 10 64bit) could compile and run i.segment 
module without error. I found that windows compile has some random error 
happens. I can now working on the project with one of my computer but sometimes 
when I run "i.segment --ui" it will reported:
" the program can't start because libgcc_s_dw2-1.dll is missing from your 
computer. Try reinstalling the program to fix this problem."

I use another computer to install 32bit packages since I see that some error 
only reported in 64bit environmental. Below is my procedures:

1. I downloaded 32 bit OSGeo4W installer with selection of:
cairo
gdal
geos
fftw
fftw-devel (32bit only)
freetype-devel
freetype-devel-mingw (32bit only)
iconv
libjpeg
liblas-devel
libpng
libpq
libtiff
libxdr
pdcurses
proj
regex-devel
sqlite3

2. I downloaded 32bit MSYS2 terminal and install requirements:
pacman -S tar libintl make bison diffutils subversion dos2unix zip
pacman -S mingw-w64-i686-toolchain mingw-w64-i686-cairo 
mingw-w64-i686-python2-numpy mingw-w64-i686-sqlite3

3. I checked out codes from trunk and build it:
svn checkout https://svn.osgeo.org/grass/grass/trunk grass_trunk
PACKAGE_POSTFIX=-daily ./mswindows/osgeo4w/package.sh

After built it reported:
Started compilation: Thu May 19 00:45:39 EDT 2016
--
Errors in:
/usr/src/grass_trunk/raster/r.in.lidar
/usr/src/grass_trunk/raster3d/r3.in.lidar
/usr/src/grass_trunk/vector/v.out.lidar
/usr/src/grass_trunk/vector/v.in.lidar
--
In case of errors please change into the directory with error and run 'make'.
If you get multiple errors, you need to deal with them in the order they
appear in the error log. If you get an error building a library, you will
also get errors from anything which uses the library.

5. Because the module "i.segment" which I am focusing report no error, so I 
just change to i.segment folder and run "make":
$ make
make: Nothing to be done for 'first'.

6. I suppose run 'make' in "i.segment" folder works and I changed to the binary 
files in "msys32\usr\src\grass_trunk\dist.i386-w64-mingw32\bin" and run 
'i.segment --ui'. But it reported:
"the program can't start because libgrass_btree2.7.1.svn.dll is missing from 
your computer. Try reinstalling the program to fix this problem."

I searched that libgrass_btree2.7.1.svn.dll are located in folder of " 
msys32\usr\src\grass_trunk\dist.i386-w64-mingw32\lib" but I don't know why the 
program still can not find it. Then I tried to copy all files from "..\lib" to 
"..\bin", then run 'i.segment --ui' again:

Then the error is:
" the program can't start because libgcc_s_dw2-1.dll is missing from your 
computer. Try reinstalling the program to fix this problem."

I searched again and found libgcc_s_dw2-1.dll are located in both " 
C:\msys32\mingw32\bin " and " C:\OSGeo4W\bin ".

PS: I tried to copy either of them to the folder of 
"msys32\usr\src\grass_trunk\dist.i386-w64-mingw32\bin" but the i.segment juse 
start and force closed.

Given this missing dll error always reported, I am writing to ask if anyone 
could help. Any suggestions would be greatly appreciated.

Best regards,
Bo Yang


-Original Message-----
From: neteler.os...@gmail.com [mailto:neteler.os...@gmail.com] On Behalf Of 
Markus Neteler
Sent: Saturday, May 14, 2016 6:03 AM
To: Yang, Bo (yangb2) <yan...@mail.uc.edu>
Cc: GRASS developers list <grass-dev@lists.osgeo.org>; Moritz Lennert 
<mlenn...@club.worldonline.be>; Markus Metz <markus.metz.gisw...@gmail.com>; 
Helmut Kudrnovsky <hel...@web.de>
Subject: Re: [GRASS-dev] Seeking advices for image segmentation algorithms and 
windows compile question

Hi,

On Fri, May 13, 2016 at 3:44 AM, Yang, Bo (yangb2) <yan...@mail.uc.edu> wrote:
...
> For the 32 bit version, error is appendix I; After I run ‘make’, the 
> report is in appendix II.

please be so kind and reduce the copy.paste stuff to a minimum.
Repetitive errors you may remove and replace with [...] in order to make it 
readable.

> Appendix I:
> GRASS GIS 7.1.svn r68419 compilation log
> --
> Started compilation: Wed, May 11, 2016  7:34:55 PM Errors in:
> /usr/src/grass_trunk/lib/python/ctypes
[...]

> /usr/src/grass_trunk/temporal/t.vect.univar
> In case of errors please change into the directory with error and run 
> 'make'.

Now, where is the error message of
/usr/src/grass_trunk/lib/python/ctypes
?
The same as below?


> -
>
> Appendix II:
>
> $ make
>
> make /usr/src/grass_trunk/dist.i386-w64-mingw32/etc/python/grass/lib
> make[1]: Entering directory '/usr/src/grass_trunk/lib/python/ctypes'
> make[1]: '/usr/src/grass_trunk/dist.i386-w64-mingw32/etc/python/grass/lib'
> is up 

Re: [GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question

[Yang, Bo (yangb2)]

Hi Helmut,


Thanks for the help. Now I think I sort of solved the issue. Below are the 
updates:

1)
>could you do following steps to test if there is some interference with
>other python installation?

>- rename the ArcGIS python installation folder temporarily (e.g. Python27 ->
Yyypython27)

>- do the same with the anaconda python installation folder

>- try to start start again your self compiled winGRASS 7.1svn 

>- report back here if your self compiled winGRASS 7.1svn starts or not 

>- rename back the both folders

I did it. Even changed the python27 folders name, winGRASS 7.1svn can not start 
either, and it reported the same error. I think it not python's problem.

2)
>for a workaround see:

>https://trac.osgeo.org/grass/ticket/3011#comment:4

>and see 

>https://grass.osgeo.org/grass71/manuals/grass7.html

>howto start grass71 in text mode and then start the GUI:

>e.g. in the OSGeo4W-console:

C:\>grass71svn.bat -text C:\grassdata\test3035\data
C:\>g.gui wxpython


Thanks! I tried and both text mode and g.gui mode are able to start GRASS71svn 
without any issue. So I think I came across the exactly same situation reported 
in that ticket case.

3)
>ok, good to know that it compiles now. 

>for the error message, see 

>https://trac.osgeo.org/grass/ticket/3011

>I'll add your example to the ticket. 

>if you have another windows box without another python installation, try to
compile there until this ticket is solved.

Actually, I created 2 clean installed VM win7. One is win7 pro 64 bit, the 
other is win 7 pro 32bit (for the 64 bit system, I use 64bit version of Osgeo4w 
and msys, and vice versa). I follow the same tutorial. This time it's very 
clean system without any software installed. But neither can successfully built 
the GRASS 71svn.
For the 32 bit version system the error:
-
GRASS GIS 7.1.svn r68419 compilation log
--
Started compilation: Wed, May 11, 2016  7:34:55 PM
--
Errors in:
/usr/src/grass_trunk/lib/python/ctypes
/usr/src/grass_trunk/display/d.grid
/usr/src/grass_trunk/display/d.path
/usr/src/grass_trunk/display/d.vect
/usr/src/grass_trunk/display/d.vect.chart
/usr/src/grass_trunk/display/d.vect.thematic
/usr/src/grass_trunk/display/d.where
/usr/src/grass_trunk/general/g.copy
/usr/src/grass_trunk/general/g.findfile
/usr/src/grass_trunk/general/g.list
/usr/src/grass_trunk/general/g.proj
/usr/src/grass_trunk/general/g.region
/usr/src/grass_trunk/general/g.remove
/usr/src/grass_trunk/general/g.rename
/usr/src/grass_trunk/raster/r.carve
/usr/src/grass_trunk/raster/r.contour
/usr/src/grass_trunk/raster/r.cost
/usr/src/grass_trunk/raster/r.drain
/usr/src/grass_trunk/raster/r.external
/usr/src/grass_trunk/raster/r.external.out
/usr/src/grass_trunk/raster/r.flow
/usr/src/grass_trunk/raster/r.horizon
/usr/src/grass_trunk/raster/r.in.gdal
/usr/src/grass_trunk/raster/r.in.lidar
/usr/src/grass_trunk/raster/r.latlong
/usr/src/grass_trunk/raster/r.out.gdal
/usr/src/grass_trunk/raster/r.proj
/usr/src/grass_trunk/raster/r.random
/usr/src/grass_trunk/raster/r.reclass
/usr/src/grass_trunk/raster/r.region
/usr/src/grass_trunk/raster/r.resamp.bspline
/usr/src/grass_trunk/raster/r.resamp.rst
/usr/src/grass_trunk/raster/r.sim/r.sim.water
/usr/src/grass_trunk/raster/r.sim/r.sim.sediment
/usr/src/grass_trunk/raster/r.stream.extract
/usr/src/grass_trunk/raster/r.sun
/usr/src/grass_trunk/raster/r.sunhours
/usr/src/grass_trunk/raster/r.sunmask
/usr/src/grass_trunk/raster/r.to.vect
/usr/src/grass_trunk/raster/r.volume
/usr/src/grass_trunk/raster/r.walk
/usr/src/grass_trunk/raster/r.what
/usr/src/grass_trunk/raster3d/r3.flow
/usr/src/grass_trunk/raster3d/r3.in.lidar
/usr/src/grass_trunk/vector/v.buffer
/usr/src/grass_trunk/vector/v.build
/usr/src/grass_trunk/vector/v.build.polylines
/usr/src/grass_trunk/vector/v.category
/usr/src/grass_trunk/vector/v.class
/usr/src/grass_trunk/vector/v.clean
/usr/src/grass_trunk/vector/v.cluster
/usr/src/grass_trunk/vector/v.colors
/usr/src/grass_trunk/vector/v.colors.out
/usr/src/grass_trunk/vector/v.db.connect
/usr/src/grass_trunk/vector/v.db.select
/usr/src/grass_trunk/vector/v.decimate
/usr/src/grass_trunk/vector/v.delaunay
/usr/src/grass_trunk/vector/v.distance
/usr/src/grass_trunk/vector/v.drape
/usr/src/grass_trunk/vector/v.edit
/usr/src/grass_trunk/vector/v.extract
/usr/src/grass_trunk/vector/v.extrude
/usr/src/grass_trunk/vector/v.generalize
/usr/src/grass_trunk/vector/v.hull
/usr/src/grass_trunk/vector/v.info
/usr/src/grass_trunk/vector/v.in.ascii
/usr/src/grass_trunk/vector/v.in.db
/usr/src/grass_trunk/vector/v.in.dxf
/usr/src/grass_trunk/vector/v.in.region
/usr/src/grass_trunk/vector/v.kcv
/usr/src/grass_trunk/vector/v.kernel
/usr/src/grass_trunk/vector/v.label
/usr/src/grass_trunk/vector/v.lidar.correction
/usr/src/grass_trunk/vector/v.lidar.edgedetection
/usr/src/grass_trunk/vector/v.lidar.growing
/usr/src/grass_trunk/vector/v.lrs/v.lrs.create

Re: [GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question

[Yang, Bo (yangb2)]

Hi Martin,

Nailed it! Thanks for asking.

Best,
Bo Yang

-Original Message-
From: Martin Landa [mailto:landa.mar...@gmail.com] 
Sent: Wednesday, May 11, 2016 5:32 AM
To: Yang, Bo (yangb2) <yan...@mail.uc.edu>
Cc: grass-dev@lists.osgeo.org; Markus Metz <markus.metz.gisw...@gmail.com>
Subject: Re: [GRASS-dev] Seeking advices for image segmentation algorithms and 
windows compile question

Hi,

2016-05-05 1:19 GMT+02:00 Yang, Bo (yangb2) <yan...@mail.uc.edu>:
> This is Bo Yang from the University of Cincinnati. I am working with 
> Moritz and Markus for the GSoC 2016 project-- Additional segmentation 
> algorithms for i.segment [0]. Currently, the i.segment module only 
> provides one

please link your page here [1]. Thanks, Martin

[1] https://trac.osgeo.org/grass/wiki/GSoC#a2016

> rem Set environmental variables
>
> rem
>
> call %OSGEO4W_ROOT%\bin\o4w_env.bat
>
> call %OSGEO4W_ROOT%\apps\grass\grass-7.1.svn\etc\env.bat
>
>
>
> rem
>
> rem Launch GRASS GIS
>
> rem
>
> "%GRASS_PYTHON%" "%GISBASE%\etc\grass71.py" %*
>
>
>
> rem
>
> rem Pause on error
>
> rem
>
> if %ERRORLEVEL% GEQ 1 pause
>
>
>
> [0] https://wiki.osgeo.org/wiki/GRASS_GSoC_2016_Segment_Algorithms
>
> [1] https://trac.osgeo.org/grass/wiki/CompileOnWindows
>
>
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev



--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question

[Yang, Bo (yangb2)]

Hi Helmut and Moritz,

>error: 
>libintl-8.dell missing 
>libsystre-0.dll missing
[...]

>ERROR: wxGUI requires wxPython. No module named wxversion

>It looks like the running/buildenvironment is inkompetent.

>all these dll's and wxpython should be available by the OSGeo4W environment. 

>try the OSGeo4W advanced install to install all these missing libs and wxpython

>Regarding missing dll's and wxpython, try to install e.g. OSGeo4W-winGRASS 
>7.0.4, then all dependencies should be installed.

I installed wxpython and OSGeo4W-winGRASS 7.0.4 via OSGeo4W, then build GRASS 
again (20min, no error reported). Now on my desktop there are both shortcuts of 
"GRASS GIS 7.1.svn" and "GRASS GIS 7.0.4".
Currently the GRASS GIS 7.0.4 can be normally started without any issue. 
However, when start GRASS GIS 7.1.svn. the error below showed. 
I did some research on google. Given all the errors come from python, I am 
thinking probably there are conflicts come from multi-python installations of 
my computer (I have anaconda and ArcGIS installed on my computer, both have 
python 2.7). If you think so too I will find another computer to clean install 
a new win7/10 and try to start over the compile follow that tutorial. 

Best,
Bo

Appendix I: Error screenshot:
---
Cleaning up temporary files...
Starting GRASS GIS...
Traceback (most recent call last):
  File "C:\OSGEO4~1\apps\grass\grass-7.1.svn\gui\wxpython\gis_set.py", line 
1200, in 
GRASSStartUp = StartUp(0)
  File 
"C:\OSGEO4~1\apps\Python27\lib\site-packages\wx-2.8-msw-unicode\wx\_core.py", 
line 7981, in __init__
self._BootstrapApp()
  File 
"C:\OSGEO4~1\apps\Python27\lib\site-packages\wx-2.8-msw-unicode\wx\_core.py", 
line 7555, in _BootstrapApp
return _core_.PyApp__BootstrapApp(*args, **kwargs)
  File "C:\OSGEO4~1\apps\grass\grass-7.1.svn\gui\wxpython\gis_set.py", line 
1175, in OnInit
StartUp = GRASSStartup()
  File "C:\OSGEO4~1\apps\grass\grass-7.1.svn\gui\wxpython\gis_set.py", line 
230, in __init__
self._set_properties(grassVersion, grassRevisionStr)
  File "C:\OSGEO4~1\apps\grass\grass-7.1.svn\gui\wxpython\gis_set.py", line 
282, in _set_properties
self.OnSetDatabase(None)
  File "C:\OSGEO4~1\apps\grass\grass-7.1.svn\gui\wxpython\gis_set.py", line 
929, in OnSetDatabase
self.UpdateLocations(self.gisdbase)
  File "C:\OSGEO4~1\apps\grass\grass-7.1.svn\gui\wxpython\gis_set.py", line 
796, in UpdateLocations
self.lblocations.InsertItems(self.listOfLocations, 0)
  File "C:\OSGEO4~1\apps\grass\grass-7.1.svn\gui\wxpython\gis_set.py", line 
1152, in InsertItems
self._LoadData(choices, disabled)
  File "C:\OSGEO4~1\apps\grass\grass-7.1.svn\gui\wxpython\gis_set.py", line 
1141, in _LoadData
index = self.InsertStringItem(sys.maxsize, item)
  File 
"C:\OSGEO4~1\apps\Python27\lib\site-packages\wx-2.8-msw-unicode\wx\_controls.py",
 line 4761, in InsertStringItem
return _controls_.ListCtrl_InsertStringItem(*args, **kwargs)
wx._core.PyAssertionError: C++ assertion "m_count == 
ListView_GetItemCount(GetHwnd())" failed at ..\..\src\msw\listctrl.cpp(1629) in 
wxListCtrl::InsertItem(): m_count should match ListView_GetItemCount
ERROR: Error in GUI startup. See messages above (if any) and if necessary, 
please report this error to the GRASS developers.
On systems with package manager, make sure you have the right GUI package, 
probably named grass-gui, installed.
To run GRASS GIS in text mode use the -text flag.
Exiting...
Press any key to continue . . .
--

Appendix II: file of error.log (usr/src/grass_trunk):

GRASS GIS 7.1.svn r68375 compilation log
--
Started compilation: Tue, May 10, 2016 10:46:44 PM
--
Errors in:
No errors detected.
--
Finished compilation: Tue, May 10, 2016 10:48:16 PM
--




___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question

[Yang, Bo (yangb2)]

Hi Helmut and Moritz,

Thanks for the reply and advise, here is my updates:
1)
> > no error reported in former steps either, and I can see the file " 
> > grass71svn.bat " is located in the right place.
> what is the "right place"? what is the path to the "right place"?

According to the tutorial [0], after compile with the default setting, the 
grass71svn.bat should be located in " c:\osgeo4w\bin\grass71svn.bat.". I see it 
is there, but when I run it via cmd (or double click), it always give the error:
'""' is not recognized as an internal or external command,
operable program or batch file.
Press any key to continue . . .

2)
> > SET OSGEO4W_ROOT=@osgeo4w@ 
> could it be that OSGEO4W_ROOT isn't defined?
> was winGRASS also installed or eventually only compiled?

Win GRASS was not installed yet, because in the tutorial the step of "Creating 
a WinGRASS Installer" was located after the step of "Compiling and Installing 
GRASS GIS". And the tutorial mentioned: " Do not move on to step two until you 
have successfully tested your new version of GRASS. "
So I didn't install WinGRASS since my compile part didn't go through yet.

3)
>compare OSGEO4W_ROOT above. OSGEO4W_ROOT has to be defined, otherwise the 
>other bat-files, which define all needed variables, and grass71.py can't be 
>found.
I edit the grass71svn.bat file compare with your file.
I change line " SET OSGEO4W_ROOT=@osgeo4w@ " of the bat file to " SET 
OSGEO4W_ROOT=C:\osgeo4w64 " since my path is C:\OSGeo4W64\bin.
I run the grass71svn.bat again and poped up the below error:
libintl-8.dell missing
libsystre-0.dll missing
...
I Googled the missing dll solutions[1] and copy them from C:\OSGeo4W64\bin to 
C:\osgeo4w64 and run again. Then it shoed on the screen:
---
Cleaning up temporary files...
Starting GRASS GIS...
ERROR: wxGUI requires wxPython. No module named wxversion
ERROR: Error in GUI startup. See messages above (if any) and if necessary, 
please report this error to the GRASS developers.
On systems with package manager, make sure you have the right GUI package, 
probably named grass-gui, installed.
To run GRASS GIS in text mode use the -text flag.
Exiting...
Press any key to continue . . . 

I think this time is most close to start compiled GRASS so far.


4)
>Yes, I agree: don't worry about Lidar at this stage. You should be able 
>to just ignore these errors and run GRASS anyhow. Have you tried running 
>it after this compile?

I found that if the compile result have errors, there are no file of 
grass71svn.bat in the path of C:\OSGeo4W64\bin. So I don't know how to ignore 
the error and run GRASS anyway because on the tutorial the  grass71svn.bat is 
needed for start GRASS.


Best,
Bo Yang


[0] https://trac.osgeo.org/grass/wiki/CompileOnWindows
[1] http://forums.codeblocks.org/index.php?topic=20598.0


-Original Message-
From: Moritz Lennert [mailto:mlenn...@club.worldonline.be] 
Sent: Monday, May 9, 2016 3:40 AM
To: Helmut Kudrnovsky ; grass-dev@lists.osgeo.org
Subject: Re: [GRASS-dev] Seeking advices for image segmentation algorithms and 
windows compile question

On 09/05/16 08:26, Helmut Kudrnovsky wrote:
> For MS windows have a look here:
>
> https://lists.osgeo.org/pipermail/grass-dev/2016-May/080159.html
>
> https://lists.osgeo.org/pipermail/grass-dev/2016-May/080160.html
>
>> I assume win10 is too new so I tried win 7 and win8.1 using different 
>> computers. I
>
> AFAIK the Windows version doesn't matter.
>
>> Errors in:
>> /usr/src/grass_trunk/raster/r.in.lidar
>> /usr/src/grass_trunk/raster3d/r3.in.lidar
>> /usr/src/grass_trunk/vector/v.out.lidar
>> /usr/src/grass_trunk/vector/v.in.lidar
>
> please check if the development dependencies for the lidar tools are 
> present in your build development.
>
> install them or disable to build them (maybe the latter is better in 
> Windows 64bit as there may be some issues with the las tools in 
> OSGeo4W 64bit AFAIR).
>
>

Yes, I agree: don't worry about Lidar at this stage. You should be able to just 
ignore these errors and run GRASS anyhow. Have you tried running it after this 
compile ?

Moritz

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question

[Yang, Bo (yangb2)]

Hi All,

Thanks Moritz! Actually, this weekend I've tried both. I assume win10 is too 
new so I tried win 7 and win8.1 using different computers. I followed same 
tutorial [0], after I compiled for release builds on 64bit, I got the error 
report for both win 7 and win 8.1 OS:
>Errors in:
>/usr/src/grass_trunk/raster/r.in.lidar
>/usr/src/grass_trunk/raster3d/r3.in.lidar
>/usr/src/grass_trunk/vector/v.out.lidar
>/usr/src/grass_trunk/vector/v.in.lidar

I tried to change into the directory with error and run 'make'. The error msg 
was long and I think I need time to read them.

I've also tried compile GRASS on VM OS X El Captain using homebrew[1] first. 
But got stuck at:

brew install --HEAD grass-71
==>Installing grass-71 from rkrug/head-only
==>Cloning https://svn.osgeo.org/grass/grass/trunk
then the terminal freezing here forever. 

Sorry for the slow progress. I think I need more time to do the research work. 
Any help would be appreciated.

Best,
Bo Yang


[0] https://trac.osgeo.org/grass/wiki/CompileOnWindows
[1] https://grasswiki.osgeo.org/wiki/Compiling_on_MacOSX_using_homebrew


-Original Message-
From: Moritz Lennert [mailto:mlenn...@club.worldonline.be] 
Sent: Saturday, May 7, 2016 8:24 PM
To: Yang, Bo (yangb2) <yan...@mail.uc.edu>
Cc: Maris Nartiss <maris@gmail.com>; Markus Metz 
<markus.metz.gisw...@gmail.com>; grass-dev@lists.osgeo.org; Helmut Kudrnovsky 
<hel...@web.de>
Subject: Re: [GRASS-dev] Seeking advices for image segmentation algorithms and 
windows compile question

Hi all,

[Bo, please keep such discussions on the list.]

Even though I agree with Maris that compiling in GNU/Linux is easier, I do 
think that we should rather support those who want to develop in a windows 
environment. We lack windows devs, and telling everyone at the first difficulty 
to move over to GNU/Linux will not increase that number.

Helmut, would you have any advice to give to Bo on his issue in launching the 
windows version ?

Moritz

Le Thu, 5 May 2016 16:24:51 +,
"Yang, Bo (yangb2)" <yan...@mail.uc.edu> a écrit :

> Hi Māris,
> 
> Thanks for the advice! Yes, I agree that GRASS could be compiled 
> easier in Linux/Unix than windows. I recalled that I actually have a 
> VM OS X El Captain (2 core/ 6Gb/ 80GB on SSD) on my desktop (i7 4 
> core/ 12GB/ 256 SSD). Previously it was set to test Xcode. I will try 
> to compile it on OS X and Ubuntu to see if works better.
> 
> Best,
> Bo Yang
> 
> 
> -Original Message-
> From: Maris Nartiss [mailto:maris@gmail.com]
> Sent: Thursday, May 5, 2016 2:39 AM
> To: Yang, Bo (yangb2) <yan...@mail.uc.edu>
> Cc: grass-dev@lists.osgeo.org; Markus Metz 
> <markus.metz.gisw...@gmail.com> Subject: Re: [GRASS-dev] Seeking 
> advices for image segmentation algorithms and windows compile question
> 
> I would strongly suggest to set up a dual boot on your system with 
> Ubuntu or Debian as a development platform. You will save tons of time 
> wasted on fighting with Windows'isms. Don't waste your time on 
> virtualisation unless you can give VM two cores + 8Gb RAM. No, 
> developing GRASS GIS doesn't need so much resources but full 
> virtualisation does (to be reasonable fast). Yes, it will take a day 
> or two to get dualboot up and running but will pay back (by time) 
> really fast.
> 
> Save yours (and our) time!
> Māris.
> 
> 2016-05-05 2:19 GMT+03:00 Yang, Bo (yangb2) <yan...@mail.uc.edu>:
> > Hello,
> >  
> 
> >
> > In addition, is there anyone who use win10 OS to compile the GRASS?
> > I have compiled GRASS in window 10 64bit system followed the 
> > tutorial [1]. In last step of the tutorial it mentioned:
> >  
> > >Usage:  
> >  
> > >To start GRASS use the icon on the desktop or if
> > >you   
> > want to be able to use the command line from within GRASS.
> >  
> > >Type in cmd console (assuming that we compiled
> > >GRASS 7.1):  
> >  
> > >c:\osgeo4w\bin\grass71svn.bat
> >
> > However, No matter I use CMD console or the OSGeo4W Shell. I got the 
> > same error below:
> >
> > '""' is not recognized as an internal or external 
> > command, operable program or batch file.
> >
> > From the error.log there is no error during the compiling. There is 
> > no error reported in former steps either, and I can see the file "
> > grass71svn.bat " is located in the right place. But I still can't 
> > start the compiled GRASS. I Googled this error but can't find 
> > helpful information. Any suggestion would be greatly appreciate.
> >
> >

[GRASS-dev] Seeking advices for image segmentation algorithms and windows compile question

[Yang, Bo (yangb2)]

Hello,

This is Bo Yang from the University of Cincinnati. I am working with Moritz and 
Markus for the GSoC 2016 project-- Additional segmentation algorithms for 
i.segment [0]. Currently, the i.segment module only provides one segmentation 
algorithm: region-growing. The code of i.segment was structured in a way that 
allows addition of other algorithms. I plan to add

More algorithms such as mean-shift and watershed.  To prepare for it, I 
searched some literatures about both algorithms below, I'd like to consult if 
anyone have more recommended references.



Mean-shift:

Comaniciu, D., & Meer, P. (2002). Mean shift: a robust approach toward feature 
space analysis. IEEE Transactions on Pattern Analysis and Machine Intelligence, 
24(5), 1-37.



Watershed:
Shafarenko, Leila, Maria Petrou, and Josef Kittler. "Automatic watershed 
segmentation of randomly textured color images." Image Processing, IEEE 
Transactions on 6.11 (1997): 1530-1544.
Haris, Kostas, et al. "Hybrid image segmentation using watersheds and fast 
region merging." Image Processing, IEEE Transactions on 7.12 (1998): 1684-1699.


In addition, is there anyone who use win10 OS to compile the GRASS? I have 
compiled GRASS in window 10 64bit system followed the tutorial [1]. In last 
step of the tutorial it mentioned:

>Usage:

>To start GRASS use the icon on the desktop or if you want to 
be able to use the command line from within GRASS.

>Type in cmd console (assuming that we compiled GRASS 7.1):

>c:\osgeo4w\bin\grass71svn.bat

However, No matter I use CMD console or the OSGeo4W Shell. I got the same error 
below:

'""' is not recognized as an internal or external command, 
operable program or batch file.
>From the error.log there is no error during the compiling. There is no error 
>reported in former steps either, and I can see the file " grass71svn.bat " is 
>located in the right place. But I still can't start the compiled GRASS. I 
>Googled this error but can't find helpful information. Any suggestion would be 
>greatly appreciate.

P.S. scripts in grass71svn.bat:
@echo off
rem #
rem #
rem # GRASS initialization bat script (OSGeo4W)
rem #
rem #

SET OSGEO4W_ROOT=@osgeo4w@

rem
rem Set environmental variables
rem
call %OSGEO4W_ROOT%\bin\o4w_env.bat
call %OSGEO4W_ROOT%\apps\grass\grass-7.1.svn\etc\env.bat

rem
rem Launch GRASS GIS
rem
"%GRASS_PYTHON%" "%GISBASE%\etc\grass71.py" %*

rem
rem Pause on error
rem
if %ERRORLEVEL% GEQ 1 pause

[0] https://wiki.osgeo.org/wiki/GRASS_GSoC_2016_Segment_Algorithms
[1] https://trac.osgeo.org/grass/wiki/CompileOnWindows

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] FW: FW: OSGeo-SoC 2016 application

[Yang, Bo (yangb2)]

Dear Moritz,

Thank you for the reply, and thanks you and Markus could be the mentor of the 
i.segment project! There are only two days left for submitting the proposal, 
take into consideration I think I need to switch to the topic of i.segment 
project now. For my cokriging fusion topic I think I could do it after this 
summer in the future work. 
I've read the source code and Eric's wiki of GSoC 2012 [0]. I think I will 
prepare the proposal following the direction of adding new algorithms to 
segment an image into objects-- more than region-growing algorithm. Moritz, you 
mentioned segmentation algorithm: mean-shift, split-window and watershed. I 
think some unsupervised classification algorithms would also be possible such 
as: dynamic thresholding and markov random field (MRF). If you think it is OK, 
I will start the preparing the draft of proposal from now on, and I think I 
could have the first version send back to you by tomorrow (Thursday). If you 
have any suggestions and comments please let me know.
Thanks again to both you and Luca for your guidance and patient. 

Best wishes,
Bo Yang

[0] https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2012_Image_Segmentation


-Original Message-
From: Moritz Lennert [mailto:mlenn...@club.worldonline.be] 
Sent: Wednesday, March 23, 2016 10:12 AM
To: Yang, Bo (yangb2) <yan...@mail.uc.edu>
Cc: Luca Delucchi <lucadel...@gmail.com>; grass-dev@lists.osgeo.org; Markus 
Metz <markus.metz.gisw...@gmail.com>
Subject: Re: [GRASS-dev] FW: FW: OSGeo-SoC 2016 application

Le Wed, 23 Mar 2016 09:09:06 +0100,
Luca Delucchi <lucadel...@gmail.com> a écrit :

> On 23 March 2016 at 05:04, Yang, Bo (yangb2) <yan...@mail.uc.edu>
> wrote:
> > Dear Luca,
> >  
> 
> Dear Bo,
> 
> > Last weekend I've tried using my computer checking out the source 
> > codes and compiled the GRASS in the windows OS environment [0]. In 
> > addition, I've studied both t.rast.gapfill and r.series.interp 
> > modules. I think that it would be possible to add an interpolation 
> > method because it currently supports only linear interpolation. I 
> > think it would be a good idea to add Kriging/cokriging to the 
> > interpolation methods since it is a wide used rater interpolation 
> > algorithm. Although Kriging/cokriging computational time is 
> > significantly longer than the traditional linear method, it 
> > completes the gap filling process within a reasonable period with 
> > much better fusion results, especially for some heterogeneous 
> > region. If you think it is OK, I can prepare the proposal follow 
> > this direction (it is due this Friday).
> 
> I think you should start the proposal, because there is no so much 
> time
> 
> > However, I've got the reply from Soeren (see below). He said he 
> > can't mentor the project due to too busy this year. Do you have any 
> > other person in mind to recommend as mentor? Or are you available 
> > for  mentoring this project? Please advise. Thank you for being 
> > patient and helping me.
> 
> I have no enough C skills to be the first mentor, I could be the 
> co-mentor (for testing, helping you with t.rast.gapfill and adding 
> tests). Is someone else interested to be mentor?

As mentioned privately, I'm only available, like you, as co-mentor for testing 
and applied advice, not so much on the coding side.

In light of the absence of mentors, you might want to reconsider the choice of 
topics. For i.segment, Markus Metz is willing to deal with the C-side and I 
mentor for the rest.

Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] FW: FW: OSGeo-SoC 2016 application

[Yang, Bo (yangb2)]

Dear Luca,

Last weekend I've tried using my computer checking out the source codes and 
compiled the GRASS in the windows OS environment [0]. In addition, I've studied 
both t.rast.gapfill and r.series.interp modules. I think that it would be 
possible to add an interpolation method because it currently supports only 
linear interpolation. I think it would be a good idea to add Kriging/cokriging 
to the interpolation methods since it is a wide used rater interpolation 
algorithm. Although Kriging/cokriging computational time is significantly 
longer than the traditional linear method, it completes the gap filling process 
within a reasonable period with much better fusion results, especially for some 
heterogeneous region. If you think it is OK, I can prepare the proposal follow 
this direction (it is due this Friday). 

However, I've got the reply from Soeren (see below). He said he can't mentor 
the project due to too busy this year. Do you have any other person in mind to 
recommend as mentor? Or are you available for  mentoring this project? Please 
advise. 
Thank you for being patient and helping me.

Best wishes,
Bo Yang

[0] https://trac.osgeo.org/grass/wiki/CompileOnWindows


-Original Message-
From: Sören Gebbert [mailto:soeren.gebb...@thuenen.de] 
Sent: Monday, March 21, 2016 10:36 AM
To: Yang, Bo (yangb2) <yan...@mail.uc.edu>
Subject: Re: FW: [GRASS-dev] OSGeo-SoC 2016 application

Dear Bo,
sorry for my late response.

Your project sounds very interesting indeed. However, i am really sorry to tell 
you that i have no time this year to mentor a GSoC2016 project. I have to work 
on so many different projects right now, that i am not able to spend time on 
GSoC2016.

Best regards
Soeren

> Dear Soeren,
>
> I hope this email finds you well.
> I apologize for the multiple emails, I am forwarding this email in 
> case you didn't see the earlier one I sent to "soerengebb...@googlemail.com ".
> Thank you and have a good day.
>
> Best regards,
> Bo yang
>
>
> -Original Message-
> From: Yang, Bo (yangb2)
> Sent: Thursday, March 17, 2016 12:39 AM
> To: 'Luca Delucchi' <lucadel...@gmail.com>; Sören Gebbert 
> <soerengebb...@googlemail.com>
> Cc: grass-dev@lists.osgeo.org
> Subject: RE: [GRASS-dev] OSGeo-SoC 2016 application
>
> Dear Soeren and Luca,
>
> First, let me introduce myself again to Soeren. My name is Bo Yang, a Ph.
> D. student in the Department of Geography, University of Cincinnati, 
> OH, USA.  I have a bachelor degree in Mathematics and MS in Computer Science.
> I am really interested in OSGeo-SoC2016. It would be a great 
> opportunity if I can make contributions as well as learn to become an 
> open-source developer.
>
> Currently I have an idea based on my MA thesis project: 
> Spatio-temporal fusion of multi-scale data with in a cokriging framework.
> This project extends traditional cokriging method for blending spatial 
> data sets with different temporal sampling frequency and spatial 
> resolution (density). It can be used for both raster data and vector 
> data, effectively fill in data gaps due to severe weather condition, 
> instrument malfunction, or other reasons, filtering out data noise, 
> and generate reliable results at both high spatial resolution and high 
> temporal frequency with associated uncertainty estimates.
>
> Soeren, I noticed you are the author of r.series.interp. I discussed a 
> little with Luca, I agree this project is highly related to the package.
> So I am writing to ask if you are interest in mentoring this project.
> Currently I have the preliminary python code for the raster fusion 
> attached(ImageFusion_SoC.py). It was written during my master degree, 
> so it is sort of rough and haven't been re-constructed to OOP yet. But 
> it runs well for fusion MODIS and Landsat data.
>
> I attached an fusion example for NDVI[0] images.  The program is able 
> to blend Landsat TM/ETM+ NDVI image (30m) with MODIS NDVI image (250m)[1].
> The NDVI can be calculated from the combination of the red band (Band 
> 3 of Landsat TM or ETM+ multispectral imagery, or Band 1 of MODIS 
> multispectral
> imagery) and near infrared band (Band 4 of Landsat TM or ETM+ 
> multispectral imagery, or Band 2 of MODIS multispectral imagery). 
> MODIS data has been resampled to 270m to co-registered with Landsat pixels.
>
> I selected a relatively cloud free period (07/19/2002-07/29/2002) to 
> demonstrate the fusion process, the study region is Lake Tahoe region, 
> NV, USA. Both Landsat and MODIS NDVI images need to be converted to 
> ASCII file, source data can be found here[2]. Text files start with 
> "A" are daily MODIS NDVI images and "lt5ndvi_0716" is the Landsat TM 
> data. The goal of this example is to fuse daily MODIS NDVI i

Re: [GRASS-dev] OSGeo-SoC 2016 application

[Yang, Bo (yangb2)]

Dear Soeren and Luca,

First, let me introduce myself again to Soeren. My name is Bo Yang, a Ph. D. 
student in the Department of Geography, University of Cincinnati, OH, USA.  I 
have a bachelor degree in Mathematics and MS in Computer Science. I am really 
interested in OSGeo-SoC2016. It would be a great opportunity if I can make 
contributions as well as learn to become an open-source developer.

Currently I have an idea based on my MA thesis project: Spatio-temporal fusion 
of multi-scale data with in a cokriging framework.
This project extends traditional cokriging method for blending spatial data 
sets with different temporal sampling frequency and spatial resolution 
(density). It can be used for both raster data and vector data, effectively 
fill in data gaps due to severe weather condition, instrument malfunction, or 
other reasons, filtering out data noise, and generate reliable results at both 
high spatial resolution and high temporal frequency with associated uncertainty 
estimates.

Soeren, I noticed you are the author of r.series.interp. I discussed a little 
with Luca, I agree this project is highly related to the package. So I am 
writing to ask if you are interest in mentoring this project. Currently I have 
the preliminary python code for the raster fusion attached(ImageFusion_SoC.py). 
It was written during my master degree, so it is sort of rough and haven't been 
re-constructed to OOP yet. But it runs well for fusion MODIS and Landsat data. 

I attached an fusion example for NDVI[0] images.  The program is able to blend 
Landsat TM/ETM+ NDVI image (30m) with MODIS NDVI image (250m)[1]. The NDVI can 
be calculated from the combination of the red band (Band 3 of Landsat TM or 
ETM+ multispectral imagery, or Band 1 of MODIS multispectral imagery) and near 
infrared band (Band 4 of Landsat TM or ETM+ multispectral imagery, or Band 2 of 
MODIS multispectral imagery). MODIS data has been resampled to 270m to 
co-registered with Landsat pixels. 

I selected a relatively cloud free period (07/19/2002-07/29/2002) to 
demonstrate the fusion process, the study region is Lake Tahoe region, NV, USA. 
Both Landsat and MODIS NDVI images need to be converted to ASCII file, source 
data can be found here[2]. Text files start with "A" are daily MODIS NDVI 
images and "lt5ndvi_0716" is the Landsat TM data. The goal of this example is 
to fuse daily MODIS NDVI images with a Landsat NDVI images (30m) to generate 
images at 30 m spatial resolution for everyday, using spatio-temporal cokriging 
method. Namely, I intend to use a single high resolutions Landsat NDVI images 
to sharpen daily time series MODIS images. Also the program is able to fill in 
the missing value. I artificially generated a missing data region in each input 
MODIS image and we can see the result fill in the missing data region very 
well. One good application of this algorithm is to fill in the gaps in the 
Landsat ETM+ images after 2002 due to the sensor's malfunction. 

The fusion module is attached, it need an input exponential/Gaussian model 
parameter which was calculated via semi-variogram fitting module. I did export 
the parameters in the attached text file for this case so the fusion module can 
be run independently. To run the program quickly, just put attached text file 
and source data[2] in the working folder and apply it to line22 of the fusion 
module. Of course other MODIS data can be used for this program if converted to 
ASCII files. There are two fusion methods, first one (line 330: 
fusion_with_covariable) is used for the MODIS data, which can sharpening and 
fill-in the missing data values. Second one is cokriging which incorporated the 
fine Landsat image as co-variable, it can achieve much better sharpening result 
as well as fill-in missing data values. Both method generated the gap filled 
result at 30m spatial resolution.

Please let me know if you have and comments or suggestions. Luca, thank you for 
sending me the compile method and programming manual. I normally used windows 
OS, and Eclipse + Pydev as primary IDE. I am going to look into the manual and 
GRASS codes. Any more advice would be greatly appreciated.

Best regards,
Bo Yang



[0] https://en.wikipedia.org/wiki/Normalized_Difference_Vegetation_Index
[1] https://lpdaac.usgs.gov/dataset_discovery/modis/modis_products_table/mod09gq
[2] 
https://drive.google.com/folderview?id=0B25sQdmthpGJS0JOdEh5cDd4S1k=sharing

-Original Message-
From: Luca Delucchi [mailto:lucadel...@gmail.com] 
Sent: Wednesday, March 16, 2016 11:18 AM
To: Yang, Bo (yangb2) <yan...@mail.uc.edu>; Sören Gebbert 
<soerengebb...@googlemail.com>
Cc: grass-dev@lists.osgeo.org
Subject: Re: [GRASS-dev] OSGeo-SoC 2016 application

On 16 March 2016 at 04:49, Yang, Bo (yangb2) <yan...@mail.uc.edu> wrote:
> Hi Luca,
>

Hi Bo Yang,

> Thank you for the reply and info. It is great if you could co-mentor this 
> project. I would be more 

Re: [GRASS-dev] OSGeo-SoC 2016 application

[Yang, Bo (yangb2)]

Hi Luca,

Thank you for the reply and info. It is great if you could co-mentor this 
project. I would be more interest in implementing my spatio-temporal fusion 
algorithm as an open source plug-in. Actually, I already have the preliminary 
python code for the raster fusion, including modules of spatio-temporal 
semi-variogram calculating, exponential/Gaussian fitting, spatio-temporal 
fusion, uncertainty estimation and etc. Currently it runs well for fusing MODIS 
and Landsat data. But it is just a preliminary program, I think a lot more 
works need to be done to make it professional and could incorporated into GRASS 
framework. 
I've read the link you sent to me. I think it is a good point to add it to 
r.series.interp, which I noticed author is Sören Gebbert. Should I ask Sören if 
he is interested to be a potential mentor? Furthermore, could you advise what 
should I do now to get start for the programming environmental as well as 
prepare the proposal? 

Best,
Bo Yang


-Original Message-
From: Luca Delucchi [mailto:lucadel...@gmail.com] 
Sent: Tuesday, March 15, 2016 5:28 AM
To: Yang, Bo (yangb2) <yan...@mail.uc.edu>
Cc: grass-dev@lists.osgeo.org
Subject: Re: [GRASS-dev] OSGeo-SoC 2016 application

On 15 March 2016 at 03:54, Yang, Bo (yangb2) <yan...@mail.uc.edu> wrote:
> Hello,
>

Hi Bo Yang,

>
> In addition, I have an idea based on my MA thesis project:
>
> Spatio-temporal fusion of multi-scale data with in a cokriging framework.
>
> This project extends traditional cokriging method for blending spatial 
> data sets with different temporal sampling frequency and spatial 
> resolution (density). It can be used for both raster data and vector 
> data, effectively fill in data gaps due to severe weather condition, 
> instrument malfunction, or other reasons, filtering out data noise, 
> and generate reliable results at both high spatial resolution and high 
> temporal frequency with associated uncertainty estimates.
>
> It would be greatly appreciated if someone interested in my idea and 
> could guide me how to get start and prepare the proposal. Thanks for 
> your time and I am looking forward to hearing from you.
>

This is really interesting, In GRASS GIS Temporal Framework [0][1] already 
exists a module for raster gapfilling [2], it uses the module r.series.interp 
[3]. The idea could be to add a new method in r.series.interp and a new vector 
module something like v.series.interp and after you could add the new 
functionality to GRASS GIS Temporal Framework.

I could co-mentor this proposal, maybe Soeren could be a good mentor for this 
proposal

> Best regards,
>
> Bo Yang
>

[0] https://grass.osgeo.org/grass71/manuals/temporalintro.html
[1] https://grasswiki.osgeo.org/wiki/Temporal_data_processing
[2] https://grass.osgeo.org/grass71/manuals/t.rast.gapfill.html
[3] https://grass.osgeo.org/grass71/manuals/r.series.interp.html

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] OSGeo-SoC 2016 application

[Yang, Bo (yangb2)]

Dear Moritz,

Thank you for the reply. Yes, I agree that I should focus on one subject and 
get start preparing the proposal based on it. After a quick research for both 
subjects. I would like to choose pursuing my latter idea about spatio-temporal 
image fusion algorithm. For one thing, It is my novel algorithm and I have the 
confidence and motivation to make it available for using. For another, I code 
in python more skillful than in C/C++ language. I will contact Luca Delucchi 
for the possibility of developing that project. 
Thank you again for guiding me earlier. Any more advice would be greatly 
appreciated. 

Best regards,
Bo Yang

-Original Message-
From: Moritz Lennert [mailto:mlenn...@club.worldonline.be] 
Sent: Tuesday, March 15, 2016 8:10 AM
To: Yang, Bo (yangb2) <yan...@mail.uc.edu>; grass-dev@lists.osgeo.org
Subject: Re: [GRASS-dev] OSGeo-SoC 2016 application

Dear Bo,

On 15/03/16 03:54, Yang, Bo (yangb2) wrote:
> Hello,
>
> My name is Bo Yang, a Ph. D. student in the Department of Geography, 
> University of Cincinnati.  I have a bachelor degree in Mathematics and 
> MS in Computer Science. I am proficient in Python, C/C++, R and have 
> utilized QGIS and GRASS a lot in my study and research project. I am 
> really interested in OSGeo-SoC2016. It would be a great opportunity if 
> I can make contributions as well as learn to become an open-source developer.
>
> For years I have worked with raster processing algorithms and 
> computation efficiency, for example, coding (python) to process large 
> volume of remote sensing data, therefore I am interested in the 
> existing
> idea:
>
> GRASS: Additional segmentation algorithms for i.segment.

In our previous exchange via private mail, I already sent you the necessary 
pointers for this subject. Markus Metz and I are willing to mentor a student on 
this. I think it would be a marvelous addition to GRASS' image treatment 
toolbox.

Don't hesitate to post on this list if you have any other questions concerning 
this subject.

I think you will have to chose quite quickly which one of your two subjects you 
wish to pursue, as the deadline for applications will arrive fast, and it is 
probably better to concentrate on one subject and do that well. There have been 
cases, however, of students proposing more than one subject.

Best wishes,
Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] OSGeo-SoC 2016 application

[Yang, Bo (yangb2)]

Hello,
My name is Bo Yang, a Ph. D. student in the Department of Geography, University 
of Cincinnati.  I have a bachelor degree in Mathematics and MS in Computer 
Science. I am proficient in Python, C/C++, R and have utilized QGIS and GRASS a 
lot in my study and research project. I am really interested in OSGeo-SoC2016. 
It would be a great opportunity if I can make contributions as well as learn to 
become an open-source developer.
For years I have worked with raster processing algorithms and computation 
efficiency, for example, coding (python) to process large volume of remote 
sensing data, therefore I am interested in the existing idea:
GRASS: Additional segmentation algorithms for i.segment.
In addition, I have an idea based on my MA thesis project:
Spatio-temporal fusion of multi-scale data with in a cokriging framework.
This project extends traditional cokriging method for blending spatial data 
sets with different temporal sampling frequency and spatial resolution 
(density). It can be used for both raster data and vector data, effectively 
fill in data gaps due to severe weather condition, instrument malfunction, or 
other reasons, filtering out data noise, and generate reliable results at both 
high spatial resolution and high temporal frequency with associated uncertainty 
estimates.
It would be greatly appreciated if someone interested in my idea and could 
guide me how to get start and prepare the proposal. Thanks for your time and I 
am looking forward to hearing from you.
Best regards,
Bo Yang
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev