Import/Export
Import
Section titled “Import”wanderer supports bulk uploading of trails via an auto-upload folder. A file watcher automatically detects new files added to this directory and imports them into your library.
Configuration
Section titled “Configuration”Environment variables
Section titled “Environment variables”The following environment variable must be present in the wanderer-web docker container and set to a valid volume path (see below).
| Environment Variable | Description | Default |
|---|---|---|
| UPLOAD_FOLDER | Path to the auto-upload folder | /app/uploads |
Volume
Section titled “Volume”Make sure to mount the upload folder as a volume to your host system. The default docker-compose.yml already includes this volume. Ensure that the mapped value matches the one in the UPLOAD_FOLDER environment variable.
API token
Section titled “API token”The bulk upload process uses API tokens to authenticate requests and determine which user account the uploaded trails should be assigned to.
- Create an API token: Follow the steps in the Authentication section to generate a new API token.
- Prepare the folder structure: Create the folder: Inside your UPLOAD_FOLDER, create a sub-folder named exactly after your API token.
- Upload: Move your trail files (e.g., .gpx, .fit, or .kml) into that sub-folder.
Example structure:
/app/uploads/wanderer_key_<...>/my_trail.gpx
Export
Section titled “Export”To export selected trails head over to /trails and select the trails you want to export. From the ⋮ menu select “Export”. You can export the route data either in GPX or in GeoJSON format. Furthermore, you can choose whether you want to include the photos and the summit book of the trail. In any case, wanderer will create a ZIP archive with all the data that is then downloaded.
You can also export all of your trails at once. To do so, head over to /settings/export and click “Export all trails”. The other steps remain analogous to exporting a single trail.