Re: [GRASS-dev] GRASS GIS and GSoC

2017-03-28 Thread Vaclav Petras
Zeke, you should try to fix some tickets (as suggested on the GSoC wiki page you linked); see the lists below. Alternatively, for your project, it may be appropriate to implement a small tool for some dataset which is easy to handle for you (e.g. something you used before). Look at the r.modis

[GRASS-dev] Recruiting Teaching assistant/PhD candidate

2017-03-28 Thread Moritz Lennert
Hello to all, My department at the Free University of Brussels (ULB) is recruiting a PhD candidate who will teach practicals in GIS, remote sensing and others. All geomatics teaching is with FOSS4G, currently GRASS GIS, QGIS, PostGIS, ... It is a 6-year position with half time teaching and

Re: [GRASS-dev] [release] GRASS 7.2.1 planning

2017-03-28 Thread Markus Neteler
On Tue, Mar 28, 2017 at 2:20 PM, Moritz Lennert wrote: > On 28/03/17 08:03, Martin Landa wrote: >> 2017-03-03 10:28 GMT+01:00 Markus Neteler : > > I ask myself the question of this schedule is appropriate for point > releases. Maybe 1

Re: [GRASS-dev] [release] GRASS 7.2.1RC1

2017-03-28 Thread Blumentrath, Stefan
Maybe enough (best) to handle it in the manual? Meaning, add that information to the notes? Users can avoid that lines/boundaries are broken by running v.dissolve in advance if needed? Cheers Stefan ___ grass-dev mailing list

Re: [GRASS-dev] [release] GRASS 7.2.1RC1

2017-03-28 Thread Helmut Kudrnovsky
Martin Landa wrote > Hi, > > 2017-03-27 21:39 GMT+02:00 Helmut Kudrnovsky > hellik@ > : >> G7A:v.clip - very easy to use and expected GIS functionality without >> hassle >> of complicated commmands :-) >> >> tested v.clip quite a lot in the last weeks; very nice module with >> expected >> GIS

Re: [GRASS-dev] GRASS GIS and GSoC

2017-03-28 Thread Blumentrath, Stefan
Hi Zeke, I cannot offer to mentor your project, but I could make some shell scripts available for you, that turn publicly available data into GRASS Locations and mapsets. It is not really much, but depending on the approach you choose they might be a helpful startingpoint. BTW. comparable

Re: [GRASS-dev] GRASS GIS and GSoC

2017-03-28 Thread Zechariah Krautwurst
Stefan, Thanks for the reply! Shell scripts, documentation, or any further advice about finding mentors or otherwise would be a huge help. And yes, I would definitely like to create a more broadly applicable framework that could accommodate toolsets like r.modis. Thanks again, and I look forward

Re: [GRASS-dev] [release] GRASS 7.2.1 planning

2017-03-28 Thread Moritz Lennert
On 28/03/17 08:03, Martin Landa wrote: Hi, 2017-03-03 10:28 GMT+01:00 Markus Neteler : I ask myself the question of this schedule is appropriate for point releases. Maybe 1 month between soft and hard freeze is a lot ? I would agree. Two/three weeks could be enough... Ma

Re: [GRASS-dev] [release] GRASS 7.2.1RC1

2017-03-28 Thread Moritz Lennert
On 27/03/17 21:53, Markus Neteler wrote: On Mon, Mar 27, 2017 at 9:39 PM, Helmut Kudrnovsky wrote: Markus Neteler wrote On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa ... Please (all) check https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.1tobebackported Addon

Re: [GRASS-dev] [GRASS GIS] #3322: t.info: h-flag has no effect

2017-03-28 Thread GRASS GIS
#3322: t.info: h-flag has no effect --+- Reporter: sbl | Owner: grass-dev@… Type: defect | Status: new Priority: minor| Milestone: 7.2.1 Component: Temporal |Version:

[GRASS-dev] [GRASS GIS] #3322: t.info: h-flag has no effect

2017-03-28 Thread GRASS GIS
#3322: t.info: h-flag has no effect +- Reporter: sbl | Owner: grass-dev@… Type: defect | Status: new Priority: minor | Milestone: 7.2.1 Component: Temporal|Version:

Re: [GRASS-dev] [release] GRASS 7.2.1 planning

2017-03-28 Thread Martin Landa
Hi, 2017-03-03 10:28 GMT+01:00 Markus Neteler : >>> I ask myself the question of this schedule is appropriate for point >>> releases. Maybe 1 month between soft and hard freeze is a lot ? >> >> I would agree. Two/three weeks could be enough... Ma > > > +1 do you agree to