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
Currently area used for 3D-scanning/point cloud creation is limited by a bounding sphere defined in NED-coordinates/radius by hand when post-processing. Especially for bigger objects (like buildings) this is cumbersome.
For example, limiting area (or volume) could also be defined as:
3D convex hull around the object, tags (=timestamps) used to define points.
2D convex hull (in NE-plane) around the object, tags (=timestamps) used to the define points, height being either infinite or definable by user. This could be used with objects like buildings when user is unable to set 3D-points high enough.
It should be figured out how this could be improved and then implemented.
The text was updated successfully, but these errors were encountered:
Currently area used for 3D-scanning/point cloud creation is limited by a bounding sphere defined in NED-coordinates/radius by hand when post-processing. Especially for bigger objects (like buildings) this is cumbersome.
For example, limiting area (or volume) could also be defined as:
It should be figured out how this could be improved and then implemented.
The text was updated successfully, but these errors were encountered: