A Database

This is a short section because a database is simple: it aggregates data consistently for reference. It is optimized for scale and consistent structure, and as it grows, its utility as a reference grows. A well-built database answers the question: what are the facts?

A database's great strengh is that it treats everything the same: You go to a database when you want to filter an area for the 5.11s over 2 stars. Or when you want all climbs in an area put up by Fred Beckey in the 80s. Or when you want a complete list of climbs in an area sorted by grade.

A database is perfectly suited to answer these questions. Nothing beats it.

When you open a database, you're getting facts.

A Guidebook

A guidebook orients and introduces the reader to a place. It requires an author with local knowledge building a picture of an area that they care about. A prepared guidebook author knows what is where, but also how it relates to the environment (sun? rain?), how it fits into the local history, what the place feels like, and what a visitor needs to understand before arriving. They also know the local places to eat, camp, and take rest days.

A guidebook answers the question how should visitors experience this place? with design, context, anecdotes, etc. see The Climbing Guidebook Handbook

Guidebooks are laid out to match what the area has to offer, and they take opportunities while enumerating routes to tie it into the broader context of the area.

This is not something that the database alone can do. It requires a caring author writing for their audience about a place that they love. Their job is to convey feelings and broader understanding while dosing out the data of an area to the reader.

When you open a guidebook, you're having an experience.

A database and a guidebook are not competing for the same job.

The gap between a database and a guidebook is not a failure of either one. They are just two tools to do two different things.

A database cannot become a guidebook by accumulating more data. Comprehensive coverage of an area with no cultural context, no editorial voice, and no curatorial judgment produces a larger database.

The guidebook requires an expert willing to curate for outsiders. that role can't be filled by all the data in a database

A guidebook cannot be built without data to build on. Routes need grades, approaches need distances, areas need maps need coordinates. The database and the guidebook are complementary, not competing. The best guidebooks are built on database and take it beyond what the data itself could offer.

For more on how databases operate at scale and the structural consequences of that model, see [SSORD]. For more on what makes a guidebook valuable to a climbing community, see [The Value of Climbing Guidebooks].