# COLLADA

**URL:** <https://community.cesium.com/t/collada/37>\
**Category:** CesiumJS\
**Created:** [June 19, 2012, 8:32pm UTC](https://community.cesium.com/t/collada/37 "2012-06-19T20:32:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrick](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/patrick/32/2045_2.png) [@patrick](https://community.cesium.com/u/patrick)\
**Post date:** [June 19, 2012, 8:32pm UTC](https://community.cesium.com/t/collada/37/1 "2012-06-19T20:32:40Z")

</div>

Hi,

I started compiling ideas for supporting COLLADA in Cesium - [https://github.com/AnalyticalGraphicsInc/cesium/wiki/Models-Details](https://github.com/AnalyticalGraphicsInc/cesium/wiki/Models-Details). Also, see the discussion with the larger WebGL community - [https://groups.google.com/forum/?fromgroups#!topic/webgl-dev-list/fS84N2KTjwA](https://groups.google.com/forum/?fromgroups#!topic/webgl-dev-list/fS84N2KTjwA).

We’ll support COLLADA FX, COLLADA Animation, and interaction with CZML. We are thinking server-side convert COLLADA to JSON. Use the COLLADA Refinery and perhaps some custom conditioners to optimize the original model for rendering, e.g., generate shaders for common profile -\> triangulate -\> flatten hierarchy -\> reduce texture sizes -\> generate discrete LODs -\> vertex cache optimize. Finally, use [JSON.NET](http://JSON.NET), XSLTJSON, or our own code, to convert to JSON. When the client receives the JSON, it almost has no processing to do, and can just render it. The JSON is not a full COLLADA spec; for example, the server will convert polygons to triangles, and generate shaders to support the COLLADA Common Profile.

There are lots of open questions. Take a look at the wiki, [https://github.com/AnalyticalGraphicsInc/cesium/wiki/Imagery-Layers-Details](https://github.com/AnalyticalGraphicsInc/cesium/wiki/Imagery-Layers-Details), and let’s discuss.

Patrick