GeoCue Group’s repository of knowledge base articles and FAQs covering Terrasolid tools, tips and workflows.
A macro fails when launched through Geocue Dispatch. Checklist Step Details, System Messages error reads “No design files on the working segment”. Additionally, reviewing the Sub Tasks for the specified task on the Dispatch Manager reveals the machine timing out and returning to pending queue. If the macro is set up to run in TerraScan:…
Only when running TerraScan macros on a project in TerraScan or through GeoCue’s LIDAR 1 CuePac can an overedge region be specified. The macro loads points from neighbor tiles to: support the algorithms maintain continuity between data files, such as providing for a continuous surface at the block edge Should be done when doing routines…
The LAS specification requires that the File Source IDs and the Point Source IDs match (i.e. are the same number) when the LAS file contains data from a single flight line, drive pass, or strip of data. To ensure that this requirement is met, we can use a combination of TerraScan and GeoCue processes. Step…
At times while working with GeoCue Group Support it may become necessary to exchange large files or large numbers of files. We suggest the use of an FTP Client to make this easier. If you don’t have your own, or are not familiar with using an FTP client we suggest using the FileZilla project. FileZilla…
If you choose to load backdrop images while editing in TerraScan (while through GeoCue’s Process in TerraScan, DirectDrive, or directly in MicroStation’s Raster Manager) and your images show up in the wrong place relative to your LAS points, MicroStation’s Raster Manager may be interpreting your TFW (sister file) or coordinates incorrectly. Raster Manager defaults the…
With the release of TerraScan v017.001 for CE, TerraScan should now be preserving the projection VLR information in the LAS header. However, when processing with TerraScan, either directly or indirectly through GeoCue, there are some scenarios in which VLRs can be stripped from your data, or at least appear to be removed. Scenario 1: Reading…
An important evaluation to make when performing a QAQC analysis of a LIDAR data set is a control point comparison. Typically, this refers to checking the vertical accuracy of a LIDAR data set. In regards to vertical check/control point location: “Unlike horizontal checkpoints, vertical checkpoints are not necessarily required to be clearly defined or readily…
Service pack 5 for GeoCue 2014 enables some capabilities to process your LASA v1.4 files from start to finish using TerraScan for CE. We leverage GeoCue’s ability to launch a TerraScan project for an external application and a registry edit to direct GeoCue to use the TerraSlave for CE. To facilitate use the links below…
A quick and basic way to get information about projection information, GPS time and the number of points within an LAS file is to run the LDDump executable. The program is designed to pull the information directly from the public header block of the LAS file, provided the header has been correctly populated with the…
If you’re i/o bound, which is usually the case with LIDAR or photogrammetric point cloud processing, you need to figure out what kind of i/o you’re doing at the bottleneck. Case 1: If you’re just waiting for a single tile to load, your slowdown may be from low RPM HDD, but more likely you’re hitting…
