Hi,
it's one week GRASS 7.2.0RC2 has been released. It's time to think
about 7.2.0 final release. I don't see any blocker [1], if no
objection I would vote for going ahead and release 7.2.0 in the
beginning of the next week. Any comments?
Thanks, Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
On Dec 3, 2016 6:00 PM, “Martin Landa” <landa.martin@gmail.com> wrote:
Hi,
it’s one week GRASS 7.2.0RC2 has been released. It’s time to think
about 7.2.0 final release. I don’t see any blocker [1], if no
objection
… what about the NULL export in r.out.xyz? Currently it looks like an anomaly.
Markus
I would vote for going ahead and release 7.2.0 in the
beginning of the next week. Any comments?Thanks, Ma
–
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On 5 December 2016 at 08:10, Markus Neteler <neteler@osgeo.org> wrote:
On Dec 3, 2016 6:00 PM, "Martin Landa" <landa.martin@gmail.com> wrote:
Hi,
it's one week GRASS 7.2.0RC2 has been released. It's time to think
about 7.2.0 final release. I don't see any blocker [1], if no
objection... what about the NULL export in r.out.xyz? Currently it looks like an
anomaly.
Yes I also think this, but I'm not sure if it is better to change the
behavior of r.out.xyz or keep it like the actual one and change it in
the next main release.
For sure we should add parameter to permit to return also NULL values
before the 7.2 release
Markus
--
ciao
Luca
www.lucadelu.org
Hi,
2016-12-05 9:33 GMT+01:00 Luca Delucchi <lucadeluge@gmail.com>:
Yes I also think this, but I'm not sure if it is better to change the
behavior of r.out.xyz or keep it like the actual one and change it in
the next main release.
For sure we should add parameter to permit to return also NULL values
before the 7.2 release
I am not sure complicated it is and who will do it soon. We cannot
wait forever. There will be 7.2.1 quite soon (in three/four months).
Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
On Mon, Dec 5, 2016 at 1:49 PM, Martin Landa <landa.martin@gmail.com> wrote:
Hi,
2016-12-05 9:33 GMT+01:00 Luca Delucchi <lucadeluge@gmail.com>:
Yes I also think this, but I'm not sure if it is better to change the
behavior of r.out.xyz or keep it like the actual one and change it in
the next main release.
For sure we should add parameter to permit to return also NULL values
before the 7.2 releaseI am not sure complicated it is
It is just a change in a Python script:
grep r.stats scripts/r.out.xyz/r.out.xyz.py
# This is a simple wrapper script for "r.stats -1ng"
grass.run_command("r.stats", **parameters)
around the -n usage of the r.stats call in r.out.xyz.
and who will do it soon. We cannot
wait forever. There will be 7.2.1 quite soon (in three/four months).
If we change the behavior of the r.out.xyz script we need to postpone
that to 7.4.0 or correctly 8.0.0.
Markus
On Mon, Dec 5, 2016 at 1:49 PM, Martin Landa <landa.martin@gmail.com> wrote:
Hi,
2016-12-05 9:33 GMT+01:00 Luca Delucchi <lucadeluge@gmail.com>:
Yes I also think this, but I'm not sure if it is better to change the
behavior of r.out.xyz or keep it like the actual one and change it in
the next main release.
For sure we should add parameter to permit to return also NULL values
before the 7.2 releaseI am not sure complicated it is and who will do it soon.
Solved with a non-invasive new flag.
Now the current showstopper is MacOSX it seems...
Markus
On Dec 7, 2016 10:02 PM, “Markus Neteler” <neteler@osgeo.org> wrote:
Now the current showstopper is MacOSX it seems…
Is this really a GRASS issue?
Do we still wait?
Markus
Hi,
2016-12-10 16:51 GMT+01:00 Markus Neteler <neteler@osgeo.org>:
On Dec 7, 2016 10:02 PM, "Markus Neteler" <neteler@osgeo.org> wrote:
Now the current showstopper is MacOSX it seems...
Is this really a GRASS issue?
Do we still wait?
I don't think so. Putting to cpy Anna and Vaclav who knows more. Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
On Sat, Dec 10, 2016 at 10:57 AM, Martin Landa <landa.martin@gmail.com>
wrote:
2016-12-10 16:51 GMT+01:00 Markus Neteler <neteler@osgeo.org>:
> On Dec 7, 2016 10:02 PM, "Markus Neteler" <neteler@osgeo.org> wrote:
>> Now the current showstopper is MacOSX it seems...
>
> Is this really a GRASS issue?
> Do we still wait?I don't think so. Putting to cpy Anna and Vaclav who knows more. Ma
The issue is with Mac OS system Python. On Linux, I would say "ask your
maintainers," no idea what you do on Mac. The Python version needs to be
updated. There is no way around it except for a major code change in GRASS
which would workaround a bug in Python on Mac (Mac libs (newly?) behaving
differently then other unixes or something like that). The bug is already
fixed and fix is released, so Mac needs to update Python.
I would say, even at the download site, that there are no Mac binaries
until Mac Python maintainers update to latest Python 2.7.
Regarding the release there is also a major issue with v.in.lidar - Vasek is this still a problem in 7.2?
Helena
On Dec 10, 2016, at 11:18 AM, Vaclav Petras <wenzeslaus@gmail.com> wrote:
On Sat, Dec 10, 2016 at 10:57 AM, Martin Landa <landa.martin@gmail.com> wrote:
2016-12-10 16:51 GMT+01:00 Markus Neteler <neteler@osgeo.org>:
> On Dec 7, 2016 10:02 PM, "Markus Neteler" <neteler@osgeo.org> wrote:
>> Now the current showstopper is MacOSX it seems...
>
> Is this really a GRASS issue?
> Do we still wait?I don't think so. Putting to cpy Anna and Vaclav who knows more. Ma
The issue is with Mac OS system Python. On Linux, I would say "ask your maintainers," no idea what you do on Mac. The Python version needs to be updated. There is no way around it except for a major code change in GRASS which would workaround a bug in Python on Mac (Mac libs (newly?) behaving differently then other unixes or something like that). The bug is already fixed and fix is released, so Mac needs to update Python.
I would say, even at the download site, that there are no Mac binaries until Mac Python maintainers update to latest Python 2.7.
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Helena Mitasova
Professor at the Department of Marine,
Earth, and Atmospheric Sciences
and Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmitaso@ncsu.edu
http://geospatial.ncsu.edu/osgeorel/publications.html
"All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.”
Hi Helena,
2016-12-10 17:52 GMT+01:00 Helena Mitasova <hmitaso@ncsu.edu>:
Regarding the release there is also a major issue with v.in.lidar - Vasek is this still a problem in 7.2?
do you mean Windows issue reported on ML. If so, it's problem of
liblas package and WinGRASS packaging. Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
On Sat, Dec 10, 2016 at 1:04 PM, Martin Landa <landa.martin@gmail.com>
wrote:
2016-12-10 17:52 GMT+01:00 Helena Mitasova <hmitaso@ncsu.edu>:
> Regarding the release there is also a major issue with v.in.lidar -
Vasek is this still a problem in 7.2?do you mean Windows issue reported on ML. If so, it's problem of
liblas package and WinGRASS packaging. Ma
Yes, that's it. Do you know how/where to push it upstream/downstream, so
that the right people look at it? It seemed that it is fixed at one point,
but the same behavior is back now.
On Sat, Dec 10, 2016 at 8:00 PM, Vaclav Petras <wenzeslaus@gmail.com> wrote:
On Sat, Dec 10, 2016 at 1:04 PM, Martin Landa <landa.martin@gmail.com>
wrote:2016-12-10 17:52 GMT+01:00 Helena Mitasova <hmitaso@ncsu.edu>:
> Regarding the release there is also a major issue with v.in.lidar -
> Vasek is this still a problem in 7.2?do you mean Windows issue reported on ML. If so, it's problem of
liblas package and WinGRASS packaging. MaYes, that's it. Do you know how/where to push it upstream/downstream, so
that the right people look at it? It seemed that it is fixed at one point,
but the same behavior is back now.
Sorry to bother: this does not sound like a GRASS GIS 7.2 problem to
me but a winGRASS packaging issue?
Markus
Hi,
2016-12-11 20:39 GMT+01:00 Markus Neteler <neteler@osgeo.org>:
Sorry to bother: this does not sound like a GRASS GIS 7.2 problem to
me but a winGRASS packaging issue?
yes, it seems to be a WinGRASS packaging issue (I will have time to
look at it later in the end of week - Friday). From my POV, it's not
blocker for GRASS release. Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
On Sun, Dec 11, 2016 at 2:43 PM, Martin Landa <landa.martin@gmail.com>
wrote:
2016-12-11 20:39 GMT+01:00 Markus Neteler <neteler@osgeo.org>:
> Sorry to bother: this does not sound like a GRASS GIS 7.2 problem to
> me but a winGRASS packaging issue?yes, it seems to be a WinGRASS packaging issue (I will have time to
look at it later in the end of week - Friday). From my POV, it's not
blocker for GRASS release. Ma
I more or less agree, but what I don't know is if to package WinGRASS or
not if the lidar stuff is broken. For example, the current situation is
that from the current packages for the 7.0.x releases some support C++
modules and some lidar modules. However, I'm not sure if there is one 7.0.x
release which supports both. Of course, it is the packaging issue not the
release issue, but then should the package exist if it has a major issue?
Markus Neteler wrote
On Sat, Dec 10, 2016 at 8:00 PM, Vaclav Petras <
wenzeslaus@
> wrote:
On Sat, Dec 10, 2016 at 1:04 PM, Martin Landa <
landa.martin@
>
wrote:
2016-12-10 17:52 GMT+01:00 Helena Mitasova <
hmitaso@
>:
> Regarding the release there is also a major issue with v.in.lidar -
> Vasek is this still a problem in 7.2?do you mean Windows issue reported on ML. If so, it's problem of
liblas package and WinGRASS packaging. MaYes, that's it. Do you know how/where to push it upstream/downstream, so
that the right people look at it? It seemed that it is fixed at one
point,
but the same behavior is back now.Sorry to bother: this does not sound like a GRASS GIS 7.2 problem to
me but a winGRASS packaging issue?
yes it may be a winGRASS packaging isse.
OTOH just tested the example from v.in.lidar manual:
v.in.lidar -t -b input=D:\dl\Serpent Mound Model LAS Data.las
output=Serpent_Mound_Model_pts
Projection of input dataset and current location appear to match
Scanning 3265110 points...
7437968 points imported (limit was 1024)
211 input points were skipped by count-based decimation
The rest of points was ignored
another nice to have for winGRASS 7.2.0:
https://trac.osgeo.org/osgeo4w/ticket/413#comment:29
no blocker, just an OSGeo4W-packaging issue; if this is solved, the
R-winGRASS-coupling-functionality will be the same in standalone winGRASS
and OSGeo4W-winGRASS.
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/release-planning-7-2-0-tp5298469p5299575.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
Helmut Kudrnovsky wrote
another nice to have for winGRASS 7.2.0:
https://trac.osgeo.org/osgeo4w/ticket/413#comment:29
no blocker, just an OSGeo4W-packaging issue; if this is solved, the
R-winGRASS-coupling-functionality will be the same in standalone winGRASS
and OSGeo4W-winGRASS.
done for OSGeo4W-winGRASS by
enable same R-winGRASS-coupling-functionality as already available in
standalone winGRASS:
r70067 - trunk
r70068 - grass/branches/releasebranch_7_2
r70069 - grass/branches/releasebranch_7_0
testing welcome of one the upcoming winGRASS dailys.
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/release-planning-7-2-0-tp5298469p5299618.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
Hi,
2016-12-10 20:00 GMT+01:00 Vaclav Petras <wenzeslaus@gmail.com>:
Yes, that's it. Do you know how/where to push it upstream/downstream, so
that the right people look at it? It seemed that it is fixed at one point,
but the same behavior is back now.
I tested various winGRASS versions on my Windows machine and most of
them worked [1]. I lost track what version of GRASS is not working
you? Ma
[1] https://trac.osgeo.org/grass/ticket/2996#comment:17
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
On Sat, Dec 17, 2016 at 9:59 AM, Martin Landa <landa.martin@gmail.com> wrote:
Hi,
2016-12-10 20:00 GMT+01:00 Vaclav Petras <wenzeslaus@gmail.com>:
Yes, that's it. Do you know how/where to push it upstream/downstream, so
that the right people look at it? It seemed that it is fixed at one point,
but the same behavior is back now.I tested various winGRASS versions on my Windows machine and most of
them worked [1]. I lost track what version of GRASS is not working
you? Ma
No version was working for me. The weird thing is it worked for one
student (I tested it myself on his computer), but for many other
students it failed. So I tested different versions on freshly
installed Windows 10 in Virtual Box on linux and nothing worked. This
was couple weeks back, I can test again this week.
Anna
[1] https://trac.osgeo.org/grass/ticket/2996#comment:17
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Sun, Dec 18, 2016 at 9:39 PM, Anna Petrášová <kratochanna@gmail.com> wrote:
On Sat, Dec 17, 2016 at 9:59 AM, Martin Landa <landa.martin@gmail.com> wrote:
Hi,
2016-12-10 20:00 GMT+01:00 Vaclav Petras <wenzeslaus@gmail.com>:
Yes, that's it. Do you know how/where to push it upstream/downstream, so
that the right people look at it? It seemed that it is fixed at one point,
but the same behavior is back now.I tested various winGRASS versions on my Windows machine and most of
them worked [1]. I lost track what version of GRASS is not working
you? MaNo version was working for me. The weird thing is it worked for one
student (I tested it myself on his computer), but for many other
students it failed. So I tested different versions on freshly
installed Windows 10 in Virtual Box on linux and nothing worked. This
was couple weeks back, I can test again this week.
Shall I wait with the release or just get it out?
Markus
Anna