Search Knowledge Base by Keyword
Getting Started
This article will cover how and when you should adjust your Scanner Range and/or Point Spacing settings when running Process Scans. While the default settings for scanner range and point spacing are usually fine, there are specific scenarios where you may want to deviate from the default settings. Keep in mind, the default values for scanner range and point spacing were decided on based on a fairly accurate scanner with low noise.
Scanner Range
For the first setting, Scanner Range, we would recommend adjusting this setting away from the default if:
a) You have a scanner that generates noisy data before the 40m default setting. In this case you would want to lower the scanner range setting to account for this.
b) You have a scanner that doesn’t generate noisy data until significantly after the 40m default setting. In this case you could raise the scanner range setting. Ensure you don’t go too far as to generate potential noisy data at a certain range limit. It is usually not recommend to adjust this setting above 40m.
c) You have a project where scanner locations are very far apart. In this case, despite the data becoming nosier at further distances, you may have to increase this setting in order to get enough coverage to extract items. Generally better coverage is preferred over reduced noise.
d) You have a project where scanner locations are very close. In this case, you will have a lot of higher-accuracy overlap of scanners at short distances, so you can lower this setting. Since you have plenty of coverage, the next goal would be to reduce noise, and you can achieve this by decreasing the range of included points on each scanner as long as you have good coverage.
Point Spacing
For the second setting, Point Spacing, we would recommend adjusting this setting away from the default if:
a) You have plenty of disk space and plenty of time to wait for the creation of the point cloud during process scans. The higher the value, the sparser the point cloud will be, the lower, the more dense. If you’d rather have a denser point cloud and don’t mind the additional time and disk space it takes, then you can lower this value.
b) You have an extremely accurate scanner, even at long ranges, and don’t have a lot of time to wait for process scans. This is a very rare occurrence, and we wouldn’t really recommend making your point cloud sparser than the default. This will make it harder for EdgeWise to perform automatic and even semi-automated extraction. However, if you do have a scanner that has insanely good accuracy (sub millimeter), even at 40m, then you can look into raising this setting a bit, but we would not recommend it.