GBD Mapping
Mapping of GBD entities to their metadata.
There are two packages offered in this distribution. The first, the gbd_mapping_generator is a set of scripts that define templates and data gathering code used to produce the second, the gbd_mapping. The gbd_mapping_generator package will not function without access to the IHME cluster and some of our internally used data access libraries.
The gbd_mapping is a programmatically accessible (and TAB-complete-able) set of mappings for GBD entities including:
Causes
Risks
Covariates
Etiologies
Sequelae
There are additional mappings for objects mostly built around custom data. The primary instance of this is the coverage_gap mapping. Coverage Gaps are non-GBD entities representing the lack of coverage of interventions to particular GBD causes and risks.
You can install gbd_mapping from PyPI with pip:
> pip install gbd_mapping
or build it from source with
> git clone https://github.com/ihmeuw/gbd_mapping.git
> cd gbd_mapping
> python setup.py install
Metadata
Release files for gbd-mapping 1.0.2
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 |
|---|---|---|---|---|
| gbd_mapping-1.0.2.tar.gz | 163.9 kB | Without provenance | Details for gbd_mapping-1.0.2.tar.gz |
Release files / gbd_mapping-1.0.2.tar.gz
| Download URL | gbd_mapping-1.0.2.tar.gz |
|---|---|
| Size | 163.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8289bd50ce7aa078785b876d46bfed3e133e628dc09d98f3defca10ec699821e
|
|
BLAKE2b-256 checksum How to use checksums |
9309bf6ff489e684f874bf7e0ea204d7c751d9bdf411fc859725aee65e432aa5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.6.3
|
Security for gbd-mapping 1.0.2
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.