May 2012
1 post
Coming Changes to Nike+
Nike has informed me of changes they are planning to their systems, which will mean that eagerfeet will be down from June 5 to June 12. I will be traveling during that time, but I will try to monitor the site and only turn it off when I see lots of connections failing.
The good news is that going forward, it will be easier to get access to your runs. I will talk more about this once things are...
April 2012
2 posts
Anonymous asked: I used the Nike Sportband, which doesnt have GPS. When I import my run data from the Nike site, it pulls all the runs, but doesn't have a button to download a GPX file. Is that because there is no GPS data? Is there any way to create a file I can upload to Garmin Connect that has the Nike+ data, i.e., date, time, distance, etc., even though there is no GPS data? Thanks.
Download Issues Fixed
The problems with some runs not being found when you try to download are now fixed. This issue was quite tricky to track down, because it happened only occasionally, and it was the result of inconsistent data being returned by Nike’s servers: they initially claim that a run has GPS data, but then don’t return it when queried for it.
My code now retries automatically in this case,...
March 2012
1 post
Download Issues
I’m getting reports that some users can’t download their latest runs, even though the green “Download GPX File” button appears. I haven’t had much time to investigate, but it looks like a subtle change in the data I get from Nike. This should be easy to fix once I get to it, which will hopefully be this weekend. I’m traveling right now though, so my Internet...
January 2012
1 post
Alphanumeric User IDs Finally Working
I have finally implemented some changes to make it possible for people whose user IDs are not purely numerical to use the site. If your Nike URL contains something like 4ac5d135-7700-41c3-b54c-9478f412d051 (I made that up, that’s not an actual user ID), the site used to partially match one of the numbers and then complain that it can’t find the user. This now works.
There will be...
September 2011
3 posts
Precision Errors, fixed
I just fixed a problem that caused exported files to have low precision in the latitude and longitude values, due to the way they were stored in the database. This is now fixed.
If you have exported a run using the new version of the site (i.e., the one with the black bar across the top) before 1pm EDT on September 29, you should export that run again. The lower precision will lead to the totals...
New Look, Faster Site!
Welcome to EagerFeet 2.0! The site not only looks different, it’s also much better engineered and much faster. If it doesn’t look different, you might need to hit the Reload button in your browser.
The changes to the interface will hopefully make the site more pleasant to use, and make it easier to expand it further in the future. But the big change is in the backend: it now only...
About the recent problems
Over the last two weeks, there have been lots of issues with people’s runs not loading when they entered their data. I first suspected a bug, because I had made a few changes behind the scenes, but the explanation is unfortunately a problem with Nike: their servers are incredibly slow. That’s a problem because it’s not something I can easily fix on my end, and it causes timeouts...
May 2011
4 posts
Making the site more useful for power users
I have noticed that people seem to come back regularly to update runs they’ve logged with the Nike+ app but want to see in RunKeeper (or whatever other site they’re using). This was not my original idea about how the site would be used, I figured it would mostly be a one-off for people switching over completely.
In response to that, I’m trying to make the site more efficient to...
Aaaaand we're back!
This was a bit faster than expected: EagerFeet is live again! Go and try it out, especially if you’re a SportWatch user. Let me know if you run into any issues!
The reason for being coy earlier was that the Nike servers were throwing inexplicable errors. It turns out that they like to report errors when there’s some kind of timeout, so now the program will retry getting GPS data when...
Slight delay, but things are moving
This is taking a bit longer than expected, but that is more due to my lack of time on the weekend than Nike+. It took me some time to figure out how to get to the data, but fortunately they only put in a little roadblock, nothing major. My main fear was that I would need to do full-fledged authentication and require passwords, which I really do not want to do.
The good news is that I am now able...
EagerFeet currently down
The eagerfeet site is currently down, because Nike is apparently changing its API (i.e., the way applications talk to its servers). I am working on restoring the service, and hope to have that completed by the weekend (May 22).
Going forward, this blog will be the place for status updates and announcements about new features. I have quite a few things in the pipeline, but it will take some time...