π Community / Help
Welcome to OpenCanyon.org. We are a motley bunch of different canyoneers who (mainly) want to provide up-to-date canyoning information in the German-speaking area. Of course, we can't do this alone, so we ask for your help.
Who is behind OpenCanyon.org
We are many, come from different corners, countries and communities, but at least one passion unites us ... canyoning. The Austrian Canyoning Association (ACA for short, see also https://www.canyoning.or.at) has thankfully agreed to take over the patronage of OpenCanyon. People who have been particularly involved can be found on the "OpenCanyon Teamππ" page. A list of all users can be found here.
Log in and report inspections
You can log in at the top right and then enter canyon ascents. This is important so that subsequent ascenders know whether everything is OK or whether there are potential problems. Ideally, when you are at the car after the tour, click on Proximity at the top, then the canyon you have climbed should be visible and then on Ascent, New ascent.
Enter into dialog
We talk about almost every idea/innovation together on Slack. It is important to look at different perspectives in order to get something good in the end. You can find an insight into current topics at the bottom of this page (the latest messages in #general), the list of currently open bugs https://www.opencanyon.org/community/bugs ππ and the list of currently open feature requests https://www.opencanyon.org/community/features ππ. You can easily join by using the link https://communityinviter.com/apps/canyoning/invite
Editing canyons
Currently, editing canyons is reserved for authors only. If you are known in the canyoning community and would like to actively participate here, please contact us or request your rights at https://www.opencanyon.org/user/request. It is also important to know that many of the users of ACA or Cwiki are already registered in the system, simply log in with the same e-mail address and off you go. You can edit canyons when you get an edit button in the canyon detail view.
Customize software
We currently use the following frameworks: Laravel, Tailwindcss, Livewire, Filament, Alpine and Openlayer. If you have already worked with one or the other and are interested in contributing, please contact us on Slack. If you want to participate but have little/no experience, you should start with some of the following topics. For video access, please ask in Slack.
- Laravel Bootcamp https://bootcamp.laravel.com/ or https://laravel.com/docs/10.x
- Screencast Laravel from Scatch is not quite up to date but teaches the basics. An updated version is available at http://30daystolearnlaravel.com. There are also many other interesting screencasts on Laracasts
- Livewire Screencasts see e.g. for Livewire V2 or Livewire V3
- For Tailwindcss you typically use the official documentation in combination with examples and the Browser-Devtools->Styles->Classes as well as one or the other Youtube video.
- In addition to the official documentation, Filament offers a demo app where you can learn a thing or two, and various courses also exist
- Openlayer is explained particularly well at https://www.webgis.dev in conjunction with Laravel/Livewire/Alpine in addition to the official documentation, which also provides many examples
Using data
Over the last few months, we have had many requests to use the Opencanyon data for other projects, apps etc. Basically, it should be said that the data (similar to other canyoning platforms) is under a CC license which does not support commercial purposes. (For details, see https://www.opencanyon.org/legal or details on CC-NC here Study on "Defining None Commercial" on page 54). If this can be complied with and we as the OpenCanyon team understand/can understand what the data is used for, it is possible for us to provide the majority of the data in daily updated form as a download and, if necessary, also offer APIs for smaller amounts of data (e.g. to create reports, web links, etc.).
Local canyoning community
The best ideas often don't come from a PC but from a beer after a canyon. It is therefore important to network with local canyoning communities, to exchange ideas, to educate, train and so on. Here is a (certainly not complete) list of some starting points...
Local clubs:
- https://ficanyon.org/fic-members
- https://www.bachab.ch
- https://www.aic-canyoning.it
- https://www.schluchten.de
- https://www.canyoning.or.at
Education:
Date | Name | Message |
---|---|---|
13.06.2025 08:48:05
|
Max
|
*Update 0.18.3 is live*
- Adding translation forcast call and display as admin backend page
- Improve translation cache generation in job GenerateTranslationCache
- We need to fix locale of weblinks, needed for translations (TODO: "php artisan db:seed --class=CanyonSeederInitLocale")
- We need to import some translations (TODO: "php artisan db:seed --class=TranslationCacheSeeder")
|
07.06.2025 15:14:09
|
Max
|
*Update 0.18.2 is live*
- Improve canyon search on favorites
- Improve translation matching with md5 hash (TODO: php artisan db:seed --class=TranslationCacheGenerateMd5HashSeeder)
- Improve picture rotation (add errorhandling and ftp support)
|
02.06.2025 15:25:36
|
Max
|
*Update 0.18.1 is available on playground/production*
- Fix merge translation command line breaks
- Add rotate canyon picture function for backend (admins only)
- Add change canyon description language for backend (admins only)
- Add new model UserStatistic and add user statistic data for last 3 and 6 months
- Add logged in user context to contact form
- Remove mergeCanyons function from canyon model
- Refactor warnings fiels active to enabled to avoid confusion
- Add app page for prefill (key: community-app)
- Add tutorial page for prefill (key: community-tutorials)
- Show report pictures also on user profile page
|
30.05.2025 18:10:30
|
Max
|
*Update 0.17.9 is live*
- Enforce unix style file endings on git checkout and vs-code (pint on windows is working locally now)
- Fix warning api field active by changing the mapping to the calculated property is_active
- Improve webpage contact form with different categories, name field, e.g.
- Update vite from 3 to 6 (and therefore change package.json type to module)
|
26.05.2025 13:08:27
|
Max
|
*Update 0.17.8 is live*
- Fix crash on AITextarea with empty values
- Fix type hinting on updateTranslation function
|