You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The summary looks only at pre-computed number of first return while retrieve_pulse used the gpstime attribute in order to compute the exact pulse ID of each point. This way if you have a 2nd or 3rd return only without the first one (e.g. on the edge of the dataset) you still get a pulse.
The difference should be minimal in most cases but here you chose an extraordinary tiny dataset (30 points) where a single point difference can change a lot the final value.
Yes, difference is minimal, noticed some decimal differences on my real dataset.
Small dataset here only as reprex.
Maybe it can be clarified in your documentation for summary function ?
Is it expected that the calculation of the pulse, point density / m**2 does not align with the manual calculation?
summary(las) provides pulse density as 2.63 pulses/m2 whereas manual calculation gives 2.83?
The text was updated successfully, but these errors were encountered: