I’ve been using the CESIUM 3D Tiles transformer, and my experience has been somewhat tricky because of (I hope) the version that FME writes (1.0). I wonder if future versions of FME will support the 1.1 version to help resolve some issues I’ve encountered, such as the structure of the .json output or to be able to select the type of geometry compression, like Draco, Meshopt, or Quantization.
Page 1 / 1
Yes, we are also having some problems while transforming data into the 3DTiles format, because the writer format is outdated, it writes data in version 1.0 format, it does not support the current version 1.1 which was released 2 years ago. Please
You can take a look at the free command line based tool called 3d-tiles-tools: https://github.com/CesiumGS/3d-tiles-tools This tool has the option to Upgrade a 3DTiles dataset to 1.1.
My team has also had issues with transforming the data into 3DTiles format. We couldn't find the cause until we saw this post. If it's possible to do it from
FME is not very friendly in 3D support, it can't be better textured, and the model created by python itself can't be manipulated with the model created by FME, I hope FME can have more results in 3D
New→Open
New→Open
Hi Liz, it would be nice to know if
Also, this is especially relevant, since the standard was adopted by the Open Geospatial Consortium as a Community Standard on May 4th, 2023.
Currently the only working solution that we have is to export the 3DTiles in v.1.1 from Agisoft Metashape, and this prevents us from incorporating FME in the current workflow, in order to automate some processes.
We handle very complex 3D scenes and very large datasets, that is photogrammetry and point clouds obtained with drone flights that in conjunction cover the entire city, and this is only version of 3DTiles that is suitable for displaying those 3D scenes in web apps.
What started supporting 3dtiles 1.1 and Doubleside?