[GRASS-dev] [release] GRASS 7.2.1RC1

Hi all,

based on roadmap published in ML [1] we are close to RC1. There are no
blockers registered [2], so it is seems that we can slowly start
preparing RC1. Any objections?

Ma

[1] https://lists.osgeo.org/pipermail/grass-dev/2017-February/084328.html
[2] https://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&priority=blocker&priority=critical&milestone=7.2.1&milestone=7.2.0&group=type&order=priority

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa <landa.martin@gmail.com> wrote:

Hi all,

based on roadmap published in ML [1] we are close to RC1. There are no
blockers registered [2], so it is seems that we can slowly start
preparing RC1. Any objections?

Ma

[1] https://lists.osgeo.org/pipermail/grass-dev/2017-February/084328.html
[2] https://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&priority=blocker&priority=critical&milestone=7.2.1&milestone=7.2.0&group=type&order=priority

Please (all) check
https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.1tobebackported

Markus

On Mon, Mar 27, 2017 at 7:51 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa <landa.martin@gmail.com> wrote:

Hi all,

based on roadmap published in ML [1] we are close to RC1. There are no
blockers registered [2], so it is seems that we can slowly start
preparing RC1. Any objections?

Ma

[1] https://lists.osgeo.org/pipermail/grass-dev/2017-February/084328.html
[2] https://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&priority=blocker&priority=critical&milestone=7.2.1&milestone=7.2.0&group=type&order=priority

Please (all) check
https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.1tobebackported

I have backported the fix to v.overlay (#3319) in r70803.

Markus M

Markus Neteler wrote

On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa &lt;

landa.martin@

&gt; wrote:

Hi all,

based on roadmap published in ML [1] we are close to RC1. There are no
blockers registered [2], so it is seems that we can slowly start
preparing RC1. Any objections?

Ma

[1] https://lists.osgeo.org/pipermail/grass-dev/2017-February/084328.html
[2]
https://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&priority=blocker&priority=critical&milestone=7.2.1&milestone=7.2.0&group=type&order=priority

Please (all) check
https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.1tobebackported

Addon candidate to be moved to trunk

Interesting:
​G7A:v.clip - very easy to use and expected GIS functionality without hassle
of complicated commmands :slight_smile:

tested v.clip quite a lot in the last weeks; very nice module with expected
GIS functionality

I'm in favour of moving it to trunk.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/release-GRASS-7-2-1RC1-tp5314467p5314493.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Mon, Mar 27, 2017 at 9:39 PM, Helmut Kudrnovsky <hellik@web.de> wrote:

Markus Neteler wrote

On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa &lt;

...

Please (all) check
https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.1tobebackported

Addon candidate to be moved to trunk

https://trac.osgeo.org/grass/wiki/Grass7Planning#Addoncandidatetobemovedtotrunk

Interesting:
G7A:v.clip - very easy to use and expected GIS functionality without hassle
of complicated commmands :slight_smile:

tested v.clip quite a lot in the last weeks; very nice module with expected
GIS functionality

I'm in favour of moving it to trunk.

+1

The other two trunk candidates are

- r.geomorphon
- v.profile - expected GIS functionality

Markus

Markus Neteler wrote

On Mon, Mar 27, 2017 at 9:39 PM, Helmut Kudrnovsky &lt;

hellik@

&gt; wrote:

Markus Neteler wrote

On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa &lt;

...

Please (all) check
https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.1tobebackported

Addon candidate to be moved to trunk

https://trac.osgeo.org/grass/wiki/Grass7Planning#Addoncandidatetobemovedtotrunk

Interesting:
G7A:v.clip - very easy to use and expected GIS functionality without
hassle
of complicated commmands :slight_smile:

tested v.clip quite a lot in the last weeks; very nice module with
expected
GIS functionality

I'm in favour of moving it to trunk.

+1

The other two trunk candidates are

- r.geomorphon
- v.profile - expected GIS functionality

used r.geomorphon several times here; a would-be nice addition to grass
trunk.

but AFAIR there were some discussion about some memory issues of
r.geomorphon ....

though

http://meetingorganizer.copernicus.org/EGU2015/EGU2015-6873.pdf

with an example of a large region use or r.geomorphon.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/release-GRASS-7-2-1RC1-tp5314467p5314528.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Hi,

2017-03-27 21:39 GMT+02:00 Helmut Kudrnovsky <hellik@web.de>:

G7A:v.clip - very easy to use and expected GIS functionality without hassle
of complicated commmands :slight_smile:

tested v.clip quite a lot in the last weeks; very nice module with expected
GIS functionality

please note that v.clip has one known issue, it breaks lines on
intersections, see attached screenshots. In this case input line
should not be broken I would say. Ma

(attachments)

clip_after.png
clip_before.png

On 27/03/17 21:53, Markus Neteler wrote:

On Mon, Mar 27, 2017 at 9:39 PM, Helmut Kudrnovsky <hellik@web.de> wrote:

Markus Neteler wrote

On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa &lt;

...

Please (all) check
https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.1tobebackported

Addon candidate to be moved to trunk

https://trac.osgeo.org/grass/wiki/Grass7Planning#Addoncandidatetobemovedtotrunk

Interesting:
G7A:v.clip - very easy to use and expected GIS functionality without hassle
of complicated commmands :slight_smile:

tested v.clip quite a lot in the last weeks; very nice module with expected
GIS functionality

I'm in favour of moving it to trunk.

+1

The other two trunk candidates are

- r.geomorphon
- v.profile - expected GIS functionality

Do all these modules have tests ? AFAIR we decided that moves to trunk can only happen for modules that have tests.

Moritz

Martin Landa wrote

Hi,

2017-03-27 21:39 GMT+02:00 Helmut Kudrnovsky &lt;

hellik@

&gt;:

G7A:v.clip - very easy to use and expected GIS functionality without
hassle
of complicated commmands :slight_smile:

tested v.clip quite a lot in the last weeks; very nice module with
expected
GIS functionality

please note that v.clip has one known issue, it breaks lines on
intersections, see attached screenshots. In this case input line
should not be broken I would say. Ma

clip_after.png (27K)
&lt;http://osgeo-org.1560.x6.nabble.com/attachment/5314552/0/clip_after.png&gt;
clip_before.png (30K)
&lt;http://osgeo-org.1560.x6.nabble.com/attachment/5314552/1/clip_before.png&gt;

that's what I would expect: breaking lines on intersections if the clip
vector has more polygons.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/release-GRASS-7-2-1RC1-tp5314467p5314637.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

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