LasPublish.exe problem generating potree HTML
429 views
Skip to first unread message
p.kennedy
Mar 9, 2016, 1:56:27 AM3/9/16
to LAStools - efficient tools for LiDAR processing
Morning,
Trying to produce a dataset for web publishing...
The tools works great for small data LAZ sets, and I can see them in a browser (using nginx for web hosting) without trouble.
I then tried with a larger set of data. LasPublish runs through the data, completes and creates the published portal folder, HTMl file, libs etc just as it would for the small test. I then move it under nginx, and can open it in chrome, but only the potree framework appears, not data :-(
Using chrome debuger, there are no javascript exceptions in the debug console, so the error is subtle. Here is the feedback from ,the tool...
D:\Projects\Gp1500\MBES>laspublish -i GP1483_Recce_GA4421_25m_I3_Mean.laz -odir portal -title MH370Bathy -o portal.html -olaz
WARNING: no projection information. omitting 2D download map ...
== params ==
source[0]: GP1483_Recce_GA4421_25m_I3_Mean.laz
outdir: portal
spacing: 0
diagonal-fraction: 200
levels: -1
format:
scale: 0
pageName: portal
output-format: LAZ
projection:
AABB:
min: [447,800, 5.64045e+06, -6,979.25]
max: [2.11945e+06, 7.30138e+06, -623]
size: [1.67165e+06, 1.66093e+06, 6,356.25]
cubic AABB:
min: [447,800, 5.64045e+06, -6,979.25]
max: [2.11945e+06, 7.3121e+06, 1.66467e+06]
size: [1.67165e+06, 1.67165e+06, 1.67165e+06]
spacing calculated from diagonal: 14,476.9
READING: GP1483_Recce_GA4421_25m_I3_Mean.laz
INDEXING: 1,000,000 points processed; 1,000,000 points written; 2.203 seconds passed
INDEXING: 2,000,000 points processed; 2,000,000 points written; 3.661 seconds passed
INDEXING: 3,000,000 points processed; 3,000,000 points written; 5.193 seconds passed
INDEXING: 4,000,000 points processed; 4,000,000 points written; 6.683 seconds passed
INDEXING: 5,000,000 points processed; 5,000,000 points written; 8.237 seconds passed
INDEXING: 6,000,000 points processed; 6,000,000 points written; 9.89 seconds passed
INDEXING: 7,000,000 points processed; 7,000,000 points written; 11.486 seconds passed
INDEXING: 8,000,000 points processed; 8,000,000 points written; 13.03 seconds passed
INDEXING: 9,000,000 points processed; 9,000,000 points written; 14.805 seconds passed
...
FLUSHING: 5.907s
INDEXING: 291,000,000 points processed; 291,000,000 points written; 662.9 seconds passed
INDEXING: 292,000,000 points processed; 292,000,000 points written; 664.362 seconds passed
INDEXING: 293,000,000 points processed; 293,000,000 points written; 665.783 seconds passed
INDEXING: 294,000,000 points processed; 294,000,000 points written; 667.194 seconds passed
INDEXING: 295,000,000 points processed; 295,000,000 points written; 668.598 seconds passed
INDEXING: 296,000,000 points processed; 296,000,000 points written; 669.995 seconds passed
closing writer
conversion finished
296,989,906 points were processed and 296,989,906 points ( 100% ) were written to the output.
duration: 676.078s
D:\Projects\Gp1500\MBES>
when I open the resulting portal.html file, all I see is the potree interface, no data whatsoever.
any thoughts what I am doing wrong?
regards
Howard Butler
Mar 9, 2016, 2:07:21 PM3/9/16
to last...@googlegroups.com
> On Mar 9, 2016, at 12:44 AM, p.kennedy <p.ke...@fugro.com> wrote:
> min: [447,800, 5.64045e+06, -6,979.25]
> max: [2.11945e+06, 7.30138e+06, -623]
> size: [1.67165e+06, 1.66093e+06, 6,356.25
Patrick Lines
Mar 9, 2016, 2:11:19 PM3/9/16
to last...@googlegroups.com
Have you tried loading the sample data for potree that has already been converted? You may have an issue with IIS not handling unknown types. See this page for more info: http://www.serverintellect.com/support/iis/enable-no-extensions/
I've uploaded the point cloud to a web server but it is not visible.
Did it work on a local web server?
If yes and the error console shows the following error, then it is likely that your uploader altered the data/r* files:
Uncaught RangeError: byte length of Float32Array should be a multiple of 4
To solve this, tell your uploader to treat files as BINARY rather than ASCII. In Filezilla you can do this here: Edit -> Settings -> Transfers -> File Types -> Default Transfer Type
Another option is to pack all your data into a zip file, upload it and unpack it on the server.
Are you using IIS?
IIS may cause problems with files that have no extension, such as the data/r* files for potree format up to 1.3.
In this case, you can try to configure IIS: http://www.serverintellect.com/support/iis/enable-no-extensions/
--
Download LAStools at
http://lastools.org
http://rapidlasso.com
Be social with LAStools at
http://facebook.com/LAStools
http://twitter.com/LAStools
http://linkedin.com/groups/LAStools-4408378
Manage your settings at
http://groups.google.com/group/lastools/subscribe
 | Patrick Lines GIS Developer 1410 Indian Trail Lilburn Road, Norcross, GA 30093 P: (770) 564 9843 ext 238 |
p.kennedy
Mar 9, 2016, 11:15:06 PM3/9/16
to LAStools - efficient tools for LiDAR processing
Hi
I ran lasinfo on the single input file, and it reports this...
D:\Projects\Gp1500\MBES>lasinfo -i GP1483_Recce_GA4421_25m_I3_Mean.laz
lasinfo (160228) report for GP1483_Recce_GA4421_25m_I3_Mean.laz
reporting all LAS header entries:
file signature: 'LASF'
file source ID: 0
global_encoding: 0
project ID GUID data 1-4: 00000000-0000-0000-0000-000000000000
version major.minor: 1.2
system identifier: ''
generating software: 'SfxConvert 3.2.23'
file creation day/year: 19/2016
header size: 227
offset to point data: 227
number var. length records: 0
point data format: 0
point data record length: 20
number of point records: 296989906
number of points by return: 296989906 0 0 0 0
scale factor x y z: 25 25 0.25
offset x y z: 1200000 6400000 0
min x y z: 447800 5640450 -6979.25
max x y z: 2119450 7301375 -623
LASzip compression (version 2.2r0 c2 50000): POINT10 2
reporting minimum and maximum for all LAS point record entries ...
X -30088 36778
Y -30382 36055
Z -27917 -2492
intensity 0 0
return_number 1 1
number_of_returns 1 1
edge_of_flight_line 0 0
scan_direction_flag 0 0
classification 0 0
scan_angle_rank 0 0
user_data 0 0
point_source_ID 0 0
number of first returns: 296989906
number of intermediate returns: 0
number of last returns: 296989906
number of single returns: 296989906
overview over number of returns of given pulse: 296989906 0 0 0 0 0 0
histogram of classification of points:
296989906 never classified (0)
D:\Projects\Gp1500\MBES>
I do not think there is a problem with the extents of the las file. It is just a really big file.
I tried "lasinfo -r", but it says it is an invalid option.
regards
pk
p.kennedy
Mar 9, 2016, 11:18:45 PM3/9/16
to LAStools - efficient tools for LiDAR processing
Just for fun, I tried lasinfo -repair_bb, and got this result from lasinfo, which leads me to believe this is not a bounding box issue....
D:\Projects\Gp1500\MBES>lasinfo -i GP1483_Recce_GA4421_25m_I3_Mean.laz -repair_bb
bounding box is correct.
D:\Projects\Gp1500\MBES>
On Thursday, March 10, 2016 at 3:07:21 AM UTC+8, Howard Butler wrote:
Martin Isenburg
Mar 10, 2016, 12:08:51 AM3/10/16
to LAStools - efficient command line tools for LIDAR processing
Hello,
I assume it has to do with the unusual scale of
[...]
scale factor x y z: 25 25 0.25
[...]
and the fact that the default scale of Potree is 0.001 0.001 0.001. I should add the option to automatically set the Potree scale to the scale of the LAS header and that may fix it ... stay tuned as I am trying to solve this offline with 'p.kennedy'.
Martin
PS: Note that the latest Chrome update 49 for Windows is reported to break Potree's rendering engine.
--
Reply all
Reply to author
Forward
0 new messages