Metadata-Version: 2.1
Name: met-office-datasets
Version: 0.0.15
Summary: DESCRIPTION
Home-page: https://github.com/informatics-lab/met_office_datasets
Author: Theo McCaie
Author-email: theo.mccaie@informaticslab.co.uk
License: UNKNOWN
Platform: UNKNOWN
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Classifier: Natural Language :: English
Description-Content-Type: text/markdown
Requires-Dist: numpy (>=1.11)
Requires-Dist: dask (>=1.0)
Requires-Dist: xarray
Requires-Dist: zarr (>=2)
Requires-Dist: adlfs
Requires-Dist: h5netcdf (>=0.8)
Requires-Dist: intake
Requires-Dist: intake-xarray
Requires-Dist: toolz

# Met Office datasets intake driver and catalogue


## Installing

### PyPI

```shell
pip install met_office_datasets
```

### Anaconda

```shell
conda install -c conda-forge -c informaticslab met_office_datasets
```


<!-- So tips building conda stuff. I said it took ages to build the env and didn't wat to keep doing that for testing the build. Answers:
```

Wolf Vollprecht @wolfv 15:08
you can point the shell to your workdir and run the conda_build.sh from that folder
and you can source build_env.sh to get into the buidl env, then conda deactivate to get into the host env and install / modify packages in there
the workdir is shown in the error message after conda build failed
otherwise you might want to try conda mambabuild ... which is included in boa to see if that could help speed up your build env provisioning


Otherwise, you might want to try to use conda debug instead of conda build in the first place. This only creates the environment setup but doesn't start the build.
``` -->

