seamsh issueshttps://git.immc.ucl.ac.be/jlambrechts/seamsh/-/issues2024-03-25T11:25:59Zhttps://git.immc.ucl.ac.be/jlambrechts/seamsh/-/issues/31Refinement mixed-up when entities share a number on their name2024-03-25T11:25:59ZPablo HigueraRefinement mixed-up when entities share a number on their nameWe have observed that the refinement defined for points whose name includes a number is also applied to boundaries whose name includes that number. Our use case requires that boundary names are numbers, so the easy work-around is to avoi...We have observed that the refinement defined for points whose name includes a number is also applied to boundaries whose name includes that number. Our use case requires that boundary names are numbers, so the easy work-around is to avoid including any numbers in point names. However, it would be nice to find this bug and solve it to prevent unintended behaviour while creating a mesh.
Attached to this bug report is a document showing the main results and a zip containing a test case with all the files to reproduce it.
In addition, included in the zip file there is _meshing\___auxiliar.py_, which includes all the relevant functions (main one being _convertMSHtoMESH_) to convert GMSH meshes to the MIKE 21 mesh format. As discussed we would like to contribute these functions to the SEAMSH project to benefit the wider community.
[First_case_bug.docx](/uploads/c8507c42e41657799b7c2a5c4a9b1538/First_case_bug.docx)
[createSmallMesh.zip](/uploads/b3dc6272bec86be3bd86641fa48166d5/createSmallMesh.zip)
Best regards,
Pablo Higuerahttps://git.immc.ucl.ac.be/jlambrechts/seamsh/-/issues/28Clean the mesh from unused nodes2022-09-27T13:48:20ZChristophe CouletClean the mesh from unused nodesUsing polylines to define some island in my mesh, and depending on the mesh size criteria I sometimes have nodes in my msh file which are not part of the triangulation when the island are too small to be meshed.
Could we have a solution ...Using polylines to define some island in my mesh, and depending on the mesh size criteria I sometimes have nodes in my msh file which are not part of the triangulation when the island are too small to be meshed.
Could we have a solution to detect and clean the mesh?
Thankshttps://git.immc.ucl.ac.be/jlambrechts/seamsh/-/issues/27Management of longitude/latitude with GIS data2022-07-22T14:17:57ZChristophe CouletManagement of longitude/latitude with GIS dataNot fully sure this is a real incident or if this is related to the way I manage the spatial reference in my projects...
By the way, I usually define my projection with ImportFromEPSG.
I didn't had any problems when I build mesh with UTM...Not fully sure this is a real incident or if this is related to the way I manage the spatial reference in my projects...
By the way, I usually define my projection with ImportFromEPSG.
I didn't had any problems when I build mesh with UTM projection but I had to build a model in long/lat so I indicate ImportFromEPSG(4326) and then the problem occurred.
I tried to use GIS file preliminary converted in 4326, or just indicate an output_SRS in 4326 but the mesh was not at the right position.
There was always a switch between X and Y values...
I noticed there is a particular mention in field.py in the init of class Raster where there was a specific mention of _tools.osr.OAMS_TRADITIONAL_GIS_ORDER.
After adding domain_srs.SetAxisMappingStrategy(seamsh._tools.osr.OAMS_TRADITIONAL_GIS_ORDER) in my mesh script everything went well.
It's possible to add this each time but maybe this could be directly implemented in geometry.py
Regardshttps://git.immc.ucl.ac.be/jlambrechts/seamsh/-/issues/14find intersections in curves without un-refining2020-07-29T10:50:52ZJonathan Lambrechtsjonathan.lambrechts@uclouvain.befind intersections in curves without un-refiningpossibly using osgeo tools
maybe only for polylines, not for spline and bsplinespossibly using osgeo tools
maybe only for polylines, not for spline and bsplines