Re: [GRASS-dev] [GRASS GIS] #3424: v.random add minimum distance between points

2017-10-10 Thread GRASS GIS 
#3424: v.random add minimum distance between points
--+---
  Reporter:  lucadelu |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Default  |Version:  unspecified
Resolution:   |   Keywords:  v.random distance
   CPU:  Unspecified  |   Platform:  Unspecified
--+---

Comment (by neteler):

 Some related discussion is e.g. here with (pseudo) algorithm:

 https://stackoverflow.com/questions/8930796/generating-random-points-with-
 defined-minimum-and-maximum-distance

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] We need mentors for Google Code-In

2017-10-10 Thread Margherita Di Leo 
Dear Anna,

On Wed, Oct 4, 2017 at 7:41 PM, Anna Petrášová 
wrote:

> Hi Vero,
>
> On Wed, Oct 4, 2017 at 11:24 AM, Veronica Andreo 
> wrote:
> > Hey devs,
> >
> > As the subject reads: We need more mentors for Google Code-In :)
> >
> > GCI is a competition addressed to high-school students aged 13-17, as an
> > introduction to the open source world. They are supposed to complete as
> much
> > tasks as possible to win the contest. These tasks should be short simple
> > stuff (3-5 hours), but since they have to complete several to win, we
> need
> > to plan lots of them and be available to review what the students submit
> > rather quickly, so they can start with a new one. For that reason, it is
> > better if we are more mentors.
> >
> > Here is the GRASS wiki [0] with more details and a collection of ideas
> for
> > tasks that should then be further explained and developed in the format
> of
> > tasks. I think the ideas are nice and this could be a funny experience.
> > Moreover, we could attract new generations and benefit from their
> creativity
> > ;)
> >
>
> this is probably not very helpful response, but I am little bit
> skeptical about this and maybe you can clarify some things. My main
> problem is that GRASS is not the type of software you just start to
> use and understand it right away. Even making useful screenshots
> requires decent knowledge of the software and geospatial data/models.
> Do you think these students have any ideas about GIS? I confess I
> haven't spent much time thinking about this program yet, but I see a
> lot of time spent by mentors defining precise tasks without too much
> gain. I can see this could be useful for things like designing
> promotional materials, but not much beyond that. But I am open to be
> convinced otherwise.
>
>
>
I had the same doubts as you have, and I think only experience can give us
the answer. I partly overcame my doubts talking to other organizations that
run the code in. They suggested preparing some beginner tasks like
- "Install the software following the instructions here XXX and make a
screenshot"
- "Follow this tutorial XXX and make a screenshot of the result"
- "Prepare a video of 20 minutes, explaining how to get started with the
software to your fellow GCI students"
I think the more complicated is the software, the more work we need to
prepare tasks that are approachable. The good news is that, after the first
year, things get smoother, mentors learn a lot from the students, students
prepare some good material that can be reused for next editions and also
for promoting the software, and students often even come back to mentor
other students.
I have the feeling that if we never try, we never know how will end up.. ;-)


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

Re: [GRASS-dev] descriptions of some add-ons in add-on index

2017-10-10 Thread Luca Delucchi 
On 10 October 2017 at 09:00, Veronica Andreo  wrote:
> Hi devs,
>

Hi,

> I have noticed that the description for r.modis in [0] is not correct. It
> reads:
>
> "r.modis: Vegetation indices"
>
> Where is it taking the description from if there's no such piece of text in
> [1]?
>

from the module description "MODIS VI - Vegetation Indices" :-)

> In the case of r.green, it takes a number of characters from the DESCRIPTION
> in [2], but it does not look nice either:
>
> "r.green: r.green computes the residual energy potential of different
> renewable energies like biomass or hydropower. The tool is organized in the
> modules r.green.hydro and r.green.biomassfor which are composed of several
> programs considering different limits (e.g."
>
> Seems to be something related to groups of add-ons modules (?)
>

yes, I think they should follow r.li [3] way without description

I'm looking for a solution like r.li

> best,
> Vero
>
> [0] https://grass.osgeo.org/grass72/manuals/addons/
> [1] https://grass.osgeo.org/grass72/manuals/addons/r.modis.html
> [2] https://grass.osgeo.org/grass72/manuals/addons/r.green.html
>

[3] https://grass.osgeo.org/grass72/manuals/raster.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] descriptions of some add-ons in add-on index

2017-10-10 Thread Veronica Andreo 
Hi devs,

I have noticed that the description for r.modis in [0] is not correct. It
reads:

"r.modis: Vegetation indices"

Where is it taking the description from if there's no such piece of text in
[1]?

In the case of r.green, it takes a number of characters from the
DESCRIPTION in [2], but it does not look nice either:

"r.green:* r.green* computes the residual energy potential of different
renewable energies like biomass or hydropower. The tool is organized in the
modules r.green.hydro and r.green.biomassfor which are composed of several
programs considering different limits (e.g."

Seems to be something related to groups of add-ons modules (?)

best,
Vero

[0] https://grass.osgeo.org/grass72/manuals/addons/
[1] https://grass.osgeo.org/grass72/manuals/addons/r.modis.html
[2] https://grass.osgeo.org/grass72/manuals/addons/r.green.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3420: v.vect.stats: add "where" option

2017-10-10 Thread GRASS GIS 
#3420: v.vect.stats: add "where" option
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.4.0
 Component:  Vector   |Version:  svn-trunk
Resolution:  fixed|   Keywords:  v.vect.stats, where
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by veroandreo):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Thanks a lot Markus! This was almost real time enhancement! And it works
 so nicely! Cool!

 closing...

--
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3424: v.random add minimum distance between points

2017-10-10 Thread GRASS GIS 
#3424: v.random add minimum distance between points
---+-
 Reporter:  lucadelu   |  Owner:  grass-dev@…
 Type:  enhancement| Status:  new
 Priority:  normal |  Milestone:
Component:  Default|Version:  unspecified
 Keywords:  v.random distance  |CPU:  Unspecified
 Platform:  Unspecified|
---+-
 Could be really useful to add minimum distance between points in v.random

--
Ticket URL: 
GRASS GIS 

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