Location: llandudno, Wales
ZEB Scanner: ZEB Horizon
This data demonstrates the ease of capture when transitioning from overground to underground, with the ZEB Horizon.
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Saudi Arabia
ZEB Scanner: ZEB Horizon
Scan time: 15 minutes
This data was processed in GeoSLAM Connect and the volume of the stockpile was calculated (15,000 tons) in GeoSLAM Volumes.
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Victoria, Australia
ZEB Scanner: ZEB Horizon
Scan time: 10 Minutes (via car)
This data was captured using the ZEB Horizon and car mount. The point cloud visually shows clash detection between the powerlines and the overhanging trees.
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Sydney, Australia
ZEB Scanner: ZEB Horizon
Scan time: 5 Minutes
This data was captured using the ZEB Horizon in just 5 minutes and consists of 7.7 million points.
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Washington, USA
ZEB Scanner: ZEB Vision
Scan time: 2 Minutes
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Norway
ZEB Scanner: ZEB Horizon
Scan time: 15 Minutes
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Bristol, UK
ZEB Scanner: ZEB Horizon and ZEB Vision
Total Scan time: 16 Minutes
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Belgium
ZEB Scanner: ZEB Horizon and ZEB Vision
Total Scan time: 20 Minutes
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Johor Bahru, Malaysia
ZEB Scanner: ZEB Horizon and ZEB Vision
Scan time: 5 Minutes
See the data flythrough video here.
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Austria
ZEB Scanner: ZEB Horizon
Scan time: 18 Minutes
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: Europe
ZEB Scanner: ZEB Horizon/ ZEB Discovery
Scan time: 15 Minutes
Colourised data was captured using the ZEB Discovery backpack solution.
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Location: United Kingdom
ZEB Scanner: ZEB Horizon
Scan time: 5 Minutes
Colourised data was captured using the ZEB Vision camera accessory.
Would you like to see a specific dataset that’s not on this page? Contact [email protected]
Known control points are captured during a scan and automatically compared and matched to the associated coordinates during the processing stage in Connect. A rigid and/or a non-rigid adjustment can be made to the dataset and an accuracy report is exported, highlighting how successful the transformation was. Users can now view and manipulate the processing parameters to ensure a more accurate match between points.
Align multiple scans using a combination of manual and automatic processes. This workflow can be performed on two or more scans in the same project. Users have a choice to export the aligned scans separately or as a single merged point cloud.
Common data capture scenarios, such as UAV, outdoor, indoor, linear, and vehicle, have been characterised in Connect and data processing pre-sets for each environment have been defined. These can be selected at the beginning of the data processing stage allowing this process to be highly simplified.
Both methods match the scan data from a ZEB Locate system with the GPS data collected from the antenna to georeference the point cloud. When a scan starts and ends in the same place, this is classed as “closed loop”. “Open loop” is when the start and end position of a scan are in different locations. Standard SLAM practices apply to both methods of data collection.
Open Loop SLAM for the ZEB Locate is available on request – let’s talk about it.
Common static points are captured during several scans meaning that these datasets can be automatically aligned. A single point cloud is then exported as if the data was captured in a single scan.
Horizontal and vertical slices can be taken from any location within the point cloud. Horizontal floor slices can also be automatically taken at a given height above the floor as defined in the processing stage.
Mostly used in the construction industry, multiple point clouds can be compared and any areas that have changed are automatically highlighted. Point clouds can also be compared with CAD models – for instance to track progress on a construction site – and PDF reports can be generated to present this information.
Some SLAM software algorithms have been made available as open-source on the internet, but they are purely algorithms and not a product that you can take and use off-the-shelf. SLAM is most successful when it is tightly coupled and designed with specific hardware in mind. A generic SLAM cannot perform as well as one that has been specifically designed for a purpose.
Visual SLAM is closer to the way humans navigate the world, which is why it’s popular with robotic navigation. But in the same vein, vSLAM will have the same image-capture challenges as humans do, for example not being able to look into direct sunlight, or not having enough contrast between the objects picked up in the image. These can be overcome indoors, however, you may need to map a forest, tunnel or urban canyon. While SLAM technologies don’t rely on remote data (meaning you can scan areas where there is no GPS), you do need to ensure the SLAM technology you chose operate well inside, outside, in daylight and darkness.
Mapping a property is time-critical. Ideally, you want to make a single visit and gather sufficient data to create a highly accurate 3D model. Ensure the software you choose transforms 3D point cloud data into actionable information in real-time. This allows you to view and interrogate your data whilst still in the field, and make any adjustments, or collect missed data, then and there.
If you’re trying to map an enclosed environment (e.g. tunnel, mine) or a complex, difficult-to-access space such as a heritage building with tight stairwells and uneven floors, you need to use fully-mobile, adaptable technology. Wheel-based systems, often used with the vSLAM camera, will struggle with access. Handheld devices or LiDAR scanners that can be attached to a drone or pole and still deliver accurate results in a rugged environment are best for navigating hazardous spaces.
While vSLAM is able to provide a qualitative high-level map and sense of the surrounding features, if you’re needing survey-quality accuracy and rich-feature tracking at a local level, you’ll need to consider LiDAR. Cameras require a high-frame-rate and high processing to reconcile data sources and a potential error in visual SLAM is reprojection error, which is the difference between the perceived location of each setpoint
and the actual setpoint.
In order to deliver the depth required for high-quality data, a number of depth-sensing cameras are needed with a strong field of view. In most cases, this isn’t possible, especially as cameras with high processing capabilities typically require larger batteries which weigh down airborne scanners, or limit the time of flight. LiDAR is both faster and more accurate than vSLAM, and can deliver detailed point clouds without expensive (and timely) camera processing.
