You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello I am Fadel.
I am currently trying to visualize a dataset of shape file multipatch into Cesium using 3D web client.
I exported the shp multipatch to CityGML using fme. It was successfull.
After that I exported the GML into KML/GLTF using BBox option and with the tiling option was clicked. It was succesfull.
However when I try to call the data in the web browser, It only shows a blue line of border (which was Bbox) with no 3d model loaded in the box. I have tried to zoom in but I still found no model.
Then I checked the Console in the browser, There are warnings telling that this kind of ID model with .GLTF format is not found.
I checked the root directory and trace the ID. I found that the file with such ID only in .DAE format.
I tried to search any file with GLTF format in the TILES directory. I found none.
Please help me to resolve this issue.
Thank you.
The text was updated successfully, but these errors were encountered:
Hello I am Fadel.
I am currently trying to visualize a dataset of shape file multipatch into Cesium using 3D web client.
I exported the shp multipatch to CityGML using fme. It was successfull.
After that I exported the GML into KML/GLTF using BBox option and with the tiling option was clicked. It was succesfull.
However when I try to call the data in the web browser, It only shows a blue line of border (which was Bbox) with no 3d model loaded in the box. I have tried to zoom in but I still found no model.
Then I checked the Console in the browser, There are warnings telling that this kind of ID model with .GLTF format is not found.
I checked the root directory and trace the ID. I found that the file with such ID only in .DAE format.
I tried to search any file with GLTF format in the TILES directory. I found none.
Please help me to resolve this issue.
Thank you.
The text was updated successfully, but these errors were encountered: