It could be that the stringdef lines do not match the mesh boundary. Sometimes redrawing the stringdefs and setting the line vertices on the vertices of the boundary with snapping helps. Otherwise I am not sure what reason could be.

Best regards,
Matthias

I am struggling to understand Segment objects in basemesh. Are these equivalent to breaklines in the GUI? If I have a list of tuples of xyz coordinates across my model domain, including the xyz vertices of the breaklines as they would appear in QGIS, does each breakline become a Segment object using basemesh.triangle.Segment? If yes, then I have gotten basemesh.elevation_mesh(nodes, segments, keep_convex_hull = True) to create the elevation mesh object I need to now interpolate. Can I visualize the .node, .ele., or .poly files to check my work? If no, how do breaklines and Segment objects relate to each other and how do I generate the elevation mesh with a set of xyz points and breaklines?

Once I have created the elevation mesh object, and move to interpolating the mesh (I assume this is equivalent to generating the quality mesh and the computational mesh in one step rather than two like the GUI), I am getting an error on the very first line mesh = basemesh.Mesh.open(Elevation_Mesh) where Elevation_Mesh is the Mesh object created by basemesh.elevation_mesh. I get the message "TypeError: expected str, bytes or os.PathLike object, not Mesh"

If anyone has some example code they could point me towards, or has a few minutes to help me find additional documentation to learn this more methodically, I would really appreciate the assistance!

PS: there's also something wrong with the info (see this video)

EDIT: it might be due to very complex breaklines, with several vertices. A request: it might be useful to give more info regarding the duplicated vertices that are merged and so on. I would like to know where those are, for example.

Hole markers in Triangle work by first triangulating the entire mesh and subsequently deleting any elements that were within the region that was flagged as a hole. There are circumstances in which this leaves a node in the middle of the carved-out region:

- Adjacent hole regions may leave nodes behind that were part of the boundary between the two holes
- Manually-placed input points (such as elevation grids) may fall within a hole region

In BASEmesh v2.0, these disjoint nodes can cause gaps in the node ID sequence. Upcoming versions will address this issue, for BASEmesh v2.0.11 a workaround may be to set the "j" (jettison) flag in the "Extra arguments" field of the quality meshing tool. This causes Triangle to delete any disjoint nodes along with the last element they were attached to, which avoids this issue.

Best,
Leonhard

FormatError: Zero index encountered in non-zero-indexed file, C:/Users/joaop/Drive IST/PhD/MAPUTO/SIG/MESH/Modelacao_MAPUTO_quality-mesh.2dm, 3

Traceback (most recent call last):
  File "C:\Users/joaop/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\basemesh\plugin\gui\worker.py", line 90, in run
    value = self.target(self.feedback, *self.args, **self.kwargs)
  File "C:\Users/joaop/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\basemesh\plugin\gui\interpol.py", line 216, in worker
    interpol_mesh = Mesh.open(target_layer.source())
  File "C:\Users/joaop/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\basemesh\core\mesh.py", line 310, in open
    with py2dm.Reader(filename) as reader:
  File "C:\Users\joaop\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\basemesh\packages\py2dm-0.2.1-py3-none-any.whl\py2dm\_read.py", line 72, in __enter__
    self.open()
  File "C:\Users\joaop\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\basemesh\packages\py2dm-0.2.1-py3-none-any.whl\py2dm\_read.py", line 432, in open
    super().open()
  File "C:\Users\joaop\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\basemesh\packages\py2dm-0.2.1-py3-none-any.whl\py2dm\_read.py", line 279, in open
    *scan_metadata(file_, self._filepath, self._zero_index))
  File "C:\Users\joaop\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\basemesh\packages\py2dm-0.2.1-py3-none-any.whl\py2dm\_parser\_pyparser.py", line 183, in scan_metadata
    raise FormatError(
py2dm.errors.FormatError: ('Zero index encountered in non-zero-indexed file', 'C:/Users/joaop/Drive IST/PhD/MAPUTO/SIG/MESH/Modelacao_MAPUTO_quality-mesh.2dm', 3)

Any help on this?!
Thanks

you can create some raster to generate some DTM patches. Then, when you are interpolating the mesh, select the "advanced" tab instead of the "basic". There you can select any raster you want to interpolate the quality mesh. The order of the rasters (up-->bottom) gives the order of the interpolation (the highest raster in the list will be used as first raster to interpolate, the second as second and so on).

Cheers,
Matteo

thanks for your answer.
I found the problem already, it was the coordiante system (KBS) that wasn't metric...

Best,
Jonathan

Makes total sense. Thank you!

Best regards,
Cris

When trying to add noncohesive dams (moraine dams) when generating mesh, is it best practice to assign a hole to the region where the dam might be? If not what breakline assignation might be most appropriate for this type of structure?

Cheers,
Cris

thanks for pointing out. In fact, we tested the plugin for QGIS version 3.10

Cheers from Zürich!