I thought it would be nice to add a Nike+ widget to this blog, so I did a bit of searching. It didn’t take long to find the cool Nike+ WordPress Plugin by Mark Rickert. However, upon installing and configuring it, I found it failed during the curl authentication calls with:
Can not retrieve data from Nike.com.
Error: there is no user information in the request
No worries, my Nike+ data is publicly accessible, so this type of authentication is really unnecessary and only slows the retrieval time. So I edited the plugin code (nikePlus.php) to change from using up-front authentication to passing my ID on each call.
While I was in there, I also did a bit of customization and cleanup: removed unimportant details, tweaked heading levels, trimmed some things to improve performance, etc. But I deliberately kept it simple. That’s the beauty of these plug-ins: they’re easy to customize and tune. Scroll down to the “Nike+ Stats” and “Recent Runs” in the right-hand column and you’ll see it.
Hats off to Mark for a handy plugin which not only was a nice add to this site, but sparked my interest in possible further Nike+ coding.
There are plenty of good GPS running tools for the Android; my favorites are SportyPal and the new Google MyTracks. Both measure pace, distance, and route, and display results on Google Maps. With them, I get the benefits of a GPS running watch, but with more features and no extra cost.
But I’ve had mixed results with GPS tracking. Sometimes I can’t get reliable signals, even in open areas with no overhead obstructions (MyTracks can revert to determining location by cell and Wifi signals, but that’s a very weak approximation). Sometimes inaccurate map data and other things can throw distance off; that’s most noticeable when I run places where I know the exact distance of the course. And sometimes, the truly weird happens, like the run shown at right. The red (for “fastest”) lines depict how I left the course for a half mile sprint through fences, houses, and rough terrain at 27.3 miles per hour (then quicky returning to the track, of course). MyTracks reported a recent 5 mile street run as 785.16 miles in just over 39 minutes (I was ready to give up at the 784 mile mark). And tight loops on small tracks are almost never right with GPS tracking. Obviously, such failures get in the way in trying to maintain a good read on my pace.
So I decided to go with the Nike+ Sportband. Its accelerometer technology is not dependent on GPS signals for measurement: it’s nice and simple. That’s helpful because I don’t always like to carry my phone with me, nor fiddle with it while running. But I do miss the automatic mapping, especially when exploring new areas. So when running new routes, I carry both: Nike+ for accurate pace tracking, and my GPS Droid for route tracking. Call it Nike++.
Once the new wears off, I’ll probably settle into a “just one at a time” mode: Nike+ for running and Droid GPS for walking, hiking, and kayaking. But, for now, it’s belt and suspenders, and that allows for some often interesting comparisons.