[GRASS-dev] Introduction to the mini project called Easy command history navigation through the History browser panel

[Linda Karlovska via grass-dev]

Hello devs,

I'd like to introduce you to the student mini-project that I will be working on 
in the upcoming months. It is once again GUI-related and essentially involves 
refining and extending the new history browser panel, which was merged into the 
GRASS development branch about one month ago.

Right now, the panel is pretty basic. It shows the plain command history and 
you can click on the command and open the module dialog with pre-filled items. 
Quite helpful but any info about commands is completely missing. So the plan 
for this project is to add in some cool stuff, such as:

1) Allowing more information to be stored for each executed command, such as 
execution time, runtime duration, status code, region settings, if a mask was 
set, etc.

2) Creating a context menu with options for "Run Command" and "Show Info." 
"Show Info" will display a small dialog showing above-described information.

3) Adding a symbol (green checkmark, yellow dot, or red cross) in front of each 
command in the tree based on the command's status value (completed, in 
progress, failed).

4) Branching the history tree based on the date of command execution (commands 
from a specific day could be rolled up).

5) Filtering commands based on the status code (completed, in progress, failed)

Possibly some other things could be added “along the way” based on the 
discussion with the community. I plan to set up the mini-project page and 
regularly send updates about the progress. Feel free to let me know if you have 
any questions or suggestions.

Wishing you all a nice week,
Linda
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction - GSoC Student

[Vaclav Petras]

Dear all, especially Jupyter users,

Please comment or get ready to comment on the topic Caitlin is planning to
apply with: Seamless integration of GRASS GIS and Jupyter Notebooks.

https://trac.osgeo.org/grass/wiki/GSoC/2021#SeamlessintegrationofGRASSGISandJupyterNotebooks

Caitlin is working on a new notebook for the Try GRASS online page, but
that's not visible in the core or addos repos, so I just wanted to bring
that to your attention.

https://grass.osgeo.org/learn/tryonline/
https://github.com/chaedri/grass-zonal-of-solar

Best,
Vaclav


On Thu, Mar 11, 2021 at 3:49 PM Caitlin Haedrich 
wrote:

> Hi All,
>
> I'm new to the GRASS-dev community and interested in doing Google Summer
> of Code this summer so I thought I'd introduce myself here. I'm a 1st year
> PhD student at North Carolina State University working with Dr. Helena
> Mitasova and the GeoForAll Lab
> . I'm interested in
> developing geospatial models and tools that have to do with flooding, sea
> level rise and the environmental impacts of climate change. I'm currently
> developing my coding skills and beginning to contribute to GRASS GIS and 
> Tangible
> Landscape .
>
> I'm applying for the project on improving the integration of GRASS and
> Jupyter Notebooks. Before applications open at the end of the month, I'm
> going to be working on the "test of skills" listed: building a test module
> for an r.centroids module 
> I've been working on and finishing the zonal-of-solar notebook
> .
>
> Looking forward to working together,
> Caitlin
>
> --
>
> Caitlin Haedrich
>
> Ph.D. Student, Geospatial Analytics | Center for Geospatial Analytics
>
> North Carolina State University
>
> https://chaedri.github.io/
>
> --
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Introduction - GSoC Student

[Caitlin Haedrich]

Hi All,

I'm new to the GRASS-dev community and interested in doing Google Summer of
Code this summer so I thought I'd introduce myself here. I'm a 1st year PhD
student at North Carolina State University working with Dr. Helena Mitasova
and the GeoForAll Lab .
I'm interested in developing geospatial models and tools that have to do
with flooding, sea level rise and the environmental impacts of climate
change. I'm currently developing my coding skills and beginning to
contribute to GRASS GIS and Tangible Landscape
.

I'm applying for the project on improving the integration of GRASS and
Jupyter Notebooks. Before applications open at the end of the month, I'm
going to be working on the "test of skills" listed: building a test module
for an r.centroids module 
I've been working on and finishing the zonal-of-solar notebook
.

Looking forward to working together,
Caitlin

--

Caitlin Haedrich

Ph.D. Student, Geospatial Analytics | Center for Geospatial Analytics

North Carolina State University

https://chaedri.github.io/

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

Re: [GRASS-dev] Introduction and Idea ( GSOC 2019 )

[Stefan Blumentrath]

Hi guys,

First of all, I have to mention, that I have almost no experience with kind of 
models. From tensorflow I have been looking a bit at tensorflow probability[1].
Could imagine that also v.class.ml[2] and r.learn.ml[3] could give some 
inspiration how such libraries could be plugged into GRASS in principle. Other 
interesting modelling libraries would be PyMC3[4] or Stan[5].
Just for mentioning it.

I can imagine that IO is particularly important for parallelism in these 
libraries...
Maybe it would be possible develop a general framework for this?

Cheers
Stefan

1: https://www.tensorflow.org/probability
2: https://grass.osgeo.org/grass74/manuals/addons/v.class.ml.html
3: https://grass.osgeo.org/grass74/manuals/addons/r.learn.ml.html
4: https://docs.pymc.io/
5: https://mc-stan.org/

-Original Message-
From: grass-dev  On Behalf Of Maris Nartiss
Sent: tirsdag 5. mars 2019 18:00
To: Luca Delucchi 
Cc: Soumya kanta Das ; GRASS-dev 

Subject: Re: [GRASS-dev] Introduction and Idea ( GSOC 2019 )

Hello,
svētd., 2019. g. 3. marts, plkst. 08:50 — lietotājs Luca Delucchi
() rakstīja:
>
> On Sat, 2 Mar 2019 at 18:48, Soumya kanta Das 
>  wrote:
> >
> > Hello,
>
> Hi,
>
> > Myself Soumya Kanta Das, studying Geo-informatics. Currently i work on 
> > automating geospatial workflow and Machine learning applications. I have 
> > previously worked on automated identification of buildings in Satellite 
> > imagery using Deep learning. I have language proficiency in python.
> >
> > I would like to develop a Deep learning module for grass using tensorflow 
> > library and python 3. Which would be very helpful for end-users.
> >
>
> something already exists in GRASS GIS addons using tensorflow [0], you 
> can have look there..

I have a working prototype of GRASS – Keras bridge (still needs a lot of work 
to fix all edge cases + support of second image_data_format).
My first approach was to use pure Python code, but it turned out to be reay 
slooow. Large parts have to be written in C (linked via ctypes). Currently 
there still is a speed penality due to GRASS raster code not supporting 
mutlithreaded applications. It all can be worked around.

Developing any high speed interface between ML libraries and GRASS needs some 
(good) understanding of working with multidimensional arrays in C and GRASS 
rasters in C.

> > Thank you.
> >
>
> [0] https://grass.osgeo.org/grass74/manuals/addons/i.ann.maskrcnn.html
>
> --
> ciao
> Luca

Just FYI,
Māris.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction and Idea ( GSOC 2019 )

[Maris Nartiss]

Hello,
svētd., 2019. g. 3. marts, plkst. 08:50 — lietotājs Luca Delucchi
() rakstīja:
>
> On Sat, 2 Mar 2019 at 18:48, Soumya kanta Das
>  wrote:
> >
> > Hello,
>
> Hi,
>
> > Myself Soumya Kanta Das, studying Geo-informatics. Currently i work on 
> > automating geospatial workflow and Machine learning applications. I have 
> > previously worked on automated identification of buildings in Satellite 
> > imagery using Deep learning. I have language proficiency in python.
> >
> > I would like to develop a Deep learning module for grass using tensorflow 
> > library and python 3. Which would be very helpful for end-users.
> >
>
> something already exists in GRASS GIS addons using tensorflow [0], you
> can have look there..

I have a working prototype of GRASS – Keras bridge (still needs a lot
of work to fix all edge cases + support of second image_data_format).
My first approach was to use pure Python code, but it turned out to be
reay slooow. Large parts have to be written in C (linked via
ctypes). Currently there still is a speed penality due to GRASS raster
code not supporting mutlithreaded applications. It all can be worked
around.

Developing any high speed interface between ML libraries and GRASS
needs some (good) understanding of working with multidimensional
arrays in C and GRASS rasters in C.

> > Thank you.
> >
>
> [0] https://grass.osgeo.org/grass74/manuals/addons/i.ann.maskrcnn.html
>
> --
> ciao
> Luca

Just FYI,
Māris.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction and Idea ( GSOC 2019 )

[Luca Delucchi]

On Sat, 2 Mar 2019 at 18:48, Soumya kanta Das
 wrote:
>
> Hello,

Hi,

> Myself Soumya Kanta Das, studying Geo-informatics. Currently i work on 
> automating geospatial workflow and Machine learning applications. I have 
> previously worked on automated identification of buildings in Satellite 
> imagery using Deep learning. I have language proficiency in python.
>
> I would like to develop a Deep learning module for grass using tensorflow 
> library and python 3. Which would be very helpful for end-users.
>

something already exists in GRASS GIS addons using tensorflow [0], you
can have look there..

> Thank you.
>

[0] https://grass.osgeo.org/grass74/manuals/addons/i.ann.maskrcnn.html

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Introduction and Idea ( GSOC 2019 )

[Soumya kanta Das]

Hello,
Myself Soumya Kanta Das, studying Geo-informatics. Currently i work on
automating geospatial workflow and Machine learning applications. I have
previously worked on automated identification of buildings in Satellite
imagery using Deep learning. I have language proficiency in python.

I would like to develop a Deep learning module for grass using tensorflow
library and python 3. Which would be very helpful for end-users.

Thank you.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction

[Luca Delucchi]

On 23 March 2018 at 17:08, Martin Landa  wrote:
> Hi,
>

Hi,

> 2018-03-23 17:05 GMT+01:00 Luca Delucchi :
>>> I tested on nc_spm_08_grass7
>>>
>>
>> ok with this location is working also for me.
>> I did few changes and submitted with r72530
>
> isn't testsuite based on basic nc location only? Ma
>

you are right, Supreet please send new file using basic nc location as
written before

https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.tar.gz

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction

[Martin Landa]

Hi,

2018-03-23 17:05 GMT+01:00 Luca Delucchi :
>> I tested on nc_spm_08_grass7
>>
>
> ok with this location is working also for me.
> I did few changes and submitted with r72530

isn't testsuite based on basic nc location only? Ma

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

Re: [GRASS-dev] Introduction

[Luca Delucchi]

On 22 March 2018 at 11:14, Supreet Singh Gill  wrote:
> but it is working for me, I attached the grass_cmd_output and
> test_keyvalue_result.
>
> I tested on nc_spm_08_grass7
>

ok with this location is working also for me.
I did few changes and submitted with r72530

> Thank You
> Supreet Singh
> https://singhsupreet.github.io/
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction

[Stefan Blumentrath]

Hi guys,

For me it works partly:

python ~/testmode.py

100%

.
100%

F
100%

.
==
FAIL: test_2 (__main__.Testrmode)
--
Traceback (most recent call last):
  File "/home/stefan.blumentrath/testmode.py", line 37, in test_2
msg="slope in degrees must be between 0 and 38.68939")
  File "/usr/local/grass-7.5.svn/etc/python/grass/gunittest/case.py", line 474, 
in assertRasterMinMax
self.fail(self._formatMessage(msg, stdmsg))
AssertionError: slope in degrees must be between 0 and 38.68939
The actual maximum (72.40761) is greater than the reference one (38.68939) for 
raster map slope (with minimum 0)

--
Ran 3 tests in 1.194s
FAILED (failures=1)


Something related to region settings (e.g. when reference values were 
generated)?


Cheers
Stefan

