1. A concise explanation of the problem you’re experiencing.
2. A minimal code example. If you’ve found a bug, this helps us reproduce and repair it.
3. Context. Why do you need to do this? We might know a better way to accomplish your goal.
4. The Cesium version you’re using, your operating system and browser.
Here’s an example in Sandcastle.
1. A concise explanation of the problem you’re experiencing.
Thanks, that was helpful. The specific issue I am looking at is how to embed .glft s in a .kmz .and display it in Cesium.
We have some .kmz s with embedded .dae buildings.When I convert the .dae files to .glft all is well in Cesium as stand-alone s, but when I replace the .dae with the .glft in the .kmz Cesium hangs.
2. A minimal code example. If you’ve found a bug, this helps us reproduce and repair it.
3. Context. Why do you need to do this? We might know a better way to accomplish your goal.
We have an historical city that we now display in Google Earth Pro. There are some minor issues but the big advantage of Cesium is that we could display an historical context
and an informationsimultaneously. We had done this with the Google Earth Plugin.
4. The Cesium version you’re using, your operating system and browser.
I am using Windows 10 and Firefox.
1. A concise explanation of the problem you’re experiencing.
OOPS .gltf
2. A minimal code example. If you’ve found a bug, this helps us reproduce and repair it.
3. Context. Why do you need to do this? We might know a better way to accomplish your goal.
4. The Cesium version you’re using, your operating system and browser.
The KML specification only allows for COLLADA files as models. Does Google Earth Pro support yet another non-conforming use of the KML spec?
Scott
1. A concise explanation of the problem you’re experiencing.
Sorry about that, We have .kmz files that do display in Google Earth Pro. For example, http://vcities.ite-stl.org/Testing/Riverfront-Central-West.kmz . Move the timeslider marker down to see other buildings.
The hope was to move this to Cesium by migrating the .dae files to .gltf , taking advantage of Cesium’s flexability.
1. A concise explanation of the problem you’re experiencing.
I put together an outline of the problem:
http://vcities.ite-stl.org/CesiumNew/Apps/Testing.html is the sort of Cesium page I am trying to create. The building is a converted .dae to .gltf with an interesting history.
I would like to embed the building in a .kmz , showing its historic context. This works with Google Earth Pro with .dae s
**http://comp.umsl.edu/vcities/CesiumNew/Apps/Sandcastle/gallery/CesiumDemo1.html ** is where I am. I slightly modified a page you directed me to. If you load the page and set the time to say 1859 you see two blocks and a little icon on the lower one. Clicking the icon shows an information window. This is as it does in Google Earth Pro. What does not appear is the .gltf from the first link on the on the lower block as it does in Google Earth Pro
