OmarShehata
commented
4 years ago We're migrating the issues in this repository to consolidate questions, Cesium ion feature requests, and bug reports on the Cesium community forum, that way there'll be one place to search for answers.
We're tracking this issue internally now. For any follow-up questions, please use the community forum!
Let's say you had an imagery dataset on Cesium ion. Imagery on ion is served as both WMTS and TMS. If you wanted to load that tileset in a client that supports WMTS/TMS, it would require that client to support Cesium ion's authentication flow, which is documented in the REST API doc, and an implementation in CesiumJS can be found in the IonResource class.
This involves getting an initial token, which produces a token that's valid for 1 hour, which is what actually allows you to access the tiles. So it's not as simple as just taking a URL from ion with a token embedded on it and being able to load that in other clients.
One thing we can do to make it easier to load ion datasets into other clients is to create a "simple" route, that would automatically handle this. This would make it easy not just to load ion imagery into clients like QGIS without any special plugins, but also enable you to embed ion hosted 3D models to be embedded into something like the model viewer web component.
If this is something you'd like to see, please :+1: this issue or comment below!