Relax 2DM restrictions
The strict format requirements for BASEMENT input files are currently enforced for all meshes opened with or saved by BASEmesh.
This is not ideal for several reasons:
- It requires compatibility checks when loading external files into our data type, slowing down file parsing
- QGIS's mesh editing support introduces gaps and randomly ordered IDs for nodes and elements and is therefore currently incompatible with the BASEMesh workflow
- Any compatibility hacks and fixes performed will change the underlying ID ranges, which may be referenced elsewhere in the user's workflow
A more flexible approach would be to permit arbitrary IDs within BASEmesh, with a separate export_for_basement() method that validates and/or fixes meshes for use with BASEMENT while also exporting a log of all changes that were made to the mesh IDs for transparency.
On the plugin side, a pop-up could inform users that their mesh requires conversion for BASEMENT after the interpolation step, and linking them to the corresponding tool in the processing toolbox.