New Analytics Tool For Your Ticklist!

Hey all,

I’m stoked to share a major overhaul of my completely free Climbing Analytics Web App! As a climber and solo developer, I built this tool to help us dig into our ticklists and get some fun, actionable insights. It’s been a passion project, and I’ve just rolled out some big improvements to make it faster, smarter, and more user-friendly.

Experience Base - Dive into your entire climbing history to explore metrics like locations, total vert, work capacity, and progression throughout your time climbing
Performance Climbing - Zoom in on top performances, and get a list of active projects!

Would love to hear feedback, and if you found it useful!
https://prototype-climbing-analytics-app.onrender.com/

"Failed to execute 'json' on 'Response': Unexpected end of JSON input"

Worked for me. Very cool tool and analytics. Thanks for making it and sharing. 

Sorry Adam, though impressive, the 4k+ ticks you have logged are a bit too much for the free tier of the server I'm running the app on.

I can run your ticklist locally though, would you like to see some of the visualizations?  (You've almost climbed the same total vertical feet as the altitude of the International Space Station!)

If people show interest in this I'd be happy to buy more compute so that even very large data sets can be processed online.

Very cool.  I like the clean, simple layout, and it is nice to see the various charts.  I am a geek for numbers and visualizations, and I haven't found a climbing tracker that I really like.

My number of pitches doesn't match MP, and the hardest grade sent seems off.  I also don't get the attempt numbers as I don't tick stuff I haven't sent.

Thanks for the feedback Mike!

Just for some context, the hardest grade calculation is the hardest tick you have that has a lead - redpoint, flash, onsight, or pinkpoint, or for boulders a 'send'. My guess is that you ticked as lead, but didn't specify if it was redpoint, flash, etc.

There is a section to edit top sends if you want to see accurate info visualized, feel free to update it there! Try updating your ticks for hardest sends then select 'refresh data' on your homepage, that should fix it.

As far as the pitch count, sometimes a 0 sneaks into the data on the mountain project side for pitches on a certain tick, I count that as 1 because there can't be a zero pitch tick, so the totals might be slightly off from what mountain project calculates.

"The string did not match the expected pattern."

Same error as Adam with alot less ticks :Failed to execute 'json' on 'Response': Unexpected end of JSON input

If your logbook has over 2000 ticks, Please check out the demo and consider buying me a coffee! 

I'll forgo the caffeine and instead buy some compute so that we can all view our ticklists

The largest successful ticklist so far was 1012 ticks and Shaun's is failing at 1096, so looks like that's about where the cutoff is for what the free web server can handle right now. All of these tick lists work well on my local machine where there aren't cutoffs for computation time, but the server I'm hosting on cuts off after a 20 second request and downloading, then analyzing 1000+ rows in a spreadsheet takes a bit longer than that.

Annie your data is crazy though, you've surpassed the altitude of the ISS with your lifetime vertical, amazing!

Shaun, you're about to hit the edge of the mesosphere.

Here's some screenshots of the Demo

Performance pyramid and active projects:

Location Tree, Can explore unique locations you've climbed at

Difficulty categories of pitches you climb - This categorizes every pitch in relation to your max send at the time and counts pitches in those categories over time

And many more! Check out the demo to explore and interact with these charts, and if your logbook has less than 1090 ticks, try it out yourself!

Made some optimizations, the server can now handle longer tick lists, Annie's is still failing at 3000 ticks so the limit is somewhere between 1100 and 3000.

My stats showed that I did Naugahyde in NH (a 'recent hard send') flash/onsight although i ticked it as a redpoint. It may be reading my comment which says "first go second session"

Hi tT,

Thanks for the feedback, you're right, the recent sends should take into account the recorded style, even if there is only 1 pitch recorded. I have updated the calculations to only give a number of attempts if the attempts were logged, otherwise defer to what the climber has recorded.

This is sweet! Nice job on this. Tried it out with my account and it worked great! Too bad I've done a bad job of ticking all my climbs haha.

This is pretty cool. Thanks