From: grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of Supreet 
Singh Gill
Sent: torsdag 22. mars 2018 11.15
To: Luca Delucchi <lucadel...@gmail.com>
Cc: GRASS-dev <grass-dev@lists.osgeo.org>
Subject: Re: [GRASS-dev] Introduction

but it is working for me, I attached the grass_cmd_output and 
test_keyvalue_result.
I tested on nc_spm_08_grass7

Thank You
Supreet Singh
https://singhsupreet.github.io/

On Thu, Mar 22, 2018 at 3:32 PM, Luca Delucchi 
<lucadel...@gmail.com<mailto:lucadel...@gmail.com>> wrote:
On 22 March 2018 at 10:07, Supreet Singh Gill 
<sharrygill5...@gmail.com<mailto:sharrygill5...@gmail.com>> wrote:
> Hi,
>

Hi,

> I attached the fixed file.
>

still not working

> Thank You
> Supreet Singh
> https://singhsupreet.github.io/
>

--
ciao
Luca

www.lucadelu.org<http://www.lucadelu.org>

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

Re: [GRASS-dev] Introduction

[Supreet Singh Gill]

but it is working for me, I attached the grass_cmd_output and
test_keyvalue_result.

I tested on nc_spm_08_grass7

Thank You
Supreet Singh
https://singhsupreet.github.io/

On Thu, Mar 22, 2018 at 3:32 PM, Luca Delucchi  wrote:

> On 22 March 2018 at 10:07, Supreet Singh Gill 
> wrote:
> > Hi,
> >
>
> Hi,
>
> > I attached the fixed file.
> >
>
> still not working
>
> > Thank You
> > Supreet Singh
> > https://singhsupreet.github.io/
> >
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
time=0.722s
status=succeeded
total=3
failures=0
errors=0
successes=3
skipped=0
expected_failures=0
unexpected_successes=0
tested_modules=r.mode,r.mode,r.mode
supplementary_files=
test_type=not-specified
cd "Desktop"
Working directory changed to:   
"/home/sharry/Desktop" 

(Thu Mar 22 15:41:11 2018)  
python testrmode.py 
.
.
.
GRASS_INFO_PERCENT: 0
GRASS_INFO_PERCENT: 3
GRASS_INFO_PERCENT: 6
GRASS_INFO_PERCENT: 9
GRASS_INFO_PERCENT: 12
GRASS_INFO_PERCENT: 15
GRASS_INFO_PERCENT: 18
GRASS_INFO_PERCENT: 21
GRASS_INFO_PERCENT: 24
GRASS_INFO_PERCENT: 27
GRASS_INFO_PERCENT: 30
GRASS_INFO_PERCENT: 33
GRASS_INFO_PERCENT: 36
GRASS_INFO_PERCENT: 39
GRASS_INFO_PERCENT: 42
GRASS_INFO_PERCENT: 45
GRASS_INFO_PERCENT: 48
GRASS_INFO_PERCENT: 51
GRASS_INFO_PERCENT: 54
GRASS_INFO_PERCENT: 57
GRASS_INFO_PERCENT: 60
GRASS_INFO_PERCENT: 63
GRASS_INFO_PERCENT: 66
GRASS_INFO_PERCENT: 69
GRASS_INFO_PERCENT: 72
GRASS_INFO_PERCENT: 75
GRASS_INFO_PERCENT: 78
GRASS_INFO_PERCENT: 81
GRASS_INFO_PERCENT: 84
GRASS_INFO_PERCENT: 87
GRASS_INFO_PERCENT: 90
GRASS_INFO_PERCENT: 93
GRASS_INFO_PERCENT: 96
GRASS_INFO_PERCENT: 99
GRASS_INFO_PERCENT: 100
GRASS_INFO_PERCENT: 0
GRASS_INFO_PERCENT: 3
GRASS_INFO_PERCENT: 6
GRASS_INFO_PERCENT: 9
GRASS_INFO_PERCENT: 12
GRASS_INFO_PERCENT: 15
GRASS_INFO_PERCENT: 18
GRASS_INFO_PERCENT: 21
GRASS_INFO_PERCENT: 24
GRASS_INFO_PERCENT: 27
GRASS_INFO_PERCENT: 30
GRASS_INFO_PERCENT: 33
GRASS_INFO_PERCENT: 36
GRASS_INFO_PERCENT: 39
GRASS_INFO_PERCENT: 42
GRASS_INFO_PERCENT: 45
GRASS_INFO_PERCENT: 48
GRASS_INFO_PERCENT: 51
GRASS_INFO_PERCENT: 54
GRASS_INFO_PERCENT: 57
GRASS_INFO_PERCENT: 60
GRASS_INFO_PERCENT: 63
GRASS_INFO_PERCENT: 66
GRASS_INFO_PERCENT: 69
GRASS_INFO_PERCENT: 72
GRASS_INFO_PERCENT: 75
GRASS_INFO_PERCENT: 78
GRASS_INFO_PERCENT: 81
GRASS_INFO_PERCENT: 84
GRASS_INFO_PERCENT: 87
GRASS_INFO_PERCENT: 90
GRASS_INFO_PERCENT: 93
GRASS_INFO_PERCENT: 96
GRASS_INFO_PERCENT: 99
GRASS_INFO_PERCENT: 100
GRASS_INFO_PERCENT: 0
GRASS_INFO_PERCENT: 3
GRASS_INFO_PERCENT: 6
GRASS_INFO_PERCENT: 9
GRASS_INFO_PERCENT: 12
GRASS_INFO_PERCENT: 15
GRASS_INFO_PERCENT: 18
GRASS_INFO_PERCENT: 21
GRASS_INFO_PERCENT: 24
GRASS_INFO_PERCENT: 27
GRASS_INFO_PERCENT: 30
GRASS_INFO_PERCENT: 33
GRASS_INFO_PERCENT: 36
GRASS_INFO_PERCENT: 39
GRASS_INFO_PERCENT: 42
GRASS_INFO_PERCENT: 45
GRASS_INFO_PERCENT: 48
GRASS_INFO_PERCENT: 51
GRASS_INFO_PERCENT: 54
GRASS_INFO_PERCENT: 57
GRASS_INFO_PERCENT: 60
GRASS_INFO_PERCENT: 63
GRASS_INFO_PERCENT: 66
GRASS_INFO_PERCENT: 69
GRASS_INFO_PERCENT: 72
GRASS_INFO_PERCENT: 75
GRASS_INFO_PERCENT: 78
GRASS_INFO_PERCENT: 81
GRASS_INFO_PERCENT: 84
GRASS_INFO_PERCENT: 87
GRASS_INFO_PERCENT: 90
GRASS_INFO_PERCENT: 93
GRASS_INFO_PERCENT: 96
GRASS_INFO_PERCENT: 99
GRASS_INFO_PERCENT: 100

--
Ran 3 tests in 0.722s
OK
(Thu Mar 22 15:41:12 2018) Command finished (1 sec) 
"""
Name:   r.mode test
Purpose:Tests r.mode and its flags/options.
	
Author: Supreet Singh
"""

from grass.gunittest.case import TestCase
from grass.gunittest.main import test

class Testrmode(TestCase):
output='rmode'
base='facility'
cover='soils_Kfactor'

@classmethod
def setUpClass(cls):
cls.use_temp_region()

@classmethod
def tearDownClass(cls):
cls.del_temp_region()

def tearDown(self):
self.runModule('g.remove', type='raster', flags='f', name=self.output)

def test_1(self):
facility='facility'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=facility, refmin=1, refmax=1,
	msg="facility in degrees must be between 1 and 1")

def test_2(self):
slope='slope'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=slope, refmin=0, refmax=38.68939,
	msg="slope in degrees must be between 0 and 38.68939")

def test_3(self):
elevation='elevation'

Re: [GRASS-dev] Introduction

[Luca Delucchi]

On 22 March 2018 at 10:07, Supreet Singh Gill  wrote:
> Hi,
>

Hi,

> I attached the fixed file.
>

still not working

> Thank You
> Supreet Singh
> https://singhsupreet.github.io/
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction

[Supreet Singh Gill]

Hi,

I attached the fixed file.

Thank You
Supreet Singh
https://singhsupreet.github.io/

On Wed, Mar 21, 2018 at 9:17 PM, Luca Delucchi  wrote:

> On 31 January 2018 at 15:31, sharry gill  wrote:
> > Hello,
> >
>
> Hi Sharry
>
> >
> > I have attached a simple test, I wrote for r.mode.
> >
>
> I run it in nc_basic_spm_grass7 [0] but it fails
>
> GRASS 7.5.svn (nc_basic_spm_grass7):~ > python ~/testrmode.py
>
> ERROR: Raster map  not found
> ERROR: Raster map  not found
>
> E
> ERROR: Raster map  not found
> ERROR: Raster map  not found
>
> E
> ERROR: Raster map  not found
> ERROR: Raster map  not found
>
> F
> ==
> ERROR: test_1 (__main__.Testrmode)
> --
> Traceback (most recent call last):
>   File "/home/lucadelu/testrmode.py", line 31, in test_1
> msg="facility in degrees must be between 1 and 1")
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/case.py",
> line 461, in assertRasterMinMax
> stdout = call_module('r.info', map=map, flags='r')
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/gmodules.py",
> line 131, in call_module
> raise CalledModuleError(returncode, module, kwargs, errors)
> CalledModuleError: Module run 1 r.info ended with error
> Process ended with non-zero return code {'map': 'facility', 'flags':
> 'r', 'stderr': -1, 'stdout': -1}. See the following errors:
> ERROR: Raster map  not found
>
>
> ==
> ERROR: test_2 (__main__.Testrmode)
> --
> Traceback (most recent call last):
>   File "/home/lucadelu/testrmode.py", line 37, in test_2
> msg="slope in degrees must be between 0 and 38.68939")
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/case.py",
> line 461, in assertRasterMinMax
> stdout = call_module('r.info', map=map, flags='r')
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/gmodules.py",
> line 131, in call_module
> raise CalledModuleError(returncode, module, kwargs, errors)
> CalledModuleError: Module run 1 r.info ended with error
> Process ended with non-zero return code {'map': 'slope', 'flags': 'r',
> 'stderr': -1, 'stdout': -1}. See the following errors:
> ERROR: Raster map  not found
>
>
> ==
> FAIL: test_3 (__main__.Testrmode)
> --
> Traceback (most recent call last):
>   File "/home/lucadelu/testrmode.py", line 43, in test_3
> msg="geology in degrees must be between 34300 and 43600")
>   File "/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-
> linux-gnu/etc/python/grass/gunittest/case.py",
> line 468, in assertRasterMinMax
> self.fail(self._formatMessage(msg, stdmsg))
> AssertionError: geology in degrees must be between 34300 and 43600
> The actual minimum (217) is smaller than the reference one (34300) for
> raster map geology (with maximum 948)
>
> --
> Ran 3 tests in 0.905s
> FAILED (failures=1, errors=2)
>
> could you please fix it?
>
> > I am new to Open Source community so I came early, so I can get to know
> > about OSGeo and GRASS GIS.
> >
> > Thank You
> > Supreet
> >
>
> [0] https://grass.osgeo.org/sampledata/north_carolina/nc_
> basic_spm_grass7.tar.gz
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
"""
Name:   r.mode test
Purpose:Tests r.mode and its flags/options.
	
Author: Supreet Singh
"""

from grass.gunittest.case import TestCase
from grass.gunittest.main import test

class Testrmode(TestCase):
output='rmode'
base='facility'
cover='soils_Kfactor'

@classmethod
def setUpClass(cls):
cls.use_temp_region()

