Comming together -1st results

Notes about this test video:

• Filmed in Patterson Park Baltimore, May 7, 2010
• No audio in this version

The next version:

• Maps more opaque
• Add informational text overlay (stop for water, name of trail, trail highlights, bathroom)
• Parks & People just completed an audio tour- hope to use this or other audio tours in the future. 
• More shaking can be removed.

I am going to continue to test new methods to improve the results and lower the amount of time needed to create each one of these videos.
Ignite Baltimore 6 is 108 days away.  At this event I will be presenting the results of the quickexplore project.
The geeky technical details after the jump:

The raw footage shot of paterson park was 11 minutes shot in Cannon's AVCHD/MTS format and was around 1GB.    There are several deshaker / image stabilizer software packages on the market that range from a price of free to $1k+.   The version that I have found works best for this particular application is the free deshaker for virtualdub.   There are several things to note about this solution:
Results and usability for short videos is amazing.  See this sample
Virtualdub requires using uncompressed or very old style compression techniques.  This 11 minute video took over a hundred gigs of space and several hours of time and interaction to properly transcode.
This isn't a solution unless you have $2,500 in desktop computing hardware or a half that and 4 times the amount of free time.
What are the needs?

• 1-3 frames per second (frame math below)
• High shutter speeds to capture an image even with gitter
• I would like 1080p resolutions

Potential solution for the next test:

• Switch to a point and shoot camera
• Use a fixed focal length and high shutter speed (similar to scripts used in high altitude ariel balloon photography)
• Use a gorilla pod to hold a cannon point and shoot - Locked in with lots of zip ties

Doug Curtis's Steady cam that I used in the previous hardware rig has been sent back to him.  He needed it for a very cool 'ghost ride' raising awareness for bicyclists killed by motorists.  I am also not convinced his arm is the best solution for this project. Frame Math: 5 minute final video =  300 seconds or 9,000 frames

Previous source footage for 25 mile ride: 70 minutes, 4,200 seconds source or ~126,000 frames
This means I have WAY too much data
1 fps over 4,200 seconds would leave me short of the 9,000 frame goal.
I Would prefer to have 3fps but that requires a lot more batter, a much better camrea and more processing time.   Time for more testing.
File size calculations for new point and shoot method: Using canon SD870
Medium mode creates 278kB files
~2.5GB for 9,000 frames