#2996: Lidar modules broken in 64bit WinGRASS
-------------------------------------------------+-------------------------
Reporter: wenzeslaus | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 7.0.4
Component: Packaging | Version: svn-
Keywords: lasinfo, r.in.lidar, v.in.lidar, | releasebranch70
r3.in.lidar, libLAS | CPU: x86-64
Platform: Unspecified |
-------------------------------------------------+-------------------------
`lasinfo`, `r.in.lidar` and `v.in.lidar` are broken in 64bit version of
7.0.4svn (r68280) and 7.1.svn (r68287). The modules are present, show GUI
and show help but will fail to work with any file (tried two, one is
[http://courses.ncsu.edu/mea582/common/media/01/0793_016.las.zip here]).
`lasinfo` fails as well. Possible commands:
I tried to install fresh OSGeo4W64 just with `liblas` cmd package.
`lasinfo` fails with the same error as described. So it's appearently bug
in `liblas` osgeo4w packaging. I suggest to report this issue in osgeo4w
trac and close this bugreport.
Replying to [comment:4 martinl]:
> well, it depends when it will be fixed. In my eyes it's not blocker
whole GRASS release.
Well, the question is what
> We can always build fixed Windows package with updated liblas.
We've already tried that for 7.0.3 by mistake. libLAS modules and C++ were
broken. It created a lot of questions. There was no way of downloading
installer of a stable version which does what the previous one did (libLAS
and C++ modules). Now, we would have to provide 7.0.3 alongside with 7.0.4
unless we don't want users to download 6.4. We would also have to tell
users before download that they should not download 7.0.4 if they want to
use these and these modules.
Replying to [comment:5 wenzeslaus]:
> Replying to [comment:4 martinl]:
> > well, it depends when it will be fixed. In my eyes it's not blocker
whole GRASS release.
>
> Well, the question is what
liblas package in osgeo4w. It's not our deal.
> > We can always build fixed Windows package with updated liblas.
>
> We've already tried that for 7.0.3 by mistake. libLAS modules and C++
were broken. It created a lot of questions. There was no way of
downloading installer of a stable version which does
C++ modules are now fixed, so? Another reason why to not wait with 7.0.4
release.
Tested 32 and 64bit 7.0.5, 7.2, standalone and OSGeo4W and las tools and
v/r.in.lidar are not working. Several people here reported the same, it
worked for one colleague for some reason. How did it get broken again?
Replying to [comment:12 annakrat]:
> Tested 32 and 64bit 7.0.5, 7.2, standalone and OSGeo4W and las tools and
v/r.in.lidar are not working. Several people here reported the same, it
worked for one colleague for some reason. How did it get broken again?
{{{
v.in.lidar -p input=D:\temp\lidartest\Serpent_Mound_Model_LAS_Data.las
Using LAS Library Version 'libLAS 1.8.0 with GeoTIFF 1.4.0 GDAL 1.11.3
LASzip 2.2.0'
LAS File Version: 1.0
System ID: ''
Generating Software: 'TerraScan'
File Creation Day/Year: 0/0
Point Data Format: 1
Number of Point Records: 3265110
Number of Points by Return: 0 0 0 0 0
Scale Factor X Y Z: 0.01 0.01 0.01
Offset X Y Z: -0 -0 -0
Min X Y Z: 289021 4.32094e+006 166.78
Max X Y Z: 290106 4.32364e+006 215.48
Spatial Reference:
+proj=utm +zone=17 +datum=WGS84 +units=m +no_defs
Data Fields:
'X'
'Y'
'Z'
'Intensity'
'Return Number'
'Number of Returns'
'Scan Direction'
'Flighline Edge'
'Classification'
'Scan Angle Rank'
'User Data'
'Point Source ID'
'GPS Time'
[...]
}}}
{{{
v.in.lidar -e -t -b
input=D:\temp\lidartest\Serpent_Mound_Model_LAS_Data.las
output=Serpent_Mound_Model_pts
Die Projektionsinformationen des Eingabedatensatzes und der aktuellen
Location scheinen übereinzustimmen.
Scanning 3265110 points...
16416272 points imported (limit was 1024)
219 input points were skipped by count-based decimation
The rest of points was ignored
}}}
I tested on 2 machines. First one is freshly installed Windows 10 and
r.in.lidar does not even start. Here it seems some of the needed dlls are
missing. When running r.in.lidar from terminal, it says msvcp120.dll and
msvcr120.dll are missing. So I found them in some obscure system directory
and copied them to extrabin and then everything works.
Then I tested an older computer. Here nothing works, but it behaves
differently. r.in.lidar starts, but then it says GRASS7 has stopped
working. Copying those dlls does not help. I tested different grass
versions, nothing works.
Replying to [comment:18 annakrat]:
> I tested on 2 machines. First one is freshly installed Windows 10 and
r.in.lidar does not even start. Here it seems some of the needed dlls are
missing. When running r.in.lidar from terminal, it says msvcp120.dll and
msvcr120.dll are missing. So I found them in some obscure system directory
and copied them to extrabin and then everything works.
standalone or osgeo4w installer. If standalone did you installed Microsoft
Runtime Libs? Ma
Replying to [comment:19 martinl]:
> Replying to [comment:18 annakrat]:
> > I tested on 2 machines. First one is freshly installed Windows 10 and
r.in.lidar does not even start. Here it seems some of the needed dlls are
missing. When running r.in.lidar from terminal, it says msvcp120.dll and
msvcr120.dll are missing. So I found them in some obscure system directory
and copied them to extrabin and then everything works.
>
> standalone or osgeo4w installer. If standalone did you installed
Microsoft Runtime Libs? Ma