Share Your Climbing Photos
I’ve just finished the photo sharing feature. Many thanks to @nthh for adding user registration and login. The work lays the foundation for my photo sharing feature and the upcoming wiki editing feature. And also big props to @CocoisBuggy for giving the area page a much deserved facelift so that we have a home to showcase those action shots.
Without further ado, here’s a screenshot of my profile:
Visit my profile on OpenTacos.
Tag a Climb 🔖 🔖
Similar to tagging on social media, once you upload a photo, you can click anywhere on the photo to tag a climb. The tag creates a link between your photo and the climb. When people visit an area page or a climb page, they will see your photos.
Pro Tip: To search for the correct climb, I’d use the following syntax: <climb name> <climb type> <climbing area>.
For example, in order to search for Wherever I May Roam at Smith Rock, Oregon, I’d type: “wherever I may sport smith”. The search engine will suggest a list of closely matched climbs for you to pick.
Oops, I tagged a wrong climb
Simply click on the X icon to remove the tag.
Did you know you can add a similar climb search to your apps? Learn more about our free search API.
Area Explorer
We’re also working on redesigning the Area explorer page to make it easier and more intuitive to use. While this topic deserves a separate post, I wanted to briefly mention it here for you to see how we show aggregate tagged photos.
Visit Red Rock Canyon on OpenTacos
License
You may be wondering whether photos are also available for re-use under CC0, the same license we use for climbing data. The short answer is No. By default, all uploaded photos are copyrighted by the photographers (please only upload your own photos!). You must have permission from the photographer before using their photos.
We’re currently evaluating a licensing option and are looking for ways to encourage users to contribute photos of boulders and walls under CC0 for the purpose of making topos. Please take a moment and share your feedback on RFC 307.