Auto loading Terrasolid MDL applications in CONNECT

When working with Terrasolid products within MicroStation, it can be convenient for the Terrasolid applications to load automatically upon the opening of a MicroStation session.  This can be accomplished in CONNECT using the following steps: File-> Settings -> Configurations-> Configuration Variables-> Design Application From the ‘File’ drop down menu select ‘Settings’. In Settings, select ‘Configuration’. …

Share

Batch Export Raster Images using TerraScan

Export raster image command generates raster images where pixel values are derived from laser point attributes. The source data is points referenced by a TerraScan project. The raster image can be created as Windows bitmap (.BMP) or GeoTIFF (.TIF). The color of a pixel is determined using laser points whose coordinate values fall inside the…

Share

Basic Filter

The Basic Filter Point Cloud Task (PCT) allows you to define one or more point filters and assign the set of points matching the point filter to a classification. This PCT is useful for conducting simple reclassifications of point data in a LIDAR project. Reclassifying points from the old Model Keypoint class 8 to the…

Share

How to Launch an External App with a TScan project

This technical note explains how to launch an external application with a TerraScan project from GeoCue 2014 and later. In doing so one may provide a means to pass a TerraScan project to MicroStation Connect before the full support is implemented in GeoCue 2016. One may also use this command to pass a TerraScan project…

Share

Missing Images: XYZ from Camera Events (EXIF data)

Problem: Dropped images from Pixhawk drone flight and can’t georeference with dataflash logs. Probable Resolution: Create a new “Position File” that provides a row for each image filename, lat, lon, and elevation using our tool XYZsFromCAMEvents. Provide the “Image Folder” and the “Dataflash Log”. The default file is named “FlightLLAs.txt”. It DOES NOT create a “geotagged” folder, nor write…

Share

LP360 Digital Elevation Model Edge Mismatch

It may seem that there is an edge mismatch between Digital Elevation Model(s) (DEM) created with LP360 that is showing up when the grids are viewed in different software platforms. For instance, a user might see an offset between grids such as in the example below: After further research into the matter it turns out the issue is…

Share