Trimble Business Center

hello,

I - again - encountered an import problem in latest TBC version (known longer time and still present in TBC). I have a simple TXT file containing a set of 1000 points in the format EASTING,  NORTHING, ellipsoid (global) height. The horizontal coordinates are in UTM 33N based on WGS-84 ellipsoid (No transformation needed).

The input TXT file looks like this:

 So, I defined an import template as follows:

After import into my TBC project, when I select any point to have a look at its properties, TBC shows the following information:

As can be seen in red frame in the picture above, NO height information (global ellipsoid height) is present (although the import template contains it). This problem remains present in TBC already longer time and was NOT yet fixed.

Could anyone tell me a tip how to handle the problem (to get ellipsoid (global) height information for each imported point?  I already lost my hope that it will be fixed in next release, because since when I discovered the problem, there already were a few releases of TBC without fixing it.

Thanks in advance for any hint to solve the problem.

Martin Kalafut

P.S. When I specify in the import template ELEVATION (Mean Sea Level height) instead of Ellipsoid global height, the import runs problem free. But I cannot do it in such way, since I ONLY have global ellipsoid heights available and want to determine the elevations (Mean Sea Level heights) of all imported points using our precise (quasi)geoid model available in TBC GGF format. 

I currently only use 2025.10, and it doesn't work with that one either.

After the import I can see that TBC created 2 independent points for each line in the file. One has the coordinates and one has the elevation.

It seems that adding a column with arbitrary point numbers makes it work. In that case you get 1 point per line. Each point has two data entries, one with coordinates only and one with elevation only. The point itself has the combination of those 2.

This is very likely a bug in the importer. I don't see why a missing point name should cause this behavior. Internally everything should be serial number and not name based. But I've come across other instances where the programmers didn't adhere to this, i.e. causing problems when you rename surfaces and lines that are referenced in long and cross section sheets sets.

Works with or without Geoid, I first thought that would be the issue. Screenshots without Geoid.