PyZDC
PyZDC is a Python tool designed to simplify the analysis of epidemiological data related to the Aedes aegypti, focusing on diseases such as Dengue, Zika, and Chikungunya. It is fast, extensible, and easy to use.
Features
- Automated extraction of epidemiological data.
- Data transformation and validation using DuckDB and Pandera.
- Specific functions to access processed tables, including notifications, personal data, clinical signs, and more.
- Fully compatible with Python 3.12+.
Installation
Install the package via pip:
pip install pyzdc
Install the package using uv or poetry:
# uv
uv add pyzdc
# poetry
poetry add pyzdc
Quick Example
Here’s a quick example to get you started:
import pandas as pd
import pyzdc as zdc
# Fetch notification data for Chikungunya cases in 2022 and 2023
df = zdc.get_notifications(years=[2022, 2023], disease="CHIK")
# Display the first few rows
print(df.head())
# Save the DataFrame to a CSV file
df.to_csv("notifications.csv", index=False)
This will output something like:
notification_id notification_type disease_condition_id notification_date notification_week notification_year notification_state_id notification_city_id notification_region_id notification_health_unit_id
0 1 2 A92.0 20220108 202201 2022 12 120033 1941 9542566
1 2 2 A92.0 20220216 202207 2022 12 120033 1941 9542566
2 3 2 A92.0 20220126 202204 2022 12 120033 1941 9542566
3 4 2 A92.0 20220108 202201 2022 12 120033 1941 9542566
4 5 2 A92.0 20220126 202204 2022 12 120033 1941 2000083
Help
For more information, see the documentation.
Contributing
Contributions are welcome! Follow these steps to contribute:
1. Fork the Repository
Create a fork of the repository in your GitHub account.
2. Clone the Repository
Clone your fork locally:
git clone https://github.com/your-username/dq-sus.git
cd dq-sus
3. Create a Branch
Create a branch for your changes:
git checkout -b feature-name
4. Install Dependencies
Install the required dependencies using pip or uv:
pip install -r requirements.txt
5. Make Changes and Test
Implement your changes and ensure all tests pass:
pytest
6. Commit and Push
Commit your changes and push to your fork:
git add .
git commit -m "Add feature description"
git push origin feature-name
7. Open a Pull Request
Submit a pull request to the dev branch of the original repository.
Security
To report security vulnerabilities, please review our security policy.
License
This project is licensed under the MIT License.
Metadata
Release files for pyzdc 0.6.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 |
|---|---|---|---|---|
| pyzdc-0.6.1.tar.gz | 81.9 kB | Without provenance | Details for pyzdc-0.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyzdc-0.6.1-py3-none-any.whl | Python 3 | none | any | Details for pyzdc-0.6.1-py3-none-any.whl |
Total release size: 161.8 kB
Release files / pyzdc-0.6.1.tar.gz
| Download URL | pyzdc-0.6.1.tar.gz |
|---|---|
| Size | 81.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
434efab9a704192c66ebb4d78cf621062261ff9d6e2b8acbcda687cf24f2b3fe
|
|
BLAKE2b-256 checksum How to use checksums |
52ec5498d4e6f11e3ebddb69a0b14591b603dd1918749a22d474876275d9ab92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.7
|
Release files / pyzdc-0.6.1-py3-none-any.whl
| Download URL | pyzdc-0.6.1-py3-none-any.whl |
|---|---|
| Size | 79.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
931382e414cefd1784acc147ec194182d1f3ad2f3556522c3435cdaab9cd5c39
|
|
BLAKE2b-256 checksum How to use checksums |
465cf1f9f9acd4bcd2bcba219f1b848ebefad794c71a7a98035a33030d4c6980
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.7
|
Security for pyzdc 0.6.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.