@classmethod
def tearDownClass(cls):
cls.del_temp_region()

def tearDown(self):
self.runModule('g.remove', type='raster', flags='f', name=self.output)

def test_1(self):
facility='facility'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=facility, refmin=1, refmax=1,
	msg="facility in degrees must be between 1 and 1")

def test_2(self):
slope='slope'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=slope, refmin=0, refmax=38.68939,
	msg="slope in degrees must be between 0 and 38.68939")

def test_3(self):
elevation='elevation'
self.assertModule('r.mode', base=self.base, cover=self.cover, 

Re: [GRASS-dev] Introduction

[Luca Delucchi]

On 31 January 2018 at 15:31, sharry gill  wrote:
> Hello,
>

Hi Sharry

>
> I have attached a simple test, I wrote for r.mode.
>

I run it in nc_basic_spm_grass7 [0] but it fails

GRASS 7.5.svn (nc_basic_spm_grass7):~ > python ~/testrmode.py

ERROR: Raster map  not found
ERROR: Raster map  not found

E
ERROR: Raster map  not found
ERROR: Raster map  not found

E
ERROR: Raster map  not found
ERROR: Raster map  not found

F
==
ERROR: test_1 (__main__.Testrmode)
--
Traceback (most recent call last):
  File "/home/lucadelu/testrmode.py", line 31, in test_1
msg="facility in degrees must be between 1 and 1")
  File 
"/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-gnu/etc/python/grass/gunittest/case.py",
line 461, in assertRasterMinMax
stdout = call_module('r.info', map=map, flags='r')
  File 
"/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-gnu/etc/python/grass/gunittest/gmodules.py",
line 131, in call_module
raise CalledModuleError(returncode, module, kwargs, errors)
CalledModuleError: Module run 1 r.info ended with error
Process ended with non-zero return code {'map': 'facility', 'flags':
'r', 'stderr': -1, 'stdout': -1}. See the following errors:
ERROR: Raster map  not found


==
ERROR: test_2 (__main__.Testrmode)
--
Traceback (most recent call last):
  File "/home/lucadelu/testrmode.py", line 37, in test_2
msg="slope in degrees must be between 0 and 38.68939")
  File 
"/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-gnu/etc/python/grass/gunittest/case.py",
line 461, in assertRasterMinMax
stdout = call_module('r.info', map=map, flags='r')
  File 
"/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-gnu/etc/python/grass/gunittest/gmodules.py",
line 131, in call_module
raise CalledModuleError(returncode, module, kwargs, errors)
CalledModuleError: Module run 1 r.info ended with error
Process ended with non-zero return code {'map': 'slope', 'flags': 'r',
'stderr': -1, 'stdout': -1}. See the following errors:
ERROR: Raster map  not found


==
FAIL: test_3 (__main__.Testrmode)
--
Traceback (most recent call last):
  File "/home/lucadelu/testrmode.py", line 43, in test_3
msg="geology in degrees must be between 34300 and 43600")
  File 
"/home/lucadelu/compilati/grass_trunk/dist.x86_64-pc-linux-gnu/etc/python/grass/gunittest/case.py",
line 468, in assertRasterMinMax
self.fail(self._formatMessage(msg, stdmsg))
AssertionError: geology in degrees must be between 34300 and 43600
The actual minimum (217) is smaller than the reference one (34300) for
raster map geology (with maximum 948)

--
Ran 3 tests in 0.905s
FAILED (failures=1, errors=2)

could you please fix it?

> I am new to Open Source community so I came early, so I can get to know
> about OSGeo and GRASS GIS.
>
> Thank You
> Supreet
>

[0] https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.tar.gz

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Introduction

[sharry gill]

Hello,

I am Supreet Singh, from Punjab, India. Currently doing my bachelors from Guru
Nanak Dev Engineering College . I am interested
in GRASS GIS module testing so as an idea for GSOC I sent an email before.
I am Good in HTML, CSS, Javascript, C++ and especially Python as this
project idea is to be written in Python.

Link to a sample image for the project: Google Doc Link


I have attached a simple test, I wrote for r.mode.

I am new to Open Source community so I came early, so I can get to know
about OSGeo and GRASS GIS.

Thank You
Supreet
"""
Name:   r.mode test
Purpose:Tests r.mode and its flags/options.
	
Author: Supreet Singh
"""

from grass.gunittest.case import TestCase
from grass.gunittest.main import test

class Testrmode(TestCase):
output='rmode'
base='facility'
cover='geology'

@classmethod
def setUpClass(cls):
cls.use_temp_region()

@classmethod
def tearDownClass(cls):
cls.del_temp_region()

def tearDown(self):
self.runModule('g.remove', type='raster', flags='f', name=self.output)

def test_1(self):
facility='facility'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=facility, refmin=1, refmax=1,
	msg="facility in degrees must be between 1 and 1")

def test_2(self):
slope='slope'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=slope, refmin=0, refmax=38.68939,
	msg="slope in degrees must be between 0 and 38.68939")

def test_3(self):
geology='geology'
self.assertModule('r.mode', base=self.base, cover=self.cover, output=self.output)
self.assertRasterMinMax(map=geology, refmin=34300, refmax=43600,
	msg="geology in degrees must be between 34300 and 43600")

if __name__ == '__main__':
test()

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

Re: [GRASS-dev] Introduction for GSoC 2017

[Markus Neteler]

On Aug 8, 2017 2:56 PM, "Žofie Cimburová"  wrote:
>
> Hi,
> I'm working on the documentation update already :)

Great, thanks!

Markus

> Zofie
>
> On Tue, Aug 8, 2017 at 2:44 PM, Markus Neteler  wrote:
>>
>> On Mon, Aug 7, 2017 at 5:52 AM, Yann Chemin 
wrote:
>> > thanks for the constant feed back Zofie, was not possible to make it
work
>> > without you guys testing it.
>>
>> Great to see orthorectification in G7! Thanks to all involved here.
>>
>> A wish: can anyone (maybe Zofie? :-) please update this outdated
overview page?
>>
>> https://grass.osgeo.org/grass73/manuals/i.ortho.photo.html
>>
>> Then it would be all complete, I suppose.
>>
>> Extra material:
>> * the old ortho chapter in the 2nd edition of our book:
>>
http://grassbook.org/wp-content/uploads/2015/04/grassbook_2nd_2004_chapter10_aerial.pdf
>> * https://svn.osgeo.org/grass/grass/trunk/imagery/i.ortho.photo/
>>   --> README
>>
>> thanks
>> Markus
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Žofie Cimburová]

Hi,
I'm working on the documentation update already :)

Zofie

On Tue, Aug 8, 2017 at 2:44 PM, Markus Neteler  wrote:

> On Mon, Aug 7, 2017 at 5:52 AM, Yann Chemin 
> wrote:
> > thanks for the constant feed back Zofie, was not possible to make it work
> > without you guys testing it.
>
> Great to see orthorectification in G7! Thanks to all involved here.
>
> A wish: can anyone (maybe Zofie? :-) please update this outdated overview
> page?
>
> https://grass.osgeo.org/grass73/manuals/i.ortho.photo.html
>
> Then it would be all complete, I suppose.
>
> Extra material:
> * the old ortho chapter in the 2nd edition of our book:
>http://grassbook.org/wp-content/uploads/2015/04/
> grassbook_2nd_2004_chapter10_aerial.pdf
> * https://svn.osgeo.org/grass/grass/trunk/imagery/i.ortho.photo/
>   --> README
>
> thanks
> Markus
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Markus Neteler]

On Mon, Aug 7, 2017 at 5:52 AM, Yann Chemin  wrote:
> thanks for the constant feed back Zofie, was not possible to make it work
> without you guys testing it.

Great to see orthorectification in G7! Thanks to all involved here.

A wish: can anyone (maybe Zofie? :-) please update this outdated overview page?

https://grass.osgeo.org/grass73/manuals/i.ortho.photo.html

Then it would be all complete, I suppose.

Extra material:
* the old ortho chapter in the 2nd edition of our book:
   
http://grassbook.org/wp-content/uploads/2015/04/grassbook_2nd_2004_chapter10_aerial.pdf
* https://svn.osgeo.org/grass/grass/trunk/imagery/i.ortho.photo/
  --> README

thanks
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

thanks for the constant feed back Zofie, was not possible to make it work
without you guys testing it.
yann

On Aug 6, 2017 12:40 PM, "Stefan Blumentrath" <stefan.blumentr...@nina.no>
wrote:

> Hi again,
>
>
>
> Zofie tested the orthorectification suite in GRASS 7 and just confirmed
> that it works as expected!
>
> Thanks so much, Yann! For me this was the last missing feature for
> completely moving to GRASS 7!
>
>
>
> Cheers
>
> Stefan
>
>
>
>
>
> *From:* grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] *On Behalf
> Of *Blumentrath, Stefan
> *Sent:* tirsdag 21. mars 2017 08.05
> *To:* Yann Chemin <dr.yann.che...@gmail.com>; Luca Delucchi <
> lucadel...@gmail.com>
> *Cc:* GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <
> mananpa...@gmail.com>
> *Subject:* Re: [GRASS-dev] Introduction for GSoC 2017
>
>
>
> Hi Yann,
>
>
>
> Thanks so much! Very cool!
>
> I will test the photo2image GUI tool ASAP!
>
>
>
> Cheers
>
> Stefan
>
>
>
> *From:* Yann Chemin [mailto:dr.yann.che...@gmail.com
> <dr.yann.che...@gmail.com>]
> *Sent:* tirsdag 21. mars 2017 07.56
> *To:* Luca Delucchi <lucadel...@gmail.com>
> *Cc:* GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <
> mananpa...@gmail.com>; Blumentrath, Stefan <stefan.blumentr...@nina.no>
> *Subject:* Re: [GRASS-dev] Introduction for GSoC 2017
>
>
>
> Hi all,
>
> I have added to SVN trunk one of the two missing gui modules of
> i.ortho.photo recently: g.gui.iphoto2image at the command line launches it.
> All other modules but one are operational (still not fully tested though),
> I have already started working on the last one, which is also GUI based.
>
> Cheers,
> Yann
>
>
>
> On Mar 20, 2017 5:25 PM, "Luca Delucchi" <lucadel...@gmail.com> wrote:
>
> On 18 March 2017 at 08:30, Blumentrath, Stefan
> <stefan.blumentr...@nina.no> wrote:
> > Hi,
> >
>
> Hi,
>
> >
> > Could also porting (competition) of the i.ortho.photo modules (and here
> > especially the missing GUI modules around it) to GRASS 7 become scope of
> > this GSoC idea?
> >
>
> I fully support this idea, GUI for i.ortho.photo is the most important
> loss from GRASS 6
>
> >
> >
> > Cheers,
> >
> > Stefan
> >
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Stefan Blumentrath]

Hi again,

Zofie tested the orthorectification suite in GRASS 7 and just confirmed that it 
works as expected!
Thanks so much, Yann! For me this was the last missing feature for completely 
moving to GRASS 7!

Cheers
Stefan


From: grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of 
Blumentrath, Stefan
Sent: tirsdag 21. mars 2017 08.05
To: Yann Chemin <dr.yann.che...@gmail.com>; Luca Delucchi <lucadel...@gmail.com>
Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <mananpa...@gmail.com>
Subject: Re: [GRASS-dev] Introduction for GSoC 2017

Hi Yann,

Thanks so much! Very cool!
I will test the photo2image GUI tool ASAP!

Cheers
Stefan

