GeoSLAM: Practice makes perfect?

Discuss all GeoSlam related products here
Post Reply
I have made <0 posts
I have made <0 posts
Posts: 1
Joined: Wed Aug 14, 2019 3:49 pm
Full Name: Andreas Broothaerts
Company Details: Ibs
Company Position Title: Junior
Country: Belgium
Linkedin Profile: No

GeoSLAM: Practice makes perfect?

Post by AndreasB »


I just wanted to discuss with all of you GeoSLAM users, what the best general practices are when you are operating the GeoSLAM devices.

I was watching the webinar from the academy a week ago, and it stated that for having the best pointcloud: practice makes perfect.

Well as all of you probably have some/a lot of practice with this devices, I just wanted to check what kind of practices greatly improved your results or what kind of practices should be avoided.
For example, when scanning a long straight trajectory, one should implement loops into the route. But how big do you make your loops? How many do you make? I know this is all really depending on the situation but just want to get some extra insights in the data collection.

Hope you guys want to share the knowledge!

Kind regards,


I have made <0 posts
I have made <0 posts
Posts: 1
Joined: Mon Mar 23, 2020 11:52 am
Full Name: Monika Zibolyte
Company Details: GeoSLAM
Company Position Title: Senior Solutions Architect
Country: United Kingdom
Linkedin Profile: Yes

Re: GeoSLAM: Practice makes perfect?

Post by monikazibolyte »

Hi Andreas,

Glad to hear you are using GeoSLAM Academy and GeoSLAM systems! I have been using GeoSLAM for about 3 years now and did lots of training on capturing data for best results.
Loops are important and one thing to mention is that the best loop to do is around an object and come back the other way. An "U" loop is all right, but an "O" loop, with a feature within a centre, is best practice.

When it comes to long corridors and tunnels, there are a couple of things to consider: first of all, how long your tunnel/corridor is and what scanner are you using? ZEB Horizon or ZEB REVO? As you might know, Horizon has 100 meters range and Revo - 30 m. If the tunnel is longer, you will have a better result with Horizon, because it will cover 100 m per each second of your scan, hence will see more features and geometry from the single shots. If you are using REVO or REVO RT, consider adding features such as chairs or boxes before the scanning and go around them. this will help to improve accuracy. as well, point the centre of the scanner to the features, as the centre front part has the most points. For both Horizon and REVO consider adding extra features if the tunnel/corridor is long. You can as well split scans to avoid having drift and then merge them in HUB software if tunnel is completely featureless.

Another general advice: if you can, avoid scanning highly reflective surfaces such as mirrors. If you cannot, then keep your back facing them. As the centre of the scanner has most points, try not to point the scanner to the mirrors/windows.
HERE is a pdf visualising the U and O loops and other general advice. I hope this helps. ... w?e=aI0hyh

User avatar
Jason Warren
Posts: 3477
Joined: Thu Aug 16, 2007 9:21 am
Full Name: Jason Warren
Company Details: Laser Scanning Forum Ltd
Company Position Title: Co-Founder
Country: UK
Skype Name: jason_warren
Linkedin Profile: No
Location: Retford, UK
Has thanked: 103 times
Been thanked: 47 times

Re: GeoSLAM: Practice makes perfect?

Post by Jason Warren »

Hi Monika,

The Sharepoint link ... w?e=aI0hyh appears to be down?
Jason Warren

Please add a LSF Google Review here ;)

Post Reply

Return to “GeoSLAM”