Prototype on top of http://www.pushsnowboarding.com/

2. Contents
• The Push Snowboarding project
• ”Pistelogs” prototype targets
• The protype implemented
• Use cases
• Screenshots
• Future possibilities
• Conclusions

3. The Push Snowboarding project
• Burton + Nokia
• Highly interesting data and implementation
– A Qt C++ client running on the Nokia N8 –
collects data via Bluetooth (BT) from sensors
running on Arduino
• Ground breaking possibilities for further
improvement
• http://www.pushsnowboarding.com/

4. ”Pistelogs” prototype targets
1. Fix the local limitation
Enhance the current Push Snowboarding prototype
to send the shred logs* online
2. Improve the social part
Expose the shreds logged via an Internet
service, add capability to follow the riders in
realtime
Rationale
The Push Snowboarding project is currently limited to device
local – desktop interoperation only. There is no way to record
and interact with others given your shredrecording data set from a snowboarding ride
*) ”Shred log” is a sensor logs

5. Fixing the local limitation
Send the logs from the device to a web service
• Current implementation in device side:
– Snippets of roughly 4 seconds of riding = 100
log entries are send periodically to the server
– Source code for sending the logs:
• https://github.com/otso/Push-Snowboarding
• Really an ugly hack to prove the feasibility
• The BT functionality is commented out as the service
aspects were the target and compiling that part is ”delicate”

6. Improving the social part
• Augment the sent log packages with the rider’s
name
– Hard coded at the moment but the service does
differ between the riders (simulated with straight curl
POSTs)
• Add board, stance and music listened
– This is also hard coded atm in the service side...
• Individual runs, i.e. when the user starts the
client, are differentiated with a GUID
– First approach with straight time stamps was not
succesful due to network latencies and order of the
received packages

7. Improving the social part, contd.
Server side:
– Support multiple users
– Support data consolidation
E.g. average speed during an individual run
– Support location AND resorts
Harvested ~1000 ski resorts to produce meaningful places rather
than plain coordinates
– Support real time logging
– Live at http://pistelogs.appspot.com/
– Source code for the server (Python/Django/JQuery/)
https://github.com/otso/Pistelogs

8. Use Cases
USER DATA INDIVIDUAL USER RUN ANONYMOUS
Total runs Map – trail path/polyline is Current rides
missing ongoing
Total kilometers - length Duration TOP resorts*
Total time Length TOP boards*
Jumps cumulative Jumps TOP riders
Sticks used* Stick used*
Recent runs* Speed (max, avg)
Activity feed, i.e. events in Stance*
runs (not just logs, but
”1st time in Flachau” etc.)*
Music listened during run*
Resort – coordinates are nothing
without the resort information –
supporting ~1000 resorts atm
*) Not implemented

11. Future Possibilities
USER USER RUN ANONYMOUS MORE
Season stats Rotations (360° etc.) TOP music Expose API
• Total jumps
• Air time
User profile Elevation graphs Rides ongoing Clients – Android/iPhone
• Change picture, (just like in profile) • Music player incorporated
boards etc.
• Authentication
Activity feed Trick details – dig Follow the verified Data needs and more sensors
into shorter time riders (e.g. team
with more riders)
data/information
Friends list OTHER IDEAS:
• First time in resort – benefits for
the user/advertisements
• ”Tour Big 5” – ticket discounts
etc.
• BURTON – Ship the service + HW
• Helmet cameras…
• Resort usage analytics

12. Conclusions
• Pistelogs is a prototype to enhance the Push
Snowboarding client with a service
• The service concept solves the local limitation
and provides social aspects for the ride
logging
• Pistelogs provides a number of possibilities for
further improvements
http://otsov.wordpress.com/2011/12/17/push/