From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
Sent: tirsdag 21. mars 2017 07.56
To: Luca Delucchi <lucadel...@gmail.com<mailto:lucadel...@gmail.com>>
Cc: GRASS-dev <grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>>; 
Manan Singh <mananpa...@gmail.com<mailto:mananpa...@gmail.com>>; Blumentrath, 
Stefan <stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>>
Subject: Re: [GRASS-dev] Introduction for GSoC 2017


Hi all,

I have added to SVN trunk one of the two missing gui modules of i.ortho.photo 
recently: g.gui.iphoto2image at the command line launches it. All other modules 
but one are operational (still not fully tested though), I have already started 
working on the last one, which is also GUI based.

Cheers,
Yann

On Mar 20, 2017 5:25 PM, "Luca Delucchi" 
<lucadel...@gmail.com<mailto:lucadel...@gmail.com>> wrote:
On 18 March 2017 at 08:30, Blumentrath, Stefan
<stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>> wrote:
> Hi,
>

Hi,

>
> Could also porting (competition) of the i.ortho.photo modules (and here
> especially the missing GUI modules around it) to GRASS 7 become scope of
> this GSoC idea?
>

I fully support this idea, GUI for i.ortho.photo is the most important
loss from GRASS 6

>
>
> Cheers,
>
> Stefan
>


--
ciao
Luca

www.lucadelu.org<http://www.lucadelu.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann]

Hi Stefan and all,

Anybody had the opportunity to try the modules ?

Any feed back?

Cheers,

Yann


On 12/05/2017 10:13, Blumentrath, Stefan wrote:

Thanks Yann! Great news!
I will use the modules on tilted digital camera images (from wildlife camera 
traps).
But I can check if we have some good aerial photos somewere in a drawer….

Cheers
Stefan


From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
Sent: fredag 12. mai 2017 09.19
To: Blumentrath, Stefan <stefan.blumentr...@nina.no>; Luca Delucchi 
<lucadel...@gmail.com>
Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <mananpa...@gmail.com>
Subject: Re: [GRASS-dev] Introduction for GSoC 2017

Hi Stefan,
the first throw is there in SVN, just update and recompile.
The two GUI are g.gui.iphoto2image and g.gui.iimage2target.
Finalization of the names are also open to suggestion, so far I just 
concatenated the old module names in v6 and added to g.gui.
Please test and if you have a scanned aerial photo with good info about camera 
and XYZ of fiducials, please throw it my side too so I can validate/finalize 
the output accuracy.
Cheers,
Yann

--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
JRC: 
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
OSGeo: https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group

On 21 March 2017 at 08:31, Yann 
<dr.yann.che...@gmail.com<mailto:dr.yann.che...@gmail.com>> wrote:
Hi Stefan,

please also launch the main menu: i.ortho.photo at the command line, it tends 
to be erratic.

(careful the i.photo.2target is not yet existing)

Ciao,
Yann



On 21/03/2017 08:04, Blumentrath, Stefan wrote:
Hi Yann,

Thanks so much! Very cool!
I will test the photo2image GUI tool ASAP!

Cheers
Stefan

From: Yann Chemin 
[mailto:dr.yann.che...@gmail.com<mailto:dr.yann.che...@gmail.com>]
Sent: tirsdag 21. mars 2017 07.56
To: Luca Delucchi <lucadel...@gmail.com<mailto:lucadel...@gmail.com>>
Cc: GRASS-dev <grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>>; Manan Singh 
<mananpa...@gmail.com<mailto:mananpa...@gmail.com>>; Blumentrath, Stefan 
<stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>>
Subject: Re: [GRASS-dev] Introduction for GSoC 2017


Hi all,

I have added to SVN trunk one of the two missing gui modules of i.ortho.photo 
recently: g.gui.iphoto2image at the command line launches it. All other modules 
but one are operational (still not fully tested though), I have already started 
working on the last one, which is also GUI based.

Cheers,
Yann

On Mar 20, 2017 5:25 PM, "Luca Delucchi" 
<lucadel...@gmail.com<mailto:lucadel...@gmail.com><mailto:lucadel...@gmail.com<mailto:lucadel...@gmail.com>>>
 wrote:
On 18 March 2017 at 08:30, Blumentrath, Stefan
<stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no><mailto:stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>>>
 wrote:
Hi,
Hi,
Could also porting (competition) of the i.ortho.photo modules (and here
especially the missing GUI modules around it) to GRASS 7 become scope of
this GSoC idea?
I fully support this idea, GUI for i.ortho.photo is the most important
loss from GRASS 6

Cheers,

Stefan

--
ciao
Luca

www.lucadelu.org<http://www.lucadelu.org><http://www.lucadelu.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org><mailto:grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>>
https://lists.osgeo.org/mailman/listinfo/grass-dev




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

Re: [GRASS-dev] Introduction for GSoC 2017

[Blumentrath, Stefan]

Thanks Yann! Great news!
I will use the modules on tilted digital camera images (from wildlife camera 
traps).
But I can check if we have some good aerial photos somewere in a drawer….

Cheers
Stefan


From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
Sent: fredag 12. mai 2017 09.19
To: Blumentrath, Stefan <stefan.blumentr...@nina.no>; Luca Delucchi 
<lucadel...@gmail.com>
Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <mananpa...@gmail.com>
Subject: Re: [GRASS-dev] Introduction for GSoC 2017

Hi Stefan,
the first throw is there in SVN, just update and recompile.
The two GUI are g.gui.iphoto2image and g.gui.iimage2target.
Finalization of the names are also open to suggestion, so far I just 
concatenated the old module names in v6 and added to g.gui.
Please test and if you have a scanned aerial photo with good info about camera 
and XYZ of fiducials, please throw it my side too so I can validate/finalize 
the output accuracy.
Cheers,
Yann

--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
JRC: 
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
OSGeo: https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group

On 21 March 2017 at 08:31, Yann 
<dr.yann.che...@gmail.com<mailto:dr.yann.che...@gmail.com>> wrote:
Hi Stefan,

please also launch the main menu: i.ortho.photo at the command line, it tends 
to be erratic.

(careful the i.photo.2target is not yet existing)

Ciao,
Yann



On 21/03/2017 08:04, Blumentrath, Stefan wrote:
Hi Yann,

Thanks so much! Very cool!
I will test the photo2image GUI tool ASAP!

Cheers
Stefan

From: Yann Chemin 
[mailto:dr.yann.che...@gmail.com<mailto:dr.yann.che...@gmail.com>]
Sent: tirsdag 21. mars 2017 07.56
To: Luca Delucchi <lucadel...@gmail.com<mailto:lucadel...@gmail.com>>
Cc: GRASS-dev <grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>>; 
Manan Singh <mananpa...@gmail.com<mailto:mananpa...@gmail.com>>; Blumentrath, 
Stefan <stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>>
Subject: Re: [GRASS-dev] Introduction for GSoC 2017


Hi all,

I have added to SVN trunk one of the two missing gui modules of i.ortho.photo 
recently: g.gui.iphoto2image at the command line launches it. All other modules 
but one are operational (still not fully tested though), I have already started 
working on the last one, which is also GUI based.

Cheers,
Yann

On Mar 20, 2017 5:25 PM, "Luca Delucchi" 
<lucadel...@gmail.com<mailto:lucadel...@gmail.com><mailto:lucadel...@gmail.com<mailto:lucadel...@gmail.com>>>
 wrote:
On 18 March 2017 at 08:30, Blumentrath, Stefan
<stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no><mailto:stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>>>
 wrote:
Hi,
Hi,
Could also porting (competition) of the i.ortho.photo modules (and here
especially the missing GUI modules around it) to GRASS 7 become scope of
this GSoC idea?
I fully support this idea, GUI for i.ortho.photo is the most important
loss from GRASS 6

Cheers,

Stefan

--
ciao
Luca

www.lucadelu.org<http://www.lucadelu.org><http://www.lucadelu.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org><mailto:grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>>
https://lists.osgeo.org/mailman/listinfo/grass-dev


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

Re: [GRASS-dev] Introduction for GSoC 2017

[Vaclav Petras]

On Fri, May 12, 2017 at 9:51 AM, Martin Landa 
wrote:

> since the tools is experimental we should not include in G7.4 I would
> say.
>

Or just say they are experimental.


> If you agree we have two options:
>
> * move it to Addons
> * after creating relbr_74 to remove the tools
>

Then I would just remove them from 74, because we want them in trunk. I
don't like it that much, but copy in addons may be good for users.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Martin Landa]

Hi,

2017-05-12 14:48 GMT+02:00 Yann Chemin :
> just did using svn mv

since the tools is experimental we should not include in G7.4 I would
say. If you agree we have two options:

* move it to Addons
* after creating relbr_74 to remove the tools

What do you think? Ma

>> >> g.gui.photo2image
>> >> g.gui.image2target
>> >>
>> >> (without the extra i)
>> >>
>> >
>> > +1
>>
>> +1
>>
>> If/when renaming, be sure to use "svn mv" for this to keep the history.
>> https://trac.osgeo.org/grass/wiki/HowToSVN#SVNusage
>> --> at the end of the section
>>
>> Markus
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://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
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

just did using svn mv

--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
*JRC:*
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
*OSGeo: *https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group


On 12 May 2017 at 10:52, Markus Neteler  wrote:

> On Fri, May 12, 2017 at 9:33 AM, Luca Delucchi 
> wrote:
> > On 12 May 2017 at 09:28, Moritz Lennert 
> wrote:
> >> On 12/05/17 09:18, Yann Chemin wrote:
> >>>
> >>> Hi Stefan,
> >>>
> >>> the first throw is there in SVN, just update and recompile.
> >>> The two GUI are g.gui.iphoto2image and g.gui.iimage2target.
> >>>
> >>> Finalization of the names are also open to suggestion, so far I just
> >>> concatenated the old module names in v6 and added to g.gui.
> >>
> >> I would suggest
> >>
> >> g.gui.photo2image
> >> g.gui.image2target
> >>
> >> (without the extra i)
> >>
> >
> > +1
>
> +1
>
> If/when renaming, be sure to use "svn mv" for this to keep the history.
> https://trac.osgeo.org/grass/wiki/HowToSVN#SVNusage
> --> at the end of the section
>
> Markus
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Markus Neteler]

On Fri, May 12, 2017 at 9:33 AM, Luca Delucchi  wrote:
> On 12 May 2017 at 09:28, Moritz Lennert  wrote:
>> On 12/05/17 09:18, Yann Chemin wrote:
>>>
>>> Hi Stefan,
>>>
>>> the first throw is there in SVN, just update and recompile.
>>> The two GUI are g.gui.iphoto2image and g.gui.iimage2target.
>>>
>>> Finalization of the names are also open to suggestion, so far I just
>>> concatenated the old module names in v6 and added to g.gui.
>>
>> I would suggest
>>
>> g.gui.photo2image
>> g.gui.image2target
>>
>> (without the extra i)
>>
>
> +1

+1

If/when renaming, be sure to use "svn mv" for this to keep the history.
https://trac.osgeo.org/grass/wiki/HowToSVN#SVNusage
--> at the end of the section

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

Re: [GRASS-dev] Introduction for GSoC 2017

[Luca Delucchi]

On 12 May 2017 at 09:28, Moritz Lennert  wrote:
> On 12/05/17 09:18, Yann Chemin wrote:
>>
>> Hi Stefan,
>>
>> the first throw is there in SVN, just update and recompile.
>> The two GUI are g.gui.iphoto2image and g.gui.iimage2target.
>>
>> Finalization of the names are also open to suggestion, so far I just
>> concatenated the old module names in v6 and added to g.gui.
>
>
> I would suggest
>
> g.gui.photo2image
> g.gui.image2target
>
> (without the extra i)
>

