Metadata-Version: 2.4
Name: cetk
Version: 0.0.6.dev0
Summary: CLAIRs Emission ToolKit cetk
Author: Christian Asker, Mattias Jakobsson, David Segersson, Eef van Dongen
Maintainer-email: FO Luft <foluftadmin@smhi.se>
License-Expression: Apache-2.0
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Scientific/Engineering :: Atmospheric Science
Requires-Python: >=3.9
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: django<6,>=4.2
Requires-Dist: fiona>=1.8.18
Requires-Dist: geopandas>=0.12
Requires-Dist: netCDF4>=1.5.4
Requires-Dist: numpy>=1.20.3
Requires-Dist: openpyxl>=3.0.7
Requires-Dist: pandas>=2.0
Requires-Dist: pyogrio>=0.4.2
Requires-Dist: rastafari>=0.4
Requires-Dist: rasterio>=1.3
Requires-Dist: shapely>=2.0
Dynamic: license-file

# Emission ToolKit cetk

Emission toolkit for command line to import, validate, edit and analyse emissions.
Used in QGIS Plugin Eclair. This package is maintained by [Eef van Dongen][] at SMHI.

[Eef van Dongen]: mailto:eef.vandongen@smhi.se

## Installation
```
python3 -m venv --prompt cetk .venv
. .venv/bin/activate
python -m pip install -e .
```
Check that installation was successful and receive information on how to use the toolkit:
```
cetk -h
```

Before using the toolkit, initialize the template database by:
```
cetkmanage migrate
```

If you did not change the default path, this should create
`~/.config/eclair/eclair.gpkg`

New databases can now be created by copying the template database. This is easiest done using the cetk command:
```
cetk create /home/myuser/mydatabase.gpkg
```

To use a specific database, set environment variable "CETK_DATABASE_PATH".
```
export CETK_DATABASE_PATH="/home/myuser/mydatabase.gpkg"
```

For more verbose logging, set environment variable CETK_DEBUG=1:
```
export CETK_DEBUG=1
```

## Contributing

### Environment
Install pre-commit hooks:

```
. .venv/bin/activate
pip install -r requirements-dev.txt
pre-commit install
```

### Testing

Run tests with
```
nox
```

### Update requirements

If any new development requirements are added to
[requirements-dev.in](requirements-dev.in), update
[requirements-dev.txt](requirements-dev.txt) by running

```
nox -s requirements
```
