Martin Landa wrote
> Hi,
>
>> - build environment reverts back to the LASzip 2.2.0 version to use
>> libLAS
>
> yes, we can downgrade version in building environment, and also in
> packaging environment (for standalone installer). But osgeo4w will
> download latest version, and the modules will
Hi,
> - build environment reverts back to the LASzip 2.2.0 version to use libLAS
yes, we can downgrade version in building environment, and also in
packaging environment (for standalone installer). But osgeo4w will
download latest version, and the modules will be likely broken on
runtime. Why
>I think the latter course of action is better in the short term. Howard,
Would this affect other software?
the GRASS lidar tools in QGIS; maybe also other sw.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
On Thu, Dec 14, 2017 at 10:43 AM, Helmut Kudrnovsky wrote:
> Helmut Kudrnovsky wrote
> > deactivated now lidar modules in winGRASS 32bit and 64bit by:
> >
> > [GRASS-SVN] r71920 - grass/trunk/mswindows/osgeo4w svn_grass at
> > osgeo.org
> > [GRASS-SVN] r71921 -
Helmut Kudrnovsky wrote
> deactivated now lidar modules in winGRASS 32bit and 64bit by:
>
> [GRASS-SVN] r71920 - grass/trunk/mswindows/osgeo4w svn_grass at
> osgeo.org
> [GRASS-SVN] r71921 - grass/branches/releasebranch_7_4/mswindows/osgeo4w
> svn_grass at osgeo.org
> [GRASS-SVN] r71922 -
Helmut Kudrnovsky wrote
>>Not that I know how to fix that, but what needs to be done?
>
> have look into
>
> 32bit issues:
>
> https://trac.osgeo.org/osgeo4w/ticket/429
> https://trac.osgeo.org/osgeo4w/ticket/539
>
> 64bit issues:
>
> https://trac.osgeo.org/osgeo4w/ticket/550
>
> the liblas
>Not that I know how to fix that, but what needs to be done?
have look into
32bit issues:
https://trac.osgeo.org/osgeo4w/ticket/429
https://trac.osgeo.org/osgeo4w/ticket/539
64bit issues:
https://trac.osgeo.org/osgeo4w/ticket/550
the liblas [1] tools and laszip in OSGeo4W are broken.
what
Helmet,
I have folks using those programs to do binning analysis of LiDAR data on
Windows. Not that I know how to fix that, but what needs to be done?
Doug
On Sun, Dec 10, 2017 at 1:23 PM, Helmut Kudrnovsky wrote:
> Helmut Kudrnovsky wrote
> > looking at
> >
> >
Helmut Kudrnovsky wrote
> looking at
>
> https://wingrass.fsv.cvut.cz/grass75/x86_64/logs/log-r71915-25/error.log
>
> Started compilation: Sat Dec 9 21:35:30 2017
> --
> Errors in:
> /c/msys64/usr/src/grass_trunk/raster/r.in.lidar
> /c/msys64/usr/src/grass_trunk/raster3d/r3.in.lidar
>
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
looking at
https://wingrass.fsv.cvut.cz/grass75/x86_64/logs/log-r71915-25/error.log
Started compilation: Sat Dec 9 21:35:30 2017
--
Errors in:
/c/msys64/usr/src/grass_trunk/raster/r.in.lidar
/c/msys64/usr/src/grass_trunk/raster3d/r3.in.lidar
/c/msys64/usr/src/grass_trunk/vector/v.out.lidar
11 matches
Mail list logo