Dear devs,
few days ago 7.2.0 has been released, it's perfect time to clean up
our backport list on wiki [1]. I went through my issues and did
backports to relebr72. I would like to ask you for doing the same
(backport or to explain on wiki why not). Thanks! I wish you happy new
year 2017, Martin
[1] https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.1tobebackported
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
Hi,
there the current list of potential backports:
https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.1tobebackported
Currently open:
- lib/python/temporal: major differences to be checked TODO
- d.linegraph: a series of improvements, see
https://trac.osgeo.org/grass/log/grass/trunk/display/d.linegraph/main.c
- i.atcorr: Sentinel-2A r70161 (Test feedback in ML needed first)
- r.grow.distance: clean up after r68611: r69327
- r.in.lidar: Storage type
- r.in.xyz: unify keywords and method descriptions with r.in.lidar
(r68596): r68600
- v.in.lidar: check for valid LAS reader as in r.in.lidar r68982 + r70134
- vector modules: Added layer specific database information to v.info
extended metadata flag: r69535
- v.vol.rst: improve wording of warning (#3100): r69439
- v.what.strds: add capabilities to use names also for temporal
dataset with minutes and seconds granularity: r69331
Markus