Q. Is there a import limit to the filesize in NaviModel?
We have received several datasets, the largest being about 10Gb.
When calculating the surface in NaviModel, the calculation speed slows down at around 25%
A. Typically when performance for terrain generation drops this dramatically, it is because the cell size is chosen too small.
Terrain generation is optimal when the density of the data points matches the cell size.
Try a larger cell size, and see if it performs better.
Apart from that, then the 10 GB file may need so much memory, that the terrain generation will need to swap more in and out of disk.
We may be able to improve on this, and read the file in smaller chunks.