The application uses the GPS and Compass sensors on your phone to extract and store the following data: latitude, longitude, compass direction, speed (kph), distance (kms), time (milliseconds), and finally an input field for optional points of interest.

The application is free and Open Source, with Processing (Android) and Openframeworks (iPhone) source code provided in hope that users can learn from and find interesting ways to visualise their data.

AntiMap Log mobile interface: record and stop screens

Data

Recorded data is saved to a CSV file at 30 FPS with filenames matching the date & time they were created. Eg: ‘150811_1230_08.csv’, was created on the 15th August 2011, at 12:30pm and 8 seconds. For Android users, files can be retrieved from the ‘AntiMap’ folder on the SD card. For iPhone users, files can be retrieved from your device in iTunes/Devices/Apps/AntiMap Log Documents (just under the ‘File Sharing’ heading).

Approximately 10 minutes of record time equates to 1mb of data on your device. To keep things tidy, I recommend deleting the files from your device once you’ve copied them to your computer.

Sample row of data from a CSV file: “-39.245163, 175.561, 320, 2.7769525, 218904, Ruapehu trail”. These 6 values shape the foundation for all current and future AntiMap desktop/online applications.

Sample CSV data

How to use?

Once you have the application installed on your device, there are a few things you need to know if you want accurate results generated for your data.

• Only use outdoors
• Data will not save unless GPS is detected, so wait until the “* Waiting for GPS signal… *” has disappeared before activating the “RECORD” button.
• Give your phone a good wave around in the air to ensure the compass configures itself properly.
• Depending on the activity your performing, the position of the phone once recording is crucial. If you require accurate orientation/axis values for snowboarding (spins/rotation) I recommend placing the phone upright against your lead hip/waist inside your pants. Just placing it in any of your pockets works fine for everything else except rotation as it moves around when loose. For skiing, maybe down the front of your pants.
• Be careful you don’t accidentally turn off the display while positioning the phone as the application does not ‘run in the background’.
• The application does not capture video, the application only logs the data. This is to keep the riding (or whatever) experience as unaffected as possible.

Version & download links: AntiMap Log 1.0

AntiMap Log is at version 1.0. Download the iPhone and Android applications below. If you want to see how these apps were built in Openframeworks (iPhone) & Processing (Android), source code can be downloaded from GitHub here.

Application and source code are released free under the MIT license (http://www.opensource.org/licenses/mit-license.php).

We’ve added a section to the GitHub page for upcoming AntiMap Log features. If you’d like to help with any of these issues, see here: https://github.com/trentbrooks/AntiMap/issues

AntiMap Video is a desktop application built in Openframeworks. It synchronises recorded data from the AntiMap Log mobile application with raw video footage (mov, avi, mp4, m4v). It was originally created as a snowboarding/skiing application to visualise real time rider data and stats similar to a video game. 

Requirements

You will need 2 things (chances are you take one or both of these to the mountain) to use the AntiMap Video desktop application:

1. A smart phone (Android/iPhone) with the AntiMap Log application installed.
2. A camera: could be your friends mobile phone, a digital camera or whatever you can get your hands on. I used a Go Pro and filmed myself (poorly), if you can get a friend to do the filming- even better.

Once you’ve got the mobile application installed and your camera ready to go, next step is to set them both to record and hit that perfect run. Be sure to check the ‘How To Use?’ section on the AntiMap Log page, for a guide on getting the most accurate results.

Post analysis

When your at home, plug in your camera and copy the raw video file somewhere on your computer. Do the same for the data file from your mobile: for Android users, mount your phone as a hard drive and navigate to the “sdcard/AntiMap” folder, for iPhone users, this file can be retrieved from your device in “iTunes/Apps/AntiMap Log Documents” (just under the ‘File Sharing’ heading). Copy across the CSV data file to the same folder as the video and run the AntiMap Video desktop application. Then simply drag and drop the video and data files onto the application, and the video should start playing with your rider data overlaid.

Adjust the timelines for the data and video so they are in sync- this is the most finicky part. Chances are you may have ‘recorded’ your data just before or just after you started recording video. The individual timelines (DATA playhead & VIDEO playhead) try to make this process a little easier, once they’re synced you can use the MAIN playhead to scrub through your video & data together.

Opening screen for AntiMap Video application

Application interface with video & data

Features

The standout feature of the AntiMap Video application is spin detection, which uses the compass data to accumulate a rotation value and attempt to determine when a 360, 540, 720, 900, 1080 has occurred and which direction (frontside/backside). The rider’s path and current position is generated from the recorded latitude and longitude into the small map in the top right. Speed, distance, and time stats also update on screen.

Location stats generate a map showing your path and position

Spin detection indicator (red is accumulated degrees)

Potential uses

• Real time snowboard/ski games. Original inspiration for this project came from playing Shaun White snowboarding on Nintendo Wii.
• Making personal snow/ski movies.
• Training/tutoring tool.
• Competitions. I’d love to see technology like this used in an accompanying role at televised events such as the Winter X Games. Giving spectators a bit more insight through data and stats would be invaluable.
• Whilst I specifically built this application for snow/ski, it could just as easily be adapted to suit other sports such as mountain biking, skateboarding, parkour, gymnastics, even running or walking.

Version & download links: AntiMap Video 0.1

AntiMap Video (version 0.1) is still an early prototype with plenty of kinks to work out before a 1.0 can be released. You can download the current working prototype application (OSX only) below. Source code, and a windows version is not yet available but is definitely on the TODO list.

Also on the TODO list for future versions:

• PC/Windows version.
• Add option to interface for riding switch.
• Use axis-y and axis-z data to detect corks/flips.
• Improve syncing between video & data timelines.
• Export video functionality.
• Point scoring system for game mechanic.
• Spin landing accuracy. A measurable result for landings after a spin. For example, a good 360 spin would accumulate close to exactly 360 degrees with a smooth ride out. Over rotation, under rotation, and too much correction/instability after a spin would equate to an average/poor spin.
• Up-dateable list for grabs?

Of course comments, suggestions, & improvements are encouraged.

Zip package below includes application and sample files to try (video & data). Note, I purposely set the included video sample to be 1.5 seconds ahead of the data. Once you drag and drop both files onto the application you can adjust the individual timelines or the ‘Video/Data time offset’ to equal -1.5 seconds. Then everything will be in sync. Press space to toggle menu on/off.

 
 

Updates:

AntiMap Video 0.2 now includes hi quality HD video exporting from the application. There is an issue when trying to use a h264 encoded mp4 video file and exporting, if this happens just convert your video to .mov or .avi before importing into the application.

The same data used in this demo, was used in the AntiMap Video snowboarding application. You can see from the visualisation, during heelside turns (left) the colours are a lot whiter/brighter than toeside turns (right). The sharper/more obvious colour changes indicate either sudden turns or spins (eg. the few black rings right in the centre).

Version & download links: 

Click the links below for demos and source code.

Zip package below (download source) includes HTML/Javascript & sample data (040811_1153_30.csv).