Re: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj

2019-11-17 Thread Rich Shepard
On Sun, 17 Nov 2019, Benjamin Trigona-Harany wrote: The change to libLAS will be fairly minor - not being built against GDAL. As far as I know, the only functional change is: "libLAS 1.6+ allows you to assign color information to a .las file if GDAL is linked in at compile-time." Ben, Here, l

Re: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj

2019-11-17 Thread Benjamin Trigona-Harany
On Sunday, 17 November 2019 09:35:20 PST Rich Shepard wrote: > On Sun, 17 Nov 2019, Benjamin Trigona-Harany wrote: > > Two scripts will have minor changes: > > gis/libLAS: loses GDAL support > > Ben, > > I read that libLAS has been deprecated and replaced by PDAL. Does that > affect anything? >

Re: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj

2019-11-17 Thread Rich Shepard
On Sun, 17 Nov 2019, Benjamin Trigona-Harany wrote: Two scripts will have minor changes: gis/libLAS: loses GDAL support Ben, I read that libLAS has been deprecated and replaced by PDAL. Does that affect anything? Regards, Rich ___ SlackBuilds-user

Re: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj

2019-11-17 Thread Benjamin Trigona-Harany
On Monday, 11 November 2019 14:31:58 PST Benjamin Trigona-Harany wrote: > There are a few regressions or scripts which will need to be removed (or > possibly patched from dev branches): > gis/OTB will lose Python support > gis/qlandkartegt no longer builds (but it's deprecated in favour of > qmapsh

Re: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj

2019-11-13 Thread Benjamin Trigona-Harany
On Wednesday, 13 November 2019 18:54:35 PST Willy Sudiarto Raharjo wrote: > > I actually started with David's branch but ended up redoing it from > > scratch since he was using an older proj (5.x) and GDAL (2.3), and the > > main changes occurred with those two version bumps. > > Oh if your branch

Re: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj

2019-11-13 Thread Willy Sudiarto Raharjo
> I actually started with David's branch but ended up redoing it from > scratch since he was using an older proj (5.x) and GDAL (2.3), and the > main changes occurred with those two version bumps. Oh if your branch has newer version, i will probably delete the older branch of David. What do you th

Re: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj

2019-11-13 Thread Benjamin Trigona-Harany
On 2019-11-13 4:19 p.m., Willy Sudiarto Raharjo wrote: On 11/12/19 5:31 AM, Benjamin Trigona-Harany wrote: Hi Ben David has been doing some work on GDAL in the past which is placed on a separate branch: gdal-review Can you have a look on it as well? See if it can be cherry-picked? I actually

Re: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj

2019-11-13 Thread Willy Sudiarto Raharjo
On 11/12/19 5:31 AM, Benjamin Trigona-Harany wrote: > In 2018, the main opensource geospatial libraries - GDAL, proj, libgeotiff, > libspatialite - started an effort to make core changes that could only be > done > simultaneously (https://gdalbarn.com/). Slowly the software that uses these > li

[Slackbuilds-users] Feedback on upgrading GDAL/geos/proj

2019-11-11 Thread Benjamin Trigona-Harany
In 2018, the main opensource geospatial libraries - GDAL, proj, libgeotiff, libspatialite - started an effort to make core changes that could only be done simultaneously (https://gdalbarn.com/). Slowly the software that uses these libraries has been adopting that new tool chain. Slackware, howev