The Rock Climbing Journal: Document Your Rock Climbs and Climb Harder

The Rock Climbing Journal is a must-have regardless of whether you're into sport climbing, trad climbing, bouldering, or even indoor climbing. It's the best way to record and remember your climbs. There are huge benefits to keeping track of the routes you climb. First, it's just fun to see how many climbs you do. Second, you know which climbs you've done and which you need to go back for. Third, you can record route beta for future reference. Fourth, you can use the journal to climb better by easily monitoring your goals. For example, if you want to onsight ten 5.11s this season, it's easy to figure out how close you are to that. Finally, when you're stuck inside on a rainy day, you can flip through your climbing journal and relive the glory days. Inside the journal is a page that explains how to use the journal followed by a page that contains examples showing the journal in use. Then there are 200 pages to record your climbs in. Room for two climbs on each page means that you've got enough space for 400 climbs! At the end of the journal are ten blank note pages. For each route you can record the following: Climb name (e.g., The Nose) Climb number Date climbed Formation (cliff, boulder, etc.) that the climb is on (e.g., El Capitan) Area (e.g., Yosemite Valley) Broad area (e.g., Sierra Nevada) State/Province Country Partner(s) Rating/Grade Type (sport, trad, boulder, etc.) Style (onsight, flash, redpoint, etc.) Quality Length Gear Other notes This was created by climbers for climbers, and it makes a great gift for yourself or any climber in your life!

ASIN

B01BW4QPJM

Embedding

CLIP ViT-L/14 · 768d

Distance metric

cosine

Doc fetch

10ms·cache missGET /v2/namespaces/amazon-products/documents/B01BW4QPJM

Similar query

34msre-embed title → /query

Doc fetch goes through Layer's Aerospike pull-through cache; cache hit served the row without touching turbopuffer. The similar query re-embeds this product's title with CLIP-text and runs a vector query — queries don't go through the doc cache, so no cache header is set.