BROmodels
The GEOTOP and REGIS data is downloaded from the DINOloket OPeNDAP server.
More information about the GEOTOP or REGIS:
- https://www.dinoloket.nl/en/search-and-request-geotop
- https://www.dinoloket.nl/en/regis-ii-hydrogeological-model
- http://dinodata.nl/opendap/
Please note that an active internet connections is mandatory!
Installation
To install this package run:
pip install bromodels
Contribution
Environment
We recommend developing in Python3.9 with a clean virtual environment (using virtualenv or conda), installing the
requirements from the requirements.txt file:
Example using virtualenv and pip to install the dependencies in a new environment .env on Linux:
python -m venv .env
source activate .env/bin/activate
python -m pip install --upgrade pip setuptools
pip install -r requirements.txt
pip install -e .
Documentation
Build the docs:
python -m pip install --upgrade pip setuptools
pip install -r requirements.txt
pip install .
sphinx-build -b html docs public
Format
We format our code with black and isort.
black --config "pyproject.toml" src tests examples docs
isort --settings-path "pyproject.toml" src tests examples docs
Lint
To maintain code quality we use the GitHub super-linter.
To run the linters locally, run the run_super_linters.sh bash script from the root directory.
UnitTest
Test the software with the use of coverage:
python -m pip install --upgrade pip setuptools
pip install -r requirements.txt
pip install .
coverage run -m pytest
Requirements
Requirements are autogenerated by pip-compile with python 3.9
pip-compile --extra=test --extra=docs --extra=lint --extra=3d --output-file=requirements.txt pyproject.toml
To update the requirements within the defined ranges, run:
pip-compile --upgrade --extra=test --extra=docs --extra=lint --extra=3d --output-file=requirements.txt pyproject.toml
Metadata
Release files for bromodels 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bromodels-0.0.1.tar.gz | 26.3 kB | Without provenance | Details for bromodels-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bromodels-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for bromodels-0.0.1-py3-none-any.whl |
Total release size: 43.8 kB
Release files / bromodels-0.0.1.tar.gz
| Download URL | bromodels-0.0.1.tar.gz |
|---|---|
| Size | 26.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10f4f56e6053401a45ea284198c57405757f148ab40874b332dd932626644ff0
|
|
BLAKE2b-256 checksum How to use checksums |
c62a0629759aac9a968c28bb6e30c6cbcdabccadd2bb4076ce601d1de41adb92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Release files / bromodels-0.0.1-py3-none-any.whl
| Download URL | bromodels-0.0.1-py3-none-any.whl |
|---|---|
| Size | 17.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2744030f0d28b903e0ae04d20d5b4f75761d743c4cf8677829ae3b65ba595fc4
|
|
BLAKE2b-256 checksum How to use checksums |
8a8621187a869828de964d3ca59a0885f5d5c58b9db789684990c99b93e0452b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Security for bromodels 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.