+1

> Moritz
>



-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Moritz Lennert]

On 12/05/17 09:18, Yann Chemin wrote:

Hi Stefan,

the first throw is there in SVN, just update and recompile.
The two GUI are g.gui.iphoto2image and g.gui.iimage2target.

Finalization of the names are also open to suggestion, so far I just
concatenated the old module names in v6 and added to g.gui.


I would suggest

g.gui.photo2image
g.gui.image2target

(without the extra i)

Moritz

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

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

Hi Stefan,

the first throw is there in SVN, just update and recompile.
The two GUI are g.gui.iphoto2image and g.gui.iimage2target.

Finalization of the names are also open to suggestion, so far I just
concatenated the old module names in v6 and added to g.gui.

Please test and if you have a scanned aerial photo with good info about
camera and XYZ of fiducials, please throw it my side too so I can
validate/finalize the output accuracy.

Cheers,
Yann

--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
*JRC:*
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
*OSGeo: *https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group


On 21 March 2017 at 08:31, Yann <dr.yann.che...@gmail.com> wrote:

> Hi Stefan,
>
> please also launch the main menu: i.ortho.photo at the command line, it
> tends to be erratic.
>
> (careful the i.photo.2target is not yet existing)
>
> Ciao,
> Yann
>
>
>
> On 21/03/2017 08:04, Blumentrath, Stefan wrote:
>
>> Hi Yann,
>>
>> Thanks so much! Very cool!
>> I will test the photo2image GUI tool ASAP!
>>
>> Cheers
>> Stefan
>>
>> From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
>> Sent: tirsdag 21. mars 2017 07.56
>> To: Luca Delucchi <lucadel...@gmail.com>
>> Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <
>> mananpa...@gmail.com>; Blumentrath, Stefan <stefan.blumentr...@nina.no>
>> Subject: Re: [GRASS-dev] Introduction for GSoC 2017
>>
>>
>> Hi all,
>>
>> I have added to SVN trunk one of the two missing gui modules of
>> i.ortho.photo recently: g.gui.iphoto2image at the command line launches it.
>> All other modules but one are operational (still not fully tested though),
>> I have already started working on the last one, which is also GUI based.
>>
>> Cheers,
>> Yann
>>
>> On Mar 20, 2017 5:25 PM, "Luca Delucchi" <lucadel...@gmail.com> ucadel...@gmail.com>> wrote:
>> On 18 March 2017 at 08:30, Blumentrath, Stefan
>> <stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>> wrote:
>>
>>> Hi,
>>>
>>> Hi,
>>
>> Could also porting (competition) of the i.ortho.photo modules (and here
>>> especially the missing GUI modules around it) to GRASS 7 become scope of
>>> this GSoC idea?
>>>
>>> I fully support this idea, GUI for i.ortho.photo is the most important
>> loss from GRASS 6
>>
>>
>>> Cheers,
>>>
>>> Stefan
>>>
>>>
>> --
>> ciao
>> Luca
>>
>> www.lucadelu.org<http://www.lucadelu.org>
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

On Mar 22, 2017 6:01 PM, "Markus Metz" <markus.metz.gisw...@gmail.com>
wrote:
>
>
>
> On Tue, Mar 21, 2017 at 8:31 AM, Yann <dr.yann.che...@gmail.com> wrote:
> >
> > Hi Stefan,
> >
> > please also launch the main menu: i.ortho.photo at the command line, it
tends to be erratic.
> >
> > (careful the i.photo.2target is not yet existing)
>
> you can clone and modify g.gui.gcp to get a wxgui replacement for
i.photo.2target.

Yes started that already.

Essentially you need to replace calls to m.transform with calls to
i.ortho.transform which I wrote a wile ago for this purpose.

I will look into that, I saw that m.transform would need replacement
indeed. Did not know it was ready yet. Thanks.

And some interface to set fiducials is missing (old i.photo.2image) which
would need to be added to the wizard of g.gui.gcp.
>
> Markus M

Thanks Markus
Yann
>
> >
> > Ciao,
> > Yann
> >
> >
> >
> > On 21/03/2017 08:04, Blumentrath, Stefan wrote:
> >>
> >> Hi Yann,
> >>
> >> Thanks so much! Very cool!
> >> I will test the photo2image GUI tool ASAP!
> >>
> >> Cheers
> >> Stefan
> >>
> >> From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
> >> Sent: tirsdag 21. mars 2017 07.56
> >> To: Luca Delucchi <lucadel...@gmail.com>
> >> Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <
mananpa...@gmail.com>; Blumentrath, Stefan <stefan.blumentr...@nina.no>
> >> Subject: Re: [GRASS-dev] Introduction for GSoC 2017
> >>
> >>
> >> Hi all,
> >>
> >> I have added to SVN trunk one of the two missing gui modules of
i.ortho.photo recently: g.gui.iphoto2image at the command line launches it.
All other modules but one are operational (still not fully tested though),
I have already started working on the last one, which is also GUI based.
> >>
> >> Cheers,
> >> Yann
> >>
> >> On Mar 20, 2017 5:25 PM, "Luca Delucchi" <lucadel...@gmail.com> wrote:
> >> On 18 March 2017 at 08:30, Blumentrath, Stefan
> >> <stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>> wrote:
> >>>
> >>> Hi,
> >>>
> >> Hi,
> >>
> >>> Could also porting (competition) of the i.ortho.photo modules (and
here
> >>> especially the missing GUI modules around it) to GRASS 7 become scope
of
> >>> this GSoC idea?
> >>>
> >> I fully support this idea, GUI for i.ortho.photo is the most important
> >> loss from GRASS 6
> >>
> >>>
> >>> Cheers,
> >>>
> >>> Stefan
> >>>
> >>
> >> --
> >> ciao
> >> Luca
> >>
> >> www.lucadelu.org<http://www.lucadelu.org>
> >> ___
> >> grass-dev mailing list
> >> grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>
> >> https://lists.osgeo.org/mailman/listinfo/grass-dev
> >
> >
> > ___
> > grass-dev mailing list
> > grass-dev@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Markus Metz]

On Tue, Mar 21, 2017 at 8:31 AM, Yann <dr.yann.che...@gmail.com> wrote:
>
> Hi Stefan,
>
> please also launch the main menu: i.ortho.photo at the command line, it
tends to be erratic.
>
> (careful the i.photo.2target is not yet existing)

you can clone and modify g.gui.gcp to get a wxgui replacement for
i.photo.2target. Essentially you need to replace calls to m.transform with
calls to i.ortho.transform which I wrote a wile ago for this purpose. And
some interface to set fiducials is missing (old i.photo.2image) which would
need to be added to the wizard of g.gui.gcp.

Markus M

>
> Ciao,
> Yann
>
>
>
> On 21/03/2017 08:04, Blumentrath, Stefan wrote:
>>
>> Hi Yann,
>>
>> Thanks so much! Very cool!
>> I will test the photo2image GUI tool ASAP!
>>
>> Cheers
>> Stefan
>>
>> From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
>> Sent: tirsdag 21. mars 2017 07.56
>> To: Luca Delucchi <lucadel...@gmail.com>
>> Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <
mananpa...@gmail.com>; Blumentrath, Stefan <stefan.blumentr...@nina.no>
>> Subject: Re: [GRASS-dev] Introduction for GSoC 2017
>>
>>
>> Hi all,
>>
>> I have added to SVN trunk one of the two missing gui modules of
i.ortho.photo recently: g.gui.iphoto2image at the command line launches it.
All other modules but one are operational (still not fully tested though),
I have already started working on the last one, which is also GUI based.
>>
>> Cheers,
>> Yann
>>
>> On Mar 20, 2017 5:25 PM, "Luca Delucchi" <lucadel...@gmail.com> wrote:
>> On 18 March 2017 at 08:30, Blumentrath, Stefan
>> <stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>> wrote:
>>>
>>> Hi,
>>>
>> Hi,
>>
>>> Could also porting (competition) of the i.ortho.photo modules (and here
>>> especially the missing GUI modules around it) to GRASS 7 become scope of
>>> this GSoC idea?
>>>
>> I fully support this idea, GUI for i.ortho.photo is the most important
>> loss from GRASS 6
>>
>>>
>>> Cheers,
>>>
>>> Stefan
>>>
>>
>> --
>> ciao
>> Luca
>>
>> www.lucadelu.org<http://www.lucadelu.org>
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Blumentrath, Stefan]

Hi Yann,

Thanks so much! Very cool!
I will test the photo2image GUI tool ASAP!

Cheers
Stefan

From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
Sent: tirsdag 21. mars 2017 07.56
To: Luca Delucchi <lucadel...@gmail.com>
Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <mananpa...@gmail.com>; 
Blumentrath, Stefan <stefan.blumentr...@nina.no>
Subject: Re: [GRASS-dev] Introduction for GSoC 2017


Hi all,

I have added to SVN trunk one of the two missing gui modules of i.ortho.photo 
recently: g.gui.iphoto2image at the command line launches it. All other modules 
but one are operational (still not fully tested though), I have already started 
working on the last one, which is also GUI based.

Cheers,
Yann

On Mar 20, 2017 5:25 PM, "Luca Delucchi" 
<lucadel...@gmail.com<mailto:lucadel...@gmail.com>> wrote:
On 18 March 2017 at 08:30, Blumentrath, Stefan
<stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>> wrote:
> Hi,
>

Hi,

>
> Could also porting (competition) of the i.ortho.photo modules (and here
> especially the missing GUI modules around it) to GRASS 7 become scope of
> this GSoC idea?
>

I fully support this idea, GUI for i.ortho.photo is the most important
loss from GRASS 6

>
>
> Cheers,
>
> Stefan
>


--
ciao
Luca

www.lucadelu.org<http://www.lucadelu.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann]

Hi Stefan,

please also launch the main menu: i.ortho.photo at the command line, it 
tends to be erratic.


(careful the i.photo.2target is not yet existing)

Ciao,
Yann



On 21/03/2017 08:04, Blumentrath, Stefan wrote:

Hi Yann,

Thanks so much! Very cool!
I will test the photo2image GUI tool ASAP!

Cheers
Stefan

From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
Sent: tirsdag 21. mars 2017 07.56
To: Luca Delucchi <lucadel...@gmail.com>
Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <mananpa...@gmail.com>; 
Blumentrath, Stefan <stefan.blumentr...@nina.no>
Subject: Re: [GRASS-dev] Introduction for GSoC 2017


Hi all,

I have added to SVN trunk one of the two missing gui modules of i.ortho.photo 
recently: g.gui.iphoto2image at the command line launches it. All other modules 
but one are operational (still not fully tested though), I have already started 
working on the last one, which is also GUI based.

Cheers,
Yann

On Mar 20, 2017 5:25 PM, "Luca Delucchi" 
<lucadel...@gmail.com<mailto:lucadel...@gmail.com>> wrote:
On 18 March 2017 at 08:30, Blumentrath, Stefan
<stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>> wrote:

Hi,


Hi,


Could also porting (competition) of the i.ortho.photo modules (and here
especially the missing GUI modules around it) to GRASS 7 become scope of
this GSoC idea?


I fully support this idea, GUI for i.ortho.photo is the most important
loss from GRASS 6



Cheers,

Stefan



--
ciao
Luca

www.lucadelu.org<http://www.lucadelu.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/grass-dev


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

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

Hi all,

I have added to SVN trunk one of the two missing gui modules of
i.ortho.photo recently: g.gui.iphoto2image at the command line launches it.
All other modules but one are operational (still not fully tested though),
I have already started working on the last one, which is also GUI based.

Cheers,
Yann

