What is the fastest way to import topography?

MargotDupont2
MargotDupont2 Posts: 3 Calcite Rank Badge
edited May 29 in Leapfrog

Hi all, Is there a recommendation to have a faster topography import? Assuming a similar resolution, which input is faster to import?

  • Points
  • Surface (as mesh)
  • GIS Vector data
  • Elevation grid
  • Polylines

Usually the processing get stuck for a while on the "topography interp" step.

Is there one format or or the other that is faster with a graphic card?

Is there a benchmark on processing time?

Cheers!

Tagged:

Answers

  • AnthonyReed1
    AnthonyReed1 Posts: 1 Calcite Rank Badge

    I have found that points is the best way, but don't add them directly to topography.

    Topography is a bit different compared to other data sets, triangulation tends to be more spatially accurate than interpolation in most cases, and RBFs do not deal with high-density, regularly spaced data well.

    I nearly always triangulate from points and then provide an error margin (depending on useful project resolution). That way I can merge multiple datasets together into the best topography surface, for instance, DGPS drillhole collars, a local Lidar survey, surrounded by 30m SRTM data, often a final 'boundary' polyline. (I use QGIS to convert grids to points)

    I add the mesh to the topography object last. the only time I use interpolation in topography is if there are only sparse hole collars for topography, and even then I'm more likely to build that in the mesh area first.

Categories