From the [**Chelsa**](https://chelsa-climate.org) or [**Envidat**](https://www.envidat.ch) websites it is easily possible to download all data needed. Chelsa is a global climate data set with a resolution of 1 km and each layer is about 90 MB in size. Since many layers are usually required for an analysis, a large download is unavoidable. Often only a small section is needed for an analysis and not the entire earth.
For WSL employees there are two mount options available which allow to simply skip the download and access the data directly! (However, the documentation remains available only through the website.) This manual is for macOS X but the procedure for Linux will be similar.
## nfs mount
The Chelsa data is stored on the server **Uranos** and directly accessible from the _WSL intranet_ (even when connected via VPN). For Linux or Mac users a simple mount of the directory is possible. Use the `/Applications/Utilities/Terminal.app` to do this. First create an _empty_ directory for the mountpoint, e.g. in your home:
```shell
mkdir-p ~/chelsa
```
Then mount the filesystem:
```shell
mount -t nfs -o rdonly,nobrowse svm-envidat:/vol_data/ckan/default/storage/uploads/chelsa ~/chelsa
```
`nobrowse` is not required, it just prevents the icon on the desktop. (see `man mount` for details). Don't forget to unmount if you don't need the access anymore by clicking on the Symbol next to the mountpoint or by typing:
```shell
umount ~/chelsa
```
**NOTE:** It is **not** allowed to use this nfs mount on the **nodes** of Hyperion! This would slow the cluster down enormously and overload **Uranos**. Instead, prepare the data you need for cluster applications e.g. on your local computer and then copy them to the cluster storage **Themis**.
You can mount **Themis** on your local computer analogous to the instructions above and to [docs.gluster.org](https://docs.gluster.org/en/latest/Administrator-Guide/Setting-Up-Clients/#manual-nfs), e.g.:
```shell
mount -t nfs -overs=3 themis01:/storage ~/themis
```
## cloud mount
The Chelsa data is also stored in the cloud **envicloud** at switch.ch. This allows a fast connection from everywhere, i.e. you don't have to be in the _WSL intranet!_ Access is achieved using an [**S3**](https://en.wikipedia.org/wiki/Amazon_S3) mount which requires the installation of additional software.
### S3 mount for macOS X
Two software components need to be installed and configured.
1.[**macFUSE**](https://osxfuse.github.io/) enables macOS X to handle third-party file systems. Download and install by double click. There is a good [**FAQ**](https://github.com/osxfuse/osxfuse/wiki/FAQ).
2.[**Rclone**](https://rclone.org/) is needed to mount **envicloud** as file system on a mountpoint. The zip archive contains the command line tool `rclone`. Put it in a directory which is included in the search path for your shell, e.g. `~/bin`.
**NOTE:** On newer OS X systems (starting with 10.14, Mojave) the **gatekeeper** may cause problems. Then it is advisable to do the [**macOS installation from precompiled binary, using curl**](https://rclone.org/install/#macos-installation-from-precompiled-binary-using-curl).
Now just type `rclone config` and accept all defaults by typing only `return` except for the following prompts (see [**rclone configuration documentation**](https://rclone.org/s3/#amazon-s3)):
```shell
name> envidat
Storage> s3
provider> Other
env_auth> false
endpoint> os.zhdk.cloud.switch.ch
e/n/d/r/c/s/q> q
```
Afterwards the newly created configuration file `~/.config/rclone/rclone.conf` should look like this:
```shell
[envidat]
type= s3
provider = Other
env_auth =false
endpoint = os.zhdk.cloud.switch.ch
```
Now create an _empty_ directory for the mountpoint, e.g. in your home
Here an icon appears also on the desktop. The option `--daemon` is not necessary but puts the mount into the background (see `rclone --help`). Note that the mount command on macOS X is `cmount`. Unmounting works exactly the same way as with the nfs mount above. The S3 mount seems to be faster than the nfs mount.
### S3 mount for Windows
The [**S3**](https://en.wikipedia.org/wiki/Amazon_S3) mount for windows is very similar to the macOS X mount.
Instead of *macFUSE* the software [**WinFsp**](https://github.com/billziss-gh/winfsp/) is used. It's a set of software components for windows computers that allows the creation of user mode file systems. [**Rclone**](https://rclone.org/) is also needed.
After extracting the zip archive open `rclone.exe` in the command prompt.
Now just type `rclone config` and accept all defaults by typing only `return` except for the following prompts (see [**rclone configuration documentation**](https://rclone.org/s3/#amazon-s3)):
```shell
n/s/q> n
name> envidat
Storage> s3
provider> Other
env_auth> false
endpoint> os.zhdk.cloud.switch.ch
```
Your final config should look like this:
```shell
[envidat]
type= s3
provider = Other
env_auth =false
endpoint = os.zhdk.cloud.switch.ch
```
To mount the filesystem type:
`rclone mount envidat:envicloud/chelsa Y:`
Instead of Y: you can use any unused drive letter.
**Note** that `--daemon` does **not** work on windows, therefore the mount is only active when the console window is open. When remounting you don't have to do the configuration part again, `rclone mount envidat:envicloud/chelsa Y:` suffices.