On Mar 20, 2017 5:25 PM, "Luca Delucchi"  wrote:

> On 18 March 2017 at 08:30, Blumentrath, Stefan
>  wrote:
> > Hi,
> >
>
> Hi,
>
> >
> > Could also porting (competition) of the i.ortho.photo modules (and here
> > especially the missing GUI modules around it) to GRASS 7 become scope of
> > this GSoC idea?
> >
>
> I fully support this idea, GUI for i.ortho.photo is the most important
> loss from GRASS 6
>
> >
> >
> > Cheers,
> >
> > Stefan
> >
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Luca Delucchi]

On 18 March 2017 at 08:30, Blumentrath, Stefan
 wrote:
> Hi,
>

Hi,

>
> Could also porting (competition) of the i.ortho.photo modules (and here
> especially the missing GUI modules around it) to GRASS 7 become scope of
> this GSoC idea?
>

I fully support this idea, GUI for i.ortho.photo is the most important
loss from GRASS 6

>
>
> Cheers,
>
> Stefan
>


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Vaclav Petras]

On Sat, Mar 18, 2017 at 3:30 AM, Blumentrath, Stefan <
stefan.blumentr...@nina.no> wrote:

> Could also porting (competition) of the i.ortho.photo modules (and here
> especially the missing GUI modules around it) to GRASS 7 become scope of
> this GSoC idea?
>

See also:

https://trac.osgeo.org/grass/browser/grass/trunk/imagery/i.ortho.photo


> The lack of Orthorectification tools in GRASS 7 is the only reason for me
> to keep GRASS 6 in parallel…
>

Perhaps, there should be a list of tickets or a wiki to collect things
needed for people to fully switch to G7 (needs to be created by those who
actually use G6).

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

Re: [GRASS-dev] Introduction for GSoC 2017

[Vaclav Petras]

On Wed, Mar 15, 2017 at 3:00 AM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:

>
> >
> >> - A tool to attribute class values to raster objects. This is much
> >>   simpler and "just" a combination of GUI + r.what + form to add a
> >>   value + writing everything to a text file. In other words, it is
> >the
> >>   current GUI raster interrogation tool enhanced to add a value and
> >to
> >>   write info to a file.
> >>
> >
> >This sounds like raster attribute table for GRASS GIS. This needs some
> >serious design.
>
> No, I was not aiming for raster attribute tables. The main motivation for
> me is that when you create segments in an object-based image analysis
> approach and you want to then extract some objects as training objects this
> is currently not easy to do. For such training you have to identify the
> objects and indicate which class they're in. My idea is not to store this
> info within the gisdbase, but to output it to text file (yes, again ;-))
> which can then be used as input to further treatment (e.g. v.class.mlR &
> co).
>
>
>
I don't say that this can't be implemented through external CSV files and
the tools for handling them and transferring raster values into them are
generally useful. The thing I'm uncomfortable about is that it looks like a
raster attribute table from user point of view but it is different and also
at one point CSV won't be enough for some they will need actual database or
SQL. We had ASCII vectors in the past... (not that I would be around for
that ;-)

>Moritz and all,
> >
> >in cases like this, when a GSoC idea can be split into a separate
> >features
> >and they are reasonable feature requests (they wouldn't be part of the
> >idea
> >otherwise, right?), it would be good if we create the appropriate
> >tickets
> >for each of those. We did this last summer when we used keywords (tags)
> >`gsoc2016` and `cartography` for each ticket related to the GSoC
> >Cartography Improvements idea:
> >
> >https://trac.osgeo.org/grass/query?status=assigned=
> >closed=new=reopened=~gsoc2016+cartography
> >
> >For this idea it could be e.g. `gsoc2017` and `ImageAnalysisGUI`, but
> >please suggest something better (it must be one word, no spaces).
>
> +1
>
> Do you think we should create these tickets now, or as part of the first
> phase of the project ?



Yes, now.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Blumentrath, Stefan]

Hi,

Could also porting (competition) of the i.ortho.photo modules (and here 
especially the missing GUI modules around it) to GRASS 7 become scope of this 
GSoC idea?

Workflows from GRASS 6 could be improved a bit in that context quite a bit too, 
e.g.:

-  Having both image and target map in an interactive window for 
setting image coordinates and GCPs

-  Possibility to move points for image coordinates to improve RMSE

-  Pick altitude from target terrain

The lack of Orthorectification tools in GRASS 7 is the only reason for me to 
keep GRASS 6 in parallel…

Cheers,
Stefan

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

Re: [GRASS-dev] Introduction for GSoC '17

[Vaclav Petras]

On Wed, Mar 15, 2017 at 7:55 AM, Anisha Godha 
wrote:

> I am a fourth year student in Geological Technology at Indian Institute of
> Technology Roorkee. This January, I built an ArcGIS plug-in in Python that
> automates the Laminar Flow Model method to give a glacier's thickness
> distribution raster. For my thesis, I will be working around developing a
> framework that gives recommendation for specific Spatial Interpolation
> Techniques based on user dataset.



It seems you have expertise in these specific areas, so it might be better
for you to consider also topics which are focused more on something related
to what you work on. The topics you can propose are not limited by the list
on the wiki [1]. However, it may be harder to find mentors in this case.

Also, for the programming now and during application period, you have a
choice of working on some ticket or you can implement some of your previous
work in GRASS GIS (or port it to GRASS GIS).

Vaclav

[1] https://trac.osgeo.org/grass/wiki/GSoC/2017
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC '17

[Moritz Lennert]

Hi Anisha and welcome to GRASS GIS !

On 15/03/17 12:55, Anisha Godha wrote:

Hi

My name is Anisha and I am a fourth year student in Geological
Technology at Indian Institute of Technology Roorkee. This January, I
built an ArcGIS plug-in in Python that automates the Laminar Flow Model
method to give a glacier's thickness distribution raster. For my thesis,
I will be working around developing a framework that gives
recommendation for specific Spatial Interpolation Techniques based on
user dataset.

When I learnt about some of the project ideas listed by OSGeo, I was
extremely eager to be a part of this open source community. I am
especially interested in 'Additional GUI tools for Image Analysis',
since I think these enhancements will make the interface very
user-friendly. I have less familiarity with GRASS-GIS but I am keen on
picking it up soon.


Concerning the specific project, please see some information in the 
thread at [1].


More generally, make sure to have gone through the more general material 
at [2].


At this stage you should spend time to get familiar with GRASS GIS. 
Install everything you need for compilation, check out the code, compile 
and read through some of the docs.


Moritz



[1] https://lists.osgeo.org/pipermail/grass-dev/2017-March/084526.html
[2] 
https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

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

[GRASS-dev] Introduction for GSoC '17

[Anisha Godha]

Hi

My name is Anisha and I am a fourth year student in Geological Technology
at Indian Institute of Technology Roorkee. This January, I built an ArcGIS
plug-in in Python that automates the Laminar Flow Model method to give a
glacier's thickness distribution raster. For my thesis, I will be working
around developing a framework that gives recommendation for specific
Spatial Interpolation Techniques based on user dataset.

When I learnt about some of the project ideas listed by OSGeo, I was
extremely eager to be a part of this open source community. I am especially
interested in 'Additional GUI tools for Image Analysis', since I think
these enhancements will make the interface very user-friendly. I have less
familiarity with GRASS-GIS but I am keen on picking it up soon.

Thanks, and I hope to make a good contribution.

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

Re: [GRASS-dev] Introduction for GSoC 2017

[Moritz Lennert]

Le 15 mars 2017 04:26:53 GMT+01:00, Vaclav Petras  a 
écrit :
>Dear Moritz and students,
>
>here are some of my ideas for these ideas. This is a good start. I
>think we
>need enhancement ticket with use cases for each item.
>
>On Tue, Mar 14, 2017 at 6:25 AM, Moritz Lennert <
>mlenn...@club.worldonline.be> wrote:
>
>> - A general vector interactive attribute table editor which pops
>>   up an attribute editing form when you click on a vector map.
>>   Currently, to do this, you have to go into digitizing mode.
>>
>
>This is what the original query dialog in GUI was doing, but then it
>was
>replaced by something which is optimized for (ready only) queries and
>does
>not allow editing. You need to specify how the editing dialog would be
>connected to the current GUI; e.g. new button?

A button in the GUI (e.g. within a query menu) would be nice, but it could 
possibly also be implemented as a g.gui.* module.

>
>
>> In
>>   addition, it would be great to be able to somehow (text input file
>?)
>>   be able to define the columns you see in the form so that you don't
>>   have to scroll through tens of lines before you reach those that
>you
>>   want to edit.
>>
>
>Is a text file the user friendly way you are looking for? Should this
>be
>stored between GUI sessions?

I find text files the most versatile, accessible and easy to handle by 
everyone, but I guess I'm a bit old school ;-). All it would need is a list of 
column names (unless we want to allow defining column input widget types). If 
time allows we could create another module that allows creating this file.


>
>
>> - A tool to attribute class values to raster objects. This is much
>>   simpler and "just" a combination of GUI + r.what + form to add a
>>   value + writing everything to a text file. In other words, it is
>the
>>   current GUI raster interrogation tool enhanced to add a value and
>to
>>   write info to a file.
>>
>
>This sounds like raster attribute table for GRASS GIS. This needs some
>serious design.

No, I was not aiming for raster attribute tables. The main motivation for me is 
that when you create segments in an object-based image analysis approach and 
you want to then extract some objects as training objects this is currently not 
easy to do. For such training you have to identify the objects and indicate 
which class they're in. My idea is not to store this info within the gisdbase, 
but to output it to text file (yes, again ;-)) which can then be used as input 
to further treatment (e.g. v.class.mlR & co).


>
>There is more of these individual features which may be useful, e.g.
>imagery group support in the Data tab or r.pack/r.unpack equivalent for
>imagery groups.
> Also the GUI dialog which shows for (instead of)
>i.group
>needs some improvements.


The r.pack/unpack idea sounds great. I haven't really encountered problems with 
the others, so I'd leave that to you. We just need to make sure we don't 
increase the number of tasks too much.

I think the rules editor that is also part of the proposal will take some work 
and thought...


>
>
>Moritz and all,
>
>in cases like this, when a GSoC idea can be split into a separate
>features
>and they are reasonable feature requests (they wouldn't be part of the
>idea
>otherwise, right?), it would be good if we create the appropriate
>tickets
>for each of those. We did this last summer when we used keywords (tags)
>`gsoc2016` and `cartography` for each ticket related to the GSoC
>Cartography Improvements idea:
>
>https://trac.osgeo.org/grass/query?status=assigned=
>closed=new=reopened=~gsoc2016+cartography
>
>For this idea it could be e.g. `gsoc2017` and `ImageAnalysisGUI`, but
>please suggest something better (it must be one word, no spaces).

+1

Do you think we should create these tickets now, or as part of the first phase 
of the project ?

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

Re: [GRASS-dev] Introduction for GSoC 2017

[Vaclav Petras]

Dear Moritz and students,

here are some of my ideas for these ideas. This is a good start. I think we
need enhancement ticket with use cases for each item.

On Tue, Mar 14, 2017 at 6:25 AM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:

> - A general vector interactive attribute table editor which pops
>   up an attribute editing form when you click on a vector map.
>   Currently, to do this, you have to go into digitizing mode.
>

This is what the original query dialog in GUI was doing, but then it was
replaced by something which is optimized for (ready only) queries and does
not allow editing. You need to specify how the editing dialog would be
connected to the current GUI; e.g. new button?


> In
>   addition, it would be great to be able to somehow (text input file ?)
>   be able to define the columns you see in the form so that you don't
>   have to scroll through tens of lines before you reach those that you
>   want to edit.
>

