\
**Category:** General\
**Created:** [May 17, 2013, 6:17pm UTC](https://community.cesium.com/t/powder-tracks-demo-synchronized-html5-video-now-available/469 "2013-05-17T18:17:43Z")\
**Posts on this page:** 3\
**Page:** 1
**Author:**  [@Greg\_Beatty](https://community.cesium.com/u/Greg_Beatty)\
**Post date:** [May 17, 2013, 6:17pm UTC](https://community.cesium.com/t/powder-tracks-demo-synchronized-html5-video-now-available/469/1 "2013-05-17T18:17:43Z")
I’ve been working on a project to demonstrate the ability synchronize HTML5 video with GPS tracking data loaded via a CZML path. The demo has just gone live on the demos page: [Powder Tracks](http://cesium.agi.com/demos/powdertracks.html). Check it out if you’ve got a few minutes, and give me some feedback!
There’s also a [blog post](http://cesium.agi.com/2013/05/17/Synchronized-Video-with-GPS-Data/) that goes into some of the implementation details.
---
**Author:**  [@Syed\_Shadab](https://community.cesium.com/u/Syed_Shadab)\
**Post date:** [November 11, 2013, 9:56am UTC](https://community.cesium.com/t/powder-tracks-demo-synchronized-html5-video-now-available/469/2 "2013-11-11T09:56:10Z")
Hi,
Could you share some more implementation details? I am also trying to bring similar feature in our application but not getting any clear idea how to start with get ‘Powder Tracks’ type of option. I actually want to implement an virtual tour type of thing in which we can showcase the important area of interest of any particular region. Thanks in advance.
Regards,
S Shadab
---
**Author:**  [@Greg\_Beatty](https://community.cesium.com/u/Greg_Beatty)\
**Post date:** [November 12, 2013, 5:29pm UTC](https://community.cesium.com/t/powder-tracks-demo-synchronized-html5-video-now-available/469/3 "2013-11-12T17:29:05Z")
Most of the data in Powder Tracks is created via CZML content ([CZML Documentation](https://github.com/AnalyticalGraphicsInc/cesium/wiki/CZML-Guide)). This data includes all of the trail lines ([Polylines](https://github.com/AnalyticalGraphicsInc/cesium/wiki/CZML-Content#polyline)), the skier’s path ([Path](https://github.com/AnalyticalGraphicsInc/cesium/wiki/CZML-Content#path)), and the markers for videos ([Billboard](https://github.com/AnalyticalGraphicsInc/cesium/wiki/CZML-Content#billboard)). See [CZML files](https://github.com/gbeatty/cesium/tree/skitracks/Apps/SkiTracks/Gallery) for examples of the various czml files that are loaded into Powder Tracks, and [Loading CZML programatically](https://github.com/gbeatty/cesium/blob/skitracks/Apps/SkiTracks/SkiTracks.js#L476) to see how I loaded the CZML files into the application. The smooth camera transitions were created by determining the the position of the skier at a particular point in time and creating a camera flight from the current camera position to the desired end position ([Camera Flight](https://github.com/gbeatty/cesium/blob/skitracks/Apps/SkiTracks/SkiTracks.js#L126)). The synchronized video overlays are quite a bit more complicated. Cesium does not currently have video support built in. We are slowly working toward supporting html5 video materials in the [Video Branch](https://github.com/AnalyticalGraphicsInc/cesium/tree/video), but there is no firm date for video support in core Cesium. Powder Tracks was originally based on the Video branch but has a number of additions to allow me to define video textured quads through CZML. If you really need video support, you can examine the compare between Cesium Master and Powder Tracks [here](https://github.com/gbeatty/cesium/compare/skitracks). Nearly all the commits up through March 11 are to support video textures and synchronize the video with the animation clock.