The latest whitepapers
Technotes provide more detailed discussions focused on specific technical topics as well as operational and business insights.
- #1044: Using Symbolic Links to centralize any directory / file to a network location
There are scenarios where you may wish to manage files or directories from a network location for deploying TopoDOT supplementary files to your technicians. This can be managed through a ...
- #1043: Minimum AWS Permission Policy for TopoShare
The TopoShare platform only requires a handful of functions to operate nominally on the S3 platform. By utilizing AWS Identity and Access Management (IAM), you can create a TopoShare AWS ...
- #1041: Migrating the V8i DOT Workspace into TopoDOT-CONNECT
Purpose TopoDOT 64bit and CONNECT are the preferred choice when it comes to overall productivity as well as utilizing the latest tools & features, however many DOTs have not moved over ...
- #1040: Copying TopoDOT & MicroStation user preferences to other machines
Purpose Setting up user preferences can be an arduous process on one machine (let alone dozens!), however once finalized for one we’d like to carry over all of these settings to ...
- #1039: Is the Requirement for Point Cloud Classification Dead?
Is the Requirement for Point Cloud Classification Dead? Mobile LiDAR system (MLS) point cloud delivery requirements often call for the initial “classification” of the point cloud data; typically identified as ...
- #1037: The Right Way to Evaluate Point-Cloud Processing Software
The Right Way to Evaluate Point-Cloud Processing Software The first step in organising any software evaluation is not to focus on the software simply as an application. Instead, software should be ...
- #1036: How to display V8i style TopoDOT tools in MicroStation CONNECT
Purpose The tools in TopoDOT 64bit (used in MicroStation CONNECT) are by default organized differently than TopoDOT 32bit (used in MicroStation V8i). TopoDOT 64bit tools are located in both the Taskbar ...
- #1035: TopoDOT Default Levels
By default, TopoDOT defines three global levels that are required for proper functionality. Temp Level – Level used by tools to place temporary point elements during QAQC process. For example, the ...
- #1034: Project Data Organization Requirements for Optimized Performance and Cloud Storage
Background Regardless of the platform – tripod laser scanning, mobile LiDAR, airborne LiDAR, or UAV image-based systems – the optimized organization and accessibility of project data contributes directly to its value. ...
- #1032: Riscan Pro E57 Export with the GeoSys Manager
Riscan Pro users accustomed to importing the point cloud data and imagery data into TopoDOT using the Project.RSP file will now need to export the project as an E57 format ...
- #1030: A Comparison of TopoDOT Compatible Bentley V8i/CONNECT Products
Use the tables below as a guideline to compare some product capabilities when choosing a Bentley product for TopoDOT use. The list only includes products that have been tested for ...
- #1025: Tool menus disappearing when loading TopoDOT
TopoDOT utilizes MicroStations DGNLib for generating toolbars and menus. These menus change dynamically according to the current state of TopoDOT. Ex: If TopoDOT is not loaded, the toolboxes will be ...
- #1024: How to Use FLS (FARO) Format in TopoDOT
The FLS file is FARO’s proprietary LiDAR scan data format that stores spatial (x,y,z),Intensity, RGB, Unit and scanner origin information. In order for a compatible 3rd partysoftware (TopoDOT) to read ...
- #1022: How to Use E57 Format in TopoDOT
Background The E57 file format is a standardized point cloud format that not only stores the 3D spatial information but other metadata such as calibrated images, laser source or scan positions, ...
- #1021: Establishing Requirements, Extracting Metrics, and Evaluating Quality of LiDAR Data
Abstract This document presents a concise, efficient and intuitive process for establishing LiDAR project data requirements, incorporating them into a request for proposal (RFP) and assessing the data against those requirements. ...
- #1019: TopoDOT to Caice Workflow
TopoDOT Settings The following settings must be set in the options for the Feature Code TopoDOT Export Use the Feature Code Export tool to export the desired element(s). When ‘Saving’ the exported file ...
- #1017: Structural Wall Monitoring
TopoDOT™ offers several tools designed specifically for structural monitoring, specifically vertical objects such as buildings or retaining walls. Recognizing that an effective wall monitoring program requires a field to finish ...
- #1009: TopoDOT “Open” Calibrated Image File Format
Background The TopoDOT® application offers the capability to import calibrated images and map the image pixel orientation to the perspective view of the selected MicroStationTM view. This unique tool makes it ...
- #1008: TopoDOT Proxy Information
The TopoDOT software will need to access the licensing system through the web in order to operate properly. Should the user be disconnected from the internet at any time, TopoDOT will ...
- #1006: TopoDOT for MicroStation Connect System Requirements
Updated August 29, 2023 TopoDOT® for MicroStation Connect is a 64-bit application that will perform well on moderately priced standard workstations or laptops meeting the following specifications: Minimum (that we’ve tested): Processor: Core ...
- #1005: TopoDOT for MicroStation V8i System Requirements
TopoDOT® for MicroStation V8i is a 32-bit application that will perform well on moderately priced standard workstations or laptops meeting the following specifications: Minimum: Processor: Core 2 Duo 2.26 GHz Memory: 4GB Video Memory: ...