Is a text file the user friendly way you are looking for? Should this be
stored between GUI sessions?


> - A tool to attribute class values to raster objects. This is much
>   simpler and "just" a combination of GUI + r.what + form to add a
>   value + writing everything to a text file. In other words, it is the
>   current GUI raster interrogation tool enhanced to add a value and to
>   write info to a file.
>

This sounds like raster attribute table for GRASS GIS. This needs some
serious design.

There is more of these individual features which may be useful, e.g.
imagery group support in the Data tab or r.pack/r.unpack equivalent for
imagery groups. Also the GUI dialog which shows for (instead of) i.group
needs some improvements.


Rachit, Manan, and other students,

it is important that you look and work on some of existing tickets or even
find some problems or small possible enhancements by exploring the current
functionality.

An good example ticket is the one by Moritz:

https://trac.osgeo.org/grass/ticket/3310

You can also do some general tickets to familiarize yourself with different
parts of the GRASS GIS code base, for example:

https://trac.osgeo.org/grass/ticket/3314


Moritz and all,

in cases like this, when a GSoC idea can be split into a separate features
and they are reasonable feature requests (they wouldn't be part of the idea
otherwise, right?), it would be good if we create the appropriate tickets
for each of those. We did this last summer when we used keywords (tags)
`gsoc2016` and `cartography` for each ticket related to the GSoC
Cartography Improvements idea:

https://trac.osgeo.org/grass/query?status=assigned=
closed=new=reopened=~gsoc2016+cartography

For this idea it could be e.g. `gsoc2017` and `ImageAnalysisGUI`, but
please suggest something better (it must be one word, no spaces).

Best,
Vaclav
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Moritz Lennert]

Hi Rachit and welcome to GRASS GIS !

[CC'ing Manan as he was also interested in this topic]

Le Tue, 14 Mar 2017 14:32:56 +0530,
Rachit Kansal  a écrit :

> Hi, I'm Rachit Kansal, 4th year Computer Science student from BITS
> Pilani, India. I hope I'm not late to make the contact. I would like
> to give a small brief about myself.
> 
> 
> I am proficient in Python and have good experience in GUI programming
> using PyQT as well in GIS (specifically QGIS). I have developed
> couple of plugins for QGIS during my internship period at Indian
> Institute of Remote Sensing (ISRO)-Geoinformatics Department. ). I
> also have good experience with various python libraries like Numpy,
> Scipy, Pandas, Scikit-learn, Keras, Matplotllib, Scrapy, etc.
> 
> 
> 
> I'm interested in contributing to the GRASS GIS for GSOC 17. I am
> looking forward to working on the project “Additional GUI tools for
> image analysis”.
> 
> 
> I would like to get further details regarding the project and what
> kind of new GUI tools are required?

Have you looked at [1] ?

As mentioned there, I see three main tasks:

- A general vector interactive attribute table editor which pops
  up an attribute editing form when you click on a vector map.
  Currently, to do this, you have to go into digitizing mode. In
  addition, it would be great to be able to somehow (text input file ?)
  be able to define the columns you see in the form so that you don't
  have to scroll through tens of lines before you reach those that you
  want to edit.
- A tool to attribute class values to raster objects. This is much
  simpler and "just" a combination of GUI + r.what + form to add a
  value + writing everything to a text file. In other words, it is the
  current GUI raster interrogation tool enhanced to add a value and to
  write info to a file.
- A tool to allow easy construction of rulesets for ruleset-based
  classification. This would be a front-end to r.mapcalc and/or
  v.db.update. It should allow the user to define a series of input
  bands/columns and threshold values for those.


Note that on the wiki, I also added a link to an open enhancement
ticket. Solving one or two tasks of that ticket is a good way to get
familiar with GRASS GUI development and would allow you to demonstrate
your programming skills in your application (or after your
application and before selection). 

Moritz

[1]
https://trac.osgeo.org/grass/wiki/GSoC/2017#AdditionalGUItoolsforimageanalysis
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Introduction for GSoC 2017

[Rachit Kansal]

Hi, I'm Rachit Kansal, 4th year Computer Science student from BITS Pilani,
India. I hope I'm not late to make the contact. I would like to give a
small brief about myself.


I am proficient in Python and have good experience in GUI programming using
PyQT as well in GIS (specifically QGIS). I have developed couple of plugins
for QGIS during my internship period at Indian Institute of Remote Sensing
(ISRO)-Geoinformatics Department. ). I also have good experience with
various python libraries like Numpy, Scipy, Pandas, Scikit-learn, Keras,
Matplotllib, Scrapy, etc.



I'm interested in contributing to the GRASS GIS for GSOC 17. I am looking
forward to working on the project “Additional GUI tools for image analysis”.


I would like to get further details regarding the project and what kind of
new GUI tools are required?
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction and GSoC

[Pierre Roudier]

Hi,

As a user, I would also find the integration of say OTB in GRASS being a
plus - a very general segmentation algorithm like the watershed is provided
by OTB and is a handy tool at times. OTB being based on VTK, maybe you
could make use of some of Soeren's work on the vtk-grass-bridge?

Pierre
On Apr 4, 2012 4:47 PM, Eric Momsen eric.mom...@gmail.com wrote:

 On Tue, Apr 3, 2012 at 9:57 AM, Moritz Lennert
 mlenn...@club.worldonline.be wrote:
  I personally am a bit weary of increasing dependencies between packages,
 but
  at the same time, why re-invent the wheel. Integrating the OTB algorithms
  into GRASS would definitely be a great plus.
 
  This said, several FOSS4G programs out there already play the role of
  integrators (e.g. QGIS, gvSIG) and I'm not sure that GRASS should try to
 go
  the same direction. Generally, I'd say: let GRASS do really well what it
  does, and not try to integrate everything.
 

 This does sound critical to me.  Being new to GIS, I have been
 struggling to figure out what the differences (strength/weakness/etc)
 are between GRASS, QGIS, etc.  I started with GRASS and R and haven't
 had time to try out the other programs, so am only comparing based on
 what each website describes.  I haven't found any feature comparison
 table.  So I am interested to hear what everyone has to say about what
 packages should (or should not) be integrated into GRASS vs. what
 packages GRASS is integrated into...but I suspect it is a bigger issue
 than can be answered in a GSoC project. :)
 ___
 grass-dev mailing list
 grass-dev@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-dev

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

Re: [GRASS-dev] Introduction and GSoC

[Moritz Lennert]

On 02/04/12 22:03, Markus Neteler wrote:

On Mon, Apr 2, 2012 at 1:42 PM, Moritz Lennert
mlenn...@club.worldonline.be  wrote:
...

4. Currently GRASS does not provide any image segmentation as such. i.smap
contains image segmentation in its process, but the user cannot get
segmented outputs.


Just a small comment - even not this one?
http://grass.osgeo.org/wiki/GRASS_AddOns#r.seg
r.seg performs image segmentation and discontinuity detection (based on
the Mumford-Shah variational model).


Ah, another GRASS module I didn't know about. ;-)



Perhaps it could be extended?


I'll have a look at it.

Moritz

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

Re: [GRASS-dev] Introduction and GSoC

[Moritz Lennert]

On 03/04/12 16:12, Eric Momsen wrote:

Thanks for the input!  I added some more questions below.

Also, later today I will probably post to R-Sig-Geo (or some other
list?) to ask what tools people currently use, and what areas they
would find most helpful to be integrated into GRASS.  That might help
focus where I should spend the time.

On Mon, Apr 2, 2012 at 6:42 AM, Moritz Lennert
mlenn...@club.worldonline.be  wrote:

On 30/03/12 23:56, Eric Momsen wrote:


I am reading more about image classification (from
http://grass.osgeo.org/wiki/GRASS_SoC_Ideas ):

4. Implement image segmentation algorithms and tools
5. Implement region-based classification
6. Implement hierarchical classification tools (e.g. being able to
create a large class forest, with subclasses of different types of
forests)


...

Concerning the ideas:

4. Currently GRASS does not provide any image segmentation as such. i.smap
contains image segmentation in its process, but the user cannot get
segmented outputs. Many algorithms exist and its an ongoing field of
research. FLOSS software that provide such algorithms include Orfeo Toolbox
(OTB), SAGA, R, Sextante (?) and probably a whole series of others. I think
the implementation of a series of such algorithms could be a project on its
own.


Does it make more sense to implement the algorithms again, or pick the
most useful that are implemented in some other FLOSS and provide an
easy integration to access them from the GRASS front end?  (I'm
thinking of v.krige which uses existing R packages to do the
processing work.)

Has Sextante or OTB been tied into GRASS in this manner?


I personally am a bit weary of increasing dependencies between packages, 
but at the same time, why re-invent the wheel. Integrating the OTB 
algorithms into GRASS would definitely be a great plus.


This said, several FOSS4G programs out there already play the role of 
integrators (e.g. QGIS, gvSIG) and I'm not sure that GRASS should try to 
go the same direction. Generally, I'd say: let GRASS do really well what 
it does, and not try to integrate everything.


So, the discussion boils down to: what do we think should be integral 
part of GRASS (the same question is true for the proposal concerning a 
PostGIS manager).





5. One of the main applications of image segmentation today is in
region-based classification of very high resolution imagery. As with current
resolutions individual objects are composed of many pixels, it is often more
efficient to first identify objects or homogeneous multi-pixel regions in
the image through segmentation and then to classify these regions. OTB
provides this I think, but I don't know if any other FLOSS software does. 5
depends on 4, so it is only possible if 4. is limited to the strict minimum
in terms of segmentation algorithms and then focus is put on 5. Maybe a bit
too ambitious.


If I can use the OTB implementation from GRASS, then I will include
this as a stretch goal if time remains at the end of the summer.


As always, we should check how much integrating OTB means in terms of 
added dependencies for GRASS. Also, OTB is C++ which AFAICT tell often 
spells trouble. Then again, there is a Python wrapper which you could use.


Don't know what others think of all this.

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

Re: [GRASS-dev] Introduction and GSoC

[Eric Momsen]

On Tue, Apr 3, 2012 at 9:57 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
 I personally am a bit weary of increasing dependencies between packages, but
 at the same time, why re-invent the wheel. Integrating the OTB algorithms
 into GRASS would definitely be a great plus.

 This said, several FOSS4G programs out there already play the role of
 integrators (e.g. QGIS, gvSIG) and I'm not sure that GRASS should try to go
 the same direction. Generally, I'd say: let GRASS do really well what it
 does, and not try to integrate everything.


This does sound critical to me.  Being new to GIS, I have been
struggling to figure out what the differences (strength/weakness/etc)
are between GRASS, QGIS, etc.  I started with GRASS and R and haven't
had time to try out the other programs, so am only comparing based on
what each website describes.  I haven't found any feature comparison
table.  So I am interested to hear what everyone has to say about what
packages should (or should not) be integrated into GRASS vs. what
packages GRASS is integrated into...but I suspect it is a bigger issue
than can be answered in a GSoC project. :)
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction and GSoC

[Moritz Lennert]

On 30/03/12 23:56, Eric Momsen wrote:

