Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
An industry-standard binary file format that maintains information related to lidar data.
0
votes
Normalize height on a LAS catalog stops processing without an error message
I made a LAS catalogue from las files derived from Digital Aerial Photogrammetry. These tiles were originally 1.4 km^2, and the DEM was at a 1 metre pixel size. …
1
vote
1
answer
227
views
How to get las Zref values after normalization in lidR?
I understand that normalize_height() in lidR creates a Zref attribute so that it can be unnormalized. While I can print Z for the normalized file, I cannot print Zref. Subsequently, when I apply find_ …
1
vote
1
answer
282
views
How can I scale LiDAR intensity values to 8-bit, in order to apply the Wing2015 snag algorit...
I'm trying to identify snags using LiDAR stored in las format. The Wing 2015 algorithm used in segment_snags requires the values be in the range from 0 to 255. …
2
votes
1
answer
267
views
How do I correctly remove the buffer using catalog_apply?
I do not remove the buffer explicitly and the normalized las files, which are returned, include the hits from the buffer (i.e. my resulting las files now extend 20 metres beyond their original extent). … library(lidR)
ctg <- readLAScatalog("J:/2019/LAS")
normF = function(chunk)
{
las = readLAS(chunk)
if (is.empty(las)) return(NULL)
# skip las files that do not have ground hits
ground <- lasfilter …