Closed jmkerloch closed 1 year ago
@runette is the maintainer of PLY format https://github.com/lutraconsulting/MDAL/blob/master/mdal/frmts/mdal_ply.cpp
UGRID should be a good candidate. I don't understand the "Read data" column. You can read data with a lot of the driver in red.
@vcloarec It seems that I have an issue with my github clone. My master branch won't update anymore.
I created this table with an outdated code of MDAL... I will update the issue as soon as possible.
Do you confirm that UGRID support temporal capabilities ?
@jmkerloch yes.
@vcloarec I just updated the table but I only changed UGRID, for other drivers I don't understand that they have read support from source code.
For exemple, GDAL related drivers only have Capability::ReadMesh
.
Is there something that I missed while reading MDAL source code ?
ReadData
for the capability means the driver can only read datan no mesh frame, that is there no information about the mesh in the file. These files are related to another mesh format. Generally, 2DM format that does not store data.
@vcloarec so If capability is Capability::ReadMesh
that means that it can also read data on mesh vertices or faces ?
I didn't get this, but how should I understand the capabilities for SELAFIN Driver:
Depending on the file use you don't have information about the mesh in file ?
SELAFIN is quite particular... If I remember well, you can read some data for a mesh coming from a file from another file.
The PLY format has not concept of time datasets. Each file is one dataset.
On Mon, 29 May 2023, 10:04 Peter Petrik, @.***> wrote:
@runette https://github.com/runette is the maintainer of PLY format https://github.com/lutraconsulting/MDAL/blob/master/mdal/frmts/mdal_ply.cpp
— Reply to this email directly, view it on GitHub https://github.com/lutraconsulting/MDAL/issues/461#issuecomment-1566726438, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARC2M4SOGKFHRPWCARRJ2LXIRKBXANCNFSM6AAAAAAYSODD4U . You are receiving this because you were mentioned.Message ID: @.***>
I have always thought that table and the contents are confusing and not necessarily correct.
On Mon, 29 May 2023, 16:23 jmkerloch, @.***> wrote:
@vcloarec https://github.com/vcloarec so If capability is Capability::ReadMesh that means that it can also read data on mesh vertices or faces ?
— Reply to this email directly, view it on GitHub https://github.com/lutraconsulting/MDAL/issues/461#issuecomment-1567206701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARC2M65WW67UYMPP3KGMILXISWO3ANCNFSM6AAAAAAYSODD4U . You are receiving this because you were mentioned.Message ID: @.***>
@vcloarec @PeterPetrik It seems that only some of the drivers have temporal capabilities because of the format implemented.
Is there any way to define which driver support temporal capabilities ?
I'm closing this issue since it's not related to .ply driver.
I created a new issue #463 about documentation with my understanding of reading capabilities for MDAL.
I'm looking for a file format to create a file that will be supported by QGIS for mesh display. I need to have a format that support:
I checked the source code of MDAL and I created this table for comparison of MDAL supported drivers:
I wanted to use driver with write support in MDAL so this limits the usable driver to:
I'm doing some tests with .ply file but I'm not able to display Time dataset with this driver.
Is it supported by MDAL ?