I am reading more about image classification (from
http://grass.osgeo.org/wiki/GRASS_SoC_Ideas ):

4. Implement image segmentation algorithms and tools
5. Implement region-based classification
6. Implement hierarchical classification tools (e.g. being able to
create a large class forest, with subclasses of different types of
forests)

I see Hamish is interested in mentoring the parallelization portion of
that list.  Are these other ideas orphans, or is someone available
that could discuss the background and needs of the community around
these ideas (and/or mentor...)  Thanks!


I'm the one who added these idea to the list as I see that this is one 
of the reasons colleagues do not adopt GRASS. However, I'm not an expert 
in the matter and am not sure I would be very helpful as mentor 
(although I'm willing to try).


Concerning the ideas:

4. Currently GRASS does not provide any image segmentation as such. 
i.smap contains image segmentation in its process, but the user cannot 
get segmented outputs. Many algorithms exist and its an ongoing field of 
research. FLOSS software that provide such algorithms include Orfeo 
Toolbox (OTB), SAGA, R, Sextante (?) and probably a whole series of 
others. I think the implementation of a series of such algorithms could 
be a project on its own.


5. One of the main applications of image segmentation today is in 
region-based classification of very high resolution imagery. As with 
current resolutions individual objects are composed of many pixels, it 
is often more efficient to first identify objects or homogeneous 
multi-pixel regions in the image through segmentation and then to 
classify these regions. OTB provides this I think, but I don't know if 
any other FLOSS software does. 5 depends on 4, so it is only possible if 
4. is limited to the strict minimum in terms of segmentation algorithms 
and then focus is put on 5. Maybe a bit too ambitious.


6. In the current classification algorithms in GRASS each designated 
class of pixels is on the same hierarchical level as others. However, it 
is often interesting to provide the option to classify an image first in 
a rough manner into a series of base classes (built-up, vegetation, 
naked soils) and then to refine classification within each of these 
classes (e.g. built-up into high-density / low-density, vegetation into 
forest, grasslands, etc), but to keep the hierarchy, i.e. to allow 
extracting an image (and a legend) of the classification at each level.


Hope this helps and maybe motivates others to join-in as mentors.

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

Re: [GRASS-dev] Introduction and GSoC

[Markus Neteler]

On Mon, Apr 2, 2012 at 1:42 PM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
...
 4. Currently GRASS does not provide any image segmentation as such. i.smap
 contains image segmentation in its process, but the user cannot get
 segmented outputs.

Just a small comment - even not this one?
http://grass.osgeo.org/wiki/GRASS_AddOns#r.seg
r.seg performs image segmentation and discontinuity detection (based on
the Mumford-Shah variational model).

Perhaps it could be extended?

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

Re: [GRASS-dev] Introduction and GSoC

[Eric Momsen]

I am reading more about image classification (from
http://grass.osgeo.org/wiki/GRASS_SoC_Ideas ):

4. Implement image segmentation algorithms and tools
5. Implement region-based classification
6. Implement hierarchical classification tools (e.g. being able to
create a large class forest, with subclasses of different types of
forests)

I see Hamish is interested in mentoring the parallelization portion of
that list.  Are these other ideas orphans, or is someone available
that could discuss the background and needs of the community around
these ideas (and/or mentor...)  Thanks!

(And uDig conversation continued below...)

On Fri, Mar 23, 2012 at 5:47 PM, Wolf Bergenheim
wolf+gr...@bergenheim.net wrote:
 On Fri, Mar 23, 2012 at 22:04, Eric Momsen eric.mom...@gmail.com wrote:

 On Fri, Mar 23, 2012 at 2:41 PM, Wolf Bergenheim
 wolf+gr...@bergenheim.net wrote:
  Hi Eric!
 
  It might help us in trying to classify you if you could tell a bit about
  your programming experience. What languages are you comfortable with? I
  see

 So far I have been using mostly java.  I wrote a small implementation
 for a pattern mining algorithm in R, and will be doing a little prolog
 this semester.  Years ago I helped set up a data transfer/validation
 system ( Oracle database - visual basic - website), but those
 skills are pretty rusty now.  I certainly expect to learn more
 languages.


 Hmm If you are most strong in Java I'd recommend looking at uDig
 (http://udig.refractions.net/confluence/display/HACK/Summer+of+Code), since
 GRASS is C and Python. It might be a better match.


I'm happy to learn Python, it seems the software goal is more
important then the language that will be used.

My impression is that the goal is to provide an easy way for the user
to *manually* explore data from any available source.  The
visualization and intuitive interface look great.  But am I correct
that for doing statistics and number crunching, I should be focusing
on GRASS and R?


  that you are interested in data mining, which is unfortunately something
  I
  know very little about... Did you see any ideas which interested you?
  You

 The first project for animating raster/(and possibly vector) time
 series data was interesting, as well as a number of the imagery
 topics.


 Cool, You should probably think about more than one topic and maybe prepare
 several applications.


  can of course also come up with your own project. Is there for instance
  some
  data mining module missing from GRASS? That could be interesting,
  especially
  if you prepare a good solid proposal for it.

 I was actually hoping to get farther along with my own research to be
 able to (selfishly) propose something directly helpful to my work.  (I
 do understand the goal is the code, but if I could meet both goals...)
  So far I seem to be stuck on the pre-processing side of things.  I
 will touch base with my adviser again next week to see if we can come
 up with something interesting to propose.  If we do come up with
 something, should I sketch the idea here first?  Is someone available
 to mentor?


 There might be someone willing to mentor. That remains to be seen. Would
 your adviser be interested in helping to co-mentor you, along with a GRASS
 mentor? It would definitely be a good idea to discuss your ideas here first,
 it will improve the chances of getting selected.

  --Wolf

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

[GRASS-dev] Introduction and GSoC

[Eric Momsen]

Hi everyone,

I'm relatively new to the GRASS world, and thought I would send a
quick introduction.  After spending some time in the real world as
an engineer, I have returned to university life and have a first goal
of a master's degree in computer science.  My research currently
involves data mining in an agricultural setting, and the tools include
GRASS and R.

I'm trying to decide if I've come up the learning curve far enough to
contribute new code for GRASS as part of the Google Summer of Code.  I
must decide soon, the deadline for student applications is approaching
fast :)

I've seen the list of project ideas on the wiki, there is a lot there!
 Would anyone want to suggest a few that could be a good place for a
new arrival to start, and/or would tie in well to data mining?  I'm
happy to discuss on the list, or you can contact me at eric dot momsen
at gmail.

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

Re: [GRASS-dev] Introduction and GSoC

[Wolf Bergenheim]

Hi Eric!

It might help us in trying to classify you if you could tell a bit about
your programming experience. What languages are you comfortable with? I see
that you are interested in data mining, which is unfortunately something I
know very little about... Did you see any ideas which interested you? You
can of course also come up with your own project. Is there for instance
some data mining module missing from GRASS? That could be interesting,
especially if you prepare a good solid proposal for it.

--Wolf

On Fri, Mar 23, 2012 at 20:14, Eric Momsen eric.mom...@gmail.com wrote:

 Hi everyone,

 I'm relatively new to the GRASS world, and thought I would send a
 quick introduction.  After spending some time in the real world as
 an engineer, I have returned to university life and have a first goal
 of a master's degree in computer science.  My research currently
 involves data mining in an agricultural setting, and the tools include
 GRASS and R.

 I'm trying to decide if I've come up the learning curve far enough to
 contribute new code for GRASS as part of the Google Summer of Code.  I
 must decide soon, the deadline for student applications is approaching
 fast :)

 I've seen the list of project ideas on the wiki, there is a lot there!
  Would anyone want to suggest a few that could be a good place for a
 new arrival to start, and/or would tie in well to data mining?  I'm
 happy to discuss on the list, or you can contact me at eric dot momsen
 at gmail.

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

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

Re: [GRASS-dev] Introduction and GSoC

[Eric Momsen]

On Fri, Mar 23, 2012 at 2:41 PM, Wolf Bergenheim
wolf+gr...@bergenheim.net wrote:
 Hi Eric!

 It might help us in trying to classify you if you could tell a bit about
 your programming experience. What languages are you comfortable with? I see

So far I have been using mostly java.  I wrote a small implementation
for a pattern mining algorithm in R, and will be doing a little prolog
this semester.  Years ago I helped set up a data transfer/validation
system ( Oracle database - visual basic - website), but those
skills are pretty rusty now.  I certainly expect to learn more
languages.

 that you are interested in data mining, which is unfortunately something I
 know very little about... Did you see any ideas which interested you? You

The first project for animating raster/(and possibly vector) time
series data was interesting, as well as a number of the imagery
topics.

 can of course also come up with your own project. Is there for instance some
 data mining module missing from GRASS? That could be interesting, especially
 if you prepare a good solid proposal for it.

I was actually hoping to get farther along with my own research to be
able to (selfishly) propose something directly helpful to my work.  (I
do understand the goal is the code, but if I could meet both goals...)
 So far I seem to be stuck on the pre-processing side of things.  I
will touch base with my adviser again next week to see if we can come
up with something interesting to propose.  If we do come up with
something, should I sketch the idea here first?  Is someone available
to mentor?

-Eric


 --Wolf

 On Fri, Mar 23, 2012 at 20:14, Eric Momsen eric.mom...@gmail.com wrote:

 Hi everyone,

 I'm relatively new to the GRASS world, and thought I would send a
 quick introduction.  After spending some time in the real world as
 an engineer, I have returned to university life and have a first goal
 of a master's degree in computer science.  My research currently
 involves data mining in an agricultural setting, and the tools include
 GRASS and R.

 I'm trying to decide if I've come up the learning curve far enough to
 contribute new code for GRASS as part of the Google Summer of Code.  I
 must decide soon, the deadline for student applications is approaching
 fast :)

 I've seen the list of project ideas on the wiki, there is a lot there!
  Would anyone want to suggest a few that could be a good place for a
 new arrival to start, and/or would tie in well to data mining?  I'm
 happy to discuss on the list, or you can contact me at eric dot momsen
 at gmail.

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


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

Re: [GRASS-dev] Introduction and GSoC

[Wolf Bergenheim]

On Fri, Mar 23, 2012 at 22:04, Eric Momsen eric.mom...@gmail.com wrote:

 On Fri, Mar 23, 2012 at 2:41 PM, Wolf Bergenheim
 wolf+gr...@bergenheim.net wrote:
  Hi Eric!
 
  It might help us in trying to classify you if you could tell a bit about
  your programming experience. What languages are you comfortable with? I
 see

 So far I have been using mostly java.  I wrote a small implementation
 for a pattern mining algorithm in R, and will be doing a little prolog
 this semester.  Years ago I helped set up a data transfer/validation
 system ( Oracle database - visual basic - website), but those
 skills are pretty rusty now.  I certainly expect to learn more
 languages.


Hmm If you are most strong in Java I'd recommend looking at uDig (
http://udig.refractions.net/confluence/display/HACK/Summer+of+Code), since
GRASS is C and Python. It might be a better match.


  that you are interested in data mining, which is unfortunately something
 I
  know very little about... Did you see any ideas which interested you? You

 The first project for animating raster/(and possibly vector) time
 series data was interesting, as well as a number of the imagery
 topics.


Cool, You should probably think about more than one topic and maybe prepare
several applications.


   can of course also come up with your own project. Is there for instance
 some
  data mining module missing from GRASS? That could be interesting,
 especially
  if you prepare a good solid proposal for it.

 I was actually hoping to get farther along with my own research to be
 able to (selfishly) propose something directly helpful to my work.  (I
 do understand the goal is the code, but if I could meet both goals...)
  So far I seem to be stuck on the pre-processing side of things.  I
 will touch base with my adviser again next week to see if we can come
 up with something interesting to propose.  If we do come up with
 something, should I sketch the idea here first?  Is someone available
 to mentor?


There might be someone willing to mentor. That remains to be seen. Would
your adviser be interested in helping to co-mentor you, along with a GRASS
mentor? It would definitely be a good idea to discuss your ideas here
first, it will improve the chances of getting selected.

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