// HACKER NEWS — CYBERSECURITY
Climbing Guide as a Shared Infrastructure
A climbing guide can easily become a private database with a nice map in front of it.
When somebody adds or fixes a route, the project wants that information to remain useful even if OpenClimbing disappears. Climbing data lives in OpenStreetMap. Topo photos can live in Wikimedia Commons. The GPL-3.0 application becomes a specialized interface over shared resources.3 4
Version 2.0, released on August 11, pushes that idea much further.2
OpenClimbing no longer just displays points on a map.
It can show areas, crags and routes, convert grades, filter sectors and draw climbing lines directly over photographs. Version 2.0 improves the route in the other direction too: users can edit information, upload a photo to Wikimedia Commons and draw the route over that image from the application.1
The launch post reports almost 40,000 routes, more than 6,000 routes drawn on photos, over 1,000 climbing areas and 31 countries. Those are the project's own August 11 numbers, not an external audit.1
In a conventional app, adding a route primarily improves the product that stores the contribution. Here, route data is written into OpenStreetMap using community schemas, while imagery can be published on Commons.3 4
The application can disappear. The contribution can still be reused elsewhere.
OpenStreetMap can describe an absurd number of things. That does not make a generic map editor the ideal place to document a 6b with three bolts, a shared anchor and a crack that becomes miserable after rain.
OpenClimbing therefore builds a domain-specific interface.