# Getting sketchfab data into Slicer

**URL:** <https://discourse.slicer.org/t/getting-sketchfab-data-into-slicer/12256>\
**Category:** Feature requests\
**Created:** [June 28, 2020, 6:17pm UTC](https://discourse.slicer.org/t/getting-sketchfab-data-into-slicer/12256 "2020-06-28T18:17:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [June 28, 2020, 6:42pm UTC](https://discourse.slicer.org/t/getting-sketchfab-data-into-slicer/12256/2 "2020-06-28T18:42:03Z")

</div>

That should become available when we upgrade to the latest VTK. If it’s really in the critical path we could maybe add the classes directly to slicer (under a mangled name) as a workaround.

> [@Transferring models using glTF 2.0](https://discourse.slicer.org/t/transferring-models-using-gltf-2-0/7064):
>
> To follow up on an [email](http://massmail.spl.harvard.edu/public-archives/slicer-users/2017/011982.html) from @pieper from 2017 Transferring models is still a work in progress, but lately I’m looking at glTF [5] as an interesting option. I would like to mention that VTK has an improved support for glTF 2.0. It should be possible to create a Slicer extension leveraging the new [vtkGLTFReader](https://vtk.org/doc/nightly/html/classvtkGLTFImporter.html#details), [vtkGLTFImporter](https://vtk.org/doc/nightly/html/classvtkGLTFImporter.html#details) and [vtkGLTFExporter](https://vtk.org/doc/nightly/html/classvtkGLTFExporter.html#details) classes. You can read more details about the functionality here: [https://blog.kitware.com/introducing-gltf-2-0-support-in-vtk-and-paraview](https://blog.kitware.com/introducing-gltf-2-0-support-in-vtk-and-paraview)

---

_[View the full topic](https://discourse.slicer.org/t/getting-sketchfab-data-into-slicer/12256)._
