[GRASS-dev] [release planning] 7.2.0

[Helmut Kudrnovsky]

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. 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.
> 
> 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.