Question: What's the best way to archive/store a timelapse video?

warren is asking a question about timelapse
Follow this topic

by warren | September 16, 2016 18:48 | #13454

As folks are looking at #timelapse photography as a means to document environmental problems like water contamination, I've heard people ask what's the best way to store these images (or often videos)

We'll be testing a hunting camera at LEAFFEST 2016 and will post our video to YouTube for starters. But are there chain of custody steps we should take?

I've seen people using #method82 -- a timelapse-based Smoke School derived EPA monitoring technique (#smoke-school) for monitoring smokestacks -- and uploading their videos to YouTube, but @gretchengehrke -- is that actually part of the method, or just, I'd guess, on the side?

Update: Mark Doerrier posted this video of smokestack monitoring, which is actually real-time, not timelapse, but I'm interested in the notes he's shared on data handling for Method 82, a form of EPA approved air quality photo monitoring which uses a digital camera:


What about, as @tonyc explored, we photo a GPS unit when we start it up? What if we use a "proof of existence" app like CameraV to video the start and end of the timelapse run, pointing it at the same GPS/clock as the timelapse camera is, so the authenticated CameraV video stands as a "chain of custody" confirmation -- kind of like how a XX is used to sync audio and video tracks in filmmaking?

Clapperboard, O2 film, September 2008.jpg
By Mattbr - Clapperboard on Flickr, CC BY 2.0,

Is this a question? Click here to post it to the Questions page.

Reply to this comment...

I also wanted to note that folks may be left with a photo series, not a video -- like with the #timelapse trail cameras folks. While we have a question open for converting that into a video, we also need a solution for just storing a big batch of photos.

I'm curious if MapMill can work for this? It may have some issues with uploading really huge batches of images, but perhaps we can try to resolve those bugs and see if this can work?

Also, just to acknowledge that storing large image sets is just a tough problem -- many big companies (flickr, etc) struggle to provide a great level of service for that sort of thing.

Is this a question? Click here to post it to the Questions page.

I would like to discuss some distributed data storage approaches to issues like this.

Reply to this comment...

Log in to comment