Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raster to mesh #52313

Open
saberraz opened this issue Mar 20, 2023 · 5 comments
Open

Raster to mesh #52313

saberraz opened this issue Mar 20, 2023 · 5 comments
Labels
Feature Request Mesh Related to general mesh layer handling (not specific data formats) Processing Relating to QGIS Processing framework or individual Processing algorithms Rasters Related to general raster layer handling (not specific data formats)

Comments

@saberraz
Copy link
Contributor

Feature description

It would be good to have a native QGIS tool under processing to convert Raster to Mesh. See details here:
https://lists.osgeo.org/pipermail/qgis-developer/2023-March/065630.html

Additional context

No response

@andreasneumann andreasneumann added Rasters Related to general raster layer handling (not specific data formats) Processing Relating to QGIS Processing framework or individual Processing algorithms Mesh Related to general mesh layer handling (not specific data formats) labels Mar 21, 2023
@kannes
Copy link
Contributor

kannes commented Mar 21, 2023

As pointed out by Jean-Baptiste Peter in https://lists.osgeo.org/pipermail/qgis-developer/2023-March/065636.html, different algorithms can create vastly different triangles.

It would be great to have both a "dump" algorithm that simply meshes the terrain in lots of squares of two triangles each (like e.g. Qgis2threejs does it) and a one that creates triangles as actually needed to represent the raster's surface in a more natural way, building an optimal topology with fewer triangles.

Additionally, being able to define breaklines would be a very nice feature.

@wonder-sk
Copy link
Member

It would be great to have both a "dump" algorithm that simply meshes the terrain in lots of squares of two triangles each

QGIS 3D internally does exactly that - from a DEM it creates squares of two triangles each, without any further optimizations.

The whole thing is maybe a bit more complicated - once we have a mesh, what are we going to do with it? If it is a large mesh from a big DEM raster, it is impractical to load it at once in a 3D view - it would take both a lot of GPU memory and the rendering would be slow. So in the end one would typically want to use some "level of detail" approach - using a tiling scheme like with XYZ tiles, to make it possible to show detailed mesh from close up and approximate mesh when looking from distance. But that also brings us to more complications 🙂 - e.g. how to make sure the mesh is always watertight (with no holes on edges), or how to store such tiled mesh data (e.g. 3D tiles?)

@nyalldawson
Copy link
Collaborator

Could https://github.com/OpenDroneMap/dem2mesh be of use here?

@kannes
Copy link
Contributor

kannes commented Mar 21, 2023

@Jean-Roc
Copy link
Member

I'm adding two others repositories of kyle baron

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Mesh Related to general mesh layer handling (not specific data formats) Processing Relating to QGIS Processing framework or individual Processing algorithms Rasters Related to general raster layer handling (not specific data formats)
Projects
None yet
Development

No branches or pull requests

6 participants