Have a look at the article on the metadata window. You can share metadata interoperably with QGIS in this window. To share your model, it is best to create a SVP file. You can do this via the file-menu. For advice, you are welcome to contact us via our homepage.
Create a geometry2D object. Paint one or a few isolines for the surface you want to create and in the corresponding extension. Set the height of the isolines with the line name. Then use the function create TIN from the context menu of the geometry2D object and you have a simple reference surface. You can then export this surface to other formats. You do this via the context menu of the TIN.
You can load a raster as a TIN. You can find instructions here. Then export the TINs created in this way into a raster with the desired resolution. The raster values are always linearly interpolated.
The layer outlines have nodal points. These nodal points are understood to be the outcrop, i.e. the edge of the outcrop of a layer, in the area if the outcrop does not extend beyond the area outcrop. If you see steep walls, then either in the profile sections you have not yet adapted the lower edges of the layer to a course of wedging out to an overlying layer, or your boundary polygon of the layer does not extend sufficiently beyond the area boundary. It also occurs when an older layer has a "shorter" polygon at the edge of the area than the younger one above it. So you should look at the guidance in these articles to learn about your options for improvement: construct profile sections and set layer spread.
If your elevation model is a raster, you can try a combination on calculator for raster and the filter. We have a case study where a combined use of these two tools was used for a classification. You can adapt this example to your needs: classification of raster and voxel data.
If your elevation model is a TIN, see the articles modelling with structure maps and geometry2D. You may be able to eliminate your artefacts with isoline modelling.
Look at the info box for the model Satkhira in this article. You will find short and concise instructions on how to do this most easily with SubsurfaceViewer.
Save the project with the assessed geofactors in a SVP file. If geofactors are loaded, this process opens a window with the list of geofactors. If you select the appropriate names here, the evaluations are locked for further editing when you open the SVP file.
Use the function convert to geofactor in the context menu of your polygon shape. You must have loaded geofactors with a target dimension beforehand. Follow the instructions in the linked article.
Use the conditions. On the left side you can reduce the reference depths. By setting a minimum thickness, you exclude the thin layers. With the conditions in the central lower control panel you can set further restrictions. If the conditions do not lead to the desired result, you can combine profile types that occupy only a few cells with similar ones. You do this manually. You should read the article on profile type maps.
Have a look at the article filter.
You can only add this for the 3D view. Read the chapter background image in this article.
Use the functions *send to front" and send to back in the right-click context menus of the objects. Read the corresponding article under objects/settings for more information.
Use the centre borehole in 2D-view function for the borehole object. If you have loaded boreholes via a LocViewObject, use focus location in 2D view.
Have a look at the article filter.
In addition to the visual check of the intersection points in the profile section, use the function check all sections in the tools-menu. If necessary, read the article construct profile sections.
Read these articles construct profile sections and set layer spread and pay particular attention to the black crossing points in the profile sections.
Create a table yourself from the inclined/deflected boreholes (preferably by script) with interval-like, offset XY coordinates and a depth interval in each case. These are accompanied by the layer attributes in the same row. Load these into the parameter manager. There you create the data tree. Now you can either use table extract to write out an irregular voxel (GVMD), or create a LocViewObject. Since we haven't had any experience with this ourselves, let us know if this way would be an acceptable compromise solution. If not, please feel free to contact us regarding our further developments in SubsurfaceViewer 9.