Amazon

Wednesday, August 5, 2020

Batona FKT Announcement

For every ailment under the sun
There is a remedy, or there is none;
If there be one, try to find it;
If there be none, never mind it.
--W.W. Bartley--


Later this month, at a yet to be determined date, I plan to run the entire 53 mile length of the Batona trail in a single out and back effort in an attempt to set the self-supported Fastest Known Time (FKT) for the route. As I write this (2 August 2020) announcement, the only existing official out and back FKT for the Batona is the supported record held by Denis Streltsov set on 1 November 2015 with a time of 1 d, 3 h, 2 m, 36 s. So, as long as nothing goes terribly wrong and I finish the route, I will at least have earned the self-supported FKT. If everything goes well, I hope to finish faster than the existing supported FKT. 


If you weren’t aware of what FKTs were before pretty much all of racing was cancelled due to COVID-19, you probably are now. If not, you can learn all you want to know about FKTs at https://fastestknowntime.com/. Everything from existing routes, how to submit a new route, the three variations of support (supported, self-supported, and unsupported), and basically all other guidelines regarding FKTs can be found at the website. 


I’ve never attempted an FKT before. Why am I starting now? Probably for the same basic reason so many other ultrarunners have been submitting new FKT routes and trying to better the times of existing routes, we miss the thrill of racing. We miss being pushed by competition to achieve more than we thought we were capable of and racing the clock on a standardized route is one of the best replacements we have right now. I’m not trying to speak for all runners, but for me personally, these are some of the primary reasons. I had been interested in FKTs before, but the current situation and lack of organized races are what really motivated me to seriously start planning this thing and give it a go. That along with the fact that watching a lot of my trail running friends bettering or establishing new FKTs had me experiencing some serious FOMO.


The other factor that really pushed me to take a crack at this attempt is the uncertainty of the fall racing season. Since all of my spring and summer race plans were either deferred to next year or cancelled, planning for the fall, which should be fun, has become a painful extension of the last five months of disappointments. The first thing I checked for every race I was considering was whether it had already been cancelled. And if it hadn’t, I would pessimistically wonder to myself how long it would be until they do. The situation is upsetting, but it made me think about what I wrote near the beginning of the COVID pandemic:  “When so much of your world changes so drastically and suddenly, fear and panic are natural emotional responses. Focus on what is still under your control:  how you respond.” I realized I should take my own advice. I decided I would not plan on the uncertainty of races which are completely out of my control. I would set a goal that is still completely within my control as to when, where, how, and if I accomplish it. 


The next question to answer is why go for the Batona FKT. There’s a few pretty simple answers. It’s the nearest established FKT route to my home. I’ve had a history of running the Batona Trail. The first time I set foot on the trail was when I ran it in its entirety during a fat ass event. Since then, I’ve done some training runs on it and run it from the north end to south end one other time. So I’m familiar with the trail. And finally, I think it’s doable. I believe the existing supported out and back FKT is within my ability to improve. 


Which brings us to the final question to answer, what are my goals for this attempt? I’ve written before about how I like to have what I call cascading goals. That hasn’t changed for my first FKT attempt. My first goal is to finish the FKT attempt in the self-supported fashion. My next tiered goal is to finish it faster than the existing supported FKT time (27 h, 2 m, 36 s). And my top tiered goal is to do it in sub 24 h. Maybe I’m being a bit arrogant for my first FKT attempt to think I can run a self-supported, 106 mile route in under 24 hours, but I like having an upper tier goal that could very well be out of my reach altogether. Maybe I’m underestimating the additional challenges that a self-supported FKT attempt entails:  the loneliness of the overnight hours, the lack of competition and comradery found during races, the lack of route flagging, the lack of encouragement from aid station volunteers, etc. But the fact remains, I know this is a possible time and I think I have a chance of being able to pull it off if I have a good day. Otherwise, it would not be on my goal list. We’ll find out if I can do it or just how much I have overestimated my abilities later this month. 


Scott Snell

August 5, 2020


Sunday, June 14, 2020

Every Single Street Stalled Out...Attempting To Restart


Screenshot of StatsHunters generated heat map.

I’ve hit a few speed bumps that have delayed my progress with my run every street project. The first and worst of those speed bumps was an injury to my calf (you can read about it in this blog post) at the end of March. After what felt like a long recovery period, the injury seems to have healed and I decided to get back to making some progress on my run every street project of Egg Harbor Township, NJ just last weekend. While recovering, I avoided going more than a mile or two away from home just in case the injury flared up and I had to hobble home. So running farther away from home to continue this project was a bit of a big step in my recovery.

I decided to re-run a grouping of streets I had run once before, but for some reason the data didn’t sync to CityStrides (the mapping tool I’ve been using to track my progress). Introducing speed bump #2: tech tool issues. I didn’t mind rerunning a few streets due to a technology issue, but after the second time of running them and having them not sync I started looking into alternative tools.


Jonathanokeefe.com




This tool will create a heat map of your strava activities. You can specify activity types and the date range of activities you want a map of. It’s a really cool tool, but it lacks the really useful features for a run every street project that CityStriders offers: percentage of streets completed and node finder which can be used to pinpoint streets that have not been completed. There is a “new” option to download a KML file of the created map, but thus far I have gotten an error message everytime I tried to use that option.


StatsHunters

Another really cool tool that will create a heat map of your Strava activities and provides a plethora of statistics from all of your Strava data and loads of ways to filter your activites. The statistics are cool to look over and I like the heat map better than the jonathanokeeffe map, but this site has the same drawbacks in regard to missing the really useful features for a run every street project that CityStriders offers.

Street Ferret



This tool seems to be the best choice in my experience for a run every street project. It provides all the necessary tools to make the tracking of a run every street project effortless and make planning easier. It quickly synced all of my Strava data in a matter of minutes; CityStriders took nearly a month to complete the initial sync. I didn’t use Streetferret for as long as CityStriders, but for the week I did use it all of my runs synced quickly and consistently. This is in contrast to CityStriders which I have had syncing issues with. With CityStriders, usually it is just a 1-2 day delay, but there have been several periods when runs just don’t sync at all. Of all the tools covered here, Streetferret is the only one that is not free. It offers a free one week trial, but after that it charges a fee of $4 per month. 




With the injury and tech issues, my run every street project has not shown any progress since the end of March. It’s kind of a bummer for me, but I’m reevaluating and then will be back at it. At this point, I think my plan is to print out a large EHT road map and highlight all the roads I have run so far and update the map as I make progress. Yes, it is more labor intensive, but I also feel it is more dependable than software mapping options I have used so far. Once I am pretty confident that I am near 100% complete, I plan to pay for a month of Streetferret to get my percentage complete and determine where/which streets I still need to complete.

If there are any tools that I failed to mention here, I would love to hear about them and give them a test run. Thus far, Streetferret is by far the most useful dependable tool I’ve found for a run every street project, I’m just not willing to pay the monthly fee for the service while this is a long term project for me. Once I know that I’m within a month or two of finishing, I’ll be happy to drop that 4 